From the socket to the statement
One half talks to your chargers. The other prices, settles and reports. You see one platform; drivers see only your brand.
Everything between the socket and the bank
A central system that holds the socket
Chargers connect over WebSocket and stay connected. Start, stop, unlock, reset and update firmware over that live link.
- OCPP 1.6-J and 2.0.1, side by side, any vendor
- Every connector the market runs, GB/T included
- Faults raise the moment the charger reports them
| Accra Mall, Bay 3GH*DEX*E0311*1 | GB/T DC | Charging |
| Sarit Centre, WestlandsKE*DEX*E0142*1 | CCS2 | Available |
| Lekki Phase 1 RapidNG*DEX*E0087*2 | Type 2 | Finishing |
| Sandton City P2ZA*DEX*E0009*4 | CHAdeMO | Faulted |
Faults raise on the dashboard the moment the charger reports them, not on the next poll.
Tariffs you can correct after the fact
A session keeps the tariff it started on, and the events behind it. A pricing mistake is replayed and fixed rather than argued about.
- Per-kWh, per-minute, session and idle fees, combinable
- Prices by site, charger, time of day and driver group
- Free or discounted charging for staff, tenants and fleets
Collected as your agent, not as the seller
The charging is supplied by you. We collect for it and keep a commission, never the driver's whole payment. Two VAT positions, and the statement says so.
- Payouts on your schedule, one statement per period
- Refunds and chargebacks tied to the session that caused them
- Fleet and roaming invoices kept off the card lines
| Period line, example in USD | Amount |
|---|---|
| Energy supplied to drivers | 19,040 |
| Idle fees | 322 |
| Platform commission (6%) | −1,162 |
| Refunds | −68 |
| Settling to you | 18,132 |
The app is yours, down to the bundle id
Your developer account, your name, your domain. Nothing a driver sees says ChargeBase, and we publish no app of our own for it to sit beside.
- iOS, Android and a web flow for drivers who install nothing
- Map, live availability, start and stop, history, receipts
- Saved cards, guest checkout, push notifications
Your store listing
Your account, your reviews, your install base.
Your domain
charge.yourbrand.com, certificate included.
Your emails
Receipts sent from your sending domain.
Your support
Or ours, answering as you.
Cards for drivers who will never install an app
Depots, staff parking, tenant bays and fleets want a card that works and an invoice at month end. RFID and NFC are in every plan, app or no app.
- Tokens issued, suspended and reassigned from the dashboard
- Whitelists per site, charger and group, cached if the link drops
- Add the whitelabelled app later, same platform and cards
| 04:A2:19:7C | Depot fleet | Active |
| 04:B8:31:2E | Staff, night shift | Active |
| 04:C1:08:9A | Tenant · Unit 4 | Invoiced |
| 04:D5:44:B0 | Lost card | Suspended |
Authorisation is decided against the list you control, not the charger's own memory.
A dashboard over the whole estate
Live status, the event log, sessions with their derivation shown, tariffs, accounts and statements, all fed by the same stream the app is.
- Live feed over WebSocket, no refresh button
- Utilisation, revenue and uptime by site, charger and period
- Role-based access, full export, and an API behind all of it
Put in your own numbers
A commission on what drivers pay you, plus a flat monthly fee that does not move as the estate grows. See the plans →
Illustrative and tax-exclusive. The platform fee is invoiced separately, so it is not taken out of the settlement figure above. Energy cost, site rent and payment acquiring are yours and are not modelled here.
What is yours stays yours
| Asset | Owned by | Notes |
|---|---|---|
| Driver relationships and data | You | Exportable in full, at any time, in a documented format |
| App store listing and installs | You | Published under your developer account from day one |
| Brand, domains, certificates | You | On-demand TLS for custom domains |
| Tariffs and pricing rules | You | Edited by you, versioned, snapshotted per session |
| Charge point hardware | You | Any OCPP 1.6-J or 2.0.1 charger; no exclusivity |
| Central system and event log | ChargeBase | Operated for you; your slice of the log is yours to export |
| Where the system runs | Your choice | Our managed platform by default, a dedicated instance on Extended and Enterprise |
| Payment collection | ChargeBase, as agent | On your behalf: the supply is yours, the commission is ours |
Charger connections run on TLS with per-charger credentials, and dashboard access is role-scoped and audited. Need more separation than that? Extended and Enterprise can run as a dedicated instance in the region your policy names. Deployment options →
The ones operators actually ask
No. If it speaks OCPP 1.6-J or 2.0.1 it connects: point it at a URL and it appears in the dashboard. Mixed estates are the normal case.
Four to six weeks to a published app, and much less to a working dashboard. App store review is usually the long pole, not the integration.
You supply the charging; we collect for it as your agent and keep a commission. Two VAT positions, two taxpayers, and a statement built to be handed to an accountant as it is.
You keep the listing, the installs, the domain and the drivers, because they were never ours. Sessions and driver records export in full, and the chargers move with one URL change.
No. The Platform plan is the dashboard, tariffs, settlement and RFID cards with no app in front of it. Add the app later without moving platform or reissuing cards.