Under Infrastructure/Access Control/Authentication Media you can assign an RFID card or other medium to the contact:
An identification medium can be a MiFARE RFID card or a virtual identification medium such as an app account. The tag ID of the identification medium must be entered as a HEX code, as the OCPP specification requires this. If you do not know this data, please contact the manufacturer of the medium or our 24/7-support-team via the request form for virtual media or call the fee-based hotline +43 6452 21200-90 in Austria or +49 89 9974365-90 in Germany for German and English support.
If the field "Billing start" is not provided with a date, the medium will not be billed.
In the section Owner you determine the cardholder, Billing contact and the issuing company.
You can also assign the tariff model for each card in the settings Please note that no billing will take place without setting the tariff model!
It is also possible to activate the card for a desired billing period and provide it with a validity date.
Please note that tag ID information must be provided in Big Endian format for the RFID card to work in a roaming environment. Find here more information on Endian encoding, the deployment of charging stations for the Intercharge network and a cause analysis guide when a RFID card is rejected or the definition of the Endian encoding for charging stations.
Requirements for a settlement of a medium
In order to settle an identification medium in an automated invoicing process, the following preconditions must be fulfilled:
- The card must be activated.
- A "start of billing" must be assigned to the card.
- A tariff must be assigned to the card.
- A contact must be selected as invoice recipient.
If one of these preconditions is not fulfilled, but a tariff is assigned, chargeable charging processes will be generated and also debited when used with a prepaid account, but no invoices will be generated for these charging processes.
It is also possible to configure data retroactively: In this case, charging processes that have not yet been billed are automatically recharged during the next billing run.
Version: 2023-11-27 13:59:51 UTC