Verification Checks

Each verification type has a set of configurations that you can adjust to tailor it for your use case and risk threshold. These configurations are called verification checks.

Each verification type has a distinct set of specifically-designed checks. For example, the government ID verification type has verification checks that let you configure:

• What type(s) of government ID to accept (e.g. driver’s license, passport, etc)
• Whether to require both the front side and back side of the ID to be submitted
• Whether to reject IDs that were previously submitted by other accounts in your Persona organization

See the full set of checks in the Verification Checks table in your Dashboard.

Configure required and non-required checks

Each verification check can be configured to be required or not required. All required checks must pass in order for any given instance of a verification to pass. You can use non-required checks as additional context when you inspect the results of a verification.

Each verification type has a default set of required checks. These defaults are determined based on common needs across Persona customers.

We are happy to work with you to configure the defaults to meet your unique requirements. Please contact us to get help configuring verification checks.

Retrieve checks

Verification results, including the details of each verification attempt and its individual checks, can be viewed in the dashboard.

Verification checks can also be fetched via the Retrieve a Verification API.

Understand check results

Check statuses

A verification check has three possible resulting statuses:

Check types

Each verification check is annotated with a check type. There are two check types:

1. User behavior: Failing this type of check indicates that the user did not provide a high-enough quality submission, or did not correctly follow instructions. For example, a user behavior check may fail if the end user submits an image that does not meet the required quality bar (e.g. if they submit a blurry image). For these checks, Persona gives hints to the end user in the inquiry flow to help them fix the issue.

2. Fraud: Failing this check indicates that the end user may be trying to verify with false or altered information. For instance, one example fraud check fails if the face portrait from the submitted government ID doesn’t match the face from the submitted selfie.

Availability

Most verification checks are generally available, but there are two launch stages to be aware of:

• beta: These checks are available to the public, but may be constantly tuned by Persona with different thresholds. Their geographic coverage may also be limited and be expanded gradually.
• sunset: These are checks that Persona has deprecated in favor of other checks.

Learn more

See our Help Center for details about how you can use and customize verification checks. A few starting points:

• Enabled vs Disabled and Required vs. Non-required Verification checks
• Verification check configurations
• Verification check attributes
• Where can I find the list of verification check fail reasons?