How verifications work
Verifications move through various statuses as they progress from initialization to data submission and finally verification completion. Verifications are independent objects that are associated with an Organization. In order to configure collection options and requirement status verification checks, a VerificationTemplate is needed. A Verification can be created either through our hosted/embedded flows or through an external API.
Verification lifecycle
The basic flow of a verification looks like this:
- A new Verification is initialized with the status
initiatedwith configuration from a VerificationTemplate - Attributes and images are attached to the verification
- A verification is submitted with the status of
submittedand attributes and images are no longer able to be changed. - Persona will process the submitted data and generate checks and decision status 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 requires a reattempt, the verification status is updated to
requires_retry
Verification statuses
| Status | Description |
|---|---|
created | Verification has started, claimed information can now sent and saved to the server for verification |
confirmed | Verification has been confirmed. This is a status specific to PhoneNumber verifications where they have verified a confirmation code that was entered. |
submitted | Verification has been submitted, the claimed information is frozen and the server 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 |
cancelled | Verification timed out. This is usually indicative of an internal server error |
Updated over 2 years ago