Skip to main content
Getz EMP

Technical overview

How the platform fits together

Driver apps and a back office on one EMP platform, open standards to the charging networks, and payments through your own merchant accounts.

Illustration

White-label EMP architecture

Your brand’s app and back office run on the shared EMP platform. Charging networks come through Getz Hub; payments through your merchant accounts; your systems through signed webhooks.

Your branded appYour back-office teamGetz EMP platformYour merchant accountsGetz HubParticipating networksYour systems

The Getz EMP platform (Getz runs it)

Getz runs and updates the platform. On it, your own eMSP organisation: drivers, pricing, wallets and data kept separate from every other brand on the platform. One or more trading brands per organisation.

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

Who does what

Three parties behind every session

A plain-language reading of the diagram for anyone sponsoring the project.

  • Your organisation supplies

    The brand, the store developer accounts, the merchant agreements and payment keys, the prices and margins, your support team, and the terms and privacy text your drivers accept.

  • Getz operates

    The driver app, the back office, the pricing engine and wallet ledger, the payment adapters and the connection to Getz Hub, updated for every brand at once.

  • Charging operators decide

    Who may charge at their sites, private sites included, and the tariffs they publish over OCPI. They run the chargers: power, connectivity, faults and restoring service. The platform respects their decisions.

Building blocks

What runs where

  • Driver apps

    iOS and Android from one codebase, with runtime brand settings and phone-number sign-in.

  • Back office

    Pricing, payments, drivers, fleets, roaming, support, content and brand settings, with role-based access.

  • Pricing engine

    Deterministic; quotes, live cost and the final charge use the same calculation, recorded for replay.

  • Wallet ledger

    Append-only entries, derived balances, holds before charging, reversing corrections.

  • Roaming

    OCPI 2.3.0 (and 2.2.1) through Getz Hub; operator data kept as received.

  • Webhooks

    Signed, per event type, optionally per fleet, with retries and a log.

Security and data

Safeguards in the platform

  • In place

    Separate organisations

    Each eMSP’s drivers, pricing, users and data are separate.

  • In place

    Real-time authorisation

    Every start is checked live: driver, token and payment method.

  • In place

    Provider callbacks re-checked

    Signature- or hash-checked and confirmed with the provider before money moves.

  • In place

    Fail closed

    A provider without credentials refuses with “not available yet”; no test shortcuts.

  • In place

    Audit trail

    Back-office changes to brand, pricing and payment rules are recorded.

  • In place

    Append-only ledger

    Wallet entries are never edited or deleted; corrections are reversing entries.

Where data is stored for a Zimbabwean deployment is confirmed with each partner in writing. See security and data for details.

Operations

Look up any session, driver, token or payment

The support console ties a ticket to the session, the charge record and the payment behind it, so your team answers a driver from one record instead of four systems.

  • Tickets with photos, linked to the session and payment
  • Back-office roles for support, finance and pricing

The support console: a driver’s tickets, sessions and payments in one place.

  1. What you see: tickets and one search for any record
  2. Why it matters: faster answers for drivers

Coming soon to the platform

What we are adding next, so you can plan.

  • Coming soon

    Plug & Charge with ISO 15118 contract certificates

    Plug in and charge, with no app or card at the charger.

  • Coming soon

    Google Pay

    One more way for drivers to top up.

  • Coming soon

    Local languages, starting with Shona

    The app in the languages your drivers speak.

  • Coming soon

    Charging that still starts when the EMP or Hub is unreachable

    Sessions that start even when a link is down.

Go deeper with our engineers

Bring your technical questions; we will walk through the architecture and your integration points.