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 a KYC submission is rejected. Rejection can occur due to automated verification failures, manual review results, or other policy-related reasons. This event allows you to immediately identify the reasons for the KYC rejection and take necessary actions, such as providing feedback to the user or requesting additional information.
The projection API can exclude full_name, gender, etc.For details, refer to this link.
This event is sent only when the status is determined to be rejected through the review process. If kycStatus is changed to rejected through the PATCH/Submission API or by editing the submission from the dashboard, this event is not sent — the change is delivered as an Updated event instead.
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.)