Skip to main content

Local Communication

With local communication, your POS sends requests straight to the terminal over your local network, without going through Adyen's cloud first.

Why choose local​

  • Faster. Requests skip the trip through the cloud, so the terminal reacts sooner.
  • Less dependent on your POS's internet. Your POS talks to the terminal on the local network. The terminal still needs internet to process the payment.

It takes more setup than cloud communication. If you don't need these benefits, use cloud communication.

Setup​

  1. Get test access and test cards. Same as for cloud communication, see Get Started. You don't need an API key.
  2. Put the POS and terminal on the same network. Give the terminal a fixed IP address (static IP or a DHCP reservation on your router).
  3. Get the encryption key. In the Customer Area, go to the terminal settings, then Integrations > Encryption key. Note the key identifier, passphrase and version. Every request to the terminal must be encrypted with this key.
  4. Install Adyen's root certificate on the POS, so it trusts the terminal's TLS connection. You can download it from Adyen's documentation.
tip

Use one of Adyen's libraries (.NET, Java, Node.js and others). They handle the encryption for you.

Sending requests​

Send requests to the terminal at:

POST https://<terminal-ip>:8443/nexo

The requests are the same as for cloud communication: Payment, Save Card and Other Requests. The only difference is that each request is encrypted and has a SecurityTrailer, which the Adyen libraries add for you.