The flinks-doc Developer Hub

Welcome to the flinks-doc developer hub. You'll find comprehensive guides and documentation to help you start working with flinks-doc as quickly as possible, as well as support if you get stuck. Let's jump right in!


All customizable options for design and functionalities are controlled by the parameters that are entered directly as URL parameters into the iframe URL.

Here's an example:

All parameters and options available to you are described below:

Layout Customization

ParameterDefault ValueValid Values
themedarkdark, light
desktopLayoutfalsetrue, false
institutionFilterEnablefalsetrue, false
closeEnablefalsetrue, false
headerImgEnabletruetrue, false
headerEnabletruetrue, false
backEnabletruetrue, false
fixedHeightEnabletruetrue, false
boxLayouttruetrue, false
loadingTypedotsdots, progressbar
staticLoadingEnablefalsetrue, false


Flinks Connect support both light and classic (dark) themes for the Institution Selection menu and Institution Login page. While the changes only affects Flinks Connect layout, the main difference between themes are related to the Institution Selection menu, Institution Login page and default background colour.

Light Theme

Institution Selection menu:

Institution Login page:

Classic (Dark) Theme

Institution Selection menu:

Institution Login page:

Desktop Layout

To enable the browser responsive layout for the Institution Selection menu, you need to specify the parameter desktopLayout=true.

Institution Filter

To add a search bar into the Institution Selection Menu, you need to specify the parameter institutionFilterEnable=true.

Removing buttons and header

You can remove the back button from the Institution Login page by specifying the parameter backEnable=false. This is particularly useful for integrations that have a custom Institution Selection page.

You can remove both text and image from the header by specifying the parameter headerEnable=false, or just remove the image by specifying headerImgEnable=false.

Disable mobile fixed height

If the parameter fixedHeightEnable=false is specified, the fixed height (767px and under) on the institution selection page will be removed.

Close Button

You can give your users more flexibility and control by adding a close button directly to the Institution Login page. To enable the close button, specify the parameter closeEnable=true. If the button is clicked, Flinks Connect will show the event {step: "COMPONENT_CLOSE_SESSION", institution: "FlinksCapital"}.

Please note that this button doesn't perform any action directly in Flinks Connect besides the event in the Event Listener.

Login Page Box

If the Light Theme is being used but the desired Institution Login page layout is from the Classic theme, the parameter that needs to be added is boxLayout=true.


By default the dots animation is the one presented while Flinks processes the Authorize request. If you prefer using a more classic progress bar, specify the parameter loadingType=progressbar needs to be added.

To enable a loading screen while the app is loading, use the parameter staticLoadingEnable=true.


ParameterDefault ValueValid Values
languageenen, fr

Flinks Connect supports both English (default) and French languages for the interface. All requests initiated by Flinks Connect attempt to connect to the Financial Institution in the chosen Flinks Connect Language, which means that the Multifactor Authentication can also be prompted in the same language.

To activate the French version of Flinks Connect, the parameter language=fr must be specified.


ParameterDefault ValueValid Values
backgroundColor1c3265 (dark theme), f7f7f7 (light theme)Hex Color Code
foregroundColor1ffffff (dark theme), 000000 (light theme),Hex Color Code
foregroundColor26da4c9 (dark theme), 6da4c9 (light theme)Hex Color Code

This parameter helps you integrate Flinks Connect while maintaining the user experience and continuity that fit your brand.

Here, we played with the background and foreground colours of the Institution Selection menu:

User Consent

Consent Page

ParameterDefault ValueValid Values
consentEnablefalsetrue, false
featuresTransactionHistory, AccountNumber and AccountInfoTransactionHistory, AccountNumber and AccountInfo

Flinks Connect has an optional Consent Page that can be enabled to explicitly ask the end user for data access consent.

Each type of data accessed is listed on this page and the end user will only be able to proceed with the account connection if consent is given. This page will be displayed after the institution is selected, and before the Institution Login page.

Depending on the use-case not all types of data are collected. You might then want to limit the scope of the consent. Specify the Flinks features and their order on the list using the parameter feature.

By default all possible features are listed:

