EVerest and AFIR

// how the open-source charging stack meets EU 2023/1804

The Alternative Fuels Infrastructure Regulation (AFIR) sets EU-wide rules for public charging: how drivers pay, what price they see, how chargers talk to vehicles and backends, and which data operators must publish. This page maps each obligation that lands on charger software to what EVerest provides.

EVerest main covers every charger-side AFIR obligation today, including the 1 January 2027 ISO 15118-20 mandate: one stack runs DIN 70121, ISO 15118-2 and ISO 15118-20 with Plug & Charge on both, next to OCPP connectivity, smart charging, California Pricing, card and QR payment, and signed metering. The one item it leaves to the product is the driver-facing HMI.

EVerest main branch, upcoming 2026.10 release · Legal status as of October 2026 · Charger-side obligations only

Scorecard

12 AFIR obligations that fall on charger software, rated against what EVerest ships today.

11
Ready
Implemented in main
1
Integrator
Stack provides the hooks, product HMI decides

Deadlines

Everything up to April 2026 already applies. The next hard date is 1 January 2027.

  1. 13 Apr 2024Ad hoc payment, price display, smart-charging capability for new pointsArt. 5(1), 5(4), 5(8)
  2. 14 Oct 2024All public points digitally connectedArt. 5(7)
  3. 14 Apr 2025Static + dynamic data via national access points, 1 min latencyArt. 20, IR 2025/655
  4. 8 Jan 2026ISO 15118-1 to -5 on new public AC and DCDR 2025/656, 2.1.1
  5. 14 Apr 2026DATEX II mandatory for the data feed (backend)IR 2025/655 Art. 1
  6. 31 Dec 2026Commission AFIR review due; no proposal published yetArt. 24(2)

Obligation by obligation

AFIR names no backend protocol: Annex II 2.2 to 2.4 are still empty headings. OCPP is the practical route, not a legal one.

ObligationStatusEVerest today
Vehicle communication
ISO 15118-1 to -5 (incl. ISO 15118-2)DR 2025/656 · public AC+DC · from 8 Jan 2026 Ready The libiso15118 stack in the Evse15118D20 module runs ISO 15118-2 and DIN 70121 alongside ISO 15118-20.
EN ISO 15118-20:2022DR 2025/656 · public and private Mode 3/4 · from 1 Jan 2027 Ready The Evse15118D20 module covers:
  • Energy services AC, DC, AC_BPT, DC_BPT, MCS, MCS_BPT
  • Grid codes AC DER per IEC and SAE (Annex M), with grid_support directives relayed into running sessions
  • Control modes dynamic (default) and scheduled (supported_scheduled_mode), plus mobility needs from the SECC
  • Identification EIM and PnC with contract certificate installation in Authorization
  • Security TLS 1.3 mTLS as [V2G20-2677] requires, multiple V2G chains and leaf rotation
  • Session cable check, pre-charge, welding detection, pause and resume, contactor timeouts, data-link-loss teardown
Plug & Charge on both ISO 15118-2 and ISO 15118-20DR 2025/656 2.1.2 · where P&C is offered Ready One stack serves DIN 70121, ISO 15118-2 and ISO 15118-20 in a single SupportedAppProtocol offer, with PnC and certificate installation on both generations . The right certificate is chosen per connection: TLS 1.2 for ISO 15118-2, TLS 1.3 for ISO 15118-20. Backend provisioning goes through OCPP Get15118EVCertificate (2.x) and the 1.6 PnC whitepaper.
Paying and pricing
Card reader / contactlessArt. 5(1)(a-b) · new ≥50 kW · retrofit 1 Jan 2027 Ready RsPaymentTerminal (Rust) with pre-authorization and capture against session_cost; bank cards handled in Auth.
QR / online ad hoc paymentArt. 5(1)(c) · public <50 kW Ready AFIR asks for a device "using an internet connection" for secure payment, "such as" one generating a QR code. With OCPP 1.6 or 2.0.1 the payment happens in the backend and the charger only has to start the session:
  1. Show a QR code with the EVSE ID: a static sticker, or a dynamic code on the display via OCPP 2.0.1 SetDisplayMessage (O-block) and the qr_code field of display_message
  2. Pay on the CSMS or PSP web page, which also shows the ad hoc price (recital 84)
  3. Start with RemoteStartTransaction (1.6 Core) or RequestStartTransaction (2.0.1 F-block), both implemented
  4. Settle on StopTransaction / TransactionEvent with the metered kWh
