Getz EMP · eMSP platform
Launch your own charging brand without building the stack
- You launch
- A charging service under your name: driver app, back office, prices, plans and fleet accounts for your business customers.
- Getz operates
- The platform: app, back office, pricing engine, wallet ledger, payment adapters and the roaming connection through Getz Hub.
- You bring
- Your brand, store accounts, merchant accounts (cards, SnapScan, Zapper), operator agreements and first-line driver support.
One session, end to end
Follow one charging session from the driver’s phone to your books
The same session id, charge id and tax invoice number run through every step, so your support and finance teams can trace any charge in either direction.
Demo data A fictional partner, driver and site, from one session in the demo platform.
- Partner
- Kopano Charge (demo)
- Driver
- Lerato Mokoena
- Site
- Menlyn Park parking P2 (demo)
- Session
- 0400fd56-7e93-49e3-be01-aa81be2ebf03
- Operator session
- HVC-S-MWQZWAQY
- Charge
- 08368861-90f5-4b79-a09f-7d0e8387f652
- Tax invoice
- INV-000002: R 213.69 (operator R 162.52, margin R 23.30, VAT 15% R 27.87)
- Credit note
- CN-000002, R 15.00 goodwill, back to the wallet
- Paid
- R 198.69
- Provider payout
- SETTLE-PAYSTACK-MWQZWAQY (the wallet top-up)
Driver app
The driver starts, charges and pays
The partner’s app shows the price before the start and reserves the estimate in rand. When the operator’s charge record arrives, the real cost is taken from the wallet and the rest released.
Ties it together: Session id · Total paid
Who looks at it: Your driver
Demo data · this session
Back office
Your team sees the same charge, priced line by line
The operator’s cost, your markup and fee, the adjustment, VAT and the driver total, with the operator’s session id in the title.
Ties it together: Charge id · Operator’s session id · Driver total
Who looks at it: Your operations and support team
Demo data · this session
Receipt and tax invoice
The driver gets a tax invoice in your company’s name
Your legal name and VAT number, VAT at 15% and how it was paid. With a VAT number on file, the final receipt is the tax invoice (INV-…); a later correction is a credit note (CN-…) against it.
Ties it together: Tax invoice number · Total paid
Who looks at it: Your driver, and your finance team
Demo data · this session
Reconciliation
Finance traces it to the ledger and the money that settled
One trace links the platform and operator session ids, the operator’s charge record, the tax invoice, the credit note, the wallet ledger entries and the refund, and shows the quote at the start matched to the rated price. The provider’s payout is matched to the top-up by reference.
Ties it together: Session ids · Invoice and credit note · Ledger entries · Payout reference
Who looks at it: Your finance team
Demo data · this session
The exception
When the card provider refuses a refund
A refund the provider refuses is recorded as failed, with the provider’s reason and every attempt. It is never counted as refunded, and never lost.
Demo data · another refund of the same driver, refused by the card provider
| Who | What they do |
|---|---|
| The card provider | Refuses the refund and gives its reason. |
| Getz EMP | Records it as failed with the reason and attempts. A refund for a charge correction is retried after 15 minutes, 1 hour and 4 hours, then daily, and then escalated. |
| Your finance team | Retries it, or resolves it as paid outside (with a reference) or written off. |
| Your support team | Answers the driver, with the refund and its reason in front of them. |
Platform facts
- OCPI 2.3.0 · 2.2.1
- Roaming through the neutral Getz Hub
- Rand · VAT by date
- Prices, fees and VAT per currency and country
- Cards · QR
- Cards with Apple Pay, SnapScan and Zapper
- Many brands
- On one platform, each organisation’s data kept apart
Who builds on Getz EMP
One platform, five reasons to own the driver relationship
Each kind of business comes to charging with a different motive. Start with yours.
Forecourts and retail
Keep EV drivers in your brand
Charging inside your loyalty, offers that bring drivers into the shop, and your sites alongside participating networks.
Car brands and dealers
Make charging part of ownership
An owner app under your badge, charging credit at handover and public charging on participating networks.
Banks, insurers and telcos
Put charging on your rails
Payment volume through your cards, wallets and QR payments, and an EV product your customers use every week.
Existing eMSPs
Move to a platform built for the region
Keep your brand and drivers; gain local currencies, VAT, mobile money and one roaming connection.
Mobility and fleet platforms
Add charging to your service
Rental, ride-hail, leasing and fleet platforms that sell charging to their customers under their own name. Running charging for your own vehicles is the fleet route.
Why not build it
An eMSP is a payments, roaming and operations business with an app on top
Before the first driver charges, all of this has to work together, in every currency and country you serve. Getz EMP is that stack, already built.
Network access
An OCPI connection, agreements with operators and real-time authorisation of every start.
Pricing and tax
The operator’s cost, your margin, fees and VAT by country and date: rand at 15% VAT at home, other currencies for drivers from across the border.
Money
A wallet ledger, holds before charging, collection, refunds, payouts and local payment methods.
Operations
Driver accounts, business customers, support, privacy requests and a back office with roles.
Architecture
Where your brand sits, and what runs underneath
Your app and back-office team on your own organisation in the EMP platform; charging networks through Getz Hub; payments through your merchant accounts; your systems through signed webhooks. Select a part to read what it does.
White-label EMP architecture
Your brand’s app and back office run on the shared EMP platform. Charging networks come through Getz Hub; payments through your merchant accounts; your systems through signed webhooks.
The Getz EMP platform (Getz runs it)
Getz runs and updates the platform. On it, your own eMSP organisation: drivers, pricing, wallets and data kept separate from every other brand on the platform. One or more trading brands per organisation.
Use Tab to reach the diagram, then the arrow keys to move between parts.
Pricing engine
Your margin on the operator’s cost, never below it by accident
The operator’s tariff passes through unchanged. Your markup, fees, plan benefits and promotions sit on top, with a floor so a discount you have not funded cannot sell a session below cost.
- Markup by site, tariff or currency, with a price floor
- A simulator that runs the same engine as the receipt
- VAT by the location’s country and the session date
Every charge, built up: the operator’s cost, your margin on top, VAT, and what the driver paid.
- What you see: one DC fast charge, from the operator’s cost to the driver’s receipt
- Why it matters: your margin per session, with VAT, on the record
Network access through Getz Hub
One roaming connection instead of one per operator
Your eMSP identity connects once to Getz Hub, the neutral roaming hub, over OCPI. Charging operators that connect to Hub and agree terms with you appear in your app. Hub applies the same rules to every app, Getz’s own included.
We do not publish a coverage figure: participating networks join one by one, and your drivers see the ones you have agreements with.
- Roaming through Getz Hub over OCPI 2.3.0 and 2.2.1
- Every start authorised in real time by your EMP
Find a charger: live availability and price before you drive.
- What you see: nearby chargers with live status and price
- Why it matters: drivers stop guessing which charger works
Wallet and local payments
Reserve the estimated cost before charging
Starting a session reserves the estimated cost, and the session stops when it reaches the reserved amount. The real cost is taken when the charge record arrives and the rest is released. If a collection fails it is retried, and by default a driver who owes money cannot start again until it is paid. Drivers pay by card, Apple Pay or a SnapScan or Zapper QR code, and the money settles into your own merchant accounts.
| Capability | What it does | Supported | Settles into |
|---|---|---|---|
| Wallet holds, ledger and collection | Reserve, settle, release, refund | Yes | Your wallet ledger |
| Cards through Paystack or DPO Pay | Hosted checkout, saved cards, Apple Pay, refunds | Yes | Your Paystack or DPO Pay account |
| SnapScan and Zapper | Scan a QR code in the app | Yes | Your SnapScan and Zapper merchant accounts |
Revenue beyond the session
Business customers, recurring plans and offers you control
Fleets and corporate accounts
Sell charging to your business customers: company-pays rules by site, hours and kWh, credit limits and monthly statements. Their drivers use your app.
Fleets with company-pays rules, drivers, vehicles and corporate accounts.
- What you see: drivers, vehicles and who pays per fleet
- Why it matters: one place to run a fleet’s charging
Subscriptions
Monthly plans charged to the wallet or a card, with benefits applied by the pricing engine.
Promotions and codes
Scoped by tariff, site, vehicle, fleet or currency, with limits and expiry.
Referrals
Wallet credit for both drivers after the friend’s first billed session.
Run it day to day
Support, brands and your own systems
Support where drivers already talk
Tickets with photos, and WhatsApp, call and e-mail buttons configured per brand. Your team looks up any session, token or payment.
Multi-brand on one platform
A consumer brand and a fleet brand, or one brand per country. Runtime brand settings change without a store release.
Partner webhooks
Signed events per event type, optionally per fleet, into your CRM, loyalty, telematics or finance systems.
The back office
The screens your team would work in
Captured from the running EMP back office with fictional demo data; select a screen to enlarge it.
The partnership
You own the brand and the drivers. Getz runs the platform.
A set-up fee plus a monthly platform fee, or a revenue share, agreed per partner after discovery. We do not publish a price list.
| Capability | Owned or run by | How |
|---|---|---|
| Brand, app name, colours and store listings | You | Configured per brand in your back office |
| App Store and Google Play developer accounts | You | Store submission under your accounts |
| Merchant agreements and live payment keys | You | Keyed into your back office |
| Drivers, business customers and their accounts | You | Kept in your own organisation on the platform |
| Prices, margins, plans and promotions | You | Set in your back office |
| Roaming agreements with charging operators | You | Agreed on Getz Hub |
| Your data, if you leave | You | Handed over by Getz in a documented JSON and CSV format |
| Terms, privacy and consent text | You | Reviewed by your counsel |
| Driver app, back office, pricing engine and wallet ledger | Getz | One codebase for every brand |
| Payment adapters and the connection to Getz Hub | Getz | Live on your accounts and agreements |
| Platform operation and updates | Getz | Shipped to every brand at once |
| Moving drivers from your current platform | Getz, with your team | An onboarding service, planned and signed off in writing |
| Chargers, and who may charge at each site | The charge point operator | Set in the operator’s own systems; the platform respects it |
For procurement
The answers your procurement team will ask for
Before a first call: the contract, the quote, the accounts you need, the integrations and who owns what after launch.
- Who contracts with whom?
- You contract with Vebbah (Pty) Ltd, trading as Getz Charging. Getz operates the platform and processes your drivers’ data on your behalf; you are the controller of that data, and the data processing terms are part of your contract. You keep your own agreements with your payment providers, the app stores and the charging operators you roam with.
- What goes into a quote?
- Your markets, the number of brands, expected drivers and business customers, the payment methods you need, the networks you want to reach and any integration beyond the standard ones. Prices are on request: a set-up fee with a monthly platform fee, or a revenue share, agreed after discovery.
- Which agreements and accounts do we need?
- Merchant accounts in your name with the payment providers you choose (cards through Paystack or DPO Pay, SnapScan, Zapper), App Store and Google Play developer accounts, and a roaming agreement with each charging operator you want in your app, agreed on Getz Hub.
- Which integrations are standard, and which are scoped?
- Standard: roaming through Getz Hub over OCPI, the supported payment adapters in your market, signed webhooks for charges, tokens, wallets and coupon redemptions, and the finance CSV export. Scoped in discovery: anything mapped onto your own systems, such as a loyalty programme, a point-of-sale or till system, a connected-car app or a new payment rail.
- Who owns support, settlement, escalation and exit?
- Your support team is the first line for your drivers, with each driver’s charging timeline and the ids to quote to the operator; Getz is the second line, and response times are agreed in your contract. Money settles into your own merchant accounts. You handle disputes and chargebacks in your provider’s dashboard; the platform flags a chargeback in reconciliation and never acts on it automatically. The charge point operator restores a faulty charger and decides who may charge at its sites. Getz runs the platform and handles platform incidents. If you leave, Getz hands over your organisation’s data in a documented JSON and CSV format.
- Whose data is kept where, and for how long?
- Two different things. What you send through this website’s forms is kept in our enquiry system for up to 24 months after the last contact. Your drivers’ and customers’ data on the platform is kept in your own organisation, apart from every other brand’s, on a standard schedule: financial records (charges, invoices, credit notes, payments, refunds, statements) and the sessions behind them for 7 years, then de-identified with the amounts kept; audit records for 7 years; the real-time authorisation log for 13 months; support tickets for 3 years after closing; notifications for 12 months; exports for 30 days. A closed driver account is de-identified 2 years after closing, and a deletion request de-identifies it at once.
- What do drivers’ tax invoices look like?
- The platform issues each driver a tax invoice in your name for every paid charge, with VAT shown, and credit or debit notes for any later change. A company-paid charge’s invoice is addressed to the company, with the driver shown as the user.
Questions before an enquiry? E-mail support@getzcharging.com.The commercial model in full
Implementation
From discovery to launch
Timelines are agreed after discovery: most of the time goes on merchant agreements, store accounts, operator agreements and testing with your team.
Step 1: Discovery
Markets, driver and business customers, the networks you need, payment methods and what success looks like.
Step 2: Commercial configuration
Your organisation and eMSP identity, margins, fees, plans and team roles.
Step 3: Branding
App name, colours, icons, support contacts and a build profile for each brand.
Step 4: Integration
Connect to Getz Hub, key in your merchant accounts, subscribe your own systems to events.
Step 5: Testing
Your team and Getz check your brand on your phones, chargers and payment providers before you submit it to the stores.
Step 6: Launch
Store submission under your developer accounts, then open to your drivers and business customers.
Questions from prospective partners
How is a new brand launched?
On the same platform Getz runs itself. Getz provides the identity settings, build profiles and runtime branding; you own the App Store and Google Play developer accounts, the listings and store review. Your team and Getz check the brand on your phones, chargers and payment providers before you submit it.
How is the platform priced?
Per partner: a set-up fee with a monthly platform fee, or a revenue share. Terms are agreed after discovery; we do not publish prices. See the commercial model.
Would our app compete with Getz’s own app?
Getz runs its own driver app, DriEv, on the same platform you would use. Every brand gets the same platform and terms agreed up front, and Getz Hub applies the same rules to every connected app.
Which charging networks will our drivers see?
Operators connected to Getz Hub that agree terms with you, plus your own chargers if you run them. We do not publish a coverage figure or name networks that are not connected.
Whose merchant accounts take the money?
Yours. You sign the merchant agreements with the providers you choose and key them into your back office. Getz does not hold your drivers’ money in its own accounts.
Discuss your eMSP platform requirements
Tell us what you want to launch, for whom and in which markets. The platform team replies by e-mail to arrange a conversation and a walkthrough on demo data.