Confirm device meets requirements: Android 12 or later, Google-certified, integrated NFC, hardware key attestation support, and security patch from March 5, 2022 or later.
Add the Adyen Android Mobile SDK to your POS app; obtain an SDK authentication token from Adyen's Customer Area and implement the `AuthenticationProvider` interface to supply the token.
Establish a communication session by making a server-to-server API request to Adyen's configuration endpoint using your Adyen API credential.
Implement the Tap to Pay payment flow through the Terminal API: send a `PaymentRequest` to the SDK, present the contactless tap prompt to the customer, and await the payment result.
Handle the payment result synchronously from the SDK callback; check the `result` field and surface errors from `AdyenReaderError` to your UI.
Keep the SDK version current: each SDK version expires six months after release; monitor Adyen release notes and update before the expiry to avoid payment failures.
Known gotchas
The minimum Android OS for Adyen SoftPOS is Android 12; the SDK will not initialize on earlier versions even if you target them in your build configuration.
Each SDK version expires six months after release; an expired SDK will stop processing payments without warning from the card scheme. Subscribe to Adyen release notes and build SDK updates into your release cycle.
This is a pure Android integration; do not reference iOS SDK versions, classes, or APIs here. Adyen has a separate iOS Mobile SDK under docs.adyen.com/point-of-sale/mobile-ios.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp