In this article

1. Page 1 — Custom Consent Page
2. Page 2 — Financial Institution (FI) Selection
3. Page 3 — Authentication Flow
4. Page 4 — Success Page
5. Quick Reference: Key Parameters
6. Related Resources

1. Disable the Flinks Consent Screen.
   Add consentEnable=false to your iframe URL. This skips the default Flinks consent page.
2. Host a Custom Consent Page.
   The client creates and hosts their own branded landing page. This is the first screen the end user sees before the Flinks iframe loads.
3. Add Branding & Messaging.
   Include your logo and a clear message such as: "[Client Name] uses Flinks to securely connect your account."
4. Replicate Required Consent Disclosures.
   The custom page mustinclude the three transparency sections present on the default Flinks consent screen:
   • What information Flinks collects
   • What is shared with the client
   • Your information, your choice (data privacy options)
5. Include the Flinks Privacy Statement Agreement.
   Display a statement that by continuing, the user agrees to the Flinks Services Privacy Statement.
6. Configure the "Agree and Continue" Button.
   Create a button that, when clicked, loads the Flinks Connect iframe (with consentEnable=false in the URL).

1. Disable the Flinks Header.
   Add headerImgEnable=false to the iframe URL. This removes the Flinks logo and header from the top of the widget.
2. Create a Custom Parent Container.
   Embed the Flinks iframe inside a parent <div> that includes the client's brand colours, logo, and a custom call-to-action. Example: "Select your bank to continue with [Client Name]."
3. Size the iframe Correctly.
   Ensure the iframe height is sufficient to display the "Search 100+ financial institutions" bar and the list of banks without scrolling.
4. Preserve the Trust & Security Message.
   The Flinks security message — "Flinks is trusted by 500k+ monthly users" — must remain visible within the iframe. Do not crop or hide it.

1. Use the Same Configuration as Page 2.
   Keep headerImgEnable=false in the iframe URL and maintain the same client-branded parent container wrapping the iframe.
2. Preserve Core Authentication Functionality.
   Do not intercept or modify the iframe content. The login form, MFA prompts, and session management are handled internally by Flinks.
3. Maintain the Branded Wrapper.
   The parent container with the client logo and messaging remains visible throughout the authentication screens, providing a consistent branded experience.

1. Set the redirectUrl Parameter.
   Add redirectUrl=https%3A%2F%2Fyourclient.com%2Fsuccess to the iframe URL. Once the user completes the connection flow, Flinks will redirect them to this URL instead of the default Flinks success page.
2. Whitelist the Redirect URL with Flinks (Required).
   For security, Flinks requires that the domain used in the redirectUrl parameter be whitelisted on the Flinks side. This is a mandatory step — if the URL is not whitelisted, the iframe will fail to load and will display an error.
3. Open a Support Ticket to Request Whitelisting.
   Submit a support ticket via the Flinks Help Centre with your redirect domain and instance name:
    How to Open a Support Ticket
4. Build Your Custom Success Page.
   Design and host a branded success page at the whitelisted URL. Include confirmation messaging, next steps for the user, and your brand elements.