Which product is it related to?
What is the names matching?
Process in which we compare the names found in the criminal, legal and international databases with the “official” name of a person, to determine if a record should be presented as part of the check or not.
What is the feature?
Names matching type settings lets customers define how strict they want our system to be during the names matching process. They will have two names matching type options:
soft_match (default): Includes all the records where the name retrieved from identity databases and the one found in criminal, legal and international databases present enough similarity to be considered the same person.
Designed for customers willing to receive all possible records related to a person, willing to accept some differences between the “official” name and the name retrieved from criminal, legal and international records. Those clients are usually more worried about false negatives.
Why is soft default?
Customers should be the ones deciding if they want to take the risk of ignoring records where the name was not exact.
exact_match: Includes only the records where the name retrieved from identity databases is exactly the same as the one found in criminal, legal and international databases.
Designed for customers willing to receive records only when there is an “exact match” between the “official” name and the name retrieved from criminal, legal and international records. Those clients are usually more worried about the false positives.
What problem are we solving?
Some criminal, legal or international databases don’t include the full “official” names of the people in their records.
Each customer assesses risk differently, this is also true when defining which records should be included as part of a check when making searches by name.
Before this feature, customers were not able to decide whether they wanted to include certain records found by name as part of their checks or not, all possible records were always included.
How to do it? How do I integrate?
API clients: Using our settings endpoint as explained in our API Docs: https://docs.checks.truora.com/#post-/v1/settings
Front clients: For now, clients willing to change their names matching settings will have to fill the following form: https://docs.google.com/forms/d/e/1FAIpQLScYmYlQ_SemNGcWyb8MeNh90PVyuQgtAam01DmjrAnsmmbgfQ/viewform
What happens if we don’t have this?
All clients would have soft names matching settings, bringing all records with names presenting enough similarity to be considered the same person.