About a Flinks integration

This page goes through the required parts for a successful integration.
Most of our customers integration requires a client-side (front-end) and a server-side (back-end) component.

Most of our customers integration requires a client-side (front-end) and a server-side (back-end) component. We will focusing on in this quickstart guide.

The first piece is an iframe we call Flinks Connect. It is a plug and play widget that lives within your front-end application and allows your users to provide explicit and informed consent to authorize a secure link to their bank account.

The second piece is a series of back-end API calls in order to retrieve the data that you need about the account once it has been authenticated.

The quickstart guide will walk you through in detail how to complete this integration pattern, which can then be easily adapted for your unique Use-Cases.

🚧

Custom API integration

A small segment of our clients will opt to complete a full custom API integration rather than use Flinks Connect on the front end using our Flinks API Reference. This can provide you with more nuanced control over the UX, but does require a more significant investment and a more complex development efforts. Be sure to speak to us before diving in!

See what new insights you'll soon be able to unleash

Understand what's needed before you can go to prod


What’s Next

Ready to dive in? It's time to get building! 🛠️