This page lists the known limitations of Tap to Pay on Android so you can plan your integration around them.
Acceptance is contactless only
Tap to Pay on Android accepts contactless payments only. The customer taps a contactless card or a phone or other device with a digital wallet such as Apple Pay on the device NFC reader.
There is no card insert (chip) or swipe (magstripe). The device uses its built-in NFC reader, not a physical card slot.
To accept chip-insert or PIN-on-reader transactions, you need the Adyen NYC1 card reader, which is the separate Card reader on Android solution, not Tap to Pay.
Device and software requirements
The device must meet Adyen's hardware and software requirements, which constrain which devices you can use:
A commercial off-the-shelf (COTS) Android device, not a payment terminal, with no integrated card reader.
An integrated NFC reader. Detachable NFC modules are not compliant.
An integrated touch screen.
Support for hardware key attestation, and the device must be Google-certified.
Android 12 or later, updated to the latest security patch (minimum is the patch for March 5, 2022).
A stable internet connection is required.
SDK maintenance
The Mobile SDK for Android expires every six months. If the SDK is embedded in your app, you must update to the latest version regularly, otherwise transactions stop working. Plan for ongoing maintenance and app updates.
PIN handling
On Tap to Pay on Android (NFC tap, no card reader), customer verification follows the card scheme rules for contactless transactions. PIN entry on the device for card-reader transactions applies to the separate NYC1 card reader solution, not to Tap to Pay.
Availability
Supported countries, regions, payment methods, and functionality vary. Confirm coverage for your market before you build, and confirm what Valpay has enabled on your account.