Two directions of roaming
Inbound roaming (CPO)
A driver from another network charges on your charger. You earn revenue. Spirii invoices the driver’s eMSP or roaming hub and pays you.
Outbound roaming (eMSP)
Your driver charges on another network. You owe that network. Spirii receives their invoice and bills you on a consolidated basis.
Inbound roaming: getting paid
1
The session is authenticated
Over a roaming hub or a direct connection, depending on how that partner is reached.
2
The CDR is shared back
Spirii generates the CDR and returns it to the driver’s eMSP over the same protocol.
3
Spirii invoices the roaming partner
Priced on the roaming tariff set for that location. You enter that tariff gross, but the eMSP is billed the net amount, and net is what the session is worth to you. See Roaming pricing for how the tariff is chosen and when a change takes effect.
4
Spirii collects and pays you
Funds are collected from the roaming partner, and your share reaches you on a self-billing invoice.
Outbound roaming: consolidated billing
1
The external network invoices Spirii
At the rate that network has pre-agreed with Spirii.
2
Spirii invoices you
At the tariff configured for outbound roaming, which is the price your driver or their fleet company pays.
3
You receive one bill
A single consolidated invoice covering all outbound roaming by your drivers, rather than a separate invoice from every network they stopped at.
Roaming networks
Spirii connects to the roaming ecosystem through:
Enabling roaming on a location or a charge key reaches every network Spirii connects to. There is no per-hub configuration to repeat, and no separate agreement to negotiate with each one.
Dependencies & limitations
- Roaming pays on a different cycle to everything else. Roaming revenue reaches you in the same month Spirii invoices the roaming partner, while app, terminal, and charge key revenue pays the following month — so a single month’s income arrives in two parts.
- Peer-to-peer sessions are not in your Spirii payout. Where you settle directly with an eMSP, those sessions are excluded from the self-billing invoice and appear in the specification file marked as such. See Understanding your payout.
- Roaming sessions produce a statement, not a receipt. The statement carries no VAT details, because the invoice between networks is the VAT document for that consumption. See Receipts.
- Autocharge does not work over roaming. A vehicle charge key is read by the charger itself, so it only works on chargers managed by Spirii’s platform; your drivers need an RFID or virtual charge key to charge on partner networks. See Charge keys.
Related
Roaming connection
Publish chargers and connect charge keys across roaming networks.
Network coverage
Which networks your drivers can reach, and how to filter them.
Charge key billing
How your drivers’ sessions, roaming included, land on one monthly invoice.
Sessions and CDRs
The records that drive roaming invoicing and settlement.