For charge point operators
Reach more drivers through one Hub integration
Connect your back office to Hub once. The apps you agree to roam with can then show your chargers and start sessions on them, at your price and under your visibility rules. Joining Hub costs operators nothing.
The partner portal: each partner sees its own data, and only its own. Synthetic demo data.
- Partner isolation: a partner never sees another partner’s data
What connecting means for an operator
- One connection
- to every participating app you agree to roam with
- Three OCPI versions
- 2.1.1, 2.2.1 or 2.3.0, translated for each app
- Your tariff
- reaches each app as you published it
- Free to join
- publishing your chargers costs operators nothing
Reach
Sessions from apps drivers already use
Drivers search in the app they already have, whether they are in Borrowdale for a meeting or on the road to Bulawayo. Through Hub, every app you have an agreement with can show your locations, live availability and tariff in US dollars or ZWG, and start and stop sessions on your chargers.
You keep your own app and your customer relationship. Hub adds other apps’ drivers; it does not replace you.
Which apps you can reach depends on who is connected to Hub and which agreements you accept. Ask us about Zimbabwean counterparties and the inputs for a quote.
- Agreements per app and per OCPI module, accepted by you
- Remote start and stop routed to your back office
Roaming agreements: which partners roam together, for which OCPI modules, from when. Synthetic demo data.
- An agreement routes only once both sides accept the same revision
Control
Your visibility rules apply everywhere
Visibility is fail-closed: a location reaches an app only when your rule or an agreement allows it. Fleet, home and private sites stay hidden unless you allow a specific driver token, and their precise coordinates are protected in logs and exports too.
- Test a rule before you publish
- Unpublish a site and apps that may no longer see it are told
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.
- Dry run: nothing changes
- Home and private locations stay hidden by default
Records
See a billing mismatch before your partner does
Hub re-prices every charge record you send from your own tariff. One that does not match is held before it reaches the app, so you can correct it instead of hearing about it at month-end.
- Checked against your tariff, including tax, idle and reservation fees
Charge records checked against agreed tariffs: mismatches are held until released. Synthetic demo data.
- Overcharged records are held from the eMSP
- Hub staff release a held record with a reason; every decision is audited
Your path
From enquiry to first roamed session
Step 1: Enquiry
Tell us about your network and back office using the form below.
Step 2: Onboarding link
Register your parties and complete the OCPI handshake from your back office.
Step 3: Agreements
Accept roaming agreements with the apps you want to work with, module by module.
Step 4: Live roaming
Roamed sessions flow, with both sides watching deliveries and assurance results.
Questions operators ask
Before you connect
Will Getz use our data to compete with us?
Hub never widens your visibility and never shares your data with another partner or another Getz business. It routes sessions only between you and the app that owns the driver’s token.
Our back office does not speak OCPI 2.3.0.
You do not need it. Hub translates between 2.1.1, 2.2.1 and 2.3.0.
What does it cost an operator?
Joining Hub and publishing chargers costs operators nothing: the party that starts a roamed session pays the per-session fee, usually the app. See the pricing model.
Who resolves billing disputes?
Hub re-prices every charge record against your own tariff and holds any that do not match before they reach the app. It does not verify the charger’s meter. Commercial disputes stay between you and the app; complaints and settlement questions about Hub’s handling go to support@getzcharging.com.
Do we have to use Getz Network as our back office?
No. Any OCPI back office can connect, and there are no bundles: Hub, Getz Network and Getz EMP are separate products with separate contracts.
Can we keep connecting directly, and what happens if we leave?
Hub uses standard OCPI, so your back office keeps working with any other OCPI partner. When an agreement ends, the app stops receiving your new locations at once, its commands are refused with a recorded reason and each side is told the other is suspended. Session updates and charge records of sessions that started while it was in force are still delivered for 90 days after it ends; after that they are refused, with a recorded reason both of you can see. You can give notice from your partner portal. If you leave Hub, your credentials are revoked, routing to and from you stops, and your history and ended agreements stay on record rather than being deleted. Ask us about exporting your records during diligence.
Which apps can see our locations?
Only apps with a roaming agreement in force with you, or that your visibility rules name, and never your private or fleet sites unless you allow a specific driver token. Visibility and privacy controls.
Can dealer or destination chargers join through us?
Yes, if your back office runs them: a back office that serves several sites or owners lists each as its own OCPI party with its own agreements. Car brands can read about the options on the automotive page.
Do our sites appear in Hub’s public data products?
Only locations you publish as public are served by the read API and data feeds, and a location you unpublish is withdrawn from them. Charging data API.
Enquiry
Connect your network to Getz Hub
What happens next
Tell us about your network. We reply by e-mail, usually with a few technical questions and then an onboarding link.
Joining and publishing your chargers costs nothing: the party that starts a roamed session pays its fee.