Tap, Pay, Charge: Choosing the Right EV Charging Payment Flow for Your Chargers

The biggest leak in any public charger's revenue is the moment a driver pulls up, plugs in, and discovers they need to download yet another app and create an account before a single kilowatt flows. The right EV charging payment flow removes that wall entirely: tap a QR, pay with the card already in your phone, and charging starts on its own. This guide compares the three driver payment flows we support and shows you when to use each across the sites you run.

If you are still weighing up whether to operate chargers at all, start with our guide to what a CPMS actually does and the revenue playbook for South African site hosts. This article assumes you have a charger — or are about to — and need to decide how drivers actually pay at it.

The friction problem: why app-and-account charging loses sales

Every extra step between arrival and electrons is a place a paying driver walks away. An app download needs signal, storage, and patience — three things in short supply at a forecourt at 6pm. Account creation asks for an email, a password, a card, and often a verification step, all before the driver has any reason to trust you. For a once-off visitor passing through town, that is a deal-breaker. They either give up or resent the experience, and neither outcome helps your utilisation.

The fix is not a better app. It is removing the app from the critical path. A driver should be able to charge at your site the way they buy a coffee: point, pay, done. That principle — no app, no account, no friction — is the backbone of how we think about driver payments, and it is why our default flow needs nothing more than a phone camera and a card.

EV charging payment flow 1: prepaid pay-to-start bundles via QR

This is the workhorse for public, paid charging. A driver scans the QR code on the charger, picks a fixed bundle — say 10 kWh or 20 kWh — and pays with card, Apple Pay, or Google Pay through PayFast, in Rand. The session starts automatically the moment payment clears and stops automatically when the paid-for energy has been delivered. No app. No account. No surprise final bill, because the driver paid for a known quantity up front.

Prepaid bundles suit the visitor economy: highway stops, shopping centres, tourist routes — anywhere a meaningful share of drivers are first-timers who may never return. Because the amount is fixed before charging begins, there is nothing to reconcile, chase, or dispute afterwards. The driver knows exactly what they are buying, and you know the money is in before the connector locks. You can see this whole sequence run in the live demo.

EV charging payment flow 2: free guest access via one-time code

Some hosts do not want to charge for electricity at all — they want the charger to pull people in. A hotel, a dealership, a destination restaurant, a retail anchor: for them the charger is a magnet, not a meter. For these sites we offer free guest access. The driver scans the QR, enters their email, and receives a one-time code that unlocks a capped free session. No payment, no app, and no standing account.

The cap matters here even more than with prepaid. A sensible limit — for example up to an hour, or up to a set number of kWh — keeps a free amenity from being drained by a single all-day parker, and keeps your electricity bill predictable. The email captured is minimal and purpose-bound, which keeps you on the right side of POPIA: collect only what the session needs, nothing more.

Flow 3: account and member charging for fleets and regulars

Accounts are the wrong default for walk-up drivers — but exactly right for people who come back. Fleet operators, staff parking, residential complexes, and loyal regulars all benefit from a stored identity: consolidated billing, recognised vehicles, per-driver reporting, and the ability to skip the payment step on every visit. The friction of setting up an account is paid once and amortised over hundreds of sessions, which flips the maths completely.

The key is to offer accounts as an option for the people who want them, never as a toll gate for the people who do not. A good site can run prepaid QR for the public and accounts for the fleet on the same hardware — the CPMS decides which flow a given session uses, not the charger.

Comparing the three flows at a glance

Most operators do not pick one. The sharpest setups blend flows by site and by audience — prepaid for the passing public, free guest access where charging drives footfall, and accounts for the fleet that returns every day. Because the choice lives in software, you can change it without touching a cable.

Why local payments and minimal data matter

A payment flow that assumes a foreign card or an offshore wallet quietly excludes a chunk of South African drivers. Settling in Rand through PayFast — with card, Apple Pay, and Google Pay — means the payment methods drivers already use just work, and your settlement lands in a local account on local rails. Pricing is set in Rand too, and our default position is to sit a few cents under the major public networks on every kWh, so the driver-facing price stays competitive without you having to model it from scratch. The split between you and Origami is agreed up front and configurable per host, with the majority staying with you — see the pricing detail.

On data, less is genuinely more. Prepaid charging needs no personal account at all; guest access needs only an email tied to that session. Capturing the minimum is faster for the driver, cheaper for you to safeguard, and the most defensible posture under POPIA. You cannot leak what you never collected.

How auto-stop protects both driver and host

Every flow above leans on the same underlying safeguard: the session ends cleanly at the cap. When the paid-for energy or time runs out, the platform issues a soft-stop — it ramps the current down before cutting it, rather than yanking the load off in one step. That protects the vehicle, the connector, and your site's grid connection from a sudden swing, which is exactly what you want on a constrained supply or during a load-shedding stage.

• For the driver: a known, fixed cost and a clean finish — no runaway bill, no nasty surprise on a forecourt at night.
• For the host: no bay hogging, predictable draw per session, and automated settlement so revenue lands without you reconciling anything by hand.
• For the site: caps plus throttling and load management keep total demand inside your connection, even when several cars charge at once.

All of this rides on standards-compliant charger communication — we speak OCPP 1.6J, the protocol the vast majority of installed South African hardware already talks — so these flows work across mixed fleets of chargers rather than locking you to one vendor. Full platform detail lives in the docs.

Choosing a driver payment flow is really a commercial decision about who visits your site and why. Get it right and your chargers convert quietly in the background; get it wrong and you pay for hardware that sends paying drivers away. If you would like help mapping the right mix of prepaid, guest, and account charging to your sites, request access and tell us about your sites — we will walk through it with you.