OCPI 2.2.1
Compare this step across versionsThe charging simulation starts by asking the eMSP whether the driver's token may charge here.
Simulated copies · no peer is connected
CPO
No Session yet.
eMSP
No Session yet.
Ready to Charge
Please authorize to begin the charging session.
What's Happening?
What OCPI 2.2.1 defines for this lesson
Modules in this version
Locations
Sessions
CDRs
Tariffs
Tokens
Commands
Credentials
Hub Client Info
Charging Profiles
Payments
Bookings
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.