Introduction
Risk labels in Veriff play a crucial role in highlighting potential discrepancies during the verification process. This article explains how specific risk labels, such as "Session vendor provided name not similar with name on the document," operate and provides guidance on accessing relevant documentation.
How Risk Labels Are Triggered
Veriff's system uses a set of predefined conditions to decide whether specific risk labels are activated during a session. Below is an example of how one specific label functions:
"Session vendor provided name not similar with name on the document"
This risk label is triggered under the following conditions:
Data Population Requirements: - All four relevant name fields must be populated: the client's first and last names extracted from the document, as well as the vendor-provided first and last names. If any of these fields remain empty, the system cannot perform the comparison, and the label will not be triggered.
Similarity Threshold: - The label only activates if both the first and last names show a similarity below 60%. For instance, if the first name is a 100% match but the last name falls significantly below the threshold (e.g., 10%), the label will not trigger because the high similarity in the first name offsets the low similarity in the last name.
For example, in one specific case, the label did not appear because the extracted last name field was empty, thereby preventing the name comparison.
Finding Documentation on Risk Labels
For users looking to understand Veriff's risk labels and how they operate within the platform, detailed documentation is available. Veriff provides resources on identifying and addressing discrepancies through webhooks, which serve as a key tool for receiving real-time updates on verification sessions.
Key Documentation Resources
What are Webhooks? - Offers a general overview of webhooks and how they work.
Webhooks Guide - Explains Veriff’s webhook system in detail, including setup and data structure.
Decision Webhook Documentation - Details about webhook payloads, reasons for verification decisions, and fields used to flag risk labels.
These resources cover the operational frameworks that dictate how risk labels like "Session vendor provided name not matching with name on the document" are logged and communicated during verification sessions.
Conclusion
Understanding how Veriff’s risk labels operate can help troubleshoot discrepancies and improve workflow efficiency. Be sure to consult the relevant webhook documentation to gain insights into the rules governing each label and how they can impact verification sessions.