Recognise this?
Drivers from an eMSP you don't have a contract with can't start at your charger. Lost revenue, bad review.
You manage four roaming contracts in parallel with four separate technical integrations. Every OCPI version upgrade costs weeks.
Disputes with MSPs over sessions or billing. You can't quickly prove what actually happened — no per-session audit trail.
Concretely, in four points
One OCPI broker that connects your network to every major MSP and eMSP without you maintaining a separate technical integration per partner.
Full support for OCPI 2.1.1, 2.2.1 and 2.3.0 — and OICP 2.3 where relevant. You pick which version per partner.
Audit-grade event logging for disputes and reconciliation between CPO and MSP.
Charging Preferences and Sessions sharing supported — relevant for smart charging collaborations between networks.
The question we hear every week
Our current CPMS already has OCPI built in. What does a separate broker add?
A built-in OCPI implementation connects you to one partner per integration effort. ihomer Roaming aggregates: you talk to us once, we connect you to every MSP. We also keep OCPI versions current, if a partner moves from 2.1.1 to 2.2.1, we handle the translation.