What is Plug & Charge?

Plug & Charge is an ISO 15118 function that lets a compatible electric vehicle identify and authorise its charging contract after the cable is connected. For that session, the driver does not need an app, RFID card or payment details entered at the charger.

 

This is more specific than any setting that starts charging when a cable is inserted. Under the EU’s technical description, Plug & Charge uses automatic authentication and authorisation for contract-based payment between driver and 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 contract.
  4. If the checks pass, charging starts and the session is assigned to the correct account.

A public key infrastructure, or PKI, provides trust between those certificates. CharIN’s Plug & Charge work covers the secure authentication and authorisation system around ISO 15118.

What is required to use Plug & Charge?

The simple driver experience depends on the whole chain:

  • A compatible EV: communication hardware and firmware must support the required ISO 15118 edition and function.
  • A compatible charging station: the EVSE must support the same route and have Plug & Charge 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 system: roots, certificate authorities and revocation processes must be recognised.
  • Backend support: the CPO, CPMS, mobility provider and any roaming service must authorise the contract, record the session and handle billing.

ISO 15118: the standard behind Plug & Charge

amina wall-mounted EV charger installed on a concrete wall in a residential parking space, charging an electric car in a home setting.

2026 – 17.01

– Bidirectional Charging, Technology

ISO 15118 Explained: Plug & Charge, Smart Charging and V2G

Read more

Does “ISO 15118 ready” guarantee Plug & Charge?

No. The label may refer to fitted hardware, planned firmware or one part of the standard. It does not prove that certificates can be installed and checked, or that the vehicle, charger and backend passed end-to-end testing.

 

The backend route matters too. OCPP 2.0.1 supports ISO 15118 certificate management and Plug & Charge authorisation. The Open Charge Alliance documents a route using OCPP 1.6 with extra agreed messages. The OCPP version number alone proves no working service.

What changes under AFIR from 2027?

AFIR’s 2027 technical specifications do not require every operator to offer Plug & Charge. Public AC and DC 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.

What should buyers and operators check?

  • Which ISO 15118 editions and optional functions are active, not merely fitted?
  • Who provides, installs, renews and revokes contract certificates?
  • Which EV, charger and CPMS combinations were tested?
  • What happens when a certificate is expired, revoked or unavailable?
  • Which RFID, app or ad hoc payment route remains as 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, leaving operators free to choose specialist CPMS and service partners.

 

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