Versions and interfaces
The app offers OCPI 2.1.1, 2.2.1 and 2.3.0. The API also accepts the 2.2 compatibility version, which is not selectable in the app. Choose the version the endpoint actually runs. A module advertised for a version has a conformance suite. Before running it, check which interfaces the endpoint advertises. A CPO or eMSP is a business role; Sender and Receiver identify a module’s data interface. They do not say who starts registration. Use the suite catalogue to inspect the checks for your version and role. A conformance suite checks protocol rules. A charging journey follows a timed interaction and separates OCPI requirements, business checks and observations in its report.Extensions
Direct Payment is a separately published extension on OCPI 2.2.1 and part of the core specification on 2.3.0. Bookings on 2.3.0 follows the separately published2.3.0-booking-1.1 document. See payment-terminal testing for the applicable roles and plan.