Ask Flux
Help Center
How can we help?

Payment Terminal - Payter Onboarding

Existing integrations

P66 & Apollo models

How to onboard?

Preparation

This stage is

responsibility of the customer

.

The following steps should be done:

1. The charger you want to use with the Payter terminal must already be OCPP-compliant and certified by our team. See Certified Charge Station. Our Payter implementation relies on proper OCPP message handling by chargers.

2. You need to become a customer from Payter and handle the commercial relationship directly with Payter

Payter will need you to have a merchant account with one of these banks: Elavon, Wordline Six, Shift4/ Finaro. If you don't have it yet, it might take a while to set up. When doing it, you will get access to Payter portal so you can set up your payout system and develop a reconciliation process that works according to your needs.

When the customer is in contact with Payter, the customer needs to specify that they will be onboarding under GreenFlux Domain. They must set-up the following parameters (for both test and production environments):

1. Terminal is being added to the right Payter cloud (test or prod) * 2. GFX x Payter-account can see the terminal  3. GFX x Payter-account can manage the terminal

 

GFX acceptance is connected to Payter test

GFX prod is connected to Payter Prod

Testing in GFX ACC with a PROD terminal will not work

 

4. Inform your CSM about the Charger & Terminal models you’re planning to use.

Testing on Acceptance

This stage is optional

If chosen, it becomes a shared responsibility of the customer and your dedicated CSM.

The following steps should be done:

1. Customer / Charge Station Manufacturer: obtain test model of the payment terminal

2. Customer: inform your CSM about the testing need, Charge Station model to test with, Terminal ID to use

Only test terminals and test chargers can be used for this stage

3. CSM: prepare the acceptance environment with all the configurations

4. Customer: contact CS manufacturer, Payter technical team & GFX testing team (submit a ticket via support portal)

5. GFX testing team: testing. GFX share the testing scenarios, however, it’s the CS Manufacturer that will need to perform them on site

Go Live - Billing Configuration

This stage is a shared responsibility between CSMs and a customer

It consists of the following steps:

  1. CSM: Prepare the set-up
  1. Customer: Inform the tariffs / pricing strategy to apply
  1. CSM: Create Retail & Wholesale Billing rules for Contactless Payment eMSP
  1. CSM: Inform the customer when the set-up is ready

WARNING!

Tariff display capacity is limited on the small terminal screen. Please, simplify the tariffs you're going to apply to ensure good customer experience and real price transparency

Go Live - Charge Station Configuration

This stage is a customer's responsibility

Enable over-commit

In cases when the session amount is higher than pre-auth amount (e.g. pre-auth amount is 50€ and the session price is 60€, there are 2 possible scenarios:

  • Scenario 1: not enable over-commit. In this case we'll try to get the whole amount, but if that's not possible, only pre-auth amount will be substracted
  • Scenario 2: enable over-commit HERE. Automatically session amount will be withdrawn from driver's bank account, if it's allowed by the bank. Otherwise same as scenario #1

To avoid most of the issues, we recommend to always use the highest amount allowed in your country for contactless payments

Please, note, that all custom text in Apollo UI is currently in English. If you need another one, please, let your CSM know.

Did this answer your question?
😞
😐
🤩