If you are going to use a ready-made Mobile solution from a partner, skip this section.
This part of the documentation provides instructions for building Android Mobile solutions.
If you have not decided yet which solution to build, refer to Understand your solution. That page also discusses how the Mobile SDK works in combination with your POS app, illustrates transaction flows, and has examples of built-in UI screens for working with a card reader. This can be useful background information when building your solution.
Integration effort
Building a Mobile solution requires some development tasks that maybe you were not expecting. When planning the work, check the following sections.
Tap to Pay or Card reader on Android
A Tap to Pay or Card reader solution that integrates the Mobile SDK into the POS app requires back-end development tasks:
- Implement a server-to-server call to set up a secure communication session between the SDK and the Adyen payments platform.
- Integrate your POS app with Terminal API. You must support the
PaymentRequest, and preferably also theReversalRequest.How to integrate with Terminal API is described in other sections of our documentation.
With regard to cross-platform frameworks, note that integration of our native SDK into a cross-platform app is possible, but complex. We do not offer cross-platform wrappers at the moment.
Android Payments app
For Tap to Pay using our Payments app you need to:
- Integrate your POS app with Terminal API. You must support the
PaymentRequest, and preferably also theReversalRequest.How to integrate with Terminal API is described in other sections of our documentation.
- Board the Adyen Payments app on every Android mobile device where the app is installed.
Choose a solution
What solution do you want to build?