What role does OCPP play in AFIR?

As the European Union pushes forward with its climate goals, the Alternative Fuels Infrastructure Regulation (AFIR) is reshaping the continent’s EV charging landscape. While much attention has been paid to the rollout of physical infrastructure, there’s a less visible but equally vital component to this regulation: interoperability.

At the center of this digital interoperability is the Open Charge Point Protocol (OCPP), a widely adopted and open standard that facilitates seamless communication between EV chargers and their back-end management systems. This article explores the importance OCPP has towards securing the goals behind AFIR, including user-friendliness, transparency, uniformity and interoperability.

What is OCPP?

OCPP (Open Charge Point Protocol) is an open-source communication protocol developed by the Open Charge Alliance. It enables two-way communication between an EV charge station (hardware) and a central system (backend software) that manages it.

Among other features, OCPP's core protocol provides:

• Remote monitoring and control of charging stations
  
  
• Real-time session management
  
  
• Firmware updates
  
  
• Fault and diagnostics reporting
  
  
• Metering and billing data exchange

The current industry standard is OCPP 1.6, though OCPP 2.0.1 is gaining traction for its enhanced features including support for ISO 15118 (plug & charge) and improved security.

AFIR’s Digital Ambition: Why OCPP Matters

AFIR sets mandatory targets for EV charging infrastructure across Europe, but it also requires this infrastructure to be smart, connected, uniform and open. In particular, AFIR mandates that:

• Charging point data (availability, status, pricing) be made accessible via APIs
  
  
• Charging stations support remote operation
  
  
• Roaming and ad hoc payment be facilitated
  
  
• Interoperability and vendor neutrality be guaranteed
  

The API requirements under AFIR are not just a regulatory box to tick. They are a fundamental building block for a truly interoperable, user-friendly, and transparent EV charging ecosystem across Europe.

As the transport sector digitizes alongside decarbonization, stakeholders who embrace open APIs and interoperability standards will be best positioned to lead in the new era of sustainable mobility.

Why does AFIR insist on APIs?

To ensure real-time access to infrastructure data, seamless cross-border travel, and consumer transparency, AFIR mandates that data about charging infrastructure be made publicly accessible and machine-readable through open interfaces, such as APIs. 

These APIs are designed to support navigation services and routing tools, enable roaming between different e-mobility service providers (EMSPs) and charge point operators (CPOs), facilitate transparent payment and pricing comparisons, and provide real-time updates on the availability and operational status of charging stations to a national access point.

Jaap Burger, Senior Advisor at the Regulatory Assistance Project, reminded us that these API requirements kicked in from April 2025 onwards. “From that date, static and dynamic data on charging (and refuelling) points will have to be made available free of charge, as already set out in the AFIR.” Burger told eDRV, adding that “many Member States have also set up the required National Access Points for this data.”

AFIR’s Core API Requirements

In Article 5 of the Alternative Fuels Infrastructure Regulation (AFIR), the European Union outlines three essential categories of data that must be made accessible via APIs. These requirements are designed to ensure transparency, interoperability, and real-time information flow across the EV charging ecosystem.

1. Static Data

This category includes information that does not change frequently and forms the foundational dataset for users and service providers. Static data includes the location of charging stations, the types of plugs or connectors available, power ratings of the chargers, and the payment methods accepted at each site. Making this data accessible ensures that drivers and service platforms can plan routes, identify compatible infrastructure, and understand what to expect at a given charging point.

2. Dynamic Data

Dynamic data refers to real-time or near-real-time information that reflects the current status of the infrastructure. This includes the availability of charging stations (such as whether they are in use, out of order, or available) along with waiting times or queue information, and up-to-date pricing. Providing dynamic data through APIs is essential for accurate navigation, user decision-making, and for managing demand efficiently across networks.

3. Transaction Data (for specific services)

For services that support ad hoc payment methods like QR codes or contactless cards, the regulation requires APIs to support secure, transparent transactions. This includes enabling the secure initiation of a charging session, real-time cost calculation as the session progresses, and the issuance of a digital receipt or invoice. These functionalities are critical for ensuring ease of use and building consumer trust in public charging services.

Together, these three API data categories form the digital backbone of AFIR’s push toward a seamless and user-friendly EV charging experience across Europe.

‍

5 Ways OCPP Supports AFIR Compliance

