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.
Three ways to work with Hub
Pick what your owners and dealers need
Owner app
Roaming access for your owner app
Connect your owner app as an eMSP and roam with participating operators. Autocharge vehicle IDs roam as ordinary tokens.
In-car data
Charging data for navigation
Public locations, live availability and tariffs through a scoped read-only key or a feed.
Dealer network
Publish dealer and destination chargers
Put dealer and destination chargers in front of drivers of participating apps, under your visibility rules.
Which option fits
What each option connects, and how
| Capability | Owner app access | In-car and navigation data | Dealer and destination chargers |
|---|---|---|---|
| You connect as | eMSP over OCPI | Data customer (read-only key or feed) | CPO over OCPI |
| Drivers can start sessions | Yes | No | Yes |
| Charge records checked against tariffs | Yes | No | Yes |
| Only public data | No | Yes | No |
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.
| Capability | Your own app | A charging-service provider | A branded app from Getz EMP |
|---|---|---|---|
| Builds and runs the app | Your team | Your provider | Getz EMP, under your brand |
| OCPI connection to Hub | Your team, as an eMSP | Your provider, as an eMSP | Getz EMP, as an eMSP |
| Driver price | You set it | Agreed with your provider | You set it in Getz EMP |
| Driver payments | Your payment set-up | Agreed with your provider | Getz EMP wallets and local payments, through your merchant accounts |
| Contracts | Hub only | Your provider; it connects to Hub | Getz 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.
| Capability | Your brand, or the provider running your app | Charge point operator | Getz Hub |
|---|---|---|---|
| Owner app and driver account | Owns the app and the driver relationship | Not involved | Not involved: drivers never sign in at Hub |
| OCPI connection to Hub | Connects as an eMSP, itself or through a charging-service provider | Connects as a CPO | Routes between the two |
| Roaming agreement | Proposes it, per operator and module | Accepts or counters it | Enforces what both sides accepted |
| Starting a charge | Sends the remote start | Starts the charger | Routes the command and relays the result |
| Price and payment | Sets the driver price and takes payment | Sets its tariff | Passes the tariff through; takes no driver payment |
| Charge records | Receives checked records and bills the driver | Sends records priced from its tariff | Checks them against the agreed tariff and holds mismatches |
| Dealer chargers in apps | Not involved, unless it also runs them | The back office running dealer chargers publishes them as a CPO | Routes them to apps under the publisher’s visibility rules |
| Driver charging support | First contact for the driver | Fixes the charger or its back office | Keeps 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.
- Scopes: locations, tariffs, availability
- 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.