For licensed CPOs & eMSPs

EV charger payment system — pre-auth, kWh capture and roaming-ready reconciliation.

Pre-authorise the driver's card when the plug connects. Meter kWh through the session. Capture the true amount when the session ends. Reconcile every session, every charger, every roaming route — all in one ledger, under one API.

Book a CPO review Read the API docs
Pre-auth
per-session hold before energy delivery
kWh capture
final capture once the session closes
Contactless
EMV tap, app-initiated & RFID starts
Roaming-ready
cross-CPO settlement metadata attached

Key benefits

Why CPOs pick this ev charger payment system shape

Four properties that show up the moment charging volume stops being a one-off payment and starts being a session-lifecycle problem.

  1. Pre-auth per charging session

    The driver's card is pre-authorised for the maximum estimated session amount when the plug connects. Energy delivery starts against a live hold. Final capture reconciles to the actual kWh once the session closes — no separate 'top-up' flow, no orphaned holds.

  2. Contactless, app or RFID initiation

    The same authorisation engine handles EMV contactless taps at the charger, app-initiated sessions from the CPO's mobile app, and RFID / Plug&Charge starts from registered card-on-file drivers. One vault token per driver across every start method.

  3. Roaming-ready settlement

    Where the CPO participates in a roaming network, each session's settlement row carries the roaming-home operator and the home eMSP identifier so cross-CPO clearing reconciles cleanly. Same feed for direct and roaming sessions.

  4. Multi-currency across markets

    CPOs operating across borders accept in the driver's local currency and settle into the CPO's treasury currency. Every settlement row is tagged with the transaction currency, settlement currency and applied FX rate.

How the session flow works

From plug-in to reconciled ledger row in six steps

What actually happens between a driver tapping a card at the socket and the CPO finance team reading a ledger row tagged with session ID, kWh and currency.

  1. 01

    Driver initiates

    The driver taps a card, initiates from the CPO's app, or presents an RFID / Plug&Charge credential at the charger.

  2. 02

    Pre-auth on the platform vault

    topropay's PCI L1 vault provisions a token and pre-authorises the estimated session maximum through the routing engine's top-ranked lane.

  3. 03

    Charge starts

    The charger releases energy against the live authorisation hold; the CPO's back-office receives the pre-auth event and unlocks the session in real time.

  4. 04

    kWh metered

    The charger meters the actual energy delivered; the session ends when the driver unplugs, when a soft limit is hit, or when the pre-auth window would otherwise expire.

  5. 05

    Capture the true amount

    The CPO's back-office triggers capture for the actual kWh × tariff amount. If the true amount exceeds the pre-auth, a delta capture or re-auth is handled per acquirer policy.

  6. 06

    Reconcile per session

    Settlement rows land in the unified feed tagged by session ID, charger ID, driver token, energy delivered, currency and roaming route (if any).

Main use cases

Where an integrated ev charger payment system earns its keep

Five recurring operator shapes — CPOs, eMSPs, fleet operators, retail forecourts and municipal / workplace networks.

  • CPO

    Charge point operators (CPOs)

    CPOs running public networks — car parks, forecourts, motorway HPCs — take contactless taps at every socket and route sessions through one integration with per-session reconciliation.

  • eMSP

    eMobility service providers (eMSPs)

    eMSPs issuing driver accounts and app tokens use the same platform to charge and reconcile roaming sessions across partner CPOs, with home-operator metadata preserved end-to-end.

  • Fleet

    Fleet operators

    Commercial fleets billing driver-assigned RFID / card-on-file across depot and public chargers — one merchant record for depot invoices plus public roaming top-ups.

  • Retail

    Retail forecourts and hospitality

    Retail parking, supermarkets, hotels and hospitality venues offering charging as a customer perk or a paid service, with EMV contactless taps and app-initiated starts on the same charger fleet.

  • Muni

    Municipal and workplace charging

    Municipalities and employers running charger fleets that need audit-grade reconciliation per socket, per session, per driver — with rate transparency for public-sector or workplace-benefit reporting.

Platform features

Capabilities behind the platform's ev charger payment system

Twelve capabilities grouped into session-side, reconciliation / roaming-side and platform / compliance-side. Each applies whether the CPO runs 10 or 10,000 sockets.

