New releases: 27.11.2025

Driver socket fallbacks

Some charger vendors do not allow configuring a custom free-vending token. To support customers who assign a dedicated “free vending” token to a specific driver, we introduced driver socket fallbacks.

A driver socket fallback lets you bind a specific charger socket to a designated driver. When a transaction starts and the presented token does not match any known driver, the system automatically assigns the consumption to the fallback driver for that socket.

Example

• Driver 1 has RFID token 1111111.

• Driver 2 has no RFID tokens but is configured as the fallback driver for charger TEST_CHARGER, socket 1.

If a session starts on TEST_CHARGER / socket 1 with token 1111111, consumption is assigned to Driver 1.

If a session starts on the same charger and socket with an unknown token such as 000000, consumption falls back to Driver 2.