In rare cases, such as network retries, read timeouts, processing delays, or delivery failures, the same webhook might be sent more than once for the same event. To prevent unintended side effects, implement idempotency in your webhook handler to handle duplicate deliveries.
Add webhooks
Add your webhook URL in our system for us to deliver webhook events. Follow the instructions below to configure the webhook URL. Ensure to provide the publicly accessible HTTPS URL to your webhook endpoint.- Log in to the Merchant Dashboard and click Developers.
- Click Webhooks listed under the Secure ID card.
- Click Add Webhook URL in the Webhook screen.
- In the Add Webhook popup, fill in the following information:
- Webhook URL - Enter the URL in this field.
- Click Test & Add Webhook.

Add Webhook
Webhook events
Event | Description |
---|---|
KYC_LINK_ACTION_PERFORMED | You will receive this event when one of the verifications is performed using the link. |
KYC_LINK_SUCCESS | You will receive this event when all the verifications are performed successfully. |
KYC_LINK_EXPIRED | You will receive this event when the link expires. |
Webhook payload fields
The webhook payload contains important metadata in its top-level fields.Field | Type | Description |
---|---|---|
signature | string | A Base64-encoded HMAC-SHA256 signature of the payload, generated using a shared client secret. |
event_type | string | Indicates the type of event that triggered the webhook. |
event_time | string | The UTC timestamp of when the event occurred, formatted in ISO 8601 (YYYY-MM-DDTHH:MM:SSZ ). |
version | string | Indicates the webhook format being used. Default version is “v1”. |
data | object | Contains event-specific details related to this feature. |
Verifying the signature is mandatory before processing any response. Refer to Signature Verification for more details.