Ask Flux
Help Center
How can we help?

Payment Terminal - OCPI-based

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

  • This connection is based on an OCPI subscription connection, which means we only the send Start and Stop sessions to the payment terminal providers using OCPI protocol messages.
  • 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 inΒ pilot mode, we are working on establishing a clear process to onboard OCPI based payment terminal connection.

Pre-Requisites

First, we need to verify that no special OCPI features or additional development will be required.

Your CSM will need to confirm the following:

  • OCPI Version (2.1.1 vs 2.2.1, including extensions)
  • Required modules
  • Token information delivery method in Commands Start request (if not using Tokens module)
  • Any protocol customizations we should be aware of

After confirming compatibility between our solutions, we can proceed with the following process:

Testing Process

Β 
Β 
Β 
Did this answer your question?
😞
😐
🀩