Refresh - Resume Feature (Returning Users)

The Refresh 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.

What is the Resume Feature?

The Refresh Resume feature allows you to launch a new Flinks Connect session at the MFA 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.

How to Implement the Resume Flow

To initiate the the Refresh Resume feature:

#1. /Authorize call with loginId

With a valid loginId, the endpoint will respond with one of the following:

• 200 response:
  If you receive a 200 status, you can proceed to making a call to /GetAccountsDetail + /GetAccountsDetailAsync
  
  
• 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)
  
  

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

#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, you will then need to engage your cached call flow in order to retrieve the data for the given loginId, as you would if this was a standard connection made through Flinks Connect.

Benefits

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

• 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 Refresh Resume feature should be initiated when an end user is present and ready to action the MFA step if required.