Sample Android project aiming to provide guidelines for Skrill Checkout integration.
On June 30, the US bank Chase stops supporting in-process webview traffic. This topic raises the need for updated Skrill Checkout integration guidelines for mobile applications.
Our recommendation is to start Skrill Checkout in a browser or Custom Tabs. An essential part of being able to keep a good UX is to be able to redirect the customer from the browser back to the merchant's app once the payment is made.
In order to keep the good UX the merchant app have to initialize Skrill Checkout with return_url which on the other hand should be registered in the app as an Android App Link. This means that when the payment is made and the browser loads the return_url then the app will be able to intercept that url and get back to foreground again.
- Skrill Checkout url should be loaded in a browser or Custom Tabs (out-of-process).
- An Android App Link should be registered in the application. Step-by-step guide
- Host a .well-known/assetlinks.json file on your domain: App Links verification guidelines
- Define proper launchMode for the Activity that handles the App Links depending on your needs.
GitHub Pages is used to host the .well-known/assetlinks.json for simplicity. Note that a keystore is added to the project and used for debug builds. That allows the project, being run on multiple machines, to use the same certificate and to relate correctly with the SHA-256 defined in the .well-known/assetlinks.json meaning the auto verification will work anywhere.
No special steps required to run the app. Import the project in Android Studio, select debug build type and run it.