What we do
Tools
Industries
Department
How we workLet's talk →
Home/Adyen/Adyen Terminals Across Many Stores
Adyen point of sale

Adyen Terminals Across Every Store: Setup, Models and Downtime

Store twelve opens Monday and its four terminals are still in the box. Adyen's terminals take payments through the Terminal API, the same Adyen account and processing as your online checkout. One terminal at one till is simple. Forty across ten stores raises different questions: how your POS talks to them, which model goes where, and who hears first when one stops working.

Cloud or local: how your POS reaches the terminal

Both use the same Terminal API messages. The difference is the route they take.

Cloud communication

POS to Adyen's cloud, Adyen to the terminal

  • Your POS sends requests over the internet to Adyen, which forwards them to the terminal.
  • No need to know each terminal's IP address or manage it on the store network.
  • Suits a cloud-hosted POS and estates with many stores. Results can come back in the same call or asynchronously to your endpoint.
Local communication

POS to the terminal on the store network

  • Your POS sends requests straight to the terminal's address on the local network.
  • Needs encryption set up between the POS and terminal, and stable addressing per device.
  • Suits a POS that runs on a machine in the store. The terminal still needs internet to reach Adyen for the payment itself.

Pick per estate, not per store. Mixing both doubles the setups your team has to support.

How a terminal estate fails without telling anyone

Event notifications go to an endpoint nobody watches

How you'll know: Terminals report Shutdown, OutOfOrder or NetworkDisconnected, and the store still finds out from a customer.

Fix: Adyen sends these events to the URL you set under the Terminal API event settings. Something on your side has to turn each one into a message for the manager of that store.

A terminal that has simply gone quiet

How you'll know: No error, no transactions, nothing. It's switched off or unplugged.

Fix: A device that's off sends no events. The POS Terminal fleet report shows each terminal's status and last activity, so compare that against store opening hours to catch a reader that's been dark all morning.

Settings changed at the wrong level

How you'll know: One store's terminals behave differently from the rest, or a change meant for one store reached all of them.

Fix: Terminal settings can be set at company, merchant account, store or terminal level, and lower levels override higher ones. Decide which level owns each setting and keep changes there.

Terminals not assigned to a store

How you'll know: Store managers can't see their own takings, only the account's total.

Fix: Assign each terminal to its store in the Customer Area or through the API. Reports can then break transactions down by terminal, store or region.

Which kind of terminal suits each spot

Model names change, so check Adyen's current terminal list and what's sold in your country before ordering.

The spot Kind of terminal Watch for
A fixed till with a POS on a PC or tablet A countertop terminal, such as the P400 Plus or V400c Plus Cabling and network at each till, if you go local.
Table service, queue busting, the shop floor A portable terminal, such as the V400m or S1F2 Battery life across a full shift, and Wi-Fi or mobile data coverage in the back of the store.
Wanting the POS app on the payment device itself One of Adyen's Android terminals, such as the S1E or AMS1 Whether your POS vendor supports running on that model.
Staff on phones or tablets, pop-ups, events A card reader paired with a mobile device, such as the NYC1 Which mobile setup your POS supports.
An older Verifone model already on the counter Check it against Adyen's legacy list Models such as the VX820 and e315 are deprecated, so budget for replacement.
Let's talk

Opening stores faster than you can set up terminals?

n-frames builds the rollout around Adyen's Management API, where it allows: terminals assigned to the new store and its settings applied in one run, not forty manual changes. Then the alerting that reaches the right store manager when a reader goes down, and store-level takings your area managers can read without a finance export.

Talk through the rollout →

Adyen terminal questions

What's the Adyen Terminal API, and how is it different from Checkout?

It's the API your POS uses to send a payment request to a physical terminal and get the result back, using JSON messages over a cloud or local connection. Online Checkout uses a different API, but both run through the same Adyen account and processing, so in-store and online payments settle together.

Can one Adyen account manage terminals across multiple store locations?

Yes. You set up stores under your merchant account, assign terminals to each, and view transactions by terminal, store or region. What it doesn't do on its own is give each store manager their own view and alerts, which is the part n-frames usually builds.

Do Adyen terminals need their own separate setup from online checkout?

Each terminal needs to be assigned, configured and connected to your POS, so yes, there's setup. But it runs on the same merchant account and processing as your online checkout, not a separate payment system, and settings can be inherited from the store or account level instead of entered per device.

How do I know if an Adyen terminal has gone offline?

Two sources. Terminals send event notifications, such as a network disconnect or shutdown, to an endpoint you configure. And the POS Terminal fleet report shows each terminal's status and when it was last online. Neither alerts a store manager by default; that needs building on top.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.