Standards & Knowledge / AFIR for EV charging
AFIR: Charging Access, Payment and Technical Requirements
The Alternative Fuels Infrastructure Regulation (AFIR) addresses how public charging infrastructure is provided and used. Start with the driver’s questions: Can I pay, understand the price and charge? Then identify the technical checks relevant to your project.
Start with the legal boundary
AFIR is a system-level regulation, not a charging protocol.
AFIR regulates alternative-fuels infrastructure and the user’s access to it. Some obligations become technical EVSE (electric vehicle supply equipment, or charging station) requirements. Others belong to the operator, payment environment, data platform, infrastructure network or Member State.
The first verification decision is therefore not “Which tester do we need?”. It is “Which obligation applies, who owns it, and what evidence can prove it?”.
One regulation. Different technical owners.
Separate the obligation before selecting the verification method.
Each AFIR topic has a different responsible system and evidence type. Combining them in one undifferentiated checklist hides gaps instead of closing them.
Deployment and power targets
Coverage, distance, aggregate power and infrastructure availability are planned at Member State, network and operator level.
- Primary owner
- Member State, infrastructure owner, CPO
- Typical evidence
- Location, network capacity, asset register, rollout record
Ad hoc access and payment
Public charging must support the applicable ad hoc route without forcing a user into a contract beyond the charging transaction.
- Primary owner
- Payment terminal, payment provider, CPO backend
- Typical evidence
- User journey, transaction result, terminal and backend records
Price transparency and user choice
Price components and the selected charging route must be presented according to power class and deployment context.
- Primary owner
- CPO tariff system, display, application and payment path
- Typical evidence
- Displayed price, tariff calculation, session invoice, screenshots
Digital connection and smart recharging
Public points must meet the applicable digital-connectivity and smart-recharging capability dates.
- Primary owner
- EVSE controller, communication backend, energy-management system
- Typical evidence
- Remote communication, control response, update and operating records
Static and dynamic data plus API
Defined data must be available without charge through a technically compliant API and the national access-point chain.
- Primary owner
- CPO data platform, API provider, national access point
- Typical evidence
- Data model, API response, timestamps, completeness and quality logs
Technical interoperability and field operation
The charging interface, communication path and deployed installation must remain usable with the intended vehicle population.
- Primary owner
- EVSE manufacturer, integrator, operator and service team
- Typical evidence
- Conformance, robustness, interoperability, commissioning and service reports
Transition dates are part of the requirement
Use the deployment date, power class and location before applying a rule.
The timeline below is an engineering orientation. The current consolidated regulation, applicable delegated and implementing acts, Commission guidance and national enforcement remain authoritative.
AFIR applies
Regulation (EU) 2023/1804 becomes applicable. Rules for points deployed from this date begin to take effect.
Digital connection
All publicly accessible points must be digitally connected. Points built after 13 April 2024, or renovated after this date, must meet the applicable smart-recharging capability rule.
Data and fixed-cable milestones
Static and dynamic infrastructure data become available at no cost. Public DC points reach the fixed-cable milestone.
Updated technical specifications apply
Delegated Regulation (EU) 2025/656 applies to the relevant newly deployed or renovated infrastructure and technical routes.
DATEX II data model milestone
The relevant data exchange follows the implementation timetable in Regulation (EU) 2025/655.
Common European access point target
The Commission is to establish the common European access point for alternative-fuels infrastructure data.
Payment and ISO 15118 transition
Further rules apply to certain existing high-power public points and to newly deployed or renovated communication paths.
Technical acts make the regulation executable
Track the exact standard, edition and transition date.
A standards-family name is not an acceptance criterion. The engineering record must identify the legal reference, edition, DUT (device under test) role, deployment status and released test implementation.
Type 2 for AC. Combo 2 for DC.
The delegated technical specifications use EN IEC 62196-2:2022 Type 2 for relevant AC points and EN IEC 62196-3:2022 Combo 2 for relevant DC points that are newly deployed or renovated.
Evidence focus- Connector and inlet configuration
- Deployment or renovation date
- Vehicle-category and power context
EN ISO 15118 parts 1 to 5.
Relevant newly deployed or renovated public AC and DC points must comply at least with the listed EN ISO 15118 communication parts in the delegated regulation.
Evidence focus- Exact part and edition
- EVSE or vehicle-side role
- Protocol, physical layer and sequence result
EN ISO 15118-20 enters the route.
Relevant newly deployed or renovated public AC and DC points move to the EN ISO 15118-20:2022 baseline. Where automatic authentication such as Plug & Charge is offered, both the specified -2 and -20 routes apply. The date changes the protocol evidence required; it does not make a capable EVSE tester obsolete.
Evidence focus- Service and authentication configuration
- Backward-compatibility route
- User choice remains available
- Released protocol behaviour after the transition
Availability, quality and machine-readable access.
Delegated Regulation (EU) 2025/645 defines common API requirements. Implementing Regulation (EU) 2025/655 requires static data to be updated after a change and no later than 24 hours, dynamic data no later than one minute, and the relevant DATEX II data model from 14 April 2026.
Evidence focus- Static and dynamic data completeness
- Timestamp and update latency
- API robustness, security and validation
A compliant communication session can prove one technical requirement. It does not prove payment, tariff transparency, public-data publication, infrastructure deployment or the final legal decision.
One regulation. Three evidence lanes.
Keep technical, operator and legal evidence connected without mixing ownership.
The lanes meet in one controlled compliance file. They do not collapse into one device test.
EVSE technical function
Manufacturer, validation and service
- Connector and cable
- Low-level signal states
- High-level communication
- Power and safety response
- Interoperability and faults
- Trace and test report
Operator and backend
CPO, payment and data platforms
- Ad hoc payment route
- Price and user choice
- Digital connectivity
- Smart recharging control
- Static and dynamic data
- API and operating record
Legal and operational
Accountable compliance decision
- Public-access classification
- Deployment and location
- Power class and dates
- Actor responsibility
- National enforcement
- Approved release decision
Controlled AFIR evidence file
Requirement register · technical reports · backend evidence · accountable decision
Charging interface evidence
Connector, low-level signal, high-level communication, power behaviour, safety response, interoperability and field function.
User and data evidence
Payment route, tariff, digital connectivity, smart-control behaviour, identifiers, availability data, API and operational monitoring.
Applicability and release evidence
Public-access classification, deployment context, actor responsibility, national enforcement, approved assessment and final decision.
Technical evidence with clear boundaries
Use comemso where the charging interface owns the decision.
comemso systems can prove defined parts of the technical charging path. The released hardware, software, licence, test library and project configuration determine the exact scope.
Evidence pack
Make every result traceable to the obligation it supports.
A technically correct test becomes weak compliance evidence when the legal clause, scope, owner, edition or acceptance criterion is missing.
- 1
Legal source
Regulation article, annex, delegated act, implementing act and current consolidated version.
- 2
Applicability
Public accessibility, location, power class, deployment or renovation date and actor.
- 3
System boundary
EVSE, connector, payment, backend, API, operator process or infrastructure network.
- 4
Standard and edition
Exact part, publication, profile, DUT role and released implementation.
- 5
Method and acceptance
Configuration, counterpart, operating state, stimulus, limit, expected result and verdict rule.
- 6
Measured evidence
Trace, screenshot, API response, transaction, field record, calibration status and report.
- 7
Release decision
Open gaps, non-EVSE evidence, accountable reviewer, date and approved scope.
On smaller screens, scroll the table horizontally to see every column.
| Requirement area | Technical owner | Typical evidence | comemso role |
|---|---|---|---|
| Connector and charging communication | EVSE manufacturer, EVSE controller | Interface configuration, protocol and signal trace, conformance report | Direct technical test path where supported |
| Charging function and safety response | EVSE, installation, service organisation | Commissioning, fault, safety and field report | Laboratory and field test path where configured |
| Payment and price transparency | Payment provider, tariff backend, CPO | User journey, transaction, display and invoice | Not a complete payment or tariff certification route |
| Static and dynamic data API | CPO data platform, API provider, NAP chain | API schema, response, timestamps, quality and publication record | Outside core charging-interface test scope |
| Operational availability | CPO, monitoring and maintenance organisation | Status log, incident, repair, re-test and availability record | Supports field diagnosis and technical re-verification |
| Overall AFIR conformity | Accountable legal and compliance organisation | Complete requirement register and approved release decision | No single comemso test equals full AFIR conformity |
Authoritative starting points
Use the current legal text before freezing the test plan.
These links lead to the official EU sources used for this engineering map. Later amendments, corrigenda, Commission guidance and national enforcement can change the applicable interpretation.
Regulation (EU) 2023/1804
Current consolidated AFIR text available on EUR-Lex.
Open official source Commission guidanceAFIR questions and answers
Practical Commission explanations for payment, pricing and implementation questions.
Open official source Technical specificationsDelegated Regulation (EU) 2025/656
Updated standards for relevant recharging and vehicle-to-grid communication routes.
Open official source Common APIDelegated Regulation (EU) 2025/645
Technical requirements for the common application programme interface.
Open official source Data implementationImplementing Regulation (EU) 2025/655
Data format, frequency, quality and accessibility procedures.
Open official sourceThe current consolidated legal text, applicable standards, competent authorities and qualified legal or compliance assessment control the final decision.
Frequently asked questions
AFIR verification FAQ
Use these answers to define the boundary. Use the official legal sources for the final interpretation.
Is AFIR a product test standard?
No. AFIR is an EU regulation for alternative-fuels infrastructure. It combines deployment, user access, payment, pricing, data, interoperability and operational obligations. Product tests can prove defined technical functions, but they cannot by themselves deliver a complete AFIR compliance decision.
Does passing an ISO 15118 test prove AFIR compliance?
No. ISO 15118 testing can provide evidence for a defined communication function and edition. AFIR also covers connector requirements, payment, price display, digital connectivity, data availability, operational processes and infrastructure obligations.
Which recharging points are in scope?
The central AFIR obligations discussed here concern publicly accessible recharging points as defined by the regulation. Private, restricted-access or workplace installations can have a different legal context. Classification must be established before the test plan is written.
What changes at 50 kW?
AFIR uses the 50 kW threshold in the ad hoc payment and pricing rules. The exact deployment date, location and transition rule matter. The current consolidated regulation and Commission guidance must be checked for the specific installation.
Continue from technical context
Turn the information into the next engineering decision.
Continue to the relevant application, current product scope or responsible comemso team.