Flinks Connect – Resume Feature

The Resume feature in Flinks Connect enhances the user experience and improves conversion by enabling sessions to be reloaded at the exact point where users previously left off or where their interaction is required. This functionality is especially useful for handling drop-offs and multi-factor authentication (MFA) scenarios.

What is the Resume Feature?

The Resume feature allows you to reopen an existing Flinks Connect 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

1. Recovering from Drop-Offs

If a user drops off during a Flinks Connect session — whether due to closing the window, losing internet connection, or simply deciding to return later — the Resume feature enables the session to restart from the last active step.

Example scenario:

• A user selects their financial institution and enters login credentials but closes the window before completing MFA.

• Later, using the same session ID, the Resume flow brings them directly back to the MFA prompt without redoing the initial steps.

2. Hybrid API + UI MFA Handling

Clients can use Flinks' API to initiate a request (Refresh with LoginId), but wait until user interaction is necessary before presenting the UI.

When user action is needed — such as entering MFA codes — Flinks Connect can be launched using the session ID, and it will automatically resume at the MFA step.

Example scenario:

• A server triggers an aggregation request using Flinks' API.

• The response indicates an MFA prompt is required.

• The frontend then launches Flinks Connect using the session ID, and the user is taken directly to the MFA input screen.

This approach allows clients to manage request flows programmatically while preserving a smooth user experience when human input is required.

How to Implement the Resume Flow

To enable the Resume feature:

1. Store the requestId returned by the initial API call.

2. Launch Flinks Connect and provide this requestId as an iframe URL parameter, as in http://toolbox-iframe.private.fin.ag/v2/?demo=true&requestId={guid}.

3. Flinks Connect will use the request ID to automatically detect the step the session was at, and reload it appropriately.

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.

• Use the Resume feature for MFA handling, user interruptions, or multi-step flows.

• Ensure your UI handles reloading Flinks Connect gracefully when invoked after a delay.