Functional requirements

Outlines the basic functional requirements to allow your POS and terminal to connect to a network.


There are four basic functional requirements:

  1. The PED should be able to exchange data with the Adyen payments platform.
  2. The POS should be able to exchange data with the Adyen payments platform.
  3. The PED and the POS should be able to exchange data.
  4. Hardware flow control needs to be supported between POS and PED when a serial connection is used.

The merchant's local network should support the above listed requirements for the Adyen POS solution to perform tasks. This implies that your network settings, and especially firewall rules should be configured accordingly.

The main use cases that need to be implemented in order to integrate with the Adyen POS system are; register application, register payment terminal and perform a sale transaction.

Although it is technically possible to use a serial connection between the POS and the PED, Adyen strongly recommends using Ethernet connectivity, due to its superior speed and performance with a number of Operating Systems.

 

Recommendations

The following are our recommendations and best practices to set up a point-of-sale integration:

  • Use a dedicated network for payment transactions and related functions.
  • Use dynamic IP addresses on the local network. If not, use a DHCP server to define static IPs to ensure unique IP addresses and avoid unexpected issues.
  • Lower your Maximum Transfer Unit (MTU) size if applications are stalling, timing out, or failing to load. This is especially important in a set up involving VPNs.
  • Ensure Intrusion detection systems (IDS) and intrusion prevention systems (IPS) firmware is up to date. This set up can disrupt encrypted traffic, such as SSL, and therefore Adyen POS traffic. 

  • Use uninterrupted power supplies, and automatic 3G failover if your network is unreliable.
  • Ensure that you have a working DNS server accessible from the local network. The DNS server should be able to resolve *.adyen.com and *.adyenpayments.com.

    If a caching name server is used, the Time to live (TTL) set by Adyen (60 seconds for Disaster Recovery) must be honored.

  • If your PED and POS are connected to different networks, ensure that there is a working DNS server available on both networks. 

Proxy implementation

You may want to implement a proxy in the local network to get a stricter control over the networking traffic. Adyen does not currently support these kinds of proxies in a local network for PED. 

If you must use a proxy, make sure that it's configured so the PED can connect directly to the Adyen payments platform and bypass the proxy. 

Device network accessibility

Some routers have features as Wireless isolation, AP Isolation, Station Isolation, Client Isolation, or similar. Companies that operate wireless networks with public access often use these features.

These features restrict clients connected to the Wi-Fi network so that they:

  • Can’t interact with the devices connected to the more secure wired network.

  • Can’t communicate with each other.

  • Only access the Internet.

Since the PED and the POS need to be able to communicate with each other, these features should be disabled. Implement POS solutions on a dedicated private wireless network to enhance security and to guarantee performance.

Supported Wireless Access Points 

Apart from the wired VX820, all Adyen terminals support 2.4Ghz (802.11bn) networks.

5Ghz (802.11an) networks are only supported by the Verifone VX 690 and E355 terminal (support for E315 is depending on the paired device).

WPA and WPA2 encrypted networks

Currently WPA2 encrypted networks are supported. WPA encrypted networks are supported on Verifone Wi-Fi PED’s as from version v1.11. WEP encrypted networks and open networks are not supported.