Verification Lifecycle

In the Persona data model, a verification is an independent object that is associated with a Persona organization.

A verification moves through various statuses as it progresses from initialization to data submission and finally to verification completion.

Verification lifecycle

The basic lifecycle of a verification looks like this:

A new verification is initialized with the status initiated. It is configured from a VerificationTemplate object.
- A VerificationTemplate describes the collection options and required verification checks for a verification. You will need to create this template first.
As the end user completes the verification, attributes and images are attached to the verification.
The verification is submitted with the status of submitted. Attributes and images can no longer be changed.
Persona processes the submitted data and generates check and decision statuses based on the configuration from the VerificationTemplate.
- If verification passes, the verification status is updated to passed.
- If verification fails, the verification status is updated to failed.
- If verification skipped, the verification status is updated to skipped.

Status	Description
`initiated`	Verification has started. Claimed information can now sent and saved to the server for verification.
`confirmed`	Verification has been confirmed. This status is specific to PhoneNumber and Email verifications, where a confirmation code has been entered and verified.
`submitted`	Verification has been submitted. The claimed information is frozen and Persona will process the verification.
`passed`	Verification has passed. The required checks have passed and the information is verified.
`failed`	Verification has failed. Some or all of the required checks have failed and verification has failed.
`requires_retry`	Verification requires a resubmission. The checks could not be fully processed due to issues with the submitted information. Note: This status is now deprecated. For use cases that may require a retrying a verification, it is recommended to condition on the `passed` status, `failed` status, or if within an inquiry, number of failed verification attempts within the inquiry.
`canceled`	Verification timed out. This usually indicates an internal server error.
`skipped`	Verification skipped. This is a status specific to AAMVA verifications submitted for a non-participating jurisdiction.

See our Help Center for more details about the verification lifecycle: