Authorization takes place at the moment a charger send an OCPP Authorize message to the Longship backend. This message is send when a charge card is presented to the charger. This specific message enables the backend to validate the card. Based on the reply of the backend, the session will start charging (Accepted) or will be denied charging (Invalid).
OCPP offers possibilities to skip the Authorize process. This might affect the possibility of sending a CDR to an EMP. The configuration settings below. Obviously, this affects only charger that are publicly available and shared with roaming partners.
A charger can keep track of cards that have been accepted before. This has consequences described in paragraph LocalPreAuthorize.
Many charger have the ability to add a charge card to a so called LocalList. This is a list with cards that are always accepted. This has consequences described in paragraph LocalPreAuthorize.
This setting determines what needs to be done when a card is used that is part of the local list. If this setting is set to True, then the Authorize process will be skipped and the session is immediately started. This can cause issue because tokens and charge cards can be revoked at any time by the EMP. If a token is revoked, the CDR can not be roamed anymore and the session can not be billed to anyone.
|It is up to the charger (the firmware) to decide whether or not to send an Authorize message. Longship cannot enforce this, so the customer is always responsible for properly configuring the charger.|
The Longship portal (and API) offer the ability to change the configuration of a charger. You can navigate to the chargers screen and find the charger. When the charger details are opened, the tab Configuration can retrieve and change configuration settings and enforce the desired behaviour.