Webhook event: kyc.referred

When it fires

kyc.referred is emitted when verification is referred for manual checks. A redelivery of the same occurrence carries the same event id.

If your endpoint does not return a 2xx within the timeout, delivery is retried on an exponential backoff schedule — see Webhook delivery and retries. Design your handler to be idempotent so a redelivered event is safe to process twice.

Example delivery

{
  "id": "evt_KYCR9Z",
  "type": "kyc.referred",
  "created": "2026-07-05T12:00:00Z",
  "livemode": true,
  "api_version": "2026-07-01",
  "data": {
    "object": {
      "id": "kyc_9D2F6",
      "subject": "acct_4B8N2",
      "outcome": "referred",
      "reason": "document_review"
    }
  }
}

Handling it

A common handler will show a "checks in progress" state. Verify the signature, acknowledge with 200 within 10 seconds, then work asynchronously. Guard against out-of-order delivery using the created timestamp, and re-fetch the resource from the API if you need its live state.