Skip to main content
Getz Hub

Roaming agreements

Roaming agreements that the system actually enforces

An agreement binds two parties, the OCPI modules they exchange and the dates it applies. Hub routes nothing between two partners without one, applies start and end dates automatically, and records every change.

Roaming agreements: which partners roam together, for which OCPI modules, from when. Synthetic demo data.

  1. An agreement routes only once both sides accept the same revision

The challenge

Agreements on paper drift from reality

When agreements live in contracts and spreadsheets, the systems keep exchanging data long after the terms changed.

  • Data outlives the deal

    Locations keep flowing to an app after the relationship ended.

  • Unclear scope

    Nobody can say which modules a partner is entitled to.

  • No history

    Changes are not recorded, so disputes about what was agreed are hard to settle.

How it works

The agreement workflow

  1. Step 1: Propose

    A partner proposes an agreement from the directory of partners: counterparty, modules and dates.

  2. Step 2: Counter or accept

    The other side counters or accepts. An agreement routes only once both sides accept the same revision.

  3. Step 3: In force on its dates

    Hub starts and ends agreements on their dates and backfills what the counterparty is now owed, under visibility rules.

  4. Step 4: End cleanly

    Ended agreements are kept, never deleted. Messages already queued are re-checked when they are sent.

Capabilities

What agreements cover

  • Per OCPI module

    Locations, tariffs, tokens, sessions, CDRs, commands, charging profiles, bookings, payments and Hub Client Info.

  • One live agreement per pair

    Overlapping agreements for the same two parties are refused.

  • Connection status follows agreements

    Each party is told the status of the parties it roams with, and only those.

  • Audited changes

    Created, amended, activated, expired and ended agreements are audit events.

In the product

Partners in one directory

CPOs, eMSPs and peer hubs with their OCPI parties, status and onboarding progress, filterable by role. Captured with synthetic demonstration data.

  1. Filter partners by role
  2. Each partner can hold several OCPI parties (country code + party ID)

Partner directory with demo partners: parties, status and onboarding progress. Synthetic demo data.

Questions

Roaming agreements: questions

Can Hub staff change our agreement?

Hub staff can amend a live agreement’s modules or dates with a reason, for example to apply a correction both sides asked for. Both parties are notified and the change is audited.

What happens when an agreement ends?

Discovery and commands between the two parties stop for the covered modules, and messages already queued are re-checked when they are sent. Session updates and charge records of sessions that started under the agreement are still delivered for 90 days after it ends; after that they are refused, with a recorded reason both parties can see. Each side is told the other is no longer active for it. The agreement and its audit history stay on record.

Who contracts with whom?

An agreement in Hub is between two OCPI parties, usually an operator (CPO) and an app (eMSP). A car brand’s owner app is the eMSP side, run by the brand or its charging-service provider. Who does what in an owner-app journey. Talk to the Hub team about the commercial side.

Does a data licence need a roaming agreement?

No. Data keys cover public locations only, under a data plan; roaming agreements cover the OCPI modules two partners exchange. Charging data API.

Find partners and agree terms in one place

Become a network partner and see the directory of connected operators and apps.