Skip to main content
You can co-brand Flinks Connect so it blends into your product. This guide walks through the four stages of the flow and the parameters that control branding at each. For the full list of every parameter and its default value, see the Widget Parameters reference.
For a fully-hosted, no-code branded experience, also consider Flinks Express, a template we fully customize with your branding and host on your behalf.
The end user moves through four screens: the consent page, financial institution selection, authentication/MFA, and the success page. Each stage below explains how to blend it into your brand.

​
1. Consent page

By default, Flinks Connect shows its own consent screen listing the data the connection will access. To host your own branded consent or landing page instead, bypass the default screen with consentEnable=false.
Url Example
https://toolbox-iframe.private.fin.ag/v2/?consentEnable=false
This lets you present consent within your own design system, before the widget loads.

Hosting your own consent page is a compliance requirement

If you replace Flinks’ default consent screen with your own, you must include the three required transparency disclosures:
  1. What information is collected from the end user.
  2. How that data is shared with your organization.
  3. The user’s privacy choices.
Your consent page must also include agreement language referencing the Flinks Services Privacy Statement. This is mandatory: you cannot disable the default consent screen without providing a compliant replacement.

​
2. Financial institution selection

On the institution selection screen, remove the Flinks logo from the header so it doesn’t compete with your branding. Use headerImgEnable=false:
Url Example
https://toolbox-iframe.private.fin.ag/v2/?headerImgEnable=false
Then wrap the iframe in your own parent container that displays your logo and branding around it. The iframe renders your users’ institution options while your surrounding page carries your identity.
The security message shown to users must remain visible. Do not hide or obscure it in your wrapper.

​
3. Authentication / MFA

The credentials and multi-factor authentication (MFA) screens inherit the same configuration from the institution selection step. No additional parameters are needed. Your branded wrapper persists throughout, and the header and consent settings you applied earlier continue to apply.

​
4. Success page

After a successful connection, send users to your own branded success page instead of the generic Flinks thank-you page. Use redirectUrl:
Url Example
https://toolbox-iframe.private.fin.ag/v2/?redirectUrl=https%3A%2F%2Fexample.com%2Fthank-you
Remember to URL-encode the redirect URL, including any parameters specific to your landing page.

Whitelist your redirect domain before go-live

The domain used in redirectUrl must be whitelisted by Flinks before go-live. Share it with us by opening a support ticket. If the domain is not whitelisted, the iframe fails to load entirely and the URL updates to an error state:
https://instance-iframe.private.fin.ag/v2/Error?validRedirectUrl=false
Also remember to URL-encode the redirect URL and any of its parameters.

​
Quick reference

PARAMETERVALUEEFFECT
consentEnablefalseBypasses the default consent screen so you can host your own
headerImgEnablefalseRemoves the Flinks logo from the header
redirectUrl{encoded URL}Redirects to your own branded success page after a connection
For the complete list of parameters, default values, and valid values, see the Widget Parameters reference.

​
Next steps

Widget Parameters

The full reference for every Flinks Connect customization parameter.

Flinks Express

A fully-hosted, no-code branded experience we manage on your behalf.

UX Best Practices

Tips to maximize conversion and build trust with your customers.