Roaming · OCPI 2.2.1
Your drivers charge further. Other drivers charge with you.
ChargeIT holds the roaming agreements and the OCPI connections. You and your customers roam under ChargeIT’s identity, without negotiating a single hub contract yourselves.
Both directions
As eMSP, as CPO, or both.
Any customer that runs as a charge point operator or an eMobility service provider gets roaming in its console, whether it runs directly on ChargeIT or under its own brand.
Your drivers, on more chargers
Your app’s drivers start sessions on partner networks, and those sessions are priced, billed and settled like any other.
More drivers, at your chargers
Your stations are published to partner networks, their drivers charge with you, and the revenue comes back through roaming settlement.
Standard, not custom
OCPI 2.2.1, module by module.
Roaming runs on the open OCPI standard, so partners connect the same way they connect to everyone else.
- CredentialsThe handshake
- LocationsStations and status
- TariffsPrices per connector
- TokensWho may charge
- CommandsRemote start, stop
- SessionsLive progress
- CDRsBillable records
Settlement
Roaming money lands in the same ledger.
Roaming sessions are settled in the billing console next to everything else, and reported in their own roaming report, so a roaming euro is never handled differently from a local one.
A partner’s driver charges at your station
The session reaches ChargeIT over OCPI.
The CDR is created and priced
With your tariff for that connector.
It is settled in the billing console
Under roaming settlement, for the month.
Roam without the paperwork.
Tell us whether you want to roam as CPO, eMSP or both, and we’ll show you how it’s set up.
Book a demo