Session & flow

  • Pre-auth per session

    Estimated maximum held on the card before energy is released; final capture reconciles to actual kWh.

  • Delta capture / re-auth

    When actual exceeds pre-auth, the platform handles delta capture or re-authorisation per acquirer policy.

  • EMV contactless at the charger

    Card-present taps at the socket via licensed partner acquirers with cross-channel vault sharing.

  • App & RFID / Plug&Charge starts

    App-initiated and stored-credential starts run on the same vault token as the driver's card-on-file.

Reconciliation & roaming

  • Session-tagged settlement

    Every settlement row carries the session ID, charger ID, driver token and energy delivered for audit.

  • Roaming home-operator metadata

    Cross-CPO sessions preserve the roaming home and eMSP identifier in the reconciliation feed.

  • Multi-currency support

    Cross-border CPOs settle into their treasury currency with per-row FX rate metadata.

  • Refund per session

    Refunds against the original session token — full or partial — with reason codes required.

Platform & compliance

  • Unified API across every start method

    One REST contract for tap, app and RFID starts; three integration shapes for the CPO's own UI.

  • Smart routing across acquirers

    Per-BIN and per-currency routing across the connected acquiring panel; soft declines cascade inside the same auth.

  • PCI DSS Level 1 vault

    Card data captures into the platform vault before any acquirer sees it; PAN never lands on the charger or the CPO's app.

  • Selective 3DS2 / SCA

    Selective EMV 3DS2 handles PSD2 SCA on European card-on-file and app-initiated flows without breaking approval.

Industry relevance

Built for licensed CPOs and eMSPs across EU, UK, APAC and LATAM

topropay's ev-charger posture targets licensed charge point operators, licensed eMobility service providers and licensed fleet operators across EU, UK, APAC and LATAM. Charger hardware and OCPP / OCPI back-office stay with the operator; the platform delivers acceptance, routing, vault and reconciliation.

Trust & compliance

Compliance posture across every start method

One audited environment underpins the orchestration layer; hardware certifications sit with the CPO and their partner acquirer.

PCI DSS Level 1
Vault, switch and tokenisation are PCI DSS Level 1 service-provider components; the CPO inherits the posture across every acceptance channel — charger tap, app, RFID.
PCI MPoC / MPoC-aligned
Where SoftPOS-style flows apply (e.g. CPO staff phones), partner apps follow the PCI MPoC programme for card-present taps on commercial off-the-shelf devices.
EMV & scheme rules
Contactless CVM caps, PIN bypass and Plug&Charge credential handling follow Visa, Mastercard, Amex and regional-scheme rules.
SCA & PSD2
Selective 3DS2 on the online / app path keeps European approval high without skipping the SCA bar; card-present clears under its own CVM rules.
Sanctions & AML alignment
Sanctions screening on onboarding; AML monitoring tuned to CPO volume, driver mix and cross-border currency exposure.
Licensed operators only
Licensed CPOs, eMSPs and fleet operators with the relevant operating licences in their target markets are supported. Grey-market or unlicensed operators are out of scope regardless of vertical.

Ready to plug in payments

Bring your charger network's payments onto one orchestration platform.

A 30-minute CPO review covers your charger firmware and OCPP / OCPI back-office, the connected acquirers relevant to your geographies, and a sandbox you can test the full session lifecycle against before any commercial commitment.

Book a CPO review Read the API docs

Frequently asked

CPO questions about the ev charger payment system on topropay

