Implementation guide: Identify WebUI

In order to show the Identify WebUI, the steps mentioned above need to be completed. As previously mentioned, depending on how the user’s consent and how transactions will be sourced the user journey looks a little bit different. The sections below will describe the process in further detail, but will separate based on whether a Premium API and Open Banking or PSD2 API will be used.

Once the user has been onboarded and there is a valid consent for the user, the user journey will look as in the image below:

930930

Overview of the steps for identifying subscriptions through the WebUI

Get the WebUI URL

Our sync endpoint enables the full Identify feature; the function varies based on the state of the user's consent.

If we have a valid consent for a user, we will return a WebUI url ready for you to include in your WebView which allows the user to access the platform. While the WebUI is loading, we are asynchronously fetching transactions and identifying the user's subscriptions to ensure that all information is available in the Subscription Overview.

If we do not have a valid consent for a user and if you are providing a Premium API, we expect to get a consent that is valid to fetch transactions for in the payload for the endpoint, inserted in the code parameter. The consent inserted in the API is most likely represented by a refresh token or an authorization code that can be exchanged for a refresh token. As we are orchestrating the fetching of transactions, we will collaborate with you in order to agree on a format during the implementation.

If the user does not have a valid consent and if we are using your PSD2 or open banking API, we will return a URL from where the user will be able to provide a consent. Once the consent has been provided the user will be redirected to our platform.

Display the WebUI to the user

The response from the sync endpoint will contain a URL and an access token. You will

  1. Append the access token to the URL as a parameter &accessToken=<accessToken>.
  2. Visit the webUI.

To learn more about how to work with our WebUI, please read the WebUI guide.

Transaction fetching

For users with valid consents, we can fetch transactions and find subscriptions. The first time the user visits our platform, we fetch around 2 years of transactions to be able to give the user the best experience. The next time the user visits, a delta is calculated and we only fetch transactions we have not seen before.

10001000

Technical flow for the transaction pull method for fetching transactions