Back to Roaming

EMSP: Self-Managed Outbound Roaming

How to set up your own outbound roaming connections to CPOs with the Monta Roaming team, and track usage, sessions and CDRs in Monta Hub.

Help Center / Monta Hub / Roaming / EMSP: Self-Managed Outbound Roaming

How to set up your own outbound roaming connections to CPOs with the Monta Roaming team, and track usage, sessions and CDRs in Monta Hub.

For: Operators using Monta Hub as an eMSP (sending your own drivers to external charge points)

Self-Managed Outbound Roaming lets you set up your own roaming connections directly with charge point operators (CPOs), so your drivers can charge on their networks on terms you've agreed. You then track all usage, connections, parties and sessions for those connections in Monta Hub.

This is different from Managed Outbound Roaming, where Monta provides and manages the CPO connections for you. New to roaming? Start with the Roaming overview.

Key terms

  • Party — the roaming CPO you're roaming with.
  • Connection — the actual OCPI connection. A single connection can carry many parties.
  • CDR — the raw Charge Detail Record for a session. It is raw session data, not an invoice.

Where to find it

In Monta Hub, go to Roaming → Outbound Roaming → Self-Managed.

Before you start

The roaming CPO you want to connect to must use OCPI 2.1.1 or 2.2.1 and have the Tariffs module enabled. If they don't, the connection can't be set up as a Self-Managed Roaming connection.

Setting up the connection

Self-Managed outbound connections are established together with the Monta Roaming team:

  1. Agreement — sign an agreement directly with the roaming CPO. This is made between you and the CPO, outside the Monta platform.
  2. Bring in the Monta Roaming team — open a shared channel between you, the CPO and the Monta Roaming team.
  3. Connection — the Monta Roaming team establishes the Self-Managed outbound connection with the CPO.
  4. Prerequisites — the CPO must be on OCPI 2.1.1 or 2.2.1 with the Tariffs module (see above).
  5. Confirmation — once live, the connection appears under Outbound → Self-Managed → Parties / Connections with the status Connected.

To get started, contact the Monta Roaming team.

Verify the tariff and run a test session

Once you're connected to the CPO, you can review the tariff the CPO has sent via the API or your WL App to confirm the correct price has been applied before your drivers charge.

You can also run a test session at one of the CPO's charge points to verify the price in practice. The session and its CDR are made available in near real time, so you can check the tariff is correct rather than waiting for the first invoice to surface a problem.

What your drivers pay

In this first release, Self-Managed Outbound Roaming uses pass-through pricing: your driver pays exactly what the CPO sends via OCPI for the session. There is no separate eMSP markup applied on top of the CPO's price.

How you pay the CPO

Important - how you pay the CPO: Under Self-Managed Outbound Roaming, Monta does not settle with the CPO on your behalf and does not move money out of your Monta wallet for these sessions. The CPO invoices the Monta Operator directly, and you pay the CPO directly. See Roaming pricing and fee structure for how this differs from Managed settlement.

A CDR is not an invoice — it's the raw session data for each charge. The CPO sends you a separate invoice. If you wish, you can use the CDR export from Monta Hub to reconcile against the invoice and the CDRs the CPO sends you, and to verify what you're being billed for.

Credit and dispute risk sit with you. If a driver doesn't pay, an invoice isn't settled, or there's a dispute between you and the CPO, that is entirely between you and the CPO. Monta is not involved financially or legally in settling these sessions.

See your data and download CDRs

Under Roaming → Outbound Roaming → Self-Managed you'll find:

  • Usage — your drivers' sessions, energy delivered, total spend, unique keys/contracts, top CPOs, and energy and country share. Filter by 7, 30 or 90 days, year-to-date, or all time.
  • Connections — your connections to CPOs and hubs, with locations and status.
  • Parties — CPOs you're connected with, including connection type, OCPI version and status.
  • Sessions — every session your drivers run on those CPOs. Open a session to see full details, the raw CDR and the OCPI logs. Use Download CDR batch to export a CDR/Tx file for reconciliation or dispute handling.

Related articles