OCPI integration is the technical and operational setup that connects two EV charging platforms using OCPI (Open Charge Point Interface)—most commonly a CPO platform (operating chargers) and an eMSP platform (serving drivers). The integration enables roaming, data exchange (locations, status, tariffs), and billing flows (sessions and CDRs) so users can access chargers across networks.
What OCPI integration enables
A typical OCPI integration supports:
– Sharing locations/EVSE/connector data for charger discovery
– Real-time or near-real-time status updates (available, occupied, out of service)
– Tariff exchange for price display and billing logic
– Token exchange for authorization (RFID/app credentials)
– Session data exchange for transparency and support
– CDR (Charge Detail Record) exchange for billing and settlement
– Optional commands (start/stop, reserve) depending on OCPI version and agreement
How OCPI integration works (high level)
OCPI integration is platform-to-platform (not charger-to-backend):
– Each party exposes OCPI API endpoints (or uses a roaming hub)
– Parties authenticate using OCPI tokens and agree on roles (CPO vs eMSP)
– Data modules are synchronized on a schedule or via push updates
– Operational processes are defined for errors, disputes, and support handover
Common OCPI modules involved
Typical modules in an OCPI integration include:
– Versions and Credentials (handshake and authentication setup)
– Locations (sites, EVSEs, connectors, capabilities)
– Tariffs (pricing structures and conditions)
– Tokens (user identifiers for authorization)
– Sessions (live/ongoing charging session data)
– CDRs (finalized billing records)
– Optional: Commands (remote start/stop), Reservations, Charging Profiles (varies)
Key implementation considerations
OCPI integrations succeed or fail based on data quality and operations:
Data accuracy and mapping
– Align EVSE IDs, connector IDs, and location references consistently
– Normalize status definitions to avoid misleading availability in apps
– Keep tariff versions and effective dates synchronized to prevent billing disputes
– Define time zones, rounding, and VAT/tax handling rules for CDRs
Security and reliability
– Use TLS, strict authentication, and allow-listing between parties
– Rotate credentials and maintain audit logs for API access
– Implement retries, idempotency, and validation to handle intermittent errors
– Monitor OCPI KPIs: sync success rate, command success rate, CDR acceptance rate
Operational processes
– Define ownership boundaries for customer support (who handles what issue)
– Set SLAs for incident response, data corrections, and dispute handling
– Create reconciliation workflows for mismatched CDRs and refunds
– Plan for version upgrades and backward compatibility (OCPI versions differ)
OCPI integration vs OCPP
– OCPP connects chargers ↔ CPMS for control and monitoring
– OCPI connects CPMS/CPO ↔ eMSP/roaming platforms for roaming, discovery, tariffs, sessions, and billing
Many networks use both: OCPP for charger operations and OCPI for roaming.
Common pitfalls
– Stale location/status data leading to failed user journeys
– Tariff mismatches causing pricing complaints and charge disputes
– Incomplete CDR fields breaking settlement and invoicing logic
– Poor handling of edge cases (partial sessions, failed starts, offline chargers)
– Lack of monitoring and alerting on integration health
Related glossary terms
OCPI
Roaming
eMSP
CPO
Interoperability networks
Multi-network access
OCPI billing
Charge Detail Record (CDR)
Tariffs and pricing models
OCPP