Documentation for a newer release is available. View Latest

Name Matching

Overview

Name matching refers to the way the Verification of Payee Responder (VoP) service matches names using the IPF Identity Resolution service, which is running embedded in VoP Responder.

The name matching logic provides a way to configure the thresholds used for name matching in the Verification of Payee Responder service. The thresholds determine how closely names need to match to be considered a match, a partial match, or no match.

Default Configuration

The default configuration for name matching is defined as follows:

Property Grouping: ipf.verification-of-payee.responder.name-match

Key Description Default Value

ipf.verification-of-payee.responder.name-match.thresholds

Name matching thresholds per account type

 
[
    {
        "score-lowerbound" : 0.8,
        "score-upperbound" : 0.9,
        "type" : "default"
    }
,
    {
        "score-lowerbound" : 0.85,
        "score-upperbound" : 0.95,
        "type" : "individual"
    }
,
    {
        "score-lowerbound" : 0.75,
        "score-upperbound" : 0.85,
        "type" : "corporate"
    }

]

This sample configuration defines three types of thresholds that can be changed as required:

  • default - Used when no specific type is specified or when the specified type is not found

  • individual - Used for individual accounts

  • corporate - Used for corporate accounts

This should match what is returned in the Account Management API accountType field.

Each threshold has two values:

  • score-lowerbound - The minimum score for a partial match

  • score-upperbound - The minimum score for a full match

If the score is below the score-lowerbound, it’s considered no match. If the score is between score-lowerbound and score-upperbound, it’s considered a partial match. If the score is above score-upperbound, it’s considered a full match.

Important Notes

  1. The default threshold type is required. If it’s missing, the application will throw an exception during startup.

  2. Duplicate threshold types are not allowed. If a duplicate is found, the application will throw an exception during startup.

  3. The thresholds are loaded during application startup and cannot be changed at runtime.

  4. The score-lowerbound should be less than the score-upperbound for each threshold type.

  5. The scores must be between 0.0 and 1.0.