DocumentationAPI Reference
DocumentationAPI ReferenceStatus

Verification checks

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.

Configure and consume checks

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.

Check statuses

Check StatusDescription
PassedThe check passed for the verification attempt.
FailedThe check failed for the verification attempt.
Not ApplicableThe 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:

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

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

Checks for Verification Type

Reference the API resource page for an up to date list of checks that are run and processed for each Verification.

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

Check NameConfidence Reason Value
id_account_comparisonaccount_comparison_failure
id_age_comparisonfailed_age_comparison
id_age_inconsistency_detectionportrait_age_inconsistency
id_barcode_detectionbarcode_not_detected
id_blur_detectionblurry
id_color_inconsistency_detectioncolor_inconsistency
id_compromised_detectioncompromised_image_matched
id_disallowed_country_detectiondisabled_country_code
id_double_side_detectiondouble_front
id_electronic_replica_detectionreplica_detected
id_expired_detectionexpired
id_extracted_properties_detectionlayout_mismatched
attribute_missing
id_extraction_inconsistency_detectionattribute_missing
barcode_mismatched
id_glare_detectionglare
id_inconsistent_repeat_detectionreused_image_matched
id_inquiry_comparisonclaims_conflict
id_mrz_detectionmrz_not_detected
id_portrait_detectionportrait_missing
id_selfie_comparisonselfie_comparison_failure
id_tamper_detectionimage_manipulated
exif_inconsistency
id_unprocessable_submission_detectionunprocessable_image
id_valid_dates_detectiondate_inconsistency
selfie_account_comparisonaccount_comparison_failure
selfie_glare_detectionglare
selfie_glasses_detectionglasses
selfie_id_comparisondocument_comparison_failure
selfie_multiple_faces_detectionpose_comparison_failure
selfie_pose_detectionpose_failure
selfie_pose_repeat_detectionpose_repeat_detected