---
title: 'What is an eMSP, and why drivers should care'
description: 'eMSP, CPO, and roaming hubs explained without the jargon. How the pieces fit when you start a session in Europe.'
author: easyplug_team
date: '2026-01-12'
categories:
  - product
  - charging
tags:
  - emsp
  - roaming
  - drivers
imgSocial: what-is-an-emsp.webp
imgThumb: what-is-an-emsp.webp
toc_depth: 3
---

If you charge an EV in Europe, you already use an **eMSP** — even if you have never seen the acronym on a screen. Understanding the role helps when a session fails, a bill looks wrong, or a charger “works for everyone else.”

This post is a plain-language map of who does what at the pedestal, and where easyplug sits in that stack.

## eMSP vs CPO

Two companies are usually involved in a public charging session:

- **CPO (Charge Point Operator)** owns or operates the hardware: the pedestal, the cable, the power feed, and the software that talks OCPP to the station.
- **eMSP (e-Mobility Service Provider)** is the account you charge with: the app, the RFID card, billing, invoices, and customer support.

You can think of the CPO as the landlord of the charger, and the eMSP as the account that pays the bill and keeps your history in one place. Sometimes they are the same company. Often they are not — especially when you roam.

easyplug is the eMSP side of that equation. We do not need to own every charger to make it usable. We connect drivers to networks through roaming and direct integrations, and we keep app, RFID, and Plug & Charge on one contract.

## What happens when you hit Start

A simplified happy path looks like this:

1. You pick a charger in the easyplug app (or ask the agent).
2. We authorize the session against your contract.
3. If the station is on another network, that request may go through a roaming hub or a direct OCPI connection to the CPO.
4. The CPO tells the charger to allow energy.
5. Meter values flow back; after stop, a charge detail record (CDR) becomes your receipt.

Any hop can fail. That is why a session that works on “home” network chargers can still fail on a random highway bay: different path, different latency, different token rules.

## Why it matters at the pedestal

When a start fails, the problem is often at the **boundary** between eMSP and CPO:

- Your contract is not accepted on that network yet.
- The charger is offline at the CPO’s CSMS, even if the map still shows a pin.
- Roaming authorization timed out before the station unlocked.
- Tariff or payment rules rejected the session before energy started.

Knowing who owns the failure does not fix the cable — but it changes what you report, and it changes how we escalate. “App broken” and “station offline” are different tickets.

## One app, many networks

A good eMSP hides the alphabet soup. You should get:

- One login and one payment method
- One support path whether the charger is home network or roaming
- Clear prices before start, and the same numbers on the receipt
- A useful error when something fails — not a spinner that never ends

That is the bar we design for at easyplug.

## What’s next

If you want the next layer of detail, we have posts on [failed session starts](/blog/charger-wont-start-session), [roaming authorization](/blog/roaming-failed-authorization), and [how we think about the driver app](/blog/building-a-reliable-emsp-driver-app).

→ [Explore the product](/#features)