Skip to main content
When you enable this feature in your Flinks Connect integration, we’ll review the information the customer has provided you against the information on the account they’re attempting to connect. We’ll let you know if the results are a match.

How it works

The Field Matching service is built into your existing Flinks Connect flow. When a customer starts the process to connect their bank account to your application, call the /FieldMatch API and send us your customer’s data. We’ll review particular data points on the account they’re attempting to connect, including the full name and postal code. Set up your configuration to handle the next steps depending on the results you receive. For example, if the response you receive indicates a match, you may want to set up your integration to proceed with the account connection process. To discuss the different ways your configuration can handle the results you receive, contact your Flinks Representative. Complete the following steps to set up the Field Matching service:
2
Complete the full connection process for at least one customer account. To start using the Field Matching service, you’ll need a 200 response from the /GetAccountsDetail endpoint and at least one loginId.
3
Set up your API connection.
4
Pass us your customer data using the /FieldMatch API. Use the loginId you received from your successful /GetAccountsDetail call.
5
Set up your configuration to handle the next steps depending on the API response. For example, if the response you receive indicates a match, you may want to set up your integration to proceed with the account connection process. To discuss the different scenarios, contact your Flinks representative.
6
Work with your Flinks representative to complete testing and confirm your integration is working as expected.

Match Rate examples

The Field Matching Service allows you to confirm your customer’s identity, confirm account ownership, or verify the accuracy of the information before connecting a customer’s bank account to your financial service. The /FieldMatch API responds by providing a match rate, along with the data points on the account that the customer is attempting to connect. The match rate refers to how closely the customer information that you pass using the FieldMatch resembles the data points on the account. Refer to the table below for a description of each match score range. For examples of what this can look like in real life, see Matching Examples.

Matching examples

We review the customer’s full name and postal code on the account they’re attempting to connect. For examples of what the matches will be in each range, review the sections below. If not all fields are available, only the fields that are provided will be analyzed in the match score.

Name matching examples

Postal Code matching examples