Existing eMSPs and charging apps
Keep your brand and drivers. Change the platform underneath.
Move to a platform built for the region’s currencies, tax rules and payment habits, with one roaming connection to participating networks through Getz Hub. Getz plans and runs the move with your team.
Where platforms built elsewhere struggle
What the region asks of an eMSP platform
| Capability | What the region needs | On Getz EMP |
|---|---|---|
| Currencies | US dollar prices with Zimbabwean VAT | Prices and fees kept per currency |
| Tax | VAT by country, changing over time | Rate by location and session date |
| Payments | EcoCash, OneMoney and cards | Adapters built; live on your accounts |
| Bad debt | Card-free drivers without unpaid sessions | Wallet holds before charging |
| Roaming | Operators on OCPI 2.2.1 and 2.3.0 | One connection through Getz Hub |
| Grid | Load-shedding awareness for drivers | ZESA stages in the app |
How a move works
A move Getz runs with your team
Moving your drivers is an onboarding service, not a tool you run yourself. Getz plans and carries out the move with your team. No two moves start from the same data, so we do not promise a date before we have seen yours.
Step 1: Inventory
Drivers, tokens, tariffs, operator connections, payment providers and open balances on your current platform.
Step 2: Configure in parallel
Your organisation, eMSP identity, pricing and brand set up alongside your live service.
Step 3: Connect
Your eMSP identity on Getz Hub as your own OCPI party; your merchant accounts keyed in.
Step 4: First drivers
A first group of your drivers moves and charges on your chargers and payment providers before anyone else moves.
Step 5: Cut over
Getz moves your drivers in the order agreed in discovery, with support ready under your brand.
Rehearsed before the real move
Validation, exceptions, reconciliation and a way back, all run by Getz
Getz runs each of these with your data owner and finance team. Nothing is committed until the numbers balance and your team signs them off.
Step 1: Validation
Getz checks your export record by record in a dry run that writes nothing. A file with anything outside the agreed format is refused as a whole, so nothing is skipped silently.
Step 2: Exceptions
A report lists every rejected, adjusted and skipped record with its reason. Your data owner fixes each rejection at the source or accepts it, and the dry run is repeated until only agreed rejections remain.
Step 3: Reconciliation
Per currency, the money in your export equals what is loaded, rejected and skipped. Your finance team and Getz’s both sign it; an unbalanced move is refused.
Step 4: Rehearsal
The whole move is run on a copy first: load, check the agreed acceptance criteria, go back, and load again.
Step 5: The way back
If the move has to stop, the moved cards are blocked and withdrawn at Getz Hub, every opening balance is reversed by an entry that points at it (nothing is deleted), and drivers are signed out. If drivers have already charged, the balances to hand back are agreed with your finance team first.
What moves
What comes across, and what drivers redo
| Capability | In the move | What happens instead |
|---|---|---|
| Drivers | Active, suspended and blocked accounts | Closed accounts are settled and closed at the source |
| RFID cards and app tokens | With their status and expiry | Vehicle ids for plug-in starts are enrolled again in the app |
| Wallet balances | Paid-in money and promotional credit, in US dollars | Debts are settled at the source first |
| Driver prices | Markups on the operator’s cost and per-session fees | Driver-, fleet- and plan-specific prices are set up again |
| Saved bank cards and passwords | No | Drivers add a card again and sign in with their phone number |
| Session and invoice history | No | Stays with your old system; history on Getz starts at the move |
Before any driver moves
What a move plan agrees, in writing
Each item is agreed with your team in discovery and signed off before the cut-over starts. What Getz can bring across depends on what your current platform can export.
Your current data
Which driver, token, tariff and balance fields your current platform exports, in what format, and how Getz checks a sample with you before the move.
Wallet balances
How open balances are reconciled between the old ledger and the new one, and who signs the totals off.
RFID cards and app access
How active cards and driver sign-ins carry over, and what a driver does if one stops working.
Parallel validation
Which drivers, chargers and payment methods are tested on the new platform while the old one still runs.
Downtime and communication
Whether any start is unavailable during the move, when, and what drivers are told under your brand.
If the move stops
The conditions for stopping the move, and who is responsible for each step of going back.
If you leave
What you can take with you
Your data is yours. If you leave the platform, Getz hands over your organisation’s data in a documented JSON format, with a CSV for each part, built from your organisation only.
Drivers and tokens
Driver accounts and their app, RFID and virtual tokens, with their status.
Wallet balances and ledger
Each wallet’s balance, open holds and every ledger entry behind it, nothing summarised.
Sessions, charges and prices
Sessions and rated charges with the operator’s references, and your markups and fees.
Already happy with your app?
Keep it, and connect to Getz Hub only
If your driver app and back office work for you and you only need more networks, you do not need this platform. Getz Hub is a separate, neutral business with its own terms: one OCPI connection to the operators connected to it.
If you move to Getz EMP later, your OCPI party and roaming agreements come with you.
- Roaming through Getz Hub over OCPI 2.3.0 and 2.2.1
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.
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
- Musasa Charge (demo)
- Driver
- Tendai Moyo
- Site
- Fife Street charging hub (demo)
- Session
- 1048f124-95a4-4f1a-9231-d03be6332ec5
- Operator session
- ZPC-S-MWQZXCZO
- Charge
- 2f66a59d-dea7-4acf-a3d0-e91e8c8640ea
- Tax invoice
- INV-000002: US$ 13.01 (operator US$ 9.66, margin US$ 1.60, VAT 15.5% US$ 1.75)
- Credit note
- CN-000002, US$ 1.50 goodwill, back to the wallet
- Paid
- US$ 11.51
- Provider payout
- SETTLE-PAYNOW-MWQZXCZO (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 US dollars. 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.5% 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 a company card is refused for funds
A fleet’s prepaid US dollar wallet cannot cover a session’s estimate, so the start is refused in real time. The charger shows the reason, and the refusal is kept with it.
Demo data · a company RFID card of a fleet in the same demo
| Who | What they do |
|---|---|
| Getz EMP | Answers No credit within the authorisation deadline, with the company’s reason, and keeps the record. |
| The charge point operator | Shows the refusal at the charger; nothing is started or charged. |
| The fleet manager | Sends the driver to another approved site or asks Finance to top the wallet up. |
| Your finance team | Records the top-up with its reference; the next start is checked against the new balance. |
Questions from existing eMSPs
Do we keep our OCPI party and identity?
Yes. On the platform your eMSP identity is your trading name and your own OCPI party; drivers who sign up get tokens under it.
Who moves our drivers and balances?
Getz does, with your team, as part of onboarding. Getz loads your drivers, tokens, balances and prices, checks with you that the balances add up before anything is committed, and agrees in writing how the move would be stopped. There is no import tool to run yourself.
Can drivers start a charge when the platform is unreachable?
No. Every start is authorised in real time, which protects you from unpaid sessions and lost cards. Starting while the platform is unreachable is coming soon.
Plan your move with us
Tell us what runs your service today and what is holding it back. We reply by e-mail to arrange a technical conversation.