Banks, insurers, telcos and payment apps
Every charging session is a payment, on your merchant accounts
Run a charging service under your brand with the supported payment methods (cards with Apple Pay, SnapScan and Zapper) settling into merchant accounts you hold, and a wallet ledger your finance team can reason about.
Three motives
What each kind of financial business gets
Telcos and payment apps
A new everyday use for your wallet
SnapScan and Zapper QR payments in the app, and cards with Apple Pay, all settling into your own merchant accounts.
Banks
A wallet built like a ledger
Entries only ever added, holds before charging, payouts with approval.
Insurers and vehicle finance
An EV product customers use weekly
Partner-funded charging credit for your EV customers, issued as vouchers with limits and expiry, and signed events for your own customers’ charging.
Built for South Africa
Charge in rand, pay by card or QR code
South African drivers pay by card, Apple Pay, SnapScan or Zapper and expect 15% VAT on an itemised receipt. The platform was built with all of that in mind.
Prices and fees are kept in rand and never silently converted. VAT comes from the charging location’s country and the session date.
- VAT by country and date; rand prices at 15%
The wallet: balance, amounts reserved for charging and payment preferences.
- What you see: available and reserved rand
- Why it matters: drivers always know what they can spend
Payment adapters
Supported payment methods, on your merchant accounts
Cards, Apple Pay and QR payments, settling into the merchant accounts you hold. Any other payment service is assessed in discovery, including who settles and refunds.
| Capability | Kind | Supported | Settles into |
|---|---|---|---|
| Cards through Paystack or DPO Pay | Cards and Apple Pay | Yes | Your Paystack or DPO Pay account |
| SnapScan and Zapper | QR payments | Yes | Your SnapScan and Zapper merchant accounts |
For your finance team
From a payment to a refund and a credit note
One charge, paid by card, that the operator later corrects. Card refunds go back through Paystack or DPO Pay; SnapScan and Zapper refunds are made by hand and recorded.
Step 1: Payment
The payment carries the provider’s reference and settles into your merchant account.
Step 2: Tax invoice
The final receipt is the tax invoice (INV-…) in your company’s name, with VAT and how it was paid.
Step 3: Correction
The operator re-sends or cancels the charge record. The difference goes back the way it was paid, and a credit note (CN-…) is issued against the invoice.
Step 4: Refund that fails
A card refund the provider refuses is retried after 15 minutes, 1 hour and 4 hours, then daily, and then escalated to Finance: retry it, or resolve it as paid outside (with a reference) or written off.
Step 5: Reconciliation
The finance export lists the charge, the payment, the refund and the credit note as separate rows with their references; provider payouts are matched by reference and anything unmatched is flagged.
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. |
Questions from banks, insurers and telcos
Does Getz hold the drivers’ money?
No. Payments run through merchant accounts in your name. The wallet ledger records every movement; balances are derived from the entries and never stored.
What charging data do we receive?
Signed events for your own drivers and fleets, per event type. What you may use them for is set by your privacy notice and your drivers’ consent. No data about other brands on the platform is shared with you.
Can you add our own payment rail?
Adapters follow one pattern: initiate, confirm with the provider, credit once. A new rail is scoped in discovery; we do not promise one before seeing its interface.
Bring your payment rails to charging
Tell us which countries, payment methods and customer products matter. We reply by e-mail to arrange a conversation.