Tokens

A token is a unique identifier that authenticates a driver to start a charging session.

​

Overview

Tokens are the central object for authenticating and authorising charging sessions: they define who is charging on a network and whether they’re allowed to. A token (shown as a charge key in the Connect UI) is an umbrella over several identification technologies: RFID cards, virtual identifiers in an app, and vehicle identification by MAC address or VIN (known as Autocharge). Over roaming, the token is what lets a driver authenticate across networks, and what links each CDR to the party that should be billed.

​

Context

A token is primarily an eMSP object — it’s how a provider gives drivers access — but it works on both sides of a charge.

​

eMSP context

For an eMSP, tokens are how you identify your drivers and give them access to charge — on Spirii’s network, and over roaming across other networks too. You register and manage the tokens, and the billing customer on each one determines who’s invoiced for its usage. For roaming, tokens are exchanged with connected CPOs over hubs and direct integrations, so they must follow the roaming standard’s (OCPI) rules; we recommend eMI3 formatting like DK.SPI.C{customerPrefix} to avoid interoperability issues.

​

CPO context

For a CPO, tokens are a channel to sell access to your infrastructure. When a driver presents a valid token at a public, online location, the platform authorises the session and handles the rest.

​

Key attributes

​

Types and status

​

Types

​

Status

A token’s ability to start a session comes from two independent settings: Active (on Spirii’s CPO network) and Roaming (over roaming), so a token can have either, both, or neither. An expiry overrides both: once past its Expires at date, a token can’t authorise sessions regardless of those settings.

​

Used in