OCPI 2.2.1 Integration Platform for EV Charging Networks
Connect Charge Point Operators (CPOs), eMSPs, EV OEMs, fleet operators and roaming hubs through a secure, standards-compliant OCPI integration platform.
OCPI 2.2.1 Integration Platform for EV Charging Networks
Connect Charge Point Operators (CPOs), eMSPs, EV OEMs, fleet operators and roaming hubs through a secure, standards-compliant OCPI integration platform.
Locations
Station Discovery
Tokens
Driver Authorization
Sessions
Session Management
Tariffs
Pricing Sync
CDRs
Billing Records
Commands
Remote Control
Hub Client Info
Hub Connectivity
Payments
Payment Terminals
Built for Every Charging Stakeholder
Charge Point Operators (CPOs)
Share your network across 20+ aggregators and eMSPs. Increase station utilisation and revenue with a single OCPI integration.
eMobility Service Providers
Give drivers access to multiple CPO networks through one integration. Faster onboarding, unified billing, no per-CPO custom work.
EV OEMs
Embed real-time station discovery, session management and billing directly in vehicle apps. One OCPI connection covers all CPOs.
Fleet Operators
Centralised charging access across multiple networks. Unified billing, session data and reporting for your entire commercial fleet.
OCPI Protocol
What is OCPI?
OCPI, or Open Charge Point Interface, is an open protocol used to connect Charge Point Operators, eMobility Service Providers, EV OEMs, fleet platforms and roaming hubs.
It exists to make EV charging networks interoperable. Instead of every CPO and eMSP building custom APIs for each partner, OCPI creates a common language for sharing charging locations, tariffs, sessions, tokens, commands and billing records.
OCPI enables platform-to-platform communication between charging networks and mobility providers.
Why Implement OCPI?
Why OCPI Integration Matters
OCPI helps charging businesses scale interoperability, roaming and partner connectivity without rebuilding custom integrations for every new network.
Expand Network Reach
Make your charging network discoverable across eMSPs, OEM apps, fleet platforms and roaming partners.
Enable EV Roaming
Allow drivers to access charging stations across multiple networks through a single account or app.
Reduce Integration Costs
Replace partner-specific custom APIs with one standardized OCPI implementation.
Accelerate Partner Onboarding
Connect with new CPOs, eMSPs, OEMs and roaming platforms faster using a common protocol.
Future-Proof Infrastructure
Build on a widely adopted interoperability protocol designed for scalable EV charging ecosystems.
Why Standards Win
OCPI vs Custom Charging Integrations
Custom integrations become expensive and difficult to scale as your charging ecosystem grows. OCPI provides a standardized approach that enables faster onboarding and interoperability.
Integration Models
Direct OCPI Integration vs OCPI Roaming Hub
OCPI can be implemented as a direct bilateral integration or through a roaming hub. YoCharge supports both models depending on your business goals.
One-to-One OCPI Connection
Best when two parties want to connect directly and manage their own commercial, technical and operational relationship.
- One CPO connects to one eMSP
- Bilateral agreement required
- Separate setup for every partner
- More control, but slower expansion
One-to-Many OCPI Connectivity
Best when you want faster ecosystem access through a single connection to multiple charging networks, eMSPs, OEMs and fleet platforms.
- Connect once, access multiple partners
- Faster network expansion
- Lower integration maintenance
- Ideal for scalable EV roaming
OCPI Modules
OCPI 2.2.1 Modules Explained
YoCharge supports the key OCPI modules required for credentials exchange, charging station discovery, driver authorization, roaming, session tracking, pricing, billing, hub connectivity and direct payments.
Credentials
↔ Bidirectional
Purpose
Establishes the initial OCPI connection between two parties before any other module can operate.
Key Data
- API tokens
- Endpoint URLs
- Party identifiers
- Role and version information
Use Cases
Partner onboarding, secure handshake, endpoint registration and OCPI connection setup.
Locations
CPO → eMSP
Purpose
Shares charging station information with external platforms and roaming partners.
Key Data
- Station address and coordinates
- Connector type and power rating
- Real-time availability
- Opening hours and parking details
Use Cases
Charging station discovery, map visibility, EV OEM apps, eMSP apps and roaming networks.
Tokens
eMSP → CPO
Purpose
Enables driver authorization across charging networks.
Key Data
- RFID tokens
- App user IDs
- eMAID identifiers
- Authorization status
Use Cases
Roaming authorization, fleet driver access, RFID-based charging and app-based charging.
Sessions
CPO → eMSP
Purpose
Exchanges live charging session information while a session is active.
Key Data
- Session start and end time
- Energy consumed
- Current session status
- Running cost estimate
Use Cases
Live charging tracking, driver notifications, fleet monitoring and session reporting.
Tariffs
CPO → eMSP
Purpose
Synchronizes charging prices across platforms before and during charging.
Key Data
- Energy pricing
- Time-based pricing
- Idle fees
- Currency and tax information
Use Cases
Price transparency, tariff display, cost estimation and partner billing alignment.
CDRs
CPO → eMSP
Purpose
Transfers final Charge Detail Records after a charging session ends.
Key Data
- Total energy delivered
- Session duration
- Final cost
- Location and token reference
Use Cases
Billing, settlement, invoicing, reconciliation and fleet charging reports.
Commands
eMSP → CPO
Purpose
Allows external platforms to remotely control charging actions.
Key Data
- Start session
- Stop session
- Unlock connector
- Reserve charging point
Use Cases
Remote start/stop, app-based charging, fleet charging control and customer support.
HubClientInfo
Hub → Parties
Purpose
Maintains information about parties connected through a roaming hub.
Key Data
- Connected party details
- Supported roles
- Connection status
- Supported modules
Use Cases
Roaming hub operations, partner discovery, ecosystem visibility and hub-based OCPI connectivity.
Payments
Payment Terminal Support
Purpose
Supports direct payment workflows for charging stations with payment terminals.
Key Data
- Payment terminal data
- Payment transaction reference
- Ad-hoc charging session details
- Payment status information
Use Cases
Ad-hoc charging, card payment, payment terminal integration and direct payment compliance.
Implementation Process
How YoCharge Implements OCPI
From discovery to production deployment, YoCharge follows a structured OCPI implementation process designed to reduce integration delays and technical uncertainty.
Discovery
We understand your role, existing charging platform, partner requirements, OCPI scope and integration goals.
Credentials Exchange
OCPI credentials, endpoint URLs, authentication tokens and party details are exchanged securely.
Module Configuration
Required OCPI modules such as Locations, Sessions, Tariffs, Tokens, CDRs and Commands are configured.
Testing
We validate data flows, session lifecycle, command execution, CDR generation and roaming scenarios.
Production Deployment
After validation, the integration is moved to production with monitoring, support and rollout assistance.
Supported Use Cases
Common OCPI Use Cases
YoCharge supports practical OCPI use cases for CPOs, eMSPs, EV OEMs, fleets and payment-enabled charging networks.
EV Charging Roaming
Enable drivers to access charging stations across multiple CPO networks through interoperable OCPI connections.
Charging Station Discovery
Share station locations, connector types, availability and tariff data with eMSPs, OEM apps and fleet platforms.
Driver Authentication
Authorize drivers using tokens, RFID, app-user IDs or eMAIDs across connected charging networks.
Fleet Charging
Provide fleets with centralized access, session tracking, charging records and consolidated billing data.
EV OEM Integration
Embed charging discovery, session control and billing experience directly into EV OEM apps and vehicle ecosystems.
Direct Payments
Support payment-terminal-based charging use cases for ad-hoc charging and direct payment workflows.
Need Access to Multiple Charging Networks?
OCPI integration enables interoperability — but managing multiple bilateral roaming relationships still requires significant coordination effort. YoCharge’s OCPI Roaming Hub connects your network to 10,000+ charging stations across 25+ CPOs and 20+ aggregators through a single integration.
Why Choose YoCharge?
Built for Real-World OCPI Deployments
YoCharge helps CPOs, eMSPs, EV OEMs and fleet platforms implement OCPI faster, connect with more partners and scale roaming operations with enterprise-grade support.
Multi-Country Deployments
Deploy OCPI integrations across regions with support for different charging, pricing and partner models.
White-Label Platform
Launch OCPI-enabled charging experiences under your own brand for drivers, partners and enterprise clients.
OCPI Expertise
Implement OCPI modules including Locations, Tokens, Sessions, Tariffs, CDRs, Commands and HubClientInfo.
OCPP + OCPI Experience
Bridge charger-side OCPP operations with platform-to-platform OCPI interoperability from one technology partner.
Enterprise Support
Get guided onboarding, technical support and implementation assistance for production-grade OCPI rollouts.
Roaming Hub Available
Go beyond bilateral integrations and connect to multiple CPOs, eMSPs and EV OEMs through YoCharge OCPI Roaming Hub.
Explore Roaming Hub →Ready to Implement OCPI Integration
Connect your EV charging network to CPOs, eMSPs and aggregators with YoCharge’s fully compliant OCPI 2.2.1 platform.
Frequently asked Questions
Get answers to common questions about OCPI