zevOS

01Features · Drivers & partners

Let other networks’ drivers pay at your chargers

Utilisation on a new corridor comes from drivers who have never heard of you. Roaming puts your chargers inside apps those drivers already use, and lets your own driver base charge on networks you will never build. zevOS implements OCPI on both sides of that trade.

Roaming & OCPI

  • OCPI 2.2.1

    Protocol

  • CPO and eMSP

    Roles

  • Locations, Tokens, Sessions, CDRs, Commands

    Modules

Capabilities

What this gives you

01

Publish your network

Share locations, EVSEs, connectors, live status and tariffs with roaming partners, so your chargers appear — accurately — in their apps.

02

Accept their tokens

Authorise a partner’s driver at your charger in real time, run the session, and return a CDR the partner can bill against. Their driver charges; you get paid by their platform.

03

Charge on their network

As an eMSP, pull partner locations into your app and let your drivers start sessions remotely on chargers you do not own.

04

Reconciliation

Inbound and outbound CDRs are stored and reconciled against partner statements, so roaming revenue does not become the line nobody can explain.

Specifications

The technical detail

The things a procurement team or an integration partner will ask for, stated plainly.

Version
OCPI 2.2.1
Modules
Credentials, Locations, Tokens, Sessions, CDRs, Tariffs, Commands
Roles
CPO, eMSP
Registration
Credentials handshake with token rotation

Questions

What operators ask about this

How long does it take to connect a roaming partner?

The technical handshake is a credentials exchange and can be done in a day. The commercial agreement is usually the longer part.

Do I have to expose all my sites?

No. You choose which locations are published to which partner.

See roaming & ocpi working

A walkthrough against your own chargers and tariffs, rather than a demo tenant with tidy data.