Pre-auth mechanics, delta-capture behaviour, roaming metadata, driver-side flows, and the practicalities of running a charger network on one orchestration platform.

  1. 01

    What does the ev charger payment system on topropay actually do?

    The ev charger payment system on topropay handles the full session lifecycle — pre-authorising the driver's card for the estimated maximum before energy is released, capturing the actual kWh amount when the session closes, tagging each settlement row with session and charger metadata, and reconciling across every connected acquirer into one ledger. Contactless taps, app-initiated starts and RFID / Plug&Charge starts are all supported under the same API.

  2. 02

    How does the pre-auth mechanism work at an EV charger?

    When a driver initiates a charging session, the platform pre-authorises their card for a merchant-configured maximum (e.g. a rated session ceiling). Energy is released once the pre-auth clears. When the session ends, the platform captures the actual kWh × tariff amount and voids or reduces the unused portion of the hold — leaving no orphaned pre-auth on the driver's card.

  3. 03

    What happens if the session cost exceeds the pre-auth?

    The platform runs a delta capture or a follow-up re-authorisation for the overrun, per the acquirer's rules. For most consumer card programmes the delta capture is transparent to the driver; for stricter policies a follow-up SCA challenge may be triggered.

  4. 04

    Does the platform support contactless taps at the charger itself?

    Yes. EMV contactless taps at the charger are delivered through licensed partner acquirers, with the same PCI L1 vault sharing tokens with app-initiated and RFID starts. This is important for public-network CPOs, where scheme rules increasingly require an EMV-compliant contactless option at every socket.

  5. 05

    Are app-initiated and RFID starts handled the same way?

    Yes. Both surface as authorisations against the driver's vault token. RFID and Plug&Charge starts use stored credentials issued during onboarding; app-initiated starts use the token issued at first sign-up. The reconciliation feed shows the initiation channel for each session.

  6. 06

    How does roaming settlement work between CPOs?

    Where the CPO participates in a roaming network (Hubject / GIREVE / OCPI-compatible), each session's settlement row carries the roaming home-operator and eMSP identifier. The platform doesn't handle inter-CPO clearing itself — that sits with the roaming hub — but it preserves the metadata so the CPO's finance team can reconcile the hub-side flows against the platform-side receipts.

  7. 07

    Can drivers pay in their local currency at cross-border chargers?

    Yes. Multi-currency acceptance surfaces the local price to the driver where the scheme rules and the connected acquirer allow it. Settlement lands in the CPO's treasury currency with the applied FX rate stamped on the settlement row. Refunds default to the original transaction currency to keep the driver whole.

  8. 08

    How are refunds handled per session?

    Refunds run against the session's vault token. Full refunds reverse the entire captured amount; partial refunds reduce the captured amount. Every refund event is logged with actor identity, reason code (equipment fault, dispute, goodwill, etc.) and timestamp for audit.

  9. 09

    What acquirer options are available for CPOs?

    Connected acquirers cover EU, UK, APAC and LATAM licensed acquirers with scheme-programme registrations that fit the CPO's mix. The routing engine picks the highest-EV acquirer per authorisation across BIN, currency and country pair; soft declines cascade to the next ranked lane inside the same authorisation.

  10. 10

    How long does a CPO take to go live?

    Most CPOs go from KYB submission to first paid session in 3–6 weeks. Variables are the CPO's charger firmware compatibility (OCPP / OCPI), the choice of connected acquirer, and any scheme registrations. Sandbox covers the full session lifecycle from day one.

  11. 11

    Which charging protocols does the platform integrate with?

    The platform is protocol-agnostic on the charger side — the CPO's back-office (running OCPP 1.6 / 2.0.1, OCPI, or a proprietary stack) integrates against topropay's REST API for authorise / capture / refund events. Charger-side hardware certification stays with the CPO and their partner acquirer.

  12. 12

    Is the platform PCI-compliant for card-present at the socket?

    The platform's vault, switch and tokenisation are PCI DSS Level 1 service-provider components. Card-present acceptance at the socket sits with licensed partner acquirers whose hardware / firmware carries EMV Level 1 / Level 2 certification. The combination keeps PAN exposure out of the charger and the CPO's app code.

  13. 13

    How does driver onboarding work for card-on-file / app accounts?

    Driver onboarding happens on the CPO's app or web account flow. The first successful authorisation issues a vault token; subsequent sessions use the token against the same card. Account updaters keep tokens alive across card re-issuance. SCA is triggered on the initial card add and per PSD2 rules on subsequent sessions.

  14. 14

    What does reconciliation look like for a CPO's finance team?

    For CPO finance, reconciliation is one normalised feed across every connected acquirer, tagged per row with session ID, charger ID, driver token, energy delivered (kWh), tariff, currency, applied FX rate and roaming route. Daily exports as CSV or via API; ERP connectors push into the CPO's accounting stack.

  15. 15

    Which merchant types are out of scope?

    Unlicensed operators, grey-market energy resellers, adult-content adjacent verticals and unlicensed gambling operators are out of scope. topropay's underwriting filters these at onboarding — the platform serves licensed CPOs, licensed eMSPs, licensed fleet operators and adjacent regulated businesses only.

Related

Related on the topropay platform