Skip to main content
Getz Hub

How it works

How Getz Hub works, step by step

Seven interactive illustrations of what Hub does, drawn with invented parties and numbers. Each links to the product page with the detail. A car brand’s owner app sits where the app (eMSP) is, run by the brand or its charging-service provider.

1. Architecture

Who connects to Hub, and how

Operators on the left, apps and peer hubs on the right, data customers below. Select any part.

Illustration

How Getz Hub connects charge point operators and mobility apps

Operators publish once to Hub over OCPI. Hub applies agreements and visibility rules, then delivers to each participating app in the OCPI version it speaks.

CPO back officeCPO on Getz NetworkForecourt networkGetz HubEV charging appFleet or brand appPeer roaming hubData customers

Getz Hub: the neutral roaming layer

Hub checks every message against roaming agreements, visibility rules and each partner’s capabilities, records why it routed it, translates between OCPI versions and checks roamed charge records against the agreed tariff.

Use Tab to reach the diagram, then the arrow keys to move between parts.

2. OCPI integration

The OCPI integration flow

Step through the credentials handshake between your back office and Hub.

Illustration

The OCPI credentials handshake with Hub

How a new partner’s back office and Hub exchange credentials and agree on a version. Step through it.

You receive a registration token (Token A)

After you submit your details from your onboarding link, Hub issues a Token A bound to your partner record. It is shown once, works only for the registration calls (versions, version details and credentials), and expires with the link.

Illustration of the OCPI 2.2.1 / 2.3.0 credentials module as Hub implements it. In 2.1.1 the token is sent unencoded; in 2.2 and later it is Base64-encoded.

3. Partner onboarding

The partner onboarding workflow

Nine steps, who does each one, and when activation becomes possible.

Illustration

Partner onboarding, step by step

The nine steps every partner goes through, who does each one, and when activation becomes possible.

1. Create partner

Hub staff send you a single-use, expiring onboarding link, or create your partner record directly. The link can be prefilled with your organisation name and the roles you are expected to hold.

Illustration of the onboarding workflow built into Hub. Timelines depend on your back office and the tests; none are promised.

4. Roaming transaction

A roaming transaction, end to end

Follow one roamed charging session through Hub, message by message.

Illustration

One roamed charging session, end to end

A driver of one app charges at another operator’s charger. Follow the OCPI messages through Hub.

The CPO publishes its location and tariff

The CPO pushes locations and tariffs once. Hub delivers them to each app it has a roaming agreement with, if the CPO’s visibility rules allow that app to see the location.

Illustration of the OCPI message flow through Hub. It shows how Hub routes messages; it is not a live simulation and does not show the app’s own driver pricing, which happens after Hub.

5. Tariff check

Tariff check and mismatch handling

See how a charge record is re-priced, and what happens when it does not match.

Illustration

Tariff check and mismatch handling

Pick what the operator’s charge record says. Hub re-prices the same session from the agreed tariff and compares totals. Synthetic numbers in US dollars.

The charge record the CPO sent
Agreed tariff (shared by the CPO over OCPI)
EnergyUS$0.42 per kWh
Session feeUS$0.50
Idle timeUS$0.10 per min
VAT15.5%
Session: 32.4 kWh, 10 minutes idle
LineHub re-pricedCPO’s record
Energy, 32.4 kWh × US$0.42US$13.61US$14.90
Session feeUS$0.50US$0.50
Idle time, 10 min × US$0.10US$1.00US$1.00
Subtotal excluding VATUS$15.11US$16.40
VAT 15.5%US$2.34US$2.54
Total including VATUS$17.45US$18.94

Price mismatch of US$1.49: held

The CPO’s total is higher than the tariff gives. Hub holds the record before it reaches the app. The record itself is never changed.

Finance staff review the held record and decide, with a reason:

Illustration with invented numbers. Hub’s check compares the record with the agreed tariff; it does not test the charger’s meter or the app’s own driver price.

6. Visibility controls

Data visibility controls

Change the operator’s settings and watch the visibility rules decide.

Illustration

Will this app see this location?

Change the CPO’s settings and watch Hub’s visibility rules decide, in their fixed order. The first rule that applies decides.

The location
The CPO’s rule for this app
Agreements and tokens
  1. Explicit deny rule for this appno: continue
  2. Private or home locationpublic: continue
  3. Explicit allow rule for this appno: continue
  4. Roaming agreement in force for Locationsshare
  5. Defaultnot reached

Shared with the app

The roaming agreement covers Locations, and the location is public.

Illustration of Hub’s visibility precedence. Staff can run the same decision for a real location in the decision tester without changing anything.

7. Routing decisions

A routing decision, explained

Change the conditions and read the decision trace Hub records.

Illustration

Why did this charge record go where it went?

A CPO sends a charge record for a driver of another app. Change the conditions and read the decision trace Hub records.

Conditions
  1. No looppass
  2. Hop limitpass
  3. Sender activepass
  4. Agreement in forcepass
  5. Visibility allowspass
  6. Receiver supports the modulepass
  7. Receiver connectedpass

Routed to the app

loop check passed hop limit ok source active agreement in force visibility allows capability present destination connected routed

Illustration of the routing engine’s fixed order of checks. Each live decision keeps its trace and correlation id so it can be explained later.

Seen enough to start?

Tell us who you are and what you want to connect.