Roaming is useful only when a driver can complete the intended session. If you are evaluating EVCharge.mobi for your chargers, start with the service you can verify: connect a charger, provide access, set a tariff where needed and inspect the result. Keep cross-network requirements explicit.
Originally published in 2025. The EVCharge.mobi workflow was updated in September 2026; the historical discussion below retains its original context.
Use the quickstart to connect an OCPP 1.6 JSON charger. For private use, invite a driver and grant access. For public paid use, configure tariffs and payment, complete the location details and resolve the Publicity checklist.
Inspect the charger in the EVCharge app and complete an authorised first session. Review its record in Reports. This tests the service you intend to operate, including how the driver and operator find the same session.
If roaming is required, identify the partner networks, countries and billing arrangements you need and discuss them with us. An OCPP connection or map marker does not establish an active OCPI commercial connection, universal access or consolidated invoicing across networks.
The driver app guide explains why a location on the map is not always startable through the app. Choose a platform on demonstrated workflows and confirmed coverage.
Once upon a time, cross‑border EV trips meant five apps and a fistful of tags. In 2025, most of that friction is hidden by a behind‑the‑scenes language called OCPI. As one roaming foundation puts it, “OCPI enables information exchange between e‑mobility service providers and charge point operators.” The promise: one account, many networks — and drivers barely notice the plumbing.
Two things converged. First, AFIR rules made ad‑hoc access and per‑kWh price display at high‑power sites the European baseline. Second, OCPI adoption by operators and apps matured, so roaming works more like payments than a tech experiment. Put simply: ad‑hoc lets anyone pay; roaming is what makes planning, discounts and one invoice possible.
Quote (OCA explainer): “OCPP connects charge points to a central system… OCPI is used between service providers and charge point operators.”
Bilateral (peer‑to‑peer). A CPO and an MSP exchange credentials and open an OCPI link directly. Pros: control, fewer intermediaries. Cons: many links to reach many drivers.
Hub model. A roaming hub routes OCPI traffic among many CPOs/MSPs. Pros: one integration → many partners. Cons: extra fees/layer.
In Europe, both models run side by side; hubs speed coverage, while direct links serve strategic partners and special pricing.
Price reality: Apps should show ad‑hoc price vs roaming price side‑by‑side. Sometimes on‑site ad‑hoc wins; other times membership/loyalty via roaming is cheaper. Transparency earns trust.
Reporter’s note: studies on public charging reliability still find double‑digit failure rates, but trendlines are improving as payment and roaming stacks converge.
Is OCPI mandatory? No, but it’s the de‑facto European way to interconnect apps and networks.
Does OCPI set prices? No. It transports tariffs. The CPO sets site prices; MSPs may apply memberships/fees.
Is this Plug & Charge? No. Plug & Charge (ISO 15118) authenticates the car↔charger. OCPI is operator↔app so you can discover, start and get billed.
Create a free CPO Portal account and connect your first OCPP charger in minutes.