Seamless Charging Across Networks: A Practical Roaming Guide

Picture a driver: in Istanbul they charge with one brand's app; the following week they're in Ankara, pulling up to a station owned by a different operator. They don't want to download a new app, get a new card, or open a new account. They just want to plug in and keep driving.

That seamless experience is exactly what roaming makes possible. And today — especially in Türkiye's rapidly expanding charging market — it has become non-negotiable for any operator that wants to scale.

What Roaming Is, and What It Isn't

We know roaming from telecoms: when you're abroad, you're served by a local operator instead of your own; the bill comes back to your home operator.

EV roaming works on the same principle. With your operator's app, you charge at another operator's station. The payment is settled in the background between the two operators; for the driver, it stays one continuous experience.

Roaming isn't a single app or standard — it is a business model and a protocol stack that standardizes trust, data and money flow between operators.

OCPI 2.2.1 — The Common Language of Roaming

The de facto standard in the industry is OCPI (Open Charge Point Interface). Version 2.2.1 explicitly defines how the CPO (Charge Point Operator) and eMSP (e-Mobility Service Provider) roles communicate, which modules are shared, and which data flows.

For an operator, OCPI translates to:

• Publishing your station locations to the roaming network — drivers from other networks see you on the map.
• Synchronizing your tariffs automatically — which station, what hour, what price is transparent.
• Sharing driver tokens (RFID cards or app users) — authorization flows across both operators.
• Tracking charging sessions across networks; when a session closes, a CDR (Charge Detail Record) is generated.
• Sending remote commands (unlock, reboot, reserve) through the partner.

A detailed audit trail is kept for all of these flows — who shared what data, when.

CPO and eMSP — Two Roles, One Contract

The same operator can run as both CPO and eMSP.

• As a CPO you manage the field devices and expose your stations to the outside world.
• As an eMSP you offer your drivers access to other networks.

For most operators, enabling both roles is the soundest strategy — you give your drivers a wide reach, and you bring new revenue to your own stations.

What It Brings to the Operator

There are three critical operator-side benefits:

1. Your network isn't an island. Your stations become visible on the shared network; drivers from other operators choose them. Your utilization rate goes up.
2. Your drivers' range expands. Even if your own footprint is limited, your drivers can charge with the same app at partner sites. Your mobile app stops being "the app for one city" and becomes "the app for the country."
3. Roaming billing stops being a headache. Money flow between operators is settled automatically through CDR records. Manual reconciliation, email chains, spreadsheets — all gone.

Driver Experience: Becoming Invisible

The best part of a good roaming integration is that the driver doesn't notice they are roaming. The app opens, the nearest station appears, a card is tapped or a QR is scanned, charging starts, the invoice goes through. Whose station it is fades into the background.

That strengthens your brand identity. The driver says "I can charge anywhere with brand X's app" — they bond with your brand.

The Türkiye Picture

As the EV market grows quickly in Türkiye, roaming capacity is becoming a competitive differentiator. Most licensed operators are now opening up to OCPI-based integrations; as roaming partnerships expand, the driver experience becomes more fluid.

In the near future, roaming will move from "nice to have" to "you can't operate without it." Preparing now means opening a door today that will close tomorrow.

Running Roaming in Production

You can't set up roaming once and forget about it. The areas to monitor continuously:

• Token sharing quality: tokens you send to a partner network must authorize quickly and without errors.
• Tariff synchronization: when your tariff changes, partners must reflect it at the right moment.
• CDR accuracy: roaming sessions billed correctly; disputes minimized.
• Activity audit trail: every command, token, session and CDR — traceable historically.

Echargo runs OCPI 2.2.1 in both CPO and eMSP roles, with this audit-trail discipline baked in. Our operators experience roaming not as a separate integration project, but as a natural part of the platform.

Roaming is the path from being "an isolated island" to being "part of the national network" in EV operations. The operator who prepares today takes position in tomorrow's scale market.