Plug & Charge adoption is the uptake and real-world deployment of Plug & Charge (PnC)—a charging experience in which an EV automatically authenticates and authorizes a charging session when the driver plugs in, without using an RFID card, app, or a manual payment step. Plug & Charge is enabled by ISO 15118 and relies on digital certificates and secure communication between the vehicle, charger, and backend systems.
Why Plug & Charge Adoption Matters
Plug & Charge adoption is a major step toward a “fueling-like” EV experience and can significantly improve the usability of public charging. When implemented well, it helps:
– Reduce failed starts caused by app login issues, roaming problems, or poor connectivity
– Improve driver satisfaction by removing authentication friction
– Increase charger utilization by speeding up session initiation
– Reduce operational costs linked to user support tickets and payment troubleshooting
– Enable more seamless roaming and contract-based charging experiences across networks
What Drives Plug & Charge Adoption
Adoption depends on multiple stakeholders and ecosystem readiness:
– EV support: vehicles must support ISO 15118 features (PnC capability varies by model and software)
– Charger support: EVSE must support ISO 15118 (often alongside OCPP 2.0.1 capabilities in the backend)
– Backend readiness: CPMS, eMSPs, and contract certificate systems must support certificate provisioning and authorization flows
– PKI infrastructure: reliable certificate issuance, renewal, and revocation processes are required
– Business agreements: roaming/contract relationships must align so a vehicle contract is accepted at the charger
How Plug & Charge Adoption Works in Practice
A typical PnC user journey requires technical onboarding before the first session:
– A driver activates Plug & Charge with a mobility provider or OEM service (contract creation)
– A contract certificate is provisioned to the vehicle
– The charger and vehicle perform a secure handshake (ISO 15118) at plug-in
– The backend validates the contract and authorizes the session
– Charging starts automatically, and billing is handled via the contract
Common Barriers to Adoption
PnC adoption can be slower than expected due to ecosystem complexity:
– Mixed vehicle support and inconsistent feature availability across models and markets
– Certificate lifecycle issues (expired certificates, failed renewals, trust-chain mismatches)
– Backend interoperability gaps between CPMS, eMSPs, and roaming platforms
– Operational challenges with onboarding flows and customer support
– Sites with weak connectivity affecting backend authorization and certificate validation
– Regulatory and payment requirements still pushing ad-hoc options like payment terminals in parallel
Operational Best Practices for Driving Adoption
Organizations aiming to grow Plug & Charge adoption typically focus on:
– Clear customer onboarding and troubleshooting flows (activation, vehicle setup, supported models)
– Robust certificate lifecycle management (monitoring expiry, automated renewals)
– Controlled rollouts (pilot sites → targeted regions → full network)
– Strong incident processes for PnC failures (fallback to RFID/app, rapid diagnosis)
– Consistent firmware and security maintenance via patch management and tested OTA updates
Benefits of High Plug & Charge Adoption
– Faster, more reliable session start rates and fewer abandoned attempts
– Lower friction for roaming and cross-network usage (where agreements exist)
– Better user experience in fleet and corporate contexts (vehicle-based identity)
– Improved security compared to weaker credential methods when PKI is well managed
– More scalable operations with fewer manual authentication touchpoints
Related Glossary Terms
Plug & Charge
ISO 15118
ISO 15118-20
OCPP 2.0.1
PKI Infrastructure
Digital Certificates
TLS / mTLS
Interoperability Networks
Roaming
eMSP
Payment Terminals