Skip to main content
Getz Hub

Neutral EV roaming infrastructure

Connect the charging ecosystem.

One neutral layer between charging networks and the apps drivers use: roaming partners connect once over OCPI, and data customers read public charging data through an API or a feed.

Illustration
Getz Hub at the centre of the charging ecosystemCharging networks connect to Getz Hub on the left and mobility apps on the right. Automotive brands connect from above. Data platforms read public charging data, and peer roaming hubs connect hub to hub, below. Each message passes the roaming agreement, visibility and tariff checks inside Hub.Getz Hub at the centre: charging networks above, mobility apps below, car brands, data platforms and peer hubs beside it
Roaming partners connect once over OCPI, in the version they already run. Data customers connect through the read-only API or a feed. Hub routes each message under the roaming agreements and visibility rules in force.

Start here

What brings you to Getz Hub?

Each path leads with what Hub does for you, and ends with an enquiry form for your team.

The problem

Roaming is still built one integration at a time

Every network and every app that want to work together build, test and maintain their own connection. The cost decides who connects, so a driver on the N3 between Johannesburg and Durban, to take one example, carries several apps and smaller networks stay invisible.

Different OCPI versions, agreements kept in e-mail and charge records that do not match the tariff make each connection slower and riskier than it should be.

Illustration
Bilateral integrations compared with one connection through a hubOn the left, four charging networks and four apps each integrate with every other side: sixteen integrations. On the right, the same eight participants each connect once to a hub: eight connections.
Four networks and four apps: wired to each other, or each connected once through a hub.

How Hub connects the ecosystem

Connect once. Agree who you work with. Hub does the routing.

  1. Step 1: Connect once

    Join through a self-service link, in the OCPI version you already run.

  2. Step 2: Agree who you roam with

    Roaming agreements per partner and per module. Nothing flows without one.

  3. Step 3: Hub routes under your rules

    Chargers, tokens, sessions and commands reach only the partners your rules allow.

  4. Step 4: Records are checked

    Charge records are checked against the agreed tariff before they reach the app.

Two sides of every roamed session

What operators and apps each get

For charging operators

More drivers on your chargers

  1. Reach participating appsPublish once; every app you agree to roam with can show your chargers and start sessions on them, from a mall car park to a highway forecourt.
  2. Choose who sees your chargersYour visibility rules decide which partners see each site; your tariff passes through unchanged and private sites stay private.
  3. Catch mismatches firstRecords that do not match your tariff are held before the app sees them.

For mobility applications

More chargers for your drivers

  1. One OCPI connection to operator networksConnect once, then propose roaming agreements with participating operators. Each operator approves its own agreement; ask us which operators fit your market.
  2. Start, stop and authoriseTokens, sessions and remote commands routed in your OCPI version.
  3. Same terms as everyoneGetz’s own app connects exactly as you do. No priority lane.

OCPI interoperability

Connect in the OCPI version you already run

Hub serves OCPI 2.1.1, 2.2.1 and 2.3.0 and translates between partners on different versions, so nobody has to upgrade first.

OCPI modules Getz Hub routes, by version
CapabilityOCPI 2.1.1OCPI 2.2.1OCPI 2.3.0
Locations and live availabilityYesYesYes
TariffsYesYesYestax-inclusive
Tokens and real-time authorisationYesYesYes
Sessions and charge records (CDRs)YesYesYes
Remote start and stop commands YesYesYes
Smart-charging profilesNoYesYes
Card-terminal payments NoNoYes
Bookings NoNoYes

Roaming and transaction workflows

From a new partner to a delivered charge record

The Hub as partners and Hub staff use it, captured with synthetic demonstration data.

A partner joins from a link

A new partner registers its OCPI parties and completes the credentials handshake from its own back office. Activation waits until connection and module tests pass.

  1. The link is single-use and expires
  2. Hub staff approve the partner before it goes live
Self-onboarding page a new roaming partner opens from an invitation link, prefilled with the organisation name

Charge-record assurance

Charge records checked before anyone is billed

Hub checks every roamed charge record against the agreed tariff and identifies mismatches. It re-prices the record from the operator’s own tariff, including tax, idle and reservation fees, and holds a record that does not match before it reaches the app.

A rand tariff is checked in rand, with the VAT the tariff states: 15% for South African sessions.

  • Mismatches held until finance staff release or reject them with a reason

Charge records checked against agreed tariffs: mismatches are held until released. Synthetic demo data.

  1. Overcharged records are held from the eMSP
  2. Hub staff release a held record with a reason; every decision is audited

What assurance checks, and what it does not

A tariff and reconciliation check, with a clear scope.

What Getz Hub charge-record assurance checks, and which party handles the rest
CapabilityChecked by HubWhere it belongs
The agreed tariff applied to each roamed recordYesHub assurance
Tax, idle and reservation feesYesHub assurance
Totals, periods and energy consistent with each otherYesHub assurance
Record counts between sender and HubPartlywhere the sender reports its countsHub sync health
Accuracy of the charger’s meterNoMeter certification (hardware and CPMS)
Whether the tariff itself was agreed correctlyNoThe operator and the app
The app’s driver price, markups and refundsNoThe app
Settling money between the partiesNoThe partners’ own invoicing

Partner visibility and data controls

Operators decide who sees what. Hub never widens it.

A location reaches an app only when the operator’s rule or a roaming agreement allows it. Home, fleet and private sites stay hidden unless the operator allows a specific driver token, and an unpublished site is withdrawn from every app.

  • Test a visibility rule before you publish
  • Each partner sees its own data in the partner portal, and nothing else
  • The data API serves public locations only, never sessions or charge records

Visibility rules you can test: the tester shows the party asked about, the rule that decided and the outcome (here: visible, because a roaming agreement is in force). Synthetic demo data.

  1. Dry run: nothing changes
  2. Home and private locations stay hidden by default

Neutrality and governance

Neutral by design. Binding by contract.

Hub is owned by the group that also builds Getz Network and Getz EMP. The product controls below apply to Getz’s own products exactly as to every other partner, and the governance measures that make this binding are coming soon.

  • In place

    Equal partner treatment

    Getz’s own products connect through the same agreements, visibility rules and routing checks as every other partner.

  • In place

    One shared delivery queue

    The same queue and retry policy for every partner. No priority lane, including for Getz.

  • In place

    Controlled data access

    Partner isolation and fail-closed visibility: one partner’s data never reaches another partner or another Getz business.

  • In place

    Explainable routing

    Every routing decision is traced and can be explained to the partner it affects, with an audit trail behind it.

  • Coming soon

    One published price list

    The same prices for every partner, with notice before changes; the party that starts a roamed session pays its fee.

  • Coming soon

    Neutrality charter

    A written commitment to equal treatment in every partner contract, Getz’s own products included.

  • Coming soon

    Ring-fenced Hub entity

    Its own accounts and managing director, and at least one independent board member.

  • Coming soon

    Advisory council and audit

    Connected operators and apps consulted on fees and rules; an outside auditor checking routing and prices.

Technical integration

Your OCPI implementation is the integration

Hub is a standard OCPI hub. There is no SDK to install and no proprietary API to learn: register your parties, complete the credentials handshake from your back office and pass the connection tests.

  • Self-service onboarding with the standard credentials handshake
  • Deliveries, connection health and retries in your own portal

Partner onboarding, step by step: credentials, version negotiation, connection and module tests, then activation. Synthetic demo data.

  1. A partner is activated only after its connection and module tests pass

Connect your network to Getz Hub

Tell us who you are and what you want to connect. Joining and publishing your chargers costs nothing.