# Sessions

> The eMSP-side record of a charge one of your drivers ran, and what you bill them from.

An eMSP session is the record of a charge one of your drivers ran, and the basis for billing them for it. It is the mobility-side counterpart to the operator's [CPO session](/docs/platform/charge-point-operation/charging-sessions).

## Where a session comes from

A driver charges, on your own network or on someone else's. The operating CPO writes the charge up and sends it out over roaming as a **CDR** (Charge Detail Record). When a CDR reaches Road for one of your tokens, whether from Road's own CPO side or from an external operator, it becomes an eMSP session on your side. Sessions are created from those returning CDRs, not written at the station.

A CDR can arrive well after the charge, sometimes weeks or months later, so an eMSP session can appear, and land on an invoice, long after the driver actually charged.

## What the driver pays

A session is priced by the **billing plan** on the token that charged. That plan decides how the driver or fleet is charged for the energy and time on the session, and it is what the eMSP invoice is built from.

## Corrections

Sessions are not edited after the fact. A correction or refund is booked as a [credit session](/docs/platform/e-mobility-services/credit-sessions) against the original.

## In the API

eMSP sessions are served from the [MSP sessions](/docs/platform/reference/platform-api/msp-sessions) endpoints, and corrections come through [MSP credit sessions](/docs/platform/reference/platform-api/msp-credit-sessions).