OCPP is not explicitly required by name in AFIR, but it is fundamental for fulfilling several of AFIR’s digital and operational obligations given its de facto status for charger-server communications. It’s also worth noting that OCPP is now a standard accepted under both the IEC (International Electrotechnical Comission) and CENELEC (European Committee for Electrotechnical Standardization), further bolstering its backing in the EU.

Here are 5 ways that OCPP protocol implementation bolsters AFIR compliance. 

1. Enabling Remote Management

AFIR requires that charge points be remotely operable for updates, diagnostics, and management. OCPP allows operators to start or stop sessions remotely, push firmware updates and handle error codes and maintenance remotely.

2. Delivering Real-Time Data for APIs

AFIR mandates real-time status and pricing updates via publicly accessible APIs. OCPP enables real-time reporting of availability (plugged, charging, faulted, etc.), and metering or pricing data required for transparency. Without OCPP or a similar protocol, achieving this level of dynamic data exchange would be highly complex.

3. Enabling Ad Hoc Access and Roaming

To support user-friendly, ad hoc access, AFIR calls for charging without subscription barriers. While the API layer (often OCPI) handles roaming, OCPP ensures the hardware executes the session properly, no matter which EMSP initiates it. OCPP enables external authentication methods (QR code or RFID) as well as roaming session initiation through central systems. A full and detailed description of how OCPP helps fulfill AFIR requirements, including ad hoc access, can be found in the OCA whitepaper entitled “AFIR and OCPP”.

4. Ensuring Hardware Agnostic Infrastructure

AFIR emphasizes the need for non-discriminatory, interoperable solutions, and OCPP plays a critical role in achieving this by enabling charge stations and central systems from different vendors to communicate seamlessly. 

This interoperability empowers charge point operators (CPOs) with the flexibility to mix and match hardware brands, switch backend software providers, and upgrade their systems without being locked into a single vendor's ecosystem.

5. Supporting Future-Proof Features

As AFIR lays the groundwork for next-gen services like grid integration, and plug & charge, OCPP 2.0.1 plays a crucial role. Its support for ISO 15118 and enhanced security profiles means it will remain relevant as AFIR evolves and expands.

AFIR also requires that public chargers support smart charging, meaning they can adjust how and when electricity is delivered. For example, this can be utilized to avoid overloading the grid during peak times. Fortunately, OCPP has supported smart charging since version 1.6.

Best Practices for CPOs under AFIR

To meet the technical and operational demands of the EU's Alternative Fuels Infrastructure Regulation (AFIR), CPOs should adopt a strategic and forward-looking approach to protocol implementation and system integration. At a minimum, adopting OCPP 1.6 using JSON over WebSocket ensures compliance with AFIR’s core requirements for real-time data exchange and remote control of charging stations. However, for those aiming to support advanced features such as Plug & Charge, dynamic pricing, or intelligent load management, planning for an upgrade to OCPP 2.0.1 is highly recommended due to its more comprehensive feature set and native support for these capabilities.

Equally important is rigorous interoperability testing, particularly when operating in a multi-vendor environment. Ensuring that back-end systems and e-mobility service providers (EMSPs) can reliably interface with different brands of charging hardware avoids service fragmentation and enhances user experience.

Finally, to fully comply with AFIR’s mandates for open and transparent data exchange, CPOs should consider pairing OCPP with the OCPI protocol. While OCPP manages communication between chargers and central systems, OCPI enables efficient data sharing with EMSPs, supporting functionalities such as roaming, pricing transparency, and real-time availability updates.

By following these best practices, CPOs can build future-proof infrastructure that aligns with AFIR goals while ensuring operational flexibility and customer satisfaction.

OCPP Complements AFIR in EU’s Electrification 

While AFIR focuses on infrastructure deployment, its long-term success depends on digital infrastructure, the software and protocols that make EV charging convenient, reliable, and open. OCPP is the silent workhorse enabling this transformation and complements the charging infrastructure goals that AFIR sets out to achieve.

For CPOs, aligning with OCPP is not just a smart technical decision; it’s an essential step toward regulatory compliance, operational scalability, and customer satisfaction in the AFIR era.

To find out more about how OCPP and open APIs can help you achieve your interoperability goals, check out eDRV’s hardware-agnostic Charge Management Platform.

‍