Flinks Connect – Resume Feature

The Resume feature in Flinks Connect enhances the returning user experience and improves conversion by enabling sessions to be reloaded at the multi-factor authentication (MFA) step. This functionality is especially useful for handling drop-offs and returning users.

What is the Resume Feature?

The Resume feature allows you to reopen an existing Flinks Connect session or launch a new session at a specific step, instead of starting the process over from the beginning. This provides a seamless and efficient way for users to complete their connection journey without re-entering data or repeating prior steps.

Common Use Cases

• Recovering from Drop-Offs
• Returning Users

How to Implement the Resume Flow

#1. Initiate a session by making an /Authorize call with the loginId specified.

• Please note that "Save": true must be specified in the body of your request.

With a valid loginId, the endpoint will return one of the following responses:

• 200 response
  • If you receive a 200 status, you can proceed to making a call to /GetAccountsDetail + /GetAccountsDetailAsync.
    • Please note that any data parameters required must be specified in the body of your request (for example, "withTransactions": false).
  • If receiving the /GetAccountsDetail data via webhook integration, you will receive the data shortly.
• 203 response
  • The above snapshot shows the scenario where the endpoint returns a 203, which indicates that an MFA challenge has been prompted, and that the user's engagement is required.
  • The output of this process, RequestId, will be used as an iframe parameter on the Flinks Connect widget, as described on the next step (#2).
• Any response other than a 200 or a 203
  • The end user will need to be presented with your standard Flinks Connect flow.
    
    

#2. Launch a Flinks Connect session and provide this RequestId as an iframe URL parameter, as in http://toolbox-iframe.private.fin.ag/v2/?requestId={guid}. Flinks Connect will use the requestId to automatically resume the session.

• Please note that this requestId will remain active for 8 minutes, after which it will timeout if there is no user interaction.
• If polling our API endpoints in order to retrieve the /GetAccountsDetail data, please include the sync=true parameter in your iframe URL as well.
• If receiving the /GetAccountsDetail data via webhook integration, do not include the sync=trueparameter in your iframe URL.
  • Please note that any data parameters required must be specified in your iframe URL (for example, accountSelectorEnable=true).

#3. Once the user responds to the MFA prompt, they will be presented with the success screen and the REDIRECT event will be triggered to inform you the connection has been completed.

#4. Once you receive confirmation of a successful connection:

• If polling our API endpoints, you can proceed to making a call to /GetAccountsDetail + /GetAccountsDetailAsync.
  • Please note that any data parameters required must be specified in the body of your request (for example, "withTransactions": false).
• If receiving the /GetAccountsDetail data via webhook integration, you will receive the data shortly.
  
  

Benefits

• Improved user experience: No need to restart the flow from scratch.

• Higher conversion rates: Drop-offs are more recoverable.
• Flexible integration: Combine API-driven logic with user-facing flows seamlessly.
  
  

Tips and Best Practices

• Always store the requestId when initiating a request that may later require user input, please note that the requestId is valid for 8 minutes. Following 8 minutes, the requestId will no longer be usable.

• The Resume feature should be initiated when an end user is present and ready to action Flinks Connect if required.