What is OCPI?

OCPI stands for Open Charge Point Interface. It is an open protocol for exchanging EV roaming information between charge point operators (CPOs) and e-mobility service providers (eMSPs). It lets a driver charge on another operator’s network, and it shares locations, tariffs, sessions and charge detail records between the two back offices.

A CPO operates charging infrastructure. An eMSP provides the driver’s account, app, RFID card or other service. OCPI lets a driver with one provider find and use a charger run by another, subject to commercial agreements and access rules.

The official OCPI repository, maintained by the EV Roaming Foundation, lists OCPI 2.3.0 as the latest official release. Both parties still need to agree the same version and modules.

OCPI versions

Version Status What it means
OCPI 2.1.1 No longer supported The EV Roaming Foundation no longer supports this version.
OCPI 2.2.1 Supported (2021) The EV Roaming Foundation offers migration support from 2.2.1 to 2.3.0.
OCPI 2.3.0 Current version Compliant with the EU national access point (NAP) rules in AFIR. Adds vehicle types for locations and optional payment terminal and booking modules. On its way to becoming a CENELEC technical specification.
OCPI 3.0 Draft Target release in mid 2027, planned as a CENELEC standard. The aim is that 3.0 modules can work with 2.3.0.

How EV charging roaming works

A typical flow has several stages:

  1. The CPO shares locations, connectors, availability and tariffs.
  2. The eMSP shows eligible chargers and prices to its customers.
  3. The driver presents a token or sends a start command through the eMSP.
  4. The CPO backend checks the authorisation and tells the charger to start.
  5. Session updates pass from CPO to eMSP while charging continues.
  6. The CPO sends a charge detail record with the agreed energy, time and price fields.
  7. The eMSP bills the driver, and the businesses settle under their contract.

The connection may be direct or pass through a roaming hub. A hub reduces bilateral technical connections. It does not remove commercial, support or data-governance work.

What information OCPI exchanges

OCPI is split into modules. Common modules cover credentials, locations, tariffs, tokens, sessions, charge detail records and remote commands. Current session updates remain separate from the final billing and reconciliation record.

Not every implementation exposes every optional function. Test data freshness, identifiers, tariffs, time zones, currency, taxes, command responses and corrections with each partner.

OCPI versus OCPP

OCPP and OCPI are complementary. Each protocol connects a different pair of systems:

Protocol Connects Typical user Example messages
OCPP A charging station and its CPMS or CSMS Charge point operator Boot notification, status, start and stop of a transaction, meter values
OCPI The business platforms of CPOs, eMSPs and roaming hubs CPO, eMSP, roaming hub Locations, tariffs, tokens, sessions, charge detail records, start-session commands
ISO 15118 The electric vehicle and the charging equipment Car maker, charger maker Charging parameters, Plug & Charge authentication

A roaming start request may move from eMSP to CPO backend over OCPI. The CPO’s CPMS then sends the charger command over OCPP. That boundary helps locate a failure in the driver account, roaming link, backend or charger.

What OCPI does not guarantee

OCPI standardises data exchange. It does not guarantee that every driver can use every charger. Coverage depends on partner agreements, accepted tokens, published prices and live systems. It does not set the retail price, process card payments by itself or settle money between companies.

An eMSP price may differ from the CPO’s direct price because the customer relationship and commercial terms differ. The driver still needs clear information before charging starts.

OCPI and AFIR

Under the EU Alternative Fuels Infrastructure Regulation (AFIR, Regulation (EU) 2023/1804), operators of publicly accessible charge points must make static and dynamic data, such as location, availability and price, available free of charge through national access points (NAPs). The EV Roaming Foundation states that OCPI 2.3.0 is compliant with these EU NAP rules. OCPI itself is not a legal requirement: it is one way to share the data.

Where amina fits

amina charging stations connect to the operator’s chosen CSMS over OCPP. The amina CSMS integration guide shows that direct charger-to-CSMS route. OCPI, where needed, sits beyond the charger between the CPMS and other roaming or service platforms.

The charger remains focused on charging, local controls and OCPP communication. Specialist platforms handle accounts, roaming, tariffs and settlement.

OCPI questions

What does OCPP stand for?

OCPP stands for Open Charge Point Protocol. It connects a charging station to its management software, while OCPI connects the business platforms behind it. Our guide to OCPP explains how it works.

What is the latest version of OCPI?

OCPI 2.3.0 is the current version. OCPI 3.0 is a draft with a target release in mid 2027.

Do I need OCPI for a home charger?

No. OCPI is for roaming between operators and service providers on public or shared charging networks. A private home charger does not use it.

Sources

  • EV Roaming Foundation, OCPI versions and status (read 12 November 2026): evroaming.org
  • OCPI repository and releases: github.com/ocpi
  • AFIR, Regulation (EU) 2023/1804 on the deployment of alternative fuels infrastructure: EUR-Lex