Learn about the status and lifecycle of IdentityVerifications
Falu Identity's verification flows are asynchronous, which makes them complex to manage as they rely on customer interactions that are external to your application. IdentityVerifications, which are Falu's programmatic representation of a verification, keep track of the verification flow and, in doing so, simplify their management.
An IdentityVerification can take the following statuses through its lifecycle:
Session events
Events are created every time and IdentityVerification session changes status. Below is a full list of the IdentityVerification event types.
| EVENT TYPE | DESCRIPTION |
|---|
| identity_verification.created | The session was created. |
| identity_verification.processing | The user has successfully submitted their information, and verification checks have started processing. |
| identity_verification.verified | Processing of all the verification checks have completed, and they have all been successfully verified. |
| identity_verification.input_required | Processing of all the verification checks have completed, and at least one of the checks failed. |
| identity_verification.cancelled | The session has been canceled, and future submission attempts have been disabled. This event is sent when a session is either cancelled or redacted. |
| identity_verification.redacted | The session was redacted. You must create a webhook endpoint which explicitly subscribes to this event type to access it as webhook endpoints that subscribe to all events will not include this event type. |
- You might need to take action when certain events occur, for example, mailing your user when a verification either fails or succeeds.
- We recommend that you listen for events with webhooks