{
"event": "kycUpdated",
"eventId": "0d6f1a2b-3c4d-4e5f-8a9b-0c1d2e3f4a5b",
"kyc": {
"approved": false,
"needsWork": true,
"status": "inProgress",
"userMessage": "Please upload a current government-issued ID."
},
"occurredAt": "2026-09-29T19:00:00Z",
"organizationId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
}Webhook Events
kycUpdated
Sent to kycUpdated subscriptions when a customer’s KYC status changes, and when a write you sent was accepted but could not be applied. organizationId is the customer organization.
When kyc.needsWork is true, the customer can correct and resubmit, and kyc.userMessage says what to fix. needsWork also arrives without a status change, when one of the verification endpoints answered 202 and the work then failed; status is then the customer’s current status, and userMessage names what to send again. See KYC API error handling.
The X-Signature header contains an HMAC-SHA256 signature over the RFC 8785-canonicalized JSON body. See Verifying Webhooks.
WEBHOOK
kycUpdated
{
"event": "kycUpdated",
"eventId": "0d6f1a2b-3c4d-4e5f-8a9b-0c1d2e3f4a5b",
"kyc": {
"approved": false,
"needsWork": true,
"status": "inProgress",
"userMessage": "Please upload a current government-issued ID."
},
"occurredAt": "2026-09-29T19:00:00Z",
"organizationId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
}Headers
Body
application/json
Response
200
Return any 2xx to acknowledge the delivery.