Skip to main content
Cashfree sends event-based notifications when specific Video KYC events occur. Use these notifications to track the status and progress of VKYC in real time.
Network retries, read timeouts, processing delays, or delivery failures can cause the same webhook to be delivered more than once for the same event. To prevent unintended side effects, implement idempotency in your webhook handler to handle duplicate deliveries.

Webhook signature

You receive the webhook signature in the webhook header. The following table shows a sample header from a webhook request.
Always capture the webhook payload in its raw text format before parsing into JSON. Parsing and reserialising the payload can change the structure — for example, array ordering, spacing, or null handling — and cause a signature mismatch during verification. Use the exact raw body string from the request when computing the signature.

VKYC webhook events

The following events are triggered at different stages of the Video KYC process.

Webhook payload fields

The webhook payload contains important metadata in its top-level fields.

Data object fields

The following table describes the fields returned inside the data object.

Important status information

For certain webhook events, specifically VKYC_USER_PRECHECK_FAILED and VKYC_USER_CALL_SCHEDULED, you may encounter more than one status_code value. See the Status and status-code reference page for a comprehensive list of status and status_code combinations.
Verifying the signature is mandatory before processing any response. For more information, see Signature verification.