Token
In OCPI, what a driver starts a session with, such as a charging card, a key fob or an app account; it carries the contract ID of the driver's provider.
Explained in
How does a token reach the charger?Cached token lists or real-time authorisation: the four whitelist types of OCPI, and what each one means when the driver taps the card.A cached token is fast: the operator already knows it and can accept it at once. A real-time check gives the provider control, for example over a blocked card, but it takes longer, which OCPI notes can mean a less pleasant wait at the charger.
Also in
- What do CPO and eMSP exchange in OCPI?Before, during, after
- One CDR, field by fieldThree checks the provider runs
- How is every vehicle ready by morning?Knowing the vehicle
- How are charging costs tracked across a fleet?Public sessions arrive as records
- One night at the depot, fully understoodThe night in seven moments
- How are truck charging sessions planned and booked?A reservation in OCPI
- How is truck charging paid for?From session to invoice
- One break, fully understoodThe day in seven moments
Named in 2 further stops as well.
Related terms
- OCPIOpen Charge Point Interface: an open protocol for roaming between operators and e-mobility service providers.
- eMAIDThe contract ID of an e-mobility contract, carried in the contract certificate for Plug & Charge.
- Whitelist typeOCPI's rule per token for cached or real-time authorisation: ALWAYS, ALLOWED, ALLOWED_OFFLINE or NEVER.
- EVRoaming Foundation: OCPI 2.3.0, Tokens module: whitelist types and real-time authorisation. https://github.com/ocpi/ocpi/blob/2.3.0/release/core/mod_tokens.asciidoc. Checked 09 Oct 2026.