Plug & Charge payments are the payment and settlement processes behind a Plug & Charge (PnC) EV charging session, where charging starts automatically at plug-in, and the driver does not present a card, RFID, or app at the charger. Payments are linked to a contract associated with the vehicle and enabled by ISO 15118 using digital certificates.
Why Plug & Charge Payments Matter
PnC removes the visible payment step, so the backend payment experience must be seamless and trustworthy. Strong Plug & Charge payment handling helps:
– Reduce failed starts caused by authentication/payment friction
– Improve customer satisfaction and trust in public charging
– Enable fleet and corporate charging with vehicle-based identity
– Support roaming and cross-network charging without manual payment steps
– Reduce customer support load for login, RFID, and ad-hoc payment issues
How Plug & Charge Payments Work
A typical Plug & Charge payment flow looks like this:
– A driver signs up with an eMSP, OEM charging service, or fleet provider and agrees to a tariff
– A contract certificate is provisioned to the vehicle (PnC activation)
– At plug-in, the vehicle and charger perform an ISO 15118 handshake and authenticate
– The charger/CPMS authorizes the session against the contract identity (directly or via roaming)
– The session is metered and rated (kWh, time, idle fees, peak/off-peak rules)
– The contract owner is billed using the agreed method (invoice, card-on-file, corporate billing)
– Settlement occurs between the CPO and the eMSP/roaming partner based on the transaction record
Payment Models Used with Plug & Charge
PnC can be paired with several payment methods, depending on who owns the customer relationship:
– Card-on-file: customer card stored by the eMSP/OEM, charged per session
– Post-paid invoicing: common for fleets and corporate accounts
– Subscription + usage: membership grants access/discounts; usage billed per session
– Roaming settlement: eMSP pays the CPO under roaming terms, then bills the driver
Key Payment and Data Requirements
For reliable PnC payments, systems typically require:
– Strong contract identity and authorization records (certificate-based)
– Accurate session metering and audit trails (timestamps, meter start/end)
– Tariff transparency and correct rating (including idle fees and time-of-use rules)
– Receipt delivery through the eMSP/OEM app or portal
– Dispute workflows (refunds, session investigations) even though the driver didn’t “pay at the charger”
In many markets, compliant energy metering (e.g., MID metering) supports defensible per-kWh billing.
Common Challenges and Failure Modes
– Contract certificate issues (expired, not provisioned, trust-chain mismatch)
– Backend interoperability gaps (CPO ↔ eMSP ↔ roaming platform)
– Connectivity problems during authorization or settlement
– Session record mismatches (IDs, meter values, tariff application)
– Need to run parallel payment options (e.g., payment terminals for ad-hoc users)
– Customer confusion if tariffs/receipts are only visible in the mobility provider app
Benefits
– Seamless “plug in and go” experience with fewer manual steps
– Faster start rates and reduced dependence on charger UI and mobile connectivity
– Strong vehicle-based identity suited for fleets and repeat users
– Cleaner interoperability experience when roaming agreements support PnC
Limitations and Considerations
– Requires mature PKI infrastructure and certificate lifecycle management
– Not all vehicles and networks support PnC consistently across markets
– Operator support teams need tools to diagnose certificate and authorization issues
– Must maintain fallback methods (RFID/app/ad-hoc) to cover all users and exceptions
Related Glossary Terms
Plug & Charge
Plug & Charge Billing
ISO 15118
OCPP 2.0.1
PKI Infrastructure
Digital Certificates
Roaming
eMSP
Payment Gateway Integration
MID Metering
Payment Terminals