VoPay + Flinks Integration – Open Finance Payments Service

Our partnership with Flinks allows clients who have an existing account to integrate with VoPay and take advantage of our open banking payments service. You can learn more here. In order to enable this integration you must provide us with your own Flinks API URL, which typically looks like this:

https://{instance}-api.private.fin.ag/v3/{customerId}

Flinks should provide you with your own {customerId} and an {instance} that uniquely defines your particular Flinks integration. Once your VoPay account has been configured to use Flinks, you will be able to make API calls using a Flinks Account and Login ID instead of the bank account and institution numbers.

Getting Started

You will first want to familiarize yourself with Flinks Connect. It is the module that assists all customers in connecting their bank accounts in a secure and intuitive way. All the complicated bank multi-factor authentication, edge-cases and error are handled so you don’t have to – all while keeping credentials from ever hitting your server.

Flinks connect is a component of your app that needs to be added in a webview. No hosting or additional server is needed.

Instructions

Step 1: Set up your VoPay account 

You’ll need accounts at both VoPay and Flinks in order to use the VoPay + Flinks integration. 

First, you will need to work with the VoPay team to sign up for a VoPay account, if you do not already have one.

If you do not have a Flinks account you can simply use our iQ11 service to generate your own iFrame and embed it in your platform. To integrate the iQ11 service, please refer to our documentation here: Intelligent EFT/ACH (iQ11).

Step 2: Integration workflow

The typical workflow for a Flinks-enabled integration with iQ11 are as follows: 

1. Navigate User to the Flinks login screen, typically using an embedded iFrame.
2. User selects their preferred financial institution from the iFrame.
3. User logs in to their online banking account.
4. User selects the account they wish to use.
5. Flinks redirects the user back to your website, and provides the login ID and Account ID.
6. You make an API call to the desired EFT endpoint, providing FlinksAccountID and FlinksLoginID instead of account number, transit number, and financial institution number.
7. iQ11 fetches the account number, transit number, and financial institution number for the specified Flinks Account ID and uses that to process the EFT transaction.

Support

Have a question? See our FAQ or contact our support team. We look forward to helping you digitize online bank payments with ease.