Asynchronous verification flows are complex to manage because they depend on customer interactions that happen outside of your application. VerificationSessions simplify this by keeping track of the status of the verification flow.
|The session was created.|
|The user has successfully submitted their information, and verification checks have started processing.|
|Processing of all the verification checks have completed, and they’re all successfully verified.|
|Processing of all the verification checks have completed, and at least one of the checks failed.|
|The session has been canceled and future submission attempts have been disabled. This event is sent when a session is canceled.|
|The session was redacted. You must create a webhook endpoint which explicitly subscribes to this event type to access it. Webhook endpoints which subscribe to all events will not include this event type.|
You might want to take action in response to certain events, such as emailing your user when a verification fails or succeeds.
Stripe recommends that you listen for events with webhooks.