When a charging session is started, the platform automatically identifies the owner of the charge key and applies the correct billing setup - without the driver needing to manually select or enter a payment method.
Charge key types
Spirii supports three types of charge keys:
- RFID key – A physical key or card used to authenticate and start charging sessions.
- Virtual key – A digital key used to authenticate charging directly through the app.
-
Vehicle key – Authentication based on the vehicle’s MAC address or VIN (Autocharge).
Learn more here: Autocharge: Revolutionising Fleet Management.
Before a charge key can be used to start charging sessions, it must be created and activated in Connect and assigned to a billing customer.
A charge key can be configured in two ways:
- Credit card billing: The key is linked to a payment card through the app (available for RFID keys only).
- Monthly invoicing: Charging costs are assigned to a selected billing customer, who receives a single consolidated invoice covering all completed sessions for that month.
How to add a charge key in Connect
- Go to Charge Keys in Connect and click the "+" button (Create Charge Key)
- Select the Billing Customer.
This is the owner of the charge key and the entity that receives the monthly billing in case no credit card is attached to the key.
- Select the type of key - click on the desired box.
- Depending on the type, enter the UID (Unique ID) of the key.
- RFID: The physical and unique identifier of the RFID chip.
- Virtual: Autogenerated.
-
Vehicle: EV charging authentication via MAC address or VIN code (Autocharge).
-
Add a unique label for the key.
Examples include an RFID label (e.g. “DK.SPI.0001234”) or a fleet vehicle ID (e.g. “EVBUS.0007”). The value must be unique in Connect. - For virtual keys, select the app user who should have access in the app.
This can also be set for RFID keys for credit card association, however, is not needed in order to use the charge key (Drivers can also complete this step themselves upon receiving the key by adding it directly in their app).
- Select whether the key should be active immediately and enabled for charging and whether it should be able to be used for roaming networks worldwide.
-
Priority ensures critical vehicles (ambulances, police cars etc.) automatically receive higher charging priority when power is limited across simultaneous sessions.
Learn more here: Vehicle Charging Prioritization
-
Priority ensures critical vehicles (ambulances, police cars etc.) automatically receive higher charging priority when power is limited across simultaneous sessions.
- Define the Validity period (start and optional end date - end date can be left blank if not applicable).
-
Optionally, add a Billing reference and/or an internal Comment if needed for the key.
- Press Create.
The charge key is now created and ready to use in Connect.
You can also create multiple keys at once: Upload Multiple Charge Keys at Once
Read more about charge key groups here: Creating and Managing Charge Key Groups
Case: Depot charging (repeat vehicles/drivers, “own site”)
Goal: frictionless, reliable start of charging + clean internal billing.
Recommended charge key setup
- Primary choice: RFID keys as the default (most robust, least dependent on apps/devices).
-
Optional add-on: Vehicle keys (Autocharge) for “plug in and walk away” depot routines
- only if the fleet/vehicle brand behaves reliably -
Virtual keys: use when the depot operation is explicitly app-driven
Case: Semi-public host network (guest fleets + access requests + bookings)
Goal: controlled access to host sites + predictable charging via booking enforcement.
Recommended charge key setup
- RFID keys are the safest operational default for guest fleets (works across sites without relying on the driver’s phone).
- Vehicle keys (Autocharge) can work, but only if you’re confident the end-to-end flow supports it for the specific setup—truck charging is “high consequence” if it fails.
- Virtual keys are fine if the driver/app experience is the intended method, but they add dependency on app user/account setup.
What matters most in Connect
- UID correctness is everything (it’s what the platform uses to authorize sessions).
- Label is for humans: use it to make ops easy (e.g., Truck ID / license plate / unit number).
- Set the right Billing Customer so costs land on the right entity by default.
Best practices
- Use a consistent naming scheme for labels: e.g.
TRUCK-042,TRACTOR-12,VIN-last6, etc. - Keep keys Active and maintain validity windows (avoid surprise failures).
- Use bulk CSV upload for large fleets to reduce manual UID mistakes.