OCPP 2.1 adds native QR and web-payment messages (NotifyWebPaymentStarted), which are not needed for compliance.
Ad hoc price shown before sessionArt. 5(4) · per kWh at ≥50 kW Ready OCPP 1.6 and 2.0.1 California Pricing deliver the per-kWh default price (DefaultPrice, DefaultPriceText per language), tariff messages and running cost. EVerest publishes them on session_cost and display_message for the integrator's HMI, which is product-specific by design.
Opt-out of automatic authenticationArt. 5(2) · whenever P&C / Autocharge is offered Integrator EIM and contract auth coexist in the stack, so a session can fall back to RFID, app or card. Offering that choice to the driver is the integrator's HMI job.
kWh billing on legal-for-trade metersArt. 5(4) + national law (Eichrecht, MID) Ready powermeter start/stop transaction with OCMF; drivers for LEM, Isabellenhütte, DZG, AST, Carlo Gavazzi, Iskra; signed values reach OCPP 1.6 and 2.x. public-key display for the driver is part of the integrator's HMI.
Grid and backend
Digitally connectedArt. 5(7), def. 2(17) · all public · since 14 Oct 2024 Ready OCPP 1.6 complete, 2.0.1 OCA-certified, 2.1 in progress via OCPPmulti. Remote start/stop, monitoring, metering, security profiles 1 to 3.
Smart charging capableArt. 5(8), def. 2(65) · new or renovated Ready OCPP 1.6 Smart Charging, 2.0.1 K-block, 2.1 dynamic profiles; EnergyManager / EnergyNode external limits; EEBUS LPC.
Dynamic data within 1 minuteArt. 20, IR 2025/655, DR 2025/671 Ready StatusNotification, availability and fault mapping feed the CSMS, which owns the NAP / DATEX II feed. OCPI is out of the charger's scope.
Heavy-duty / MCSArts. 3-4 pool targets · no MCS spec in AFIR yet Ready McsDataLink (ISO 15118-10 SPE data link) and MCS / MCS_BPT energy services in the ISO 15118-20 stack, plus the cMCS connector type. Heavy-duty CCS goes through the same ISO 15118-2 / ISO 15118-20 path as light-duty.

Beyond compliance

Not required by AFIR today. Areas that would strengthen EVerest as the regulation and national rules evolve.

01

OCPP 2.1 tariffs and payment

SetDefaultTariff, GetTariffs, ChangeTransactionTariff and cost details return NotImplemented, and so do settlement, incremental authorization and NotifyWebPaymentStarted. All of them become relevant if the review mandates OCPP 2.1 (prEN IEC 63584).

02

Price to the EV over ISO 15118

Send the ad hoc tariff to the car over ISO 15118-20, so the vehicle can show the price and optimize cost.

03

Meter public key on OCPP 2.x

public_key_ocmf reaches OCPP 1.6 as MeterPublicKey, but PublicKeyWithSignedMeterValue is never consumed on 2.x, which Eichrecht transparency software relies on.

04

OCPP 2.0.1 K11-K17

External charging limits, local smart charging, and ISO 15118 load leveling and renegotiation are open, which limits grid-driven smart charging beyond the CSMS.

05

Periodic event streams

OCPP 2.1 Open, Close and AdjustPeriodicEventStream are NotImplemented. They are a cheaper way to give the CSMS the status data it needs for the 1-minute NAP rule.

Watchlist

Open items that could move the dates or add obligations.

  • ISO 15118-20 postponement. CharIN (3 Aug 2026) asks to move the ISO 15118-20 mandate to 1 Jan 2028 because no conformity scheme exists. Not adopted; 2027 still stands.
  • AFIR review. Due 31 Dec 2026; it will reassess payment means and price components. No COM proposal published yet.
  • Backend protocol. CharIN wants OCPP 2.1 (prEN IEC 63584) mandated under Annex II 2.2. That would turn the open 2.1 tariff and payment use cases into legal gaps.
  • MCS delegated act. Requested for 2026; would make MCS a hard requirement, which the stack already covers.
  • Accessibility. Annex II 1.18 is still a heading; CEN is drafting it. The European Accessibility Act may already apply to the HMI.
Sources: Regulation (EU) 2023/1804 (AFIR); Delegated Reg. (EU) 2025/656 (standards), 2025/671 (data types), 2025/645 (APIs); Implementing Reg. (EU) 2025/655 (data format); CharIN AFIR position paper v2 (3 Aug 2026) and review response (22 Apr 2026). EVerest evidence from its source code, module manifests and the libocpp implementation status, October 2026.
  • Ratings reflect an engineering review of the EVerest source code. They are not a conformity assessment or legal advice; compliance of a charger depends on the full product.
  • Obligations that sit purely on the CPO backend (NAP feed, DATEX II, e-MSP pricing, roaming) are excluded.

Get in touch.

Let’s make you ready for the future of EV charging.

Contact us