Skip to main content
Flinks provides two features to handle interrupted connections: Resume for reloading at an MFA step, and Mid-Session Reconnect for refreshing an existing account’s data within the same session.
Both features must be activated by Flinks support. Contact your Flinks Representative to enable them for your instance.

​
Resume feature

The Resume feature allows a customer to return to their MFA step if their session was interrupted (e.g., they closed the browser or navigated away).

​
How it works

  1. When a customer reaches an MFA prompt, Flinks stores the session state.
  2. If the customer leaves and returns, they can reload Flinks Connect with the same requestId.
  3. Instead of starting over, they are taken directly back to the MFA prompt.

​
Timeouts

TokenValidity
requestId8 minutes of inactivity
Authorize token15 minutes
If the session returns an HTTP 203 status code, it means the customer is in the middle of answering a security challenge and the session can be resumed.

​
Implementation

To resume a session, reload the Flinks Connect iframe with the existing requestId: 
https://{instance}-iframe.private.fin.ag/?requestId={requestId}&...
If the requestId has expired, the customer will need to start a new session.

​
Mid-session reconnect

Mid-Session Reconnect allows you to refresh an existing account’s data by initiating a new live connection using the customer’s stored loginId — without requiring them to go through the full Flinks Connect flow again.

​
How it works

  1. Call the /Authorize endpoint with the following parameters:
    • LoginId: The customer’s existing loginId
    • MostRecentCached: false (to force a live connection)
    • Save: true (to update the stored data)
  2. If the financial institution requires MFA, the API returns a 203 status with security challenges.
  3. Handle the MFA response using the /Authorize endpoint with SecurityResponses.
  4. Once authorized, call /GetAccountsDetail with the new requestId to retrieve fresh data.

​
Use cases

  • Refreshing data when Nightly Refresh has failed for an account
  • Collecting updated transaction history on demand
  • Re-authorizing when an account’s MFA answers have changed
Mid-Session Reconnect initiates a live connection to the financial institution. The customer may be prompted for MFA, and the connection will count as a billable request.