---
title: "Choose an integration architecture"
description: "Learn about local and cloud integrations with Adyen payment terminals."
url: "https://docs.adyen.com/point-of-sale/design-your-integration/choose-your-architecture"
source_url: "https://docs.adyen.com/point-of-sale/design-your-integration/choose-your-architecture.md"
canonical: "https://docs.adyen.com/point-of-sale/design-your-integration/choose-your-architecture"
last_modified: "2023-12-06T13:47:00+01:00"
language: "en"
---

# Choose an integration architecture

Learn about local and cloud integrations with Adyen payment terminals.

##### Our Standalone solution

If you do not need a fully featured API integration, we also offer [standalone terminals](/point-of-sale/standalone).

Before you start building a point-of-sale integration with our Terminal API, you need to choose an integration architecture. This determines how your POS system —also referred to as cash register— connects to the Adyen payment terminals and the Adyen payments platform.

* With [local communications](#local-communications) the POS system communicates directly with the payment terminal over the local network.
* With [cloud communications](#cloud-communications) the POS system communicates with the payment terminal over the internet.

## Requirements

Before you begin, take into account the following information.

| Requirement          | Description                                                                                                                                |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **Integration type** | The information on this page is relevant for building a point-of-sale integration with the Adyen Terminal API and Adyen payment terminals. |

## Local communications

In a Terminal API integration using local communications, your POS system communicates directly with the payment terminal over your local network. To make a payment, you send a Terminal API payment request directly to the IP address of the terminal. The shopper then completes the transaction on the terminal. You receive the result of the payment synchronously.

![](/user/pages/docs/03.point-of-sale/04.design-your-integration/06.choose-your-architecture/local-comms.svg?decoding=auto\&fetchpriority=auto)

## Cloud communications

In a Terminal API integration using cloud communications, your POS system communicates with the payment terminal over the internet. To make a payment, you send a Terminal API payment request to the Adyen payments platform. This request is forwarded to the terminal. The shopper then completes the transaction on the terminal. You receive the result of the payment synchronously or asynchronously, depending on how you choose to build your integration.

![](/user/pages/docs/03.point-of-sale/04.design-your-integration/06.choose-your-architecture/cloud-comms.svg?decoding=auto\&fetchpriority=auto)

## Choosing between cloud and local

When choosing an integration architecture, you should consider aspects like ease of integration, security, and usability. For example, cloud communications is easier to implement but does not support all use cases. Local communications on the other hand can be more robust but requires an additional effort to ensure the local network communication between the POS system and the payment terminal is safe.

To decide between cloud or local communications:

1. To find out what integration architecture we recommend in general for your type of situation, select **Start** below and answer a few questions.
2. Check if the [technical know-how](#technical-know-how) for managing the network at the physical location is at the required level.

#### Decision tree

**Make your choice**

Select **Start** and answer some questions to help you choose between cloud communications or local communications.

**Do you need offline processing?**

A local integration supports [offline EMV and Store-and-forward transactions](/point-of-sale/offline-payment). 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 are not be able to make a transaction. As a fallback you can add [standalone terminals](/point-of-sale/standalone), because these do support offline payments. Or you could set up a secondary, local integration with some of your terminals. Another option is to use [cellular failover](/point-of-sale/design-your-integration/network-and-connectivity/cellular-failover) as a backup.

* **Local communications**

  We recommend local communications because of your requirement that the terminals support offline processing.

  Note that the success of your local integration is influenced by aspects of [technical know-how](#technical-know-how) .

* **Does your POS system support cloud-based communications?**

  If your current or future POS system is cloud-based, cloud communications is the natural choice.

  * **How do you use your terminals?**

    There are various ways to use payment terminals:

    * **Stationary**: the terminals stay in the same place and remain connected to power.
    * **Portable**: your staff operates battery-powered terminals, or uses a mobile device for Tap to Pay.

    - **Cloud communications**

      We recommend cloud communications because your POS system is cloud-based, the terminals are connected to power continuously, and you don't require offline processing.

      Note that the success of your cloud integration is influenced by aspects of [technical know-how](#technical-know-how) .

    - **Contact Adyen about cloud communications**

      Cloud communications could be a good option because you have a cloud-based POS system and don't require offline processing. However, there are other factors to consider:

      * The robustness of the network and internet access in the physical locations.

      * Battery life. How long terminals can run on battery power is influenced by factors like:

        * Is it an Android terminal that runs various apps?
        * Will you need [cellular fallback](/point-of-sale/design-your-integration/network-and-connectivity/cellular-failover) often, to connect to Adyen over a cellular connection when the internet access fails?
        * How many transactions per hour does a terminal typically need to handle?

      Contact Adyen for an assessment of your situation.

    - **Consider each usage scenario separately**

      If you plan to use various terminal types, answer the questions for each use case separately and compare the outcomes.

  * **Local communications**

    We recommend local communications because your POS system doesn't support cloud-based communications.

    Note that the success of your local integration is influenced by aspects of [technical know-how](#technical-know-how) .

**Local communications**

We recommend local communications because you plan to use payment terminals in an unattended environment.

### Technical know-how

The success of your cloud or local communications integration is influenced by various technical and practical aspects.

* Infrastructure and management of the in-store network:\
  The team or service provider managing the network at the physical location needs to have the expertise to configure the network for the use of payment terminals. They also need to configure the IP addresses of the terminals:

  * A local integration should use DHCP reservation, or manually configured static IP addresses.
  * A cloud integration should use dynamic IP addresses without DHCP reservation.
  * If possible, the DHCP lease time should be set to 24 hours or more so that the IP addresses do not change too often.

  For information about technical aspects, see [Network configuration](/point-of-sale/design-your-integration/network-and-connectivity/network-configuration).

* Problems with the in-store network:\
  Adyen cannot provide support for network issues that occur at the physical location. You need to ensure you have a team or service provider with the expertise to solve any network issues.

## Next steps

[Local communications](/point-of-sale/design-your-integration/choose-your-architecture/local)

[Start building an integration with local communications.](/point-of-sale/design-your-integration/choose-your-architecture/local)

[Cloud communications](/point-of-sale/design-your-integration/choose-your-architecture/cloud)

[Start building an integration with cloud communications.](/point-of-sale/design-your-integration/choose-your-architecture/cloud)
