---
title: "In-person payments"
description: "Order hardware in time, and use the right software version and features."
url: "https://docs.adyen.com/industries/peak-season/in-person-payments"
source_url: "https://docs.adyen.com/industries/peak-season/in-person-payments.md"
canonical: "https://docs.adyen.com/industries/peak-season/in-person-payments"
last_modified: "2026-06-01T15:33:16+02:00"
language: "en"
---

# In-person payments

Order hardware in time, and use the right software version and features.

[View source](/industries/peak-season/in-person-payments.md)

Your Point of Sale is the final step in the shopper journey, and especially during peak season, speed and reliability are key to a great customer experience. To prepare for a successful peak season, this page addresses:

* Reviewing the payment methods, hardware components, and software versions you need.
* Handling network outages through offline payments and cellular failover.
* Using the correct regional endpoints if you have Terminal API integration with cloud communications.

## Payment methods

Offering shoppers a mix of local and global method is recommended for a good and fast shopper experience. However, we do not recommend adding new payment methods right *before* peak season, because you need time for testing.

We do recommend to [review your payment methods](/point-of-sale/what-we-support/payment-methods/manage-payment-methods/#view-payment-methods/) and look for the following:

* Are there [deactivated payment methods that are worth reactivating](/point-of-sale/what-we-support/payment-methods/manage-payment-methods/#activate-or-deactivate-payment-methods/)?
* Check which of your [payment methods](/point-of-sale/what-we-support/payment-methods/), including prepaid and gift cards, support referenced refunds, unreferenced refunds, or chargebacks. Consider deactivating payment methods that do not fit your refund or chargeback strategy.
* Check if you [have made your payment methods available in the regions where you need them](/point-of-sale/what-we-support/payment-methods/manage-payment-methods/#change-payment-method-settings/).
* Check if the [accepted currencies of your payment methods are correct](/point-of-sale/what-we-support/payment-methods/manage-payment-methods/#change-payment-method-settings/).
* Test your payment methods. You can use the Adyen simulator to [test QR code wallets](/point-of-sale/testing-pos-payments/#testing-qr-code-wallets/).

The Mobile solutions do not support all the payment methods that are supported on Adyen payment terminals. For payment methods supported in mobile solutions, see [Tap to Pay and card reader](/point-of-sale/ipp-mobile/#supported-payment-methods).

### Configure manual key entry

Our terminals support reading the card using either EMV chip, contactless through Near Field Communication (NFC), or magnetic swipe. Make sure that you have [manual key entry (MKE) configured](/point-of-sale/enter-payment-manually/#configure-mke), in case all other card entry methods fail.

## Hardware

For smooth terminal operations during peak season, you need to make sure that all the hardware components of your integration are working. We recommend that you:

* [Order payment terminals in advance](#order).
* [Prepare and test](#prepare-and-test-terminals) your terminal fleets and backup terminals.
* Make sure that you have the [recommended terminal software version or mobile SDK version](#software) installed.

### Order

If you intend to [order new terminals](/point-of-sale/automating-terminal-management/order-terminals-api/), do so as soon as possible. Delivery times can be longer than normal during peak season, and you need time to [assign](/point-of-sale/managing-terminals/assign-terminals/), [board](/point-of-sale/managing-terminals/board-terminal/), and test the payment terminals.\
If you do not have any backup payment terminals yet, consider adding some to your terminal fleet. If you order new mobile devices, make sure that they meet the hardware and software requirements for your [Android](/point-of-sale/mobile-android/requirements) or [iOS](/point-of-sale/mobile-ios/requirements) Mobile solution.

### Prepare and test terminals

Test your terminals and hardware ahead of peak season. Especially, if you plan to use terminals that have been switched off for some time or to add terminals out of inventory to your stores, do the following:

* If needed, assign and board the terminals.
* Make sure that the terminals are [updated to the correct firmware version](#software).
* Fully recharge the batteries of terminals that have been stored or disconnected for an extended period.
* Check if the internet connection, battery, and basic functionality work as expected.

Consider [making digital or physical copies of the terminal user manuals](/point-of-sale/user-manuals/) available to your staff in your stores.

## Software

We recommend that you check the software on your payment devices. Below you find recommendations for updating the:

* [Terminal Software](#terminal-software)
* [Mobile SDK](#mobile-sdk)

### Terminal software

The details mentioned here are for the 2025 Christmas and end-of-year peak season.

During peak season, Adyen does not roll out new software to merchants on an [automatic update strategy](/point-of-sale/release-updating/#automatic-updating) during the following periods:

* November 24, 2025 - December 7, 2025
* December 22, 2026 - January 4, 2026

Additionally, Adyen offers the option to pause the automatic software roll-out from November 3, 2025, to January 11, 2026. Contact your Adyen account manager if you want to freeze automatic software roll-outs during this time.

See our terminal software recommendations for the different update strategies:

* For the [automatic update strategy](/point-of-sale/release-updating/#automatic-updating), check that your payment terminals are on the following software versions:

  * v.120.4 for non-Android terminals, excluding UX300 and UX410.
  * v.121.8 for Android terminals, excluding S1E and S1EL.
  * v.107 for S1E and S1EL terminals.
  * v.100 for UX300 and UX410 terminals.

* For the [manual update strategy](/point-of-sale/release-updating#manual-updating), make sure that your payment terminals are on one of three latest [Long Term Support versions](/point-of-sale/release-updating#lts): v.114, v.117, or v.120.

### Mobile SDK

We recommend that you update to the latest [available version of the Mobile SDK](/point-of-sale/firmware-release-notes).

Note that each version of the Mobile SDK [expires six months after the version was released](/point-of-sale/mobile-android/manage#keep-the-mobile-sdk-up-to-date).

Additionally, make sure that your mobile devices, card readers, and docks in your [Android](/point-of-sale/mobile-android/requirements) or [iOS Mobile](/point-of-sale/mobile-ios/requirements) solutions are up to date.

## Offline payments

To process a transaction, the payment terminal or Mobile SDK must have internet access. In case of a temporary loss of internet connectivity, you should have [offline payments enabled](/point-of-sale/offline-payment/#enabling-offline-payments) to continue making point-of-sale payments.

### Payment terminals

Payment terminals support [two types of offline payments](/point-of-sale/offline-payment/#how-it-works):

* **Offline EMV**: The payment terminal verifies that the PIN entered by the shopper matches the PIN on the EMV chip embedded in the card, and then asks the card to approve the payment. Whether the transaction is approved, depends on how the issuer configured the card.
* **Store and forward**: The payment terminal approves payments without any verification. Because of this, the risk of payments being declined by the issuer is higher than for offline EMV transactions. In practice though, the authorization rates are still very high.

### Mobile solution

In a Mobile solution, you can continue making transactions offline with [Store and forward](/point-of-sale/offline-payment/#mobile-solution).

* **Store and forward**: To handle store-and-forward payments in a Mobile solution, the Adyen payments platform must have attested the security of the mobile device before the internet connectivity was lost. In a mobile solution, offline transactions with PIN cannot be completed. [Familiarize yourself with the restrictions](/point-of-sale/offline-payment/#mobile-solution) for mobile store-and-forward payments and how to [resolve common errors](/point-of-sale/mobile-ios/troubleshooting/).

## Cellular failover

To process a transaction, the terminal must have internet access. Cellular failover occurs when the payment terminal cannot access the internet over the primary network connection (usually Wi-Fi or Ethernet), and switches to a cellular connection (3G or 4G).\
Familiarize yourself with:

* The different [scenarios](/point-of-sale/design-your-integration/network-and-connectivity/cellular-failover#scenarios) when cellular failover is useful, and when it is not useful.
* How to [manage cellular connectivity on the terminal](/point-of-sale/design-your-integration/network-and-connectivity/cellular-failover/#set-up-cellular-connectivity-on-the-terminal).
* Optionally, how to [enable a third-party SIM card](/point-of-sale/design-your-integration/network-and-connectivity/cellular-failover/#activating-a-third-party-sim-card).

## Regional endpoints for cloud communication

Your live Terminal API integration with cloud communication uses regional endpoints. For the best performance, use an endpoint that is geographically closest to the location of your store. This ensures that the communication between your payment terminal and our back-end is optimal.\
If you have built integrations in different regions, make sure that each integration uses the [correct regional-specific endpoints](/point-of-sale/design-your-integration/terminal-api/#live-endpoints).

## See also

* [Software release notes](/point-of-sale/firmware-release-notes)
* [Troubleshooting terminals](/point-of-sale/pos-troubleshooting)
* [Payment methods](/point-of-sale/what-we-support/payment-methods)
* [Terminal user manuals](/point-of-sale/user-manuals)
