Verification results are delivered primarily via webhooks. This page explains how to receive and handle them, check applicant status manually as a fallback, and recover missed webhook events.

Receive results via webhooks

Webhooks are the recommended way to receive verification results. When an applicant's verification is complete, Sumsub sends an applicantReviewed webhook containing the verification result.

Before going live, configure a webhook endpoint in your Production environment so Sumsub can deliver events to your server.

Handle multiple final webhooks

Sumsub may send more than one final webhook for the same applicant. For example, an applicant can be approved and later flagged as a fraudster, triggering a follow-up RED webhook. Update the applicant's status on your side each time a final webhook is received. For details on rejection outcomes, see Rejection labels.

Check status via API

If you need to check an applicant's status outside of the webhook flow, use the Get applicant verification steps status API method.

Recover missed webhooks

If a webhook delivery fails, Sumsub retries automatically on the following schedule:

• 5 minutes after the first attempt
• 1 hour
• 5 hours
• 18 hours

When processing a retried webhook, check the createdAt field in the payload to confirm it reflects the applicant's current status rather than a previous state.

To view webhook delivery history or trigger a manual resend, go to the API Health page.