Integrate our Auth interface into your mobile applicaiton

The following flow lays out the step by step process for integrating the Fiskil Auth Interface in your mobile app

Pre-requisites

Create an Auth Session by calling the POST /auth/session endpoint. This session is required to facilitate the linking of a bank account to an End User. Two important points to note here is that this endpoint requires an redirect_uri, which will be helpful later in this guide and the POST request returns an auth_url, for example - https://auth.fiskil.com/?session_id=ea564d-56012s4-6ds4564 in the response. This URL is used to integrate the Auth Interface in your mobile app.

Integration Process

As of now, we don't provide any native sdk for the Auth Interface, instead have a web interface available. So, to integrate Auth Interface in your mobile app you first need to generate an auth_url using POST /auth/session endpoint. Then you need to open a WebView (Android / iOS) inside your mobile app and visit the auth_url returned using the WebView. Once this is done, the user should be able to see your customised Auth Interface inside your mobile app.

Once the Auth Interface is successfully rendered the user will follow the process of linking their bank account inside the Webview. When this process is completed, the user will be redirected to the redirect_uri you passed while creating an Auth Session. Again, you have control of what this redirect interface can be, but for the purpose of this guide we will use the one suggested in the tip above https://auth.fiskil.com/success

Now, here's the most important part. In order to detect if a user has completed the flow or not you have to check for the current URL being visited inside the WebView. If the current URL value of the WebView matches with your redirect_uri, you can safely assume that the user has successfully completed the flow and you can close the WebView and navigate user to any appropriate screen in your mobile application.