Explains how outbound roaming works when Monta acts as your EMSP — how drivers charge on external networks, pricing, and enabling access.
Outbound roaming means your drivers can charge on external networks using their Monta account. This article explains how it works when Monta acts as your EMSP.
How outbound roaming works
- Your driver arrives at a charge point on an external network.
- They open the Monta app and start a session at the external charge point.
- Monta sends an authorisation request to the external network (CPO) via OCPI.
- The CPO starts the session and reports energy and duration back to Monta.
- Monta charges the driver using their Monta Wallet.
Which networks are available?
Monta has roaming agreements with many networks across Europe. The available networks depend on your operator account settings and your country.
Your drivers can see available roaming charge points on the Monta map.
Pricing for outbound roaming
The external network sets the price for their charge points. Monta adds a platform fee. Drivers see the total price before starting a session.
Enabling outbound roaming for your drivers
Outbound roaming is available by default for Monta drivers with a funded Wallet. You can restrict which networks your drivers can access.
See your roaming margin
Once you set your own outbound roaming prices, the Settlement view shows what that pricing is actually earning you. Pick a month and see, grouped by roaming partner, what your drivers paid you, what the CPO cost you, and the margin left over — down to the individual session and charge.
In Monta Hub, go to Roaming → Outbound Roaming → Managed and open Settlement.
The three summary cards
The cards at the top of the view summarise the whole month:
- EMSP Wallet — what your drivers paid you over the period, with the total sessions and kWh behind it.
- Pending CPO cost — what the roaming CPOs are expected to charge you for those sessions, based on what they've reported so far.
- Net margin (forecast) — what's left after CPO cost and Monta's fee, with Margin % (the margin as a share of what your drivers paid) and Avg / kWh (the average margin you made on each kWh delivered).
It says forecast because CPO costs arrive on the CPOs' own CDRs, which can land days after the session. The margin firms up as those costs come in.
The partner breakdown
Below the cards is one row per roaming partner, so you can see which relationships earn and which cost you:
- Sessions and kWh — the sessions and energy confirmed by that CPO's CDRs. A charge with no CDR yet counts towards neither.
- Driver paid — what your drivers' Wallets were charged at that partner's charge points.
- CPO cost — what that CPO charges you for the same sessions.
- Margin — driver paid, less CPO cost, less Monta's fee. It can be negative, and the view marks whether a partner is making or losing you money.
Open a partner to see its sessions, and a session to see the individual charge, so any figure can be traced back to what produced it.
Why a figure shows a dash
A dash (—) means Monta doesn't have the data to state that figure yet. It does not mean zero.
This is most often because the CPO hasn't sent the CDR for a session yet, so there is no cost to report against it. A genuine zero is shown as 0. Figures are also left as a dash rather than added together when a partner's sessions span more than one currency.
Settlement is an always-current read, so figures fill in as the missing data arrives — a month can still change after it has ended.
Partners shown as "Unknown"
Some charges can't yet be attributed to a specific roaming CPO, because the session's CDR hasn't arrived or doesn't identify the operator in a way Monta can resolve. Rather than hiding these charges or spreading them across the named partners, they're grouped into a single Unknown partner.
Unknown behaves like any other row — open it to see exactly which sessions sit behind it. Charges move out of Unknown to their named partner once the missing CDR data arrives.
Related articles