Token authentication

Tokens are how your drivers authenticate to charge, and issuing them is how you grant your fleet access: on your own depot and workplace chargers, and out on roaming networks across the ecosystem. This is where you create tokens, decide how they’re billed, and control where they work.

​

Overview

A token — a charge key in Connect — identifies a driver or vehicle at a charger. When a session starts, the platform recognises the token, authorises the charge, and knows how to bill it, with no need for the driver to enter payment details each time. As a fleet or mobility operator, you issue tokens to your drivers and they reach two kinds of charger: The Tokens component covers what a token is and how billing attaches to it; this page is how you issue and manage them.

​

Token types

You choose a type when you issue a token, and it decides how the driver authenticates. Some chargers also support Plug & Charge, a certificate-based method where the vehicle authenticates itself on plug-in. It’s enabled on the charger rather than issued as a token type.

​

Issuing tokens

You create and manage tokens in Connect under Charge Keys. Onboarding a whole fleet at once, you can bulk-upload tokens from a CSV of UIDs and labels, up to 100 per upload, rather than creating them one by one.

​

Billing and ownership

Every token has a billing customer who’s invoiced monthly for all its sessions — the model that lets a fleet consolidate every driver’s charging into a single invoice. Alternatively, a driver can link their own payment card to a physical key in the app, so their sessions are billed to them directly. When you hand a physical key to a driver, they finish the link themselves: they add the key in Spirii Go or your branded app, attach a payment method (or rely on the company billing you’ve set up), and activate it. From then on they can charge by tapping the key, without opening the app.

​

Where a token works

​

On your own sites

At any of your public locations, an active token works straight away. To reserve a depot or workplace for your fleet alone, put its tokens in a token group (a charge key group in Connect) and bind that group to the location: only tokens in the group can charge there, and they can do so even when the location isn’t public. How that interacts with a location’s other settings is covered in Location access.

​

On roaming networks

Enable a token for roaming and it authorises on other operators’ chargers across the networks Spirii connects to — the on-the-route half of a fleet’s charging. See Roaming connection for how roaming access is established.

​

Dependencies & limitations

• A token needs a billing customer and activation. It can’t charge until it’s active and owned by a billing customer.
• Labels and IDs are unique. Each token’s UID and label must be unique in Connect.
• Bulk upload is capped. A CSV upload creates up to 100 tokens at a time.
• Requiring a token is a charger setting. Whether a charger demands authentication or lets charging start on plug-in is set on the charge box, not the token.
• Token groups override location settings. A token group always grants its members access, ahead of a location’s public setting and opening hours — see Location access.

​

Related