Skip to main content
Getz EMP

Forecourts and retail

Keep EV drivers in your brand, not in someone else’s app

Give drivers a reason to charge at your forecourt or shop. Your stops on the N1 and N3, and your sites in town, already own the moment a driver pulls in. Getz EMP lets you own the charging relationship too: your app, your offers and your loyalty, with your sites alongside participating networks.

The forecourt case

Charging that works for the shop, not only the bay

  • Loyalty that counts charging

    Codes, vouchers and signed charging events your loyalty or CRM system can act on. How the two connect is scoped in discovery.

  • Offers that bring drivers inside

    Promotions scoped to a site, a tariff or a time, including offers co-funded with a shop or site partner.

  • A margin per site

    Markup by site, tariff or currency on top of the operator’s cost, with a floor so unfunded offers never sell below it.

  • Your sites and more

    Your own chargers plus operators on Getz Hub that agree terms with you, in one map under your name.

Promotions

Run the offer, then see what it did

Percentage, amount and free-kWh promotions, stackable or not, with coupon-only codes, limits and expiry. The pricing engine applies them at the session start and on the receipt.

  1. What you see: the discount, the site scope and the campaign code
  2. Why it matters: the code travels on every coupon event to the retailer

A forecourt offer limited to the retailer’s sites, with its campaign code.

Evaluate it on one offer

From a site offer to the loyalty event your till books

What happens to one coupon at one of your sites, and what each side records. Your loyalty or till system receives signed events; Getz receives nothing back from it.

  1. Step 1: Set up the offer

    A promotion limited to your sites, with your own campaign code, and a coupon code with a total limit, a per-driver limit and an expiry. A webhook subscription limited to your promotions receives their coupon events and nothing else.

  2. Step 2: The driver redeems it

    The driver enters the code in your app, with their loyalty number if they have one. A code for a site outside the offer is refused; without a session it waits for the driver’s next charge at one of your sites.

  3. Step 3: The discount is applied once

    When the operator’s charge record is priced, the discount comes off the bill once, even if the record is priced again.

  4. Step 4: Your system books it

    The coupon.applied event is the one to book, keyed on its redemption id. Events are signed, retried until you answer and repeat the same event id on a retry, so you deduplicate on it.

The event, field by field

What your till or loyalty system receives and records

Getz never sends the driver’s name, phone number, e-mail or Getz driver id to your system. Points, shop receipts and reversals stay in your own system.

Fields of a coupon event and what your system does with them
CapabilityWhat it isYour system
Event id The same on every retry or redeliveryDeduplicate on it
redemptionIdOne redemption, the same in its redeemed, applied and voided eventsBook one entry per redemption
campaignCode and couponCodeYour own campaign reference and the code the driver usedRecord both
site.locationIdThe operator’s location id of the charging siteMap it to your own store code
sourceSessionIdThe operator’s session idRecord it
discountThe amount taken off, tax included, in minor units, with its currencyRecord the amount and currency
appliedAtWhen the discount was appliedRecord it
loyaltyMemberRefThe loyalty number the driver typed, if anyCredit the member; without it there is no member to credit

The delivery log

See every coupon event your system was sent

The subscription page lists each coupon event with its attempts and your system’s answer. A delivery your system missed is retried; a redelivery carries the same event id, so your system books it once.

  • Signed coupon events with retries and redelivery

Signed coupon events and their delivery log.

  1. What you see: each coupon event, its attempts and the HTTP answer
  2. Why it matters: retries and redeliveries keep the same event id

One session, end to end

Follow one charging session from the driver’s phone to your books

The same session id, charge id and tax invoice number run through every step, so your support and finance teams can trace any charge in either direction.

Demo data A fictional partner, driver and site, from one session in the demo platform.

Partner
Kopano Charge (demo)
Driver
Lerato Mokoena
Site
Menlyn Park parking P2 (demo)
Session
0400fd56-7e93-49e3-be01-aa81be2ebf03
Operator session
HVC-S-MWQZWAQY
Charge
08368861-90f5-4b79-a09f-7d0e8387f652
Tax invoice
INV-000002: R 213.69 (operator R 162.52, margin R 23.30, VAT 15% R 27.87)
Credit note
CN-000002, R 15.00 goodwill, back to the wallet
Paid
R 198.69
Provider payout
SETTLE-PAYSTACK-MWQZWAQY (the wallet top-up)
  1. Driver app

    The driver starts, charges and pays

    The partner’s app shows the price before the start and reserves the estimate in rand. When the operator’s charge record arrives, the real cost is taken from the wallet and the rest released.

    Ties it together: Session id · Total paid

    Who looks at it: Your driver

    Demo data · this session

  2. Back office

    Your team sees the same charge, priced line by line

    The operator’s cost, your markup and fee, the adjustment, VAT and the driver total, with the operator’s session id in the title.

    Ties it together: Charge id · Operator’s session id · Driver total

    Who looks at it: Your operations and support team

    Demo data · this session

  3. Receipt and tax invoice

    The driver gets a tax invoice in your company’s name

    Your legal name and VAT number, VAT at 15% and how it was paid. With a VAT number on file, the final receipt is the tax invoice (INV-…); a later correction is a credit note (CN-…) against it.

    Ties it together: Tax invoice number · Total paid

    Who looks at it: Your driver, and your finance team

    Demo data · this session

  4. Reconciliation

    Finance traces it to the ledger and the money that settled

    One trace links the platform and operator session ids, the operator’s charge record, the tax invoice, the credit note, the wallet ledger entries and the refund, and shows the quote at the start matched to the rated price. The provider’s payout is matched to the top-up by reference.

    Ties it together: Session ids · Invoice and credit note · Ledger entries · Payout reference

    Who looks at it: Your finance team

    Demo data · this session

The exception

When the card provider refuses a refund

A refund the provider refuses is recorded as failed, with the provider’s reason and every attempt. It is never counted as refunded, and never lost.

Demo data · another refund of the same driver, refused by the card provider

Who resolves it: when the card provider refuses a refund
WhoWhat they do
The card providerRefuses the refund and gives its reason.
Getz EMPRecords it as failed with the reason and attempts. A refund for a charge correction is retried after 15 minutes, 1 hour and 4 hours, then daily, and then escalated.
Your finance teamRetries it, or resolves it as paid outside (with a reference) or written off.
Your support teamAnswers the driver, with the refund and its reason in front of them.

Beyond retail drivers

Serve the fleets that already buy fuel from you

  • Corporate accounts

    Credit limits and monthly statements for business customers.

  • Company-pays rules

    Allowed sites, networks, hours and kWh per session, checked at every start.

  • Subscriptions

    Monthly plans for regular drivers, charged to the wallet or a card.

Questions from forecourt and retail brands

Do we need our own chargers?

No. Your app can show operators connected to Getz Hub that agree terms with you. If you do run chargers, they appear in your app like any other participating network.

Do we have to buy Getz Network or Getz Hub services as well?

No. Each Getz business has its own contract and exit. Your app reaches charging networks through Getz Hub as part of the platform; running your chargers on Getz Network is a separate, optional decision.

Is there a ready-made connector for our loyalty programme?

Not a named one. The platform sends signed events per event type and supports codes and vouchers; how they map onto your programme is worked out in discovery.

Getz EMP records the charging side: which promotion or code applied to which session and what it took off the price. A purchase in the shop is recorded by your own loyalty or point-of-sale system, so linking a charge to a shop visit is part of that mapping.

Put charging inside your brand

Tell us about your sites, loyalty programme and markets. We reply by e-mail to arrange a walkthrough on demo data.