01Case study · eMSP
Building an eMSP on roaming connections rather than capital
A fleet-card business already had the drivers. What it did not have was a charging network — and no intention of building one.
0
Chargers owned
6
Roaming partners connected
1
Invoice per fleet, per month
The deployment
Profile
- Existing base
- Corporate fuel-card customers with mixed fleets
- Assets
- None — the product is the driver relationship
- Protocol
- OCPI 2.2.1 in the eMSP role
- Billing
- Post-paid monthly against a corporate account
The problem
What was in the way
- 01Drivers were carrying four charging apps and four wallets, and expensing each separately.
- 02Every network billed differently, and nothing could be checked against what the drivers had actually consumed.
- 03Building a charging network was never the plan — the business is the account relationship.
- 04Corporate customers wanted one invoice with per-vehicle attribution, not a folder of receipts.
The approach
What was actually done
Each step names the mechanism rather than the outcome, so you can judge whether it would transfer to your situation.
Connect rather than build
OCPI credentials handshakes with six partner networks brought their locations, live status and tariffs into one app. Each connection took about a day technically; the commercial agreements took considerably longer, which is the usual ratio.
One token, every network
Driver tokens are published to partners so a single identity authorises at any connected charger. The driver sees one app and one balance regardless of whose hardware they are standing at.
CDRs reconciled, not trusted
Inbound charge detail records are stored and matched against each partner statement, so a disputed line can be traced to the session that produced it rather than argued in the abstract.
Corporate billing on top
Sessions roll up per driver, per vehicle and per department into a single monthly invoice with GST, which is the artefact the customer actually buys.
The outcome
What changed
- A charging product live without a single charger on the balance sheet.
- Partner invoices verifiable line by line against stored CDRs.
- One monthly invoice per corporate account, with per-vehicle attribution.
- New partner networks added as a credentials exchange rather than a project.
Platform
What was used
Roaming & OCPI
OCPI 2.2.1 connections for locations, tokens, sessions, CDRs and remote commands — as CPO, as eMSP, or as both.
Driver app & QR charging
A mobile web charging flow that starts from the QR sticker, plus native apps for the drivers who come back.
GST invoicing
GST-compliant invoices and receipts for drivers, fleets and partners, with HSN/SAC codes, tax splits and sequential numbering.
RFID & fleet authorisation
RFID and ID-tag management with driver groups, whitelists, per-driver limits and post-paid fleet billing.
Would the same approach work for you?
Tell us your constraints and we will say honestly which parts of this transfer and which do not.