Charging scenarios

Owned by jasmin.kljajic
Last updated: Jan 31, 2023 by Denis Leskovar
1 min read

Chargers can be configured in different ways.

You can configure it in a way that charging authorization is required, before charging. We support several types and all of them are configurable. User/Installer can configure through charger web interface which are supported:

  • RFID/NFC (local authentication): since HW module is required in the charger, it is available only in Pro model,

  • PIN authentication (local authentication): is only a SW feature and it is also supported in Home model,

  • Native app (remote authentication): is only a SW feature and it is also supported in Home model.



When local authentication occurs on the charger, Authorize message is send to the backend which decides if RFID card or PIN code is valid. Charger supports also local authenitcation/local white list in the case when connection with backend is down.

Remote authentication is always triggers from backend or other systems:

* example 1: mobile app can send unlock/Remote start command to the charger,

* example 2: parking system can send unlock/Remote start command to the charger (directly or through your backend)

* example 3: operator in backend can send unlock/Remote start command to the charger (directly or through your backend)