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.
Enable Identity in your Flinks Connect integration
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.
| RANGE | DESCRIPTION | WHEN TO USE |
|---|---|---|
| 1 | Exact Match | The data points are an exact match and the fields contain identical customer information. |
| 0.80-0.99 | Strong Match | There may be some spelling errors, nicknames, abbreviations, or missing characters in the data fields, but the information is a very close match. |
| 0.65-0.79 | Possible Match | There may be aliases or missing information, but the data points have some similarities. |
| 0.50-0.64 | Unlikely Match | The accounts have similar information, such as a last name or a postal code, but most likely do not belong to the same person. |
| 0-0.49 | Very Unlikely Match | This information has no common factors. |
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
| RANGE | DESCRIPTION | EXAMPLE |
|---|---|---|
| 1 | Exact Match | John Doe, John Doe |
| 0.80-0.99 | Strong Match, likely relates to a spelling error, nickname, or alternative spelling | John Doe, Jon Doe |
| 0.65-0.79 | Possible Match, likely relates to multiple issues such as a spelling error and an alias used | John Doe, Jane Do |
| 0.50-0.64 | Unlikely Match, could indicate a relative | John Doe, Steve Doe |
| 0-0.49 | Very Unlikely Match, no common factors | John Doe, Air Bud |
We are only matching against English characters
If you pass any names that include any non-English characters, such as é, ê, à, etc., we are not able to match against them. This may result in lower match scores for names that include these characters.Postal Code matching examples
| RANGE | DESCRIPTION | EXAMPLE |
|---|---|---|
| 1 | Exact Match | H3B 5E8, H3B 5E8 |
| 0.80-0.99 | Strong Match, format not exactly matching or addition of characters | H3B 5E8, H3B 5E8A |
| 0.65-0.79 | Possible Match, one letter/number does not match | H3B 5E8, H3B 5E5 |
| 0.50-0.64 | Unlikely Match, multiple letters/numbers do not match | H3B 5E8, H2B 1FS |
| 0-0.49 | Very Unlikely Match, no common factors | H3B 5E8, N2T 1F5 |