AFIR readiness

What a capture shows of the ISO 15118 capabilities the EU Alternative Fuels Infrastructure Regulation names for chargers, with the dates as reported and their sources. Evidence from captures, not a conformity assessment.

What it is for

Open a capture of your charger with a car, then Testing, AFIR. The tab lists the ISO 15118 items of AFIR with the date each is reported to apply from, and says for each what this capture shows: evidence the charger supports it, no evidence in this capture, or the capture contradicts it. Below it, the capabilities of the session one by one, each with the message that shows it; select a message to open it.

This is evidence from captures, not a conformity assessment, a certification or legal advice. A capability one capture does not show is no evidence either way: the car may not have asked for it, or the charger may have it switched off for this connection.

The items and their dates

Standard partFromScope, as reported
EN ISO 15118-2:20168 January 2026Publicly accessible recharging points installed or renovated from this date
EN ISO 15118-20:20221 January 2027Publicly accessible recharging points installed or renovated from this date, alongside ISO 15118-2

The dates and scopes are as the vendor guides of MENNEKES, Vector and AMPECO and the CharIN position paper of 28 April 2026 report them; the sources are listed below. They were not checked against the text of Delegated Regulation (EU) 2025/656, so the tab and the report flag them VERIFY. The sources differ on scope (summaries of the CharIN paper also name private charging points), and none read for this tool says which features, such as Plug and Charge, smart charging or TLS, a charging point has to offer. Check the regulation before relying on a date.

What the capture is read for

  • The application protocols: which standards the car offered in supportedAppProtocolReq, at which priority, and which one the charger accepted. A charger that answers Failed_NoNegotiation, or takes a protocol the car ranked lower, contradicts support for the one it passed over.
  • TLS: whether the charger answered SDP with TLS, the TLS version and cipher suite of the session, and a charger that ran ISO 15118-20 without the TLS 1.3 it requires (check HS-03).
  • Plug and Charge: the payment options the charger offered (Contract in ISO 15118-2, PnC in ISO 15118-20), the one the car took, and any contract certificate chain (check PK-03).
  • Smart charging: the schedules the charger handed the car, and a schedule renegotiated during the energy transfer. Some standards make a schedule part of every session, so it shows the charger can hand one over, not that a backend steered it.
  • Bidirectional power transfer: the BPT services the charger offered in ISO 15118-20 and the one the car took.
  • The outcome of each session, and the findings of the checks on the handshake, SDP, TLS and certificates.

A capture over TLS needs its key log for everything after the TLS handshake; without it the tab shows the link and says the messages could not be read. See Capturing a charging session for recording a session with its key log.

The report

Download the AFIR report saves one HTML file, with its styles inside and no script: the items with their dates and sources, the capabilities over the whole capture, every session with its evidence, and the disclaimer. It is made in your browser; nothing is sent anywhere.

Sources