Our Standalone solution
If you don't need a fully featured API integration, we also offer a Standalone terminal solution.
Before you start building a point of sale integration, you need to choose an integration architecture. This determines how your integration connects to the Adyen payments platform.
We offer two integration architectures for our Terminal API:
- Local communications: Your cash register communicates directly with the terminal over your local network.
- Cloud communications: Your cash register communicates with the terminal through the Adyen payments platform.
Planning to build a cloud integration? Contact our POS Support Team before you start.
With a local Terminal API integration, your cash register communicates directly with the terminal over your local network. To make a payment, you make an API request directly to the IP address of the terminal, for the shopper to complete the transaction. You receive the result of the payment synchronously.
If your existing cash register system is cloud-based, you may prefer to integrate using cloud communications.
With a cloud Terminal API integration, your cash register communicates with the terminal over the internet. To make a payment, you make an API request to the Adyen payments platform. This request is forwarded to the terminal, for the shopper to complete the transaction. You can choose whether you want to receive the result of the payments synchronously or asynchronously.
Choosing between cloud and local
There are various aspects to consider when deciding on your integration architecture.
We recommend using cloud communications only when no local connectivity to the terminal is available.
The main reason for this recommendation is that a local integration supports offline payments.
Always consult Adyen before building a cloud integration.
A local integration supports offline EMV and Store-and-forward transactions. This means you can continue making transactions when there are issues with the internet connection.
A cloud integration does not support offline EMV or Store-and-forward transactions. When the internet connection drops, you will not be able to make a transaction. As a fallback you could get some additional terminals and set these up as standalone terminals, because standalone terminals do support offline payments. Or you could set up a secondary, local integration with some of your terminals. Another option is to use 3G/4G failover to use a cellular connection as a backup.
Ease of integration:
A local integration requires an additional effort to ensure the communication between your cash register and the terminal is safe. You will need to verify the terminal's certificate and encrypt and decrypt API messages. You can protect local communications yourself, or use one of our GitHub libraries to take care of this.
Battery life of the payment terminal:
A cloud integration uses WebSockets to establish and maintain the connection. The power consumption of the WebSockets connection significantly reduces the time that terminals can run on battery power. This can be an issue if your business depends on portable or mobile terminal models.
- Prior consultation:
Although a cloud integration requires less effort to set up, the success of the integration greatly depends on the in-store network infrastructure. There are also some limitations on our side. If you are leaning towards a cloud integration, contact our POS Support Team before you start building. We can then discuss whether a cloud integration is suitable for your situation.
|Offline payments||When the internet connection is down, a local integration allows offline payments.|
|Ease of integration||A local integration requires you to authenticate the connection and encrypt and decrypt API messages.|
|Battery life||In a cloud integration the WebSockets connection reduces the time a terminal runs on battery power.|
|Start building right away||Always consult Adyen before building a cloud integration.|