Skip to main content
Getz Hub

For automotive and mobility brands

Charging for your owners, without building a network

Give an owner app roaming access, feed public charging data into navigation and in-car systems, or publish dealer chargers to participating apps. Hub connects charging networks and apps; it does not build your app.

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
Your owner app connects like any mobility app; in-car systems read public data; dealer chargers publish like any network.

Three ways to work with Hub

Pick what your owners and dealers need

Which option fits

What each option connects, and how

The three ways an automotive or mobility brand can work with Getz Hub
CapabilityOwner app accessIn-car and navigation dataDealer and destination chargers
You connect aseMSP over OCPIData customer (read-only key or feed)CPO over OCPI
Drivers can start sessionsYesNoYes
Charge records checked against tariffsYesNoYes
Only public dataNoYesNo

Owner app: three routes

Your own app, a provider, or a branded app from Getz EMP

All three reach participating operators through Hub on the same terms. What changes is who builds and runs the app, and who you sign with.

Three ways to give an owner app charging access through Getz Hub
CapabilityYour own appA charging-service providerA branded app from Getz EMP
Builds and runs the appYour teamYour providerGetz EMP, under your brand
OCPI connection to HubYour team, as an eMSPYour provider, as an eMSPGetz EMP, as an eMSP
Driver priceYou set itAgreed with your providerYou set it in Getz EMP
Driver paymentsYour payment set-upAgreed with your providerGetz EMP wallets and local payments, through your merchant accounts
ContractsHub onlyYour provider; it connects to HubGetz EMP (separate from Hub); it connects to Hub

Who does what

Responsibilities in an owner-app charging journey

A typical split when your owner app roams through Hub. Your own contracts settle who does what on your side; Hub’s part is the same in every case.

Who is responsible for each part of an owner-app charging journey through Getz Hub
CapabilityYour brand, or the provider running your appCharge point operatorGetz Hub
Owner app and driver accountOwns the app and the driver relationshipNot involvedNot involved: drivers never sign in at Hub
OCPI connection to HubConnects as an eMSP, itself or through a charging-service providerConnects as a CPORoutes between the two
Roaming agreement Proposes it, per operator and moduleAccepts or counters itEnforces what both sides accepted
Starting a charge Sends the remote startStarts the chargerRoutes the command and relays the result
Price and paymentSets the driver price and takes paymentSets its tariffPasses the tariff through; takes no driver payment
Charge records Receives checked records and bills the driverSends records priced from its tariffChecks them against the agreed tariff and holds mismatches
Dealer chargers in apps Not involved, unless it also runs themThe back office running dealer chargers publishes them as a CPORoutes them to apps under the publisher’s visibility rules
Driver charging support First contact for the driverFixes the charger or its back officeKeeps the routing trace and relays issue reports; partners contact support@getzcharging.com with a correlation ID

In-car and navigation data

Public charging data with clear permission to use it

Scoped, rate-limited keys for locations, live availability and tariffs that operators publish as public. Usage is metered per key and hour, so both sides see the same numbers.

  • Read API, OCPI, GeoJSON or signed webhooks

Scoped, rate-limited keys for the read-only public API. Synthetic demo data: limits shown are examples, not a standard plan.

  1. Scopes: locations, tariffs, availability
  2. The key is shown once; only its hash is stored

Questions

For automotive teams

Do you support Plug & Charge (ISO 15118)?

Not in this release. Autocharge is supported: the car’s vehicle ID roams as an ordinary token, and if two apps hold the same ID Hub refuses to guess.

Can you build our branded owner app?

Hub connects charging networks and apps; it does not build apps. If you need a branded app, Getz EMP is a separate option with its own contract. Hub connects any owner app, whoever built it, on the same terms.

Do we need our own charging-service provider?

Not necessarily. If your team runs OCPI, your owner app can connect to Hub as an eMSP itself; otherwise a charging-service provider can run that connection for you. Either way, Hub treats it as one eMSP party under the same rules. Technical integration.

Who supplies the data for dealer chargers?

The back office that runs those chargers connects to Hub as a CPO and publishes their locations and tariffs, under its own visibility rules. For charging networks.

Can our owners charge across borders?

Only where hub peering and roaming agreements are in place. Tell us the countries your owners need. International hub connectivity.

Which networks would our owners reach?

Participating networks: operators connected to Hub that agree to roam with your app. We do not list networks until they have agreed to be named; ask us for the current picture.

Enquiry

Talk to the Hub team

What happens next

Tell us what you are exploring for your owners or dealers. We reply by e-mail.

We do not list or imply partnerships with any car brand; every conversation starts from your requirements.

Fields marked with an asterisk are required.