App2app are made possible by policies governed by iOS and Android.
The app2app articles in our knowledge base are a culmination of our experiences to date with app2app, but they are not extensive. For more detailed resources, we advise you to consult other app2app resources (e.g. iOS and Android policies).
Our client care team does not provide support for any app2app implementation issues.
Note: This article is about app-to-app redirects on Android only.
When directing a user through our Data API authentication flow with an Auth Link you may choose to specify a redirect_uri that opens your app and continues the flow in-app.
Deep Link vs Android App Link
|Custom URI Scheme (Deep Link)||Android App Link|
|Able to redirect to webpage as a fallback?||No||Yes|
|Able to redirect to Play Store as a fallback?||No||Yes|
|Supports app routes?||Yes||Yes|
Guidelines in the UK Open Banking Documentation suggest that TPPs use Android App Link, not Custom URI Scheme.
Common issues with app-to-app redirection on Android
Note: These are common issues encountered using app-to-app redirection with TrueLayer products only.
Blank page on redirect:
This is usually caused when the redirect_uri is a custom URI scheme, and the device fails to handle the redirect. There are a lot of reasons why this could happen, which are specific to the device and previous user activity, not TrueLayer.
Use Android App Link, not Custom URI Scheme (Deep Link). With Android App Link, you have the option of multiple fallbacks if the device fails to successfully redirect and open your app, like redirecting to a webpage. (Which can trigger a callback to handle the request and offer the user a link to return to the app from there.)