New ID_Check v2.6.11 — a new ID recognition engine improves OCR for Korean documents, PII masking is now set from the dashboard, and submissions can be searched by custom fields (cf1–cf3). See what's new →
New ID_Check v2.6.11 — a new ID recognition engine improves OCR for Korean documents, PII masking is now set from the dashboard, and submissions can be searched by custom fields (cf1–cf3). See what's new →
This event is triggered when previously submitted KYC information is updated. Updates can occur due to manual changes by an administrator or system-driven modifications, and a KYC status change made through the PATCH/Submission API or the dashboard is also delivered as this event. This webhook allows you to track changes to KYC data in real-time and take immediate necessary actions.
The projection API can exclude full_name, gender, etc.For details, refer to this link.
This event is also sent when the KYC status is changed through the PATCH/Submission API or by editing the submission from the dashboard. On that path the approved / rejected webhooks are not sent; the new status is delivered as a string (approved or rejected) in data.kyc_result.In the Approved / Rejected events, which are sent as a result of review, kyc_result is an object — here it is a string. Handle this event as well so that status changes are not missed.
A unique ID is generated based on name, date of birth, gender, and nationality for duplicate checks. (*Always generated when all four criteria are provided.)
Email of the administrator who performed the update. For dashboard edits this is the signed-in administrator; for PATCH/Submission API calls it is the admin value from the request body.
English Full Name provided after KYC approval. The name is processed through transliteration and not translated. Returns null if KYC is not approved or name has not been transliterated.