OCPI Modules and their Function
The Payter OCPI solution is reliant on these modules:
Credentials
The credentials module is used to exchange tokens, that allow the CPO and Payter platforms to exchange data in a secure way. It is also used to detail the endpoints for the rest of the modules. It is important that all aspects and functions of the Credentials module are implemented. This module is critical in the initial setup of the connection, but also has an important role to play when updating OCPI to never versions or if endpoints need to change.
Locations
The Location objects live in the CPO back-end system. They describe the charging locations of an operator. This module is critical to the payment flow. Payter need to know the correct connector and evse to send a Start Session for, as well as the status of each. This module is also reliant on the Tariffs module for data.
Payter's solution mirrors the locations structure of the CPO by polling for updates periodically. The CPO is expected to push changes in EVSE status when changing. These changes are used by Payter to represent the charger status in real time.
Sessions
The Session object describes one charging session.
Commands
The Commands module enables remote commands to be sent to a Location/EVSE. Payter request a Start Session or Stop Session from the CPO using this module.
CDRs
A Charge Detail Record is the description of a concluded charging session. Payter assumes that CDRs are generated by the CPO and are sent to Payter after the charging session has ended.
Tariffs
The Tariffs module gives Payter information about the tariffs used by the CPO. Payter uses this to provide user feedback and acceptance, as well as to set some criteria for a Stop Session command. Note that the used languages in the tariff determine the available languages on the Payter terminal via the home button.
Payments
This module is of course critical for Payments, and consists of two main components.
- Terminal - allows a CPO to assign a Payter Apollo terminal to one or more locations or EVSE's
- Financial Advice Confirmation - Payter use this to confirm final costs and key data required for a compliant receipt or invoice to be created by the CPO
Tokens
When a charge session has been authorized, Payter generates an AD_HOC_USER token type to be used for the Remote Start Session.