What is Plug & Charge and what do you need to use it?

What is Plug & Charge?

Plug & Charge is the ISO 15118 feature that allows a compatible electric vehicle to identify and authorise a charging contract automatically after the cable is connected. The driver does not need to open an app, tap an RFID card or enter payment details at the charger for that session.

This is more specific than any feature that starts charging when a cable is inserted. Under the EU’s technical description, Plug & Charge uses automatic authentication and authorisation to support contract-based payment between the driver and a mobility service provider.

How does Plug & Charge work?

1. The EV and charging station establish high-level communication through ISO 15118.
2. The vehicle presents a digital contract certificate linked to the driver’s charging contract.
3. The charger and backend validate the certificate chain and check whether the contract is authorised.
4. If the checks succeed, charging starts and the session can be assigned to the correct account for billing.

A public key infrastructure, or PKI, creates the trust framework behind those certificates. CharIN’s Plug & Charge work covers the secure authentication and authorisation ecosystem required around ISO 15118.

What is required to use Plug & Charge?

The simple driver experience depends on the complete chain working:

• A compatible EV: its communication hardware and firmware must support the required ISO 15118 edition and Plug & Charge function.
• A compatible charging station: the EVSE must support the same communication route and have the feature active in firmware.
• A valid charging contract: the driver needs a supported contract with an e-mobility service provider.
• A contract certificate: a valid certificate linked to that contract must be installed in the vehicle.
• A trusted certificate ecosystem: the relevant roots, certificate authorities and revocation processes must be recognised.
• Backend support: the CPO, CPMS, mobility provider and any roaming service must be able to authorise the contract, record the session and handle billing.

Does “ISO 15118 ready” guarantee Plug & Charge?

No. The label may describe fitted communication hardware, planned firmware or only part of the standard. It does not prove that certificates can be installed and validated or that a vehicle, charger and backend have passed end-to-end interoperability testing.

The backend route also matters. OCPP 2.0.1 includes support for ISO 15118 functions, including certificate management and Plug & Charge authorisation. The Open Charge Alliance documents an implementation route with OCPP 1.6, but it requires additional agreed messages. An OCPP version number alone does not confirm a working service.

What changes under AFIR from 2027?

AFIR’s 2027 technical specifications do not force every operator to offer Plug & Charge. However, public AC and DC charging points installed or renovated from 1 January 2027 that do offer automatic authentication and authorisation must comply with both EN ISO 15118-2:2016 and EN ISO 15118-20:2022 for interoperability and security.

What should buyers and operators check?

• Which ISO 15118 editions and optional functions are active, not only fitted?
• Who provides, installs, renews and revokes the contract certificates?
• Which EV, charger and CPMS combinations have been tested?
• What happens if a certificate is expired, revoked or unavailable?
• Which RFID, app or ad hoc payment method remains available as a fallback?

How amina C2 and M2 fit

amina C2 and amina M2 contain hardware prepared for ISO 15118-20 and Plug & Charge. They use local OCPP 1.6J and are hardware-ready for OCPP 2.0.1, allowing operators to work with their chosen specialist CPMS and service partners.

Hardware readiness is not an active Plug & Charge service. Deployment still needs compatible firmware, vehicle support, certificates, charging contracts, backend integration and end-to-end testing.