In the simulation the CPO creates the charge detail record and sends it to the eMSP for billing.
Simulated copies · no peer is connected
CPO
Session COMPLETED. CDR sent.
eMSP
CDR received for billing.
Session Completed
Charging Receipt (CDR)
Total Energy:
0.00 kWh
Duration:
0 min 0 sec
Total Cost:
€0.00
What's Happening?
Step 5: Billing
The session is over. A Charge Detail Record (CDR) is created for billing purposes.
OCPI message
POST/cdrs
The CPO sends the final CDR to the eMSP for invoicing.
Test this flow runs against an eMSP endpoint you have registered. The endpoint test grades your endpoint's answer to each Session push. It does not read the stored Session back.
What OCPI 2.2.1 defines for this lesson
Modules in OCPI 2.2.1
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.