OCPI charging session lifecycle

By Abhishek Uniyal · Updated

An OCPI Session is the charging record shared between a charging network operator and a driver's service provider. Follow its authorization, updates and completion, then read the charge detail record used for billing.

Labs and branches

Follow the charging session messages

Follow the lesson one message at a time. Each step names the parties, explains the exchange and links to the governing source. The outline lets you jump to the part you are investigating.

The lab lets you inspect authored exchanges before choosing an explicit sandbox run. Its observed response and captured evidence appear separately from the example. An endpoint handoff opens the matching test setup and waits for you to start it.

Where to go next

Common questions

How can I inspect a missing Session update?

Open the relevant message step, read its explanation and Sources, then compare the authored exchange with the lab evidence. A missing update and a CDR are separate things to inspect; the lesson does not infer a billing outcome from a missing message.

How can I investigate a rejected CDR?

Use the CDR step and its source-backed example to locate the field or check in question. To inspect your endpoint, follow Test this flow, choose the target in the test setup and explicitly start the run.

What changes in OCPI 2.2.1
Modules in OCPI 2.2.1
Sessions
CDRs
Locations
Tariffs
Tokens
Commands
Credentials
Versions
Hub Client Info
Charging Profiles
Payments · extension
Advertised sender and receiver interfaces

An endpoint declares how another platform can pull or push data. Credentials uses the same interface for both roles.

The header token is encoded

The request header carries an encoded token; the Credentials body still carries the raw token.

Billing records name the Token owner

A charge record names the country and company that own the driver's Token.