OCPI 2.2.1 Integration for EV Charging Networks
Roam with other networks, peer to peer or through a hub.
YoCharge builds OCPI into the platform that already runs your chargers. Our OCPI 2.2.1 software lets charge point operators share their chargers with eMSPs and driver apps, and lets eMSPs give their drivers other networks. It’s live with operators in 25+ countries.
- OCPI 2.2.1 + earlier versions
- CPO and eMSP roles
- Peer to peer or via a hub
- Live in 3–7 business days
countries
CPO partners
charger brands
charging sessions
What is OCPI?
OCPI (Open Charge Point Interface) is the open protocol charging networks use to talk to each other. A charge point operator (CPO) uses it to share its chargers, prices and live availability with e-mobility service providers (eMSPs). The eMSP uses it to start sessions for its drivers and to receive the charge records it bills from. The EVRoaming Foundation maintains OCPI, and the current versions are OCPI 2.2.1 and OCPI 2.3.0 (released in 2025). OCPI is the protocol behind EV roaming.
One roaming session, step by step
Seven OCPI 2.2.1 modules carry a roaming session from the first handshake to the final bill. YoCharge runs them in both roles.
| Step | Module | Sent by | What it carries |
|---|---|---|---|
| 1 | Credentials | Both sides | Tokens and endpoints, exchanged once so the two platforms trust each other |
| 2 | Locations | CPO → eMSP | Chargers, connectors, power and live availability, for the driver’s map |
| 3 | Tariffs | CPO → eMSP | Prices, so the driver sees the cost before plugging in |
| 4 | Tokens | eMSP → CPO | The driver’s app ID or RFID card, so the charger accepts them |
| 5 | Commands | eMSP → CPO | Start or stop a session from the app, or reserve a charger |
| 6 | Sessions | CPO → eMSP | Live energy and running cost while the car charges |
| 7 | CDRs | CPO → eMSP | The final charge detail record (energy, time, cost) used for billing |
Built for both sides of roaming
OCPI integration for CPOs
- Publish once: your locations and tariffs reach every eMSP, driver app and EV maker you connect to.
- Accept their drivers: partner app tokens and RFID cards start sessions on your chargers.
- Get paid: every session closes with a CDR, and the revenue comes back to you.
OCPI for eMSPs
- More chargers in your app: every network you connect to shows up on your drivers’ map.
- Bring your own CPOs: connect any OCPI-compliant network you already have an agreement with.
- Drivers charge their way: start and stop from the app, with RFID cards that work on other networks and Plug & Charge at supported chargers.
EV makers and fleets with their own driver apps connect in the eMSP role. Launching a new charging brand? White-label eMSP software
Direct, or through a roaming hub
YoCharge supports both ways to roam.
-
Peer-to-peer roaming: connect straight to a partner. You negotiate the agreement and keep full control, but each partner is a separate connection to build and run.
-
Through a hub: one OCPI connection reaches every party on the hub, and new partners join without new integration work on your side.
Hubs YoCharge connects to:
YoHub, our sister OCPI roaming hub: 70+ CPO networks, 40+ eMSPs and 14,000+ charging stations reachable across its regions. In the Middle East, YoHub’s MENA hub has Eco-Movement connected. Visit YoHub
YoHub’s regional hubs in India, Southeast Asia, the Middle East and North Africa, Australia and New Zealand, Europe and North America, with partner hubs such as GreenFlux connected in Europe.
YoHub network figures across all its regions, October 2026.
Roaming revenue, credited fast
Your prices: you set the tariffs your partners see, per kWh, per minute or per session.
White-label: roaming revenue from third-party networks is collected by YoCharge and credited to you, as fast as T+2 from the session.
YoCharge Managed: roaming revenue is included in your weekly credit.
Clean records: every CDR flows into invoices and settlement reports automatically.
Live in 3–7 business days
Our OCPI implementation runs in five steps:
Discovery: your role, your platform, your partners and the modules you need.
Credentials exchange: endpoints and tokens swapped securely with each partner.
Module setup: Locations, Tariffs, Tokens, Commands, Sessions and CDRs configured for your role.
Testing: the session lifecycle, commands and CDRs checked end to end.
Production: go live with monitoring and support.
A typical OCPI integration takes 3–7 business days from credentials exchange to live data, depending on the modules and on your partner.
OCPP and OCPI on one platform
OCPP connects your chargers to your platform. OCPI connects your platform to other networks. YoCharge runs both, so roaming isn’t a separate system to buy and maintain:
- OCPP 1.6J · 2.0.1 · 2.1-ready, across 60+ charger brands OCPP software
- OCPI 2.2.1, plus earlier OCPI versions
- The OCPI 2.3.0 Payments module, for chargers with payment terminals
- Billing, invoicing and driver apps on the same platform
Roaming in India
-
UBC through YoHub: one connection for OCPI 2.2.1 + UBC (Beckn).
-
Settlement your way: in India, settle directly with each partner, or let YoCharge manage it through YoHub, which invoices the eMSP and pays the CPO, with GST invoices.
-
Your drivers’ payments: with white-label, UPI and UBC payments go straight to your account.
OCPI integration: questions buyers ask
What does OCPI integration do?
It connects your charging platform to other networks over OCPI, so your chargers appear in partner apps (as a CPO) or your drivers can charge on partner networks (as an eMSP). YoCharge builds it into the platform that runs your chargers.
Which OCPI versions do you support?
OCPI 2.2.1, plus earlier OCPI versions. For chargers with payment terminals, we also support the Payments module introduced in OCPI 2.3.0.
Which OCPI modules do you support?
The modules a roaming session needs: Credentials, Locations, Tariffs, Tokens, Commands, Sessions and CDRs, in both the CPO and the eMSP role.
How long does an OCPI integration take?
Typically 3–7 business days from credentials exchange to live data, depending on the modules and on your partner.
Do I need YoCharge’s platform to roam?
No. YoHub works with any CMS that speaks OCPI 2.2.1. On YoCharge, OCPI is built in, so there’s nothing extra to install.
Should I connect peer to peer or through a hub?
Peer to peer gives you full control of each agreement but means one connection per partner. A hub gives you many partners through one connection. Most networks use both, and YoCharge supports both.
Which roaming hubs can I connect to?
YoHub, our sister product, which runs regional hubs in India, Southeast Asia, the Middle East and North Africa, Australia and New Zealand, Europe and North America. Partner hubs are connected to it, such as Eco-Movement in the Middle East and GreenFlux in Europe.
How is roaming revenue settled?
With white-label, roaming revenue from third-party networks is collected by YoCharge and credited to you, as fast as T+2 from the session. With YoCharge Managed, it’s part of your weekly credit. In India, settle directly or let YoCharge manage it through YoHub; everywhere else, CPOs and eMSPs settle directly with each other, and YoCharge reconciles the sessions.
OCPI vs OCPP: what’s the difference?
OCPP runs between a charger and its management platform. OCPI runs between two platforms, such as a CPO and an eMSP. A roaming network needs both, and YoCharge runs both.
Do you support UBC in India?
Yes. Through YoHub, one connection covers OCPI 2.2.1 + UBC (Beckn), and YoCharge is UBC compliant for driver payments.
Start roaming in days
Tell us your role and your partners. We’ll map your OCPI integration on YoCharge.
Book a demoOr email sales@yocharge.com