When individuals attempt to verify their identity, verification checks indicate something of note with the information that was submitted. They determine whether the verification attempt passes or fails and help you understand whether the submission is valid and meets your requirements, or if additional investigation is needed.
There are a set of default checks that are required for the submission to be passed, while others are ran and used for additional review but do not affect whether an attempt passes or fails. The defaults are determined based on the common needs across our customers, but we are happy to work with you to configure the defaults to meet your unique requirements. For more information about configuring requirements and the potential tradeoffs, please contact us.
Verification checks are returned in the Retrieve a Verification API response and are viewable in the Dashboard for each verification attempt.
Different checks are evaluated across different Verification Types, which are specified at the beginning of the check slug.
The check passed for the verification attempt.
The check failed for the verification attempt.
The check was not evaluated for the verification attempt (e.g.
There are two check types:
User action required: The individual did not submit the at-minimum high-quality and unobstructed images needed for verification. For instance, if an individual submits a blurry image. Persona exposes these checks back to the individual in the inquiry flow as hints to help individuals submit better images.
Fraud: The individual may be trying to verify with false or altered information. For instance, if the face portrait from the ID doesn't match the face from the selfie. There may be additional, noteworthy details about the submission that can be used to meet specific fraud requirements for different use cases. For instance, if the individual submitted an ID from a country that was not allowed on the VerificationTemplate.
Reference the API resource page for an up to date list of checks that are run and processed for each Verification.
- Government Id Verification Checks
- Phone Number Verification Checks
- Database Verification Checks
- Phone Carrier Database Verification Checks
- TIN Database Verification Checks
If you are using our legacy verification checks, known as confidence reasons, please refer to the Confidence Reason(s) column in the table below to understand how they map to the new verification checks.
Confidence Reason Value
Updated about 1 month ago