01Solutions · Operator type
Run a driver brand across networks you do not own
An eMSP sells access and convenience, not electrons. The product is a driver relationship: one identity, one payment method, one history, across as many networks as you can sign. That requires roaming plumbing, a wallet that reconciles, and an app that is unmistakably yours.
e-Mobility service provider
Does this sound familiar
Where you probably are right now
- 01You have a driver base — a fleet, a card programme, an OEM customer list — but little or no hardware.
- 02Your drivers currently juggle four apps and four wallets.
- 03You need to settle with each CPO on CDRs you can verify.
- 04You may also own a handful of chargers, and want them in the same app.
What gets in the way
The problems, and what answers each one
Every answer links to the feature that does the work, so you can check the claim rather than take it.
Your drivers cannot charge on partner networks
OCPI 2.2.1 in the eMSP role: pull partner locations and live status into your app, authorise your tokens at their chargers, and start sessions remotely.
Every network bills you differently
Inbound CDRs are stored and reconciled against partner statements, so what you were billed and what your drivers consumed can be compared line by line.
The app has someone else’s name on it
White-label driver apps, portal and receipts carry your brand end to end. zevOS does not appear to your drivers.
A driver complains about a session on someone else’s charger
The inbound CDR, the token used and the partner’s own session identifier are all stored against the driver’s history, so support can answer with evidence and raise a dispute with the CPO that references their record rather than yours.
What changes
What you can do that you could not before
- One wallet and one invoice across every network you have signed
- Verify a partner’s bill against the CDRs behind it
- Launch a branded driver app without a mobile team
- Answer a roaming dispute with the partner’s own CDR attached
Commercial shape
Per-session platform fee
Your economics are per driver interaction rather than per charger, so the fee should sit on sessions rather than on assets you do not own.
How pricing worksQuestions
What people in your position ask
Can we be both a CPO and an eMSP?
Yes, and most networks eventually are. The same tenant can publish its own chargers to partners and consume theirs.
How do we price a roaming session to our driver?
However you choose. You can pass the CPO’s retail price through unchanged, apply a fixed margin, or price your own tariff independently of what you were charged — the wholesale cost and the retail price are stored separately on every session.
What happens when a partner network is unreachable?
Their locations are shown from the last successful sync with the sync time visible, and remote starts against them fail cleanly with a message the driver can act on rather than a spinner.
Related
You might also be this
Talk through your e-mobility service provider setup
Bring the specifics — the sites, the hardware, the constraints. That conversation is more useful than a demo.