Skip to main content

Card Payment Requirements

Whilst each of the preceding Integration Approaches are different, they mostly follow the same generic requirements.

The Integration Controller is in Charge​

All Payter terminal solutions are designed to act according to the requirements of the controller. Only when in the actual payment authorisation and settlement processes does the terminal operate within it's own logic, and this is done in a certified and compliant manner such that it is removed from the controller's scope. All of the following are in control of the integration, whether it is cloud, local, MDB or pre-configured as in Autoscan & Pulse.

  • How much to charge
  • When to request payment
  • Where and how to report success
  • What to do with non-payment data i.e. RFID cards

Authorization & Settlement​

For CPS, PSP and many MDB integrations, Authorization & Settlement are completed separately.

  • Authorization - This is the request sent by the terminal to the Cardholder's Issuer requesting that funds are reserved.
  • Settlement - This is the confirmation of the final amount that is requested from the Cardholder's funds, and may differ from the initial Authorization

The separate nature of these two Request & Responses leads to the below flow.

Basic Payment Flow​

note

There are multiple variations of the above via advanced transaction management tools available in the CPS and PSP integrations specifically.