Skip to main content
Getz EMP

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

Regional requirements and how Getz EMP handles them
CapabilityWhat the region needsOn Getz EMP
Currencies Rand at home, other currencies for visiting driversPrices and fees kept per currency
Tax VAT by country, changing over timeRate by location and session date
Payments Cards, Apple Pay, SnapScan and ZapperAdapters built; live on your accounts
Bad debt Card-free drivers without unpaid sessionsWallet holds before charging
Roaming Operators on OCPI 2.2.1 and 2.3.0One connection through Getz Hub

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.

  1. Step 1: Inventory

    Drivers, tokens, tariffs, operator connections, payment providers and open balances on your current platform.

  2. Step 2: Configure in parallel

    Your organisation, eMSP identity, pricing and brand set up alongside your live service.

  3. Step 3: Connect

    Your eMSP identity on Getz Hub as your own OCPI party; your merchant accounts keyed in.

  4. Step 4: First drivers

    A first group of your drivers moves and charges on your chargers and payment providers before anyone else moves.

  5. 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.

  1. 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.

  2. 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.

  3. 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.

  4. Step 4: Rehearsal

    The whole move is run on a copy first: load, check the agreed acceptance criteria, go back, and load again.

  5. 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

What moves to Getz EMP in a move and what stays behind
CapabilityIn the moveWhat happens instead
DriversActive, suspended and blocked accountsClosed accounts are settled and closed at the source
RFID cards and app tokensWith their status and expiryVehicle ids for plug-in starts are enrolled again in the app
Wallet balancesPaid-in money and promotional credit, in randDebts are settled at the source first
Driver pricesMarkups on the operator’s cost and per-session feesDriver-, fleet- and plan-specific prices are set up again
Saved bank cards and passwordsNoDrivers add a card again and sign in with their phone number
Session and invoice historyNoStays 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
Illustration

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.

Your branded appYour back-office teamGetz EMP platformYour merchant accountsGetz HubParticipating networksYour systems

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
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)
  1. 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

  2. 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

  3. 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

  4. 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 resolves it: when the card provider refuses a refund
WhoWhat they do
The card providerRefuses the refund and gives its reason.
Getz EMPRecords 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 teamRetries it, or resolves it as paid outside (with a reference) or written off.
Your support teamAnswers the driver, with the refund and its reason in front of them.

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.