Skip to main content

Communication Options

Payter terminals require access to the Internet in order to authorise and complete EMV payments, as well as for Terminal Management and other services. In addition, the terminal requires a Controller to function - an integrated host system. It is important to understand early in the Project what input method will be used by the Integration Solution.

Controller Options

Apollo

The Apollo family of terminals can be controlled via these options:

ChannelConnectionSolution
Internet ConnectionEthernet
Cellular/Mobile (SIM)
Cloud Payment Service (CPS)
OCPI Direct Payment
Local ConnectionTCP/IP via LAN
Serial via USB
Payter Session Protocol (PSP)
MDB Connection5-port molexMulti Drop Bus (MDB)

The Serial via USB connection requires an additional adapter, available upon request.

P6X

The P6X terminal can be controlled via these options:

ChannelConnectionSolution
Internet ConnectionEthernet
Cellular/Mobile (SIM)
Cloud Payment Service
Local Connection9-pin SerialPayter Session Protocol (PSP)
MDB Connection6-port molexMulti Drop Bus (MDB)
important

A key decision to be made by any solution Integrator is whether to use a Local or a Remote (Cloud) interface.

Payter can provide advice on this during the Integration Consultation.

The role of a Cellular/Mobile SIM connection

All Payter terminals support an optional integrated 4G/LTE Modem supporting SIM connectivity for access to the Internet. Payter can supply a roaming SIM, or Integrators & end-user customers can source their own and install upon delivery. Integrators should however consider carefully whether a SIM in each Payter terminal is optimal; Where the host solution also requires connectivity, it can often be much more efficient for this connection to be shared, usually through a Local Area Network.

A SIM 'backup' is often considered a good contingency, but be mindful of the wider installation when selecting a contingency communication method. It may be better to have a single SIM backup in place, either per solution or per site, than have multiple redundancies in place.

Each diagram below shows a different way of providing communication to four separate terminals that share the same site or location:

In this approach, all components on site have independent communication methods and no individual redundancies. Depending on your specific implementation, this approach may not be recommended.

note

The Host Solution and the Terminal both need communication, so a failure in one results in the whole solution being inoperable, albeit potentially on a per-terminal basis.

Active SIMs are a source of recurring costs, as they are typically billed monthly.

tip

Consider the whole solution when determining the integration solution's communication needs and redundancies. Not all solutions need communication for both components, and simplicity is recommended here. More complex solutions, such as a multi-charger EV charging station, benefit from a well planned communication strategy.

Payter can provide advice around best practice, but consider seeking independent infrastructure specialist advice for complex solution deployments.