Skip to main content

Integration Approach

Cloud or Local​

EV Charger Controllers need a detailed level of integration so that they can exchange complex data with the Payter payment terminal. Payter provide two options for this integration:

  • Payter Session Protocol (PSP) - Local
  • Payter Cloud Payment Service (CPS) - Cloud

Below, we detail each approach or method, and provide a list of Pro’s and Con’s for each.

info

Whilst the message names and minor functional aspects vary, the same basic flow detailed in Start Session and Stop Session is still the same.

Local Integration - Payter Session Protocol (PSP)​

  • A connection to the terminal is physically established, inside the Charger in which the Payter terminal is installed
  • The connection is via Serial cable or LAN (Apollo only) and is constantly maintained.
  • Reduced points of failure
  • The charger controller is always aware of the status of the terminal
  • Fast and responsive
  • Can optionally support some offline capabilities

Cloud Payment Service (CPS)​

  • The terminal, either via charger infrastructure or it’s own 4G/LTE Modem & SIM, maintains a connection to the Payter Cloud Payment Service
  • The CPS server acts as a proxy, sending messages to the terminal directly, and providing detailed responses to the charger controller either directly or via a callback. In this case, the charger controller is more commonly a cloud-based Charge Station Management System (CSMS)
  • Simple, modern, readable integration using RESTful JSON commands
  • No requirement for physical connection, so ideal for cloud-based Charger Controllers
  • Can accept interactions from more than one source
  • Can provide status change notifications via Webhooks
  • Will include some additional features not possible via PSP
info

Payter Implementation specialists are available to discuss your requirements and make recommendations on either approach, should you wish to talk the options through.