Plug and Charge is the process that lets an electric vehicle identify itself to a charger and start a paid session as soon as the cable is connected, with no app, card or payment terminal. Behind that simple experience sits a chain of digital certificates defined in the ISO 15118 family of standards, and a set of companies that must all trust the same roots.
This explainer sets out how the authentication works, what changes between ISO 15118-2 and ISO 15118-20, why bidirectional charging depends on the newer standard, and where interoperability still breaks down. It is written for charge point operators, fleet managers, vehicle software teams and procurement leads specifying chargers in the UK, where many suppliers also design to European requirements.
What Plug and Charge does
Hubject, one of the main operators of the underlying trust infrastructure, describes Plug&Charge as automatic authentication between vehicle and charging station, with the session starting and billing handled once the plug is inserted. In practice the car presents a digital contract, the charger checks it, and the driver’s mobility service provider is billed.
The same idea appears in law. The EU Alternative Fuels Infrastructure Regulation, AFIR, defines automatic authentication as the authentication of a vehicle at a recharging point, and requires operators that offer it to let drivers choose ad hoc payment instead. That opt-out matters for fleets that want control over which tariff a vehicle uses.
The ISO 15118 standards behind Plug and Charge
ISO 15118 is a multi-part standard for communication between the vehicle’s communication controller and the charger’s supply equipment communication controller. Two parts matter most here.
| Part | Published | What it covers |
|---|---|---|
| ISO 15118-2 | April 2014, confirmed in 2024 and under revision | Network and application protocol for energy transfer from charger to vehicle, using TLS, TCP and IPv6 |
| ISO 15118-20 | April 2022, with Amendment 1 in 2026 | Second-generation network and application layer, including messages for bidirectional power transfer |
The ISO 15118-2 record describes a message set designed to support energy transfer from the charger to the vehicle, and notes that bidirectional use cases need extensions. The ISO 15118-20 record states that the newer part defines messages and sequences for bidirectional power transfer, and lists an amendment covering AC distributed energy resource services, megawatt charging and an improved security concept. Hubject’s charge point operator page notes that communication between vehicle and charger under ISO 15118-20 is protected with TLS 1.3.
How the certificates fit together
Plug and Charge is a public key infrastructure problem. Each party holds certificates that chain back to a trusted root, and a session works only if the charger and the vehicle trust the same chain. In simplified terms:
- A V2G root. A root certificate authority anchors the trust chain. Hubject’s PKI page lists separate roots for ISO 15118-20 and for ISO 15118-2 in Europe, the US and Asia.
- Charger certificates. The charge point operator installs and renews certificates on every charger so that the vehicle can verify it is talking to a genuine station.
- Vehicle and contract certificates. The vehicle maker prepares the car to receive a contract, and the mobility operator issues the contract certificate that represents the driver’s account. Hubject lists support for installing contracts into vehicles for manufacturers and a managed PKI for contract certificates for mobility operators.
- Validation and billing. At plug-in, the charger validates the vehicle’s certificate, matches the contract to the right mobility operator and starts the session.
Each step brings an operational duty: certificates expire, keys must be protected and revocation must reach every charger. The governance questions are similar to those in our piece on signing keys in the vehicle operating model.
Where interoperability breaks down
A car and charger can both support ISO 15118 and still fail to start a Plug and Charge session. The common causes are:
- Different roots of trust. More than one V2G PKI exists. CharIN backs a protocol designed for multi-PKI environments and contributes to certificate trust list governance. It handed operational control of its V2G PKI root to Irdeto in 2024.
- Contract provisioning. The contract certificate has to reach the vehicle, which depends on the vehicle maker, the mobility operator and the PKI operator exchanging data correctly.
- Version mismatch. A vehicle using ISO 15118-20 and a charger supporting only ISO 15118-2, or the reverse, may fall back to other authorisation.
- Back-office gaps. The charger, its management system and the roaming platform must all pass certificate and contract data through.
Hubject reports that it has partnered with Gireve and Irdeto so operators can choose a Plug and Charge ecosystem operator while keeping access to others. For buyers, the lesson is that interoperability is a commercial and operational arrangement as much as a protocol, a point developed in our analysis of charging interoperability beyond the connector.
The regulatory picture for the UK and EU
In the EU, Commission Delegated Regulation (EU) 2025/656, dated 2 April 2025, sets the standards. From 8 January 2026, newly installed or renovated public recharging points must support ISO 15118 Parts 1 to 5. Public points installed or renovated from 1 January 2027 must comply with EN ISO 15118-20:2022, and those offering automatic authentication such as plug-and-charge must also comply with EN ISO 15118-2:2016. Private points face an ISO 15118-20 requirement from the same date.
In Great Britain, the Public Charge Point Regulations 2023 are organised around contactless payment, payment roaming, reliability and open data. Regulation 5 requires contactless payment on new public charge points of 8 kW or above and on existing rapid charge points. The regulations do not set a vehicle-to-charger communication protocol, so Plug and Charge remains a commercial choice in Great Britain. Manufacturers and charger suppliers serving both markets will still meet the EU dates.
Key points for charging and fleet teams
- Plug and Charge depends on certificates that chain to a shared root, not only on ISO 15118 support in the hardware.
- ISO 15118-20 adds bidirectional messages and newer security, while ISO 15118-2 remains common in today’s vehicles.
- Specify which PKIs, ecosystem operators and protocol versions a charger supports, and test them with your vehicles, as set out in our guide to procuring a successful charging session.
- EU rules require ISO 15118-20 on new public points from 1 January 2027, while British rules focus on payment, reliability and open data.
- Drivers using automatic authentication on EU public points must still be offered ad hoc payment.
Sources
- ISO: ISO 15118-2:2014 Network and application protocol requirements
- ISO: ISO 15118-20:2022 2nd generation network layer and application layer requirements
- Hubject: Plug&Charge
- Hubject: Plug&Charge PKI
- Hubject: Plug&Charge for CPOs
- CharIN: Plug & Charge
- EUR-Lex: Regulation (EU) 2023/1804 on alternative fuels infrastructure
- EUR-Lex: Commission Delegated Regulation (EU) 2025/656
- legislation.gov.uk: The Public Charge Point Regulations 2023
- legislation.gov.uk: The Public Charge Point Regulations 2023, regulation 5
Sources checked in November 2026. Rules, rates and schemes can change after publication, so check the linked official pages before acting.