Public Charging (eMSP)
Module:
operations:emsp| Role: Workspace Admin (manage), Member (read), Platform Admin (licence + enable) | Licence: Provisioned by ev.energy
The eMSP (e-Mobility Service Provider) module lets your workspace authorise public-charging taps against your Charge & Earn balance. You register the RFID cards your drivers tap with, choose who pays for each card's charging, and see every authorisation as it happens. The card issuer (Paua for the trial) is set up once by ev.energy for every workspace. When a driver taps one of your cards at a charger, the issuer asks the eMSP and gets an instant approve or decline.
Getting set up
Two things happen before you can use the tools, and only the first needs anyone outside your workspace:
- A platform admin grants your workspace the
operations:emsplicence. This makes the module available to enable. (ev.energy does this for you as part of onboarding.) - Enable the module for your workspace. A workspace admin or owner turns
operations:emspon in workspace settings (a platform admin can also do it for you). Enabling automatically links your organisation into the eMSP: there are no keys or credentials for you to create or paste. Once it is on, theoperations:emsptools appear for your workspace. (If your organisation is not connected yet, enabling won't finish the link: the tools appear but report that the eMSP isn't set up. Ask ev.energy to confirm your organisation is connected, then turn the module off and on again.)
That is the whole setup. From here everything is done from inside your workspace.
Administering it from your workspace
All of the actions below are workspace-admin actions. Every change is confirm-then-apply: Eve shows you exactly what will happen and waits for your confirmation before it does it.
Your card issuer
There is nothing to set up. ev.energy runs the card issuer for the whole platform (Paua for the trial) and holds its credential. Turning the module on links your organisation to it, and your drivers' taps through that issuer are then authorised against your balance. You never create, see or rotate an issuer credential, and there is no issuer to suspend from your workspace: the module switch is your only control (see below).
Manage the cards
- Register RFID cards you hold, in a batch of up to 500. Each card needs both its chip uid and the id printed on it: any charger can read a uid, so the printed id is the proof a card is in hand. A registered card is usable and belongs to no driver yet.
- A driver activates a card (in the app or widget) by the id printed on it, which binds it to their account.
- Pause or resume a card — reversible, for a driver who has mislaid one and may still find it. A pause you make stays until you or ev.energy lift it: the driver can't resume it, and pausing a card the driver already paused makes the pause yours. A card frozen at its issuer is treated the same way.
- Return a card to your pool if the wrong person activated it, so the right driver can take it. This is the only way to recover a mis-issued card, and it is worth knowing about: the alternative below spends the card for good.
- Block a card if it is lost or stolen, or retire one you no longer want. Both are permanent — the card can never be activated again by anyone, including its original holder, and your pool is one card smaller. Both act on a card a driver is holding: a card still sitting in your pool has nothing to block or retire, and asking is refused.
Choose who pays for a card: your organisation or the driver
Every card has one payer, and it is the card's, not the driver's. A new card is paid for by its driver, from their own ev.energy account, until you say otherwise.
- Make a card your organisation's to pay for, and its charging goes on your organisation's account, up to the credit limit ev.energy sets for you. A driver must have activated the card first: a card still sitting in your pool cannot be made yours to pay for, and asking is refused. If your credit limit is still zero, the change is made but Eve warns you, because every tap you pay for is declined until ev.energy raises the limit.
- Hand a card back to its driver to pay for when your organisation should stop paying, for example when the driver leaves. That is the step that stops the money.
- Because the payer belongs to the card, one driver can hold a work card you pay for and a personal card they pay for themselves.
- Blocking, retiring or returning a card to your pool hands it back to its driver to pay for, so the next person to activate it never charges on your account by accident. Pausing a card keeps its payer.
- List the cards your organisation pays for at any time, or the ones its drivers pay for.
Keep an eye on it
- View recent authorisations to see the taps that were approved or declined, and why.
- View the lifecycle log to see what was done to your organisation — cards frozen, blocked or returned to the pool; cards made yours to pay for or handed back to their driver — each with who did it, why, and when. A card handed back appearing here is worth knowing: it is the step that stops your organisation paying for it, and it is auditable.
- The two answer different questions: authorisations are what a driver tried to do, the lifecycle log is what your team did.
- Both look back 24 hours by default, up to 90 days, and tell you when a period holds more than one page carries — if it does, narrow the window rather than expecting a second page. You can narrow the lifecycle log to a single card or driver.
- Any member of your workspace can do both (see below).
Who can do what
| Action | Workspace Admin | Member |
|---|---|---|
| Register RFID cards | ✅ | — |
| Pause, resume, return to pool, block or retire a card | ✅ | — |
| Choose who pays for a card: your organisation or the driver | ✅ | — |
| List RFID cards, and who pays for each | ✅ | ✅ |
| View recent authorisations | ✅ | ✅ |
| View the lifecycle log | ✅ | ✅ |
In short: anything that changes state is workspace-admin only; the read-only views are open to any
member. Granting the licence is a platform-admin step (above); after that, the module switch is the
whole connection. Turning operations:emsp on connects your organisation to the eMSP; turning it
off disconnects it — your issuer's taps stop being approved, and your team stops seeing the
tools. There is no separate disconnect step.
Turning it off is not a pause. Your issuer's taps stop being approved as soon as you switch it off, and every card registered to your organisation is retired: nobody can use those cards again, whoever holds them. Switching the module back on reconnects the same organisation, with its history, but the old cards stay retired and must be re-issued. To stop one card or one driver rather than everything, freeze the card or hand it back to its driver to pay for instead.