Here’s an example of a consent page with a limited scope for Flinks features and modified order:

In this example, the parameter features=AccountInfo,AccountNumber was specified.


List Order

The specified order of values for the features parameter will affect the order of the shown list.

Terms and Conditions

ParameterDefault ValueValid Values
termsNoCheckboxfalsetrue, false

If the end user has not accepted your service's terms and conditions in a previous step, you will need to add them on the Institution Login page. You can do so using the following parameters:

termsUrl: display the URL of your service terms, so your user can access them from the Institution Login page.

termsNoCheckbox=true: if set, this parameter will remove the checkbox but still show the terms and conditions text.

customerName: display name of your company, as you want it to appear in the Institution Login page for the terms sentence.

In this example, the parameter is set to customerName=FinTech

Enhanced Multi-factor Authentication

ParameterDefault ValueValid Values
enhancedMFAfalsetrue, false
skipEnhancedMFAfalsetrue, false
withMFAQuestionsfalsetrue, false

If your use-cases requires automatic account refresh, we recommended you use the Enhanced MFA flow. To activate this feature, the parameter enhancedMFA=true must be specified.

During the Authentication step, Flinks will attempt to extract all additional MFA Questions and Answers, besides the one that is commonly prompted in the first time connection.

Flinks will prompt the user to preemptively answer all additional questions. If you want to give the end user the option to skip this step, add the parameter skipEnhancedMFA=true.

If you have a custom integration with Flinks to manually handle the Enhanced MFA flow via the API, then you only need to specify the parameter withMFAQuestions=true.

Please note that the enhanced MFA only works for Simple Security Questions, and special MFA such as 2step verification are not supported for this feature.


ParameterDefault ValueValid Values
redirectUrl[string URL]
innerRedirectfalsetrue, false
jsRedirectfalsetrue, false

Flinks Connect will redirect the end user to a landing page once their account was successfully connected.

We recommend to set the Redirect URL to your custom landing page, which can be a Thank You page or a landing page specific to the next step in your process. Any parameters you have specified in the your landing page URL must be encoded.


Parameters in your Redirect URL

You must encode all parameters that are specific to your landing page URL.

βœ… Good usage:

❌ Bad usage: redirectUrl=

If the parameter redirectUrl is not specified, a generic Flinks hosted Thank You page will be set, along with the parameter innerRedirect=true.

In case the language is set to French by using the parameter language=fr, the Thank You page is going to be set as default.

Account Selection

ParameterDefault ValueValid Values
accountSelectorEnablefalsetrue, false
accountSelectorMultiplefalsetrue, false
fetchAllAccountsfalsetrue, false
accountSelectorNoTitlefalsetrue, false
eftEligibleRatio0.80.0 to 1.0
showAllOperationsAccountsfalsetrue, false
accountSelectorCurrencycad,usdcad or usd
showAllAccountsfalsetrue, false

Add the parameter accountSelectorEnable=true to enable the Account Selection feature in Flinks Connect.

After a successful authorization with the financial institution, Flinks Connect will prompt to the end user a summary of operations accounts that are eligible for Electronic funds transfer (EFT).

If you want to present your end user all operations accounts, even those not eligible for EFT, use the parameter showAllOperationsAccounts=true.

In case the text Please select an account does not fit into your use-case, you can remove it by using the parameter accountSelectorNoTitle=true, and any other desired copy can be added just above your iframe.

Example of the redirected URL when the Account Selector is enabled:

Example of the JS event for a selected account:

   accountId: ["7d213d26-d966-4229-8774-08d731543898"],
   institution: "FlinksCapital",


Account details for selected accounts

By default, Flinks Connect only collects the details of the selected accounts, but it is possible to still gather all accounts details by specifying the parameter fetchAllAccounts=true.

Display All Accounts

To display accounts from all categories for selection, including the ones that are not eligible for transfers (ETF), use the parameter showAllAccounts=true.

Note that when this parameter is used, other operation accounts filters such as eftEligibleRatio and showAllOperationAccounts are ignored.

Multiple Selection

By default, only a single account can be selected. In order to enable multiple accounts to be selected, the parameter accountSelectorMultiple=true needs to be set.

When multiple accounts are selected,

Example of redirected URL when multiple accounts are selected:,9290ca11-8352-4e88-8775-08d731543898&institution=FlinksCapital

Example of the JS event for new multiple accounts:

   accountId: ["7d213d26-d966-4229-8774-08d731543898", "9290ca11-8352-4e88-8775-08d731543898"],
   institution: "FlinksCapital",

When this feature is enabled, the AccountId of the selected account is going to be included in the redirected URL and the Event Listener, along with the LoginId.

Use Cases

Range of Transactions

ParameterDefault ValueValid Values
daysOfTransactionsDays90Days90, Days365
withTransactionstruetrue, false

By default, Flinks Connect extracts Transactions history data for the last 90 days. It is possible to increase its range to a full year, or configure it to avoid extracting transactions altogether.

To increase the range to a full year, you need to specify the parameter daysOfTransactions=Days365. If you do not need to collect the transaction history, specify the parameter withTransactions=false.

PDF Statements

ParameterDefault Valuevalid values
statementfalsetrue, false

In case you want to retrieve bank-issued PDF statements for the last 90 days instead of accounts details in a JSON format, specify the parameter statement=true.


We Will Unlock That for You

If you want to use this feature, please contact our support so we can enable it in your private instance.

Nightly Refreshes

ParameterDefault Valuevalid values
scheduleRefreshfalsetrue, false

If your use-case requires automatic account refresh to keep track of transactional history changes, you can enable the nightly refresh for new accounts. For this, you need to specify the parameter scheduleRefresh=true.


Fees may apply for nightly refreshes.


ParameterDefault Valuevalid values

It is possible to add a custom tag to a specific connected account which will be later returned into the API or with a webhook callback response.

This feature can be useful when reconciling Flinks LoginIds with end users, for example.

Wait Summary

ParameterDefault ValueValid Values
waitSummaryfalsetrue, false

If your flow is set so the Flinks Connect redirect is required to happen only after the GetAccountsSummary process is completed, you need to add the parameter waitSummary=true. This is mostly needed for flows where the account selection feature is not handled by Flinks Connect in a custom integration.


ParameterDefault ValueValid Values
maximumRetry991 to 99

By default, Flinks Connect doesn't limit the number of times the end user can attempt to enter their login credentials. You can limit these attempts in order to prevent your end user from being locked out of their account for entering the wrong credentials too many times. Specify the maximum number of attempts by using the parameter maximumRetry.

Sync - Authorize Only

ParameterDefault ValueValid Values
syncfalsetrue, false

Some custom integrations for very specific use-cases might need Flinks Connect exclusively for handling the Authorize process β€” and not the data extraction as usual. To enable this mode, specify the parameter sync=true.



Before using this feature, let's make sure you really need it. Drop a message to our Support Desk at [email protected]


ParameterDefault ValueValid Values
stringifyfalsetrue, false

If you need to have all your events from the Event Listener as strings instead of JSON, specify the parameter stringify=true.

Session Storage

Flinks Connect relies on the session storage feature from your users' browser in order to work properly.

If we detect that the browser does not support this feature we will prevent Flinks Connect's usage and display a message explaining why. Flinks Connect will also trigger the JS event {step: "SESSION_STORAGE_BLOCKED" }.

Another JS event is triggered when the user clicks on the retry button {step: "SESSION_STORAGE_BLOCKED_RETRY" }. The parent page (not the iFrame) needs to be reloaded if this event is triggered.

If the user activates the cookies / session storage feature, the browser will reload the parent page and the iframe will work as expected.

We use the word cookies in the message because most browsers will disable session storage when disabling cookies.

Example for reloading the page if {step: "SESSION_STORAGE_BLOCKED_RETRY" } is triggered:

<iframe src="" id="frameFlks" width="800" height="800"></iframe>
    window.addEventListener('message', function(e) {


Updated 10 days ago

What's Next

Now that you have the full list of possible parameters, you can either configure the main options, or understand more about the Events for you to have the full control over your user experience.

Configure and Install Flinks Connect
Start your Integration


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.