White-label · Wallet and payments
Wallet holds before charging, with local top-ups
Starting a session reserves the estimated cost in the driver’s wallet, and the session stops at the reserved amount. The real cost is taken when the charge record arrives and the rest is released. Drivers top up by card, Apple Pay, SnapScan or Zapper, through merchant accounts you hold.
The wallet
A ledger finance teams can reason about
Append-only ledger
Entries are only ever added; balances are derived, never stored. Corrections are reversing entries, so the history stays complete.
Holds before charging
A start reserves the estimated cost, lowering the available balance but not the total. The session stops automatically at the reserved amount.
Promotional credit first
Spending takes promotional credit first, earliest expiry first, then cash. Refunds go back to the account each part came from.
Automatic collection
Every rated charge is collected by one collector: wallet first when the driver allows it, then the saved card, with retries.
Unpaid sessions policy
You decide whether a driver who owes money may keep charging. The default is no.
Payouts with approval
Drivers can ask for paid-in money back; finance approves, and card top-ups are refunded to the card.
One session, step by step
From the available balance to the final debit
What happens to a driver’s wallet during one session, and what happens if the money cannot be collected.
Step 1: Available balance
The wallet balance minus any amounts already reserved for live sessions.
Step 2: Hold
The start reserves the estimated cost. The available balance drops; the total does not.
Step 3: Session stops at the hold
If the session reaches the reserved amount, it is stopped automatically.
Step 4: Final debit and release
When the operator’s charge record is rated, the real cost is debited and the rest of the hold is released.
Step 5: If collection fails
The collector tries the wallet, then the saved card, with retries. Under the default unpaid-sessions policy, a driver who owes money cannot start again until it is paid.
Payment methods
Supported payment methods
Cards (with Apple Pay) and QR payments, each settling into the merchant account you hold with that provider.
| Capability | What drivers do | Supported | Settles into |
|---|---|---|---|
| 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 |
Payment safety
Every provider result is checked twice
Callbacks are signature- or hash-checked, then re-confirmed with the provider before money moves in the ledger.
A payment the provider confirms after it was marked failed is credited once, with an audit record. QR and card requests are tied to the charge they settle, one open request per charge, so a driver cannot pay twice for the same session.
- Wallet holds, collection and payment logic
Every wallet movement: credits, reservations and charges.
- What you see: each charge with its site and amount
- Why it matters: a clear statement drivers can trust
In the driver app
A receipt for every session, and every movement on the statement
Each session ends with an itemised receipt: energy, each price component, 15% VAT and the total in rand, built from the operator’s charge record. Drivers share it as a PDF or to WhatsApp, and can report an overcharge from the same screen.
The wallet activity lists every credit, reservation and charge with its site and amount. Captured with demo data; your brand’s colours replace the default green.
- Itemised receipts with VAT, shared as PDF or to WhatsApp
- Holds, charges and refunds on one wallet statement
An itemised receipt for every session, VAT shown.
- What you see: energy, price per component, VAT and total in ZAR
- Why it matters: built from the operator’s charge record, so it matches
Questions about payments
Whose merchant accounts are used?
Yours. You sign the merchant agreements with the providers you want and configure the keys. Getz does not hold your drivers’ money in its own accounts.
What happens when a provider is not configured?
It fails closed: until your keys for that provider are in place, it answers “not available yet”, so no driver is ever charged through a half-configured method.
Plan your payment set-up
Tell us which countries and payment methods matter to your drivers.