OCPI connection-based Payment Terminals
OCPI-based payment terminal integration is one way to connect payment terminals to your chargers.
This method's key advantage is its use of our standard OCPI developments, allowing you to manage terminal tariffs through standard billing rules.
A third party is often required between our backend and the payment terminal to convert OCPI communication into terminal APIs. Here's how it works:
This setup functions as a specialized OCPI peer-to-peer connection
Main Characteristics
- We pass only the wholesale tariff with this connection, this means you need to configure retail billling rule with a wholesale factor.
- This connection is based on an OCPI subscription connection, which means we only send Start and Stop sessions to the payment terminal providers using OCPI protocol messages. AD_HOC tokens are included as part of the Start Session command (Command module) and are therefore not shared via the Token module.
Requesting a Payment Terminal via OCPI
To request a payment terminal integration via OCPI, please contact your Customer Success Manager (CSM). The request will follow the standard OCPI connection process.
Supported Payment Terminals
The following payment terminal providers are currently supported & integrated via OCPI:
- Scheidt & Bachmann
- Fortech
- Optechain
- Nayax
OCPI Connection Setup
- Each OCPI connection is configured individually per client.
- Multiple CPOs belonging to the same client can be included under a single OCPI subscription.
- Supported OCPI protocol versions:
- 2.1.1
- 2.2.1 (Direct Payments are not supported in this protocol version)
If you require support for the Direct Payments module or a different OCPI protocol version, please contact your Customer Success Manager (CSM). This will require a feature request.
Testing & Evaluation
Testing requirements depend on several factors, including the OCPI version and the supported modules.
Once the request is submitted, the OCPI engineering team will review the requirements and confirm the next steps.
Required Information from the Payment Terminal Provider (eMSP)
During the initial contact with the OCPI engineering team, the payment terminal provider (acting as an eMSP) is required to provide the following information:
- Party ID
- Country code
- Three-character token prefix, followed by a special character separator
The high‑level testing flow is outlined below
