Verification Checks

When individuals attempt to verify themselves, 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.

Configure and consume checks

There are a set of default checks that are required for the submission to be passed, while others are running 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.

Check statuses

Check Status	Description
Passed	The check passed for the verification attempt.
Failed	The check failed for the verification attempt.
Not Applicable	The check was not evaluated for the verification attempt (e.g. `id_barcode_detection` will not be evaluated if the back of the ID is not required to be submitted).

Check types

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 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 template.

Match results

For Database Verifications, each piece of information submitted like name or birthdate is matched against the record returned from the source database, and Persona returns three possible match results for each piece of information as separate checks:

None: The information did not match.
Partial: The property matched, but did not match exactly. Persona utilizes algorithmic processes (i.e. fuzzy matching) to determine the mathematical similarity between two pieces of information. This allows for the passing of near matches, which avoids unnecessary failures if the individual inputs an accidental typo or, in the case of name, a nickname (e.g. "Mike" instead of "Mikey"). For example, a date of birth of 12/15/1990 would partially against a birthdate of 12/14/1990.
Full: The information matched exactly.

For more information about configuring the minimum match requirement for each piece of information, please contact us.

Verification Checks table

Each Verification Type has a set of Verification checks designed for that type. See the full set of checks in the Verification Checks table in your Dashboard.