Skip to main content

​
Overview

KYC validation branches into Reject / Retry / Warning based on the result. Warning skips only the affected check and continues the KYC flow — nothing is blocked and the user is not asked to retake the photo; only a record is left.The accumulated Warning records appear in the warning[] array of the GET Submission API response. Each element contains the fields userDataType, relatedEngine, and occurrenceTime. Customers can pick these values up with the “Warning Occurred” trigger in Custom Policy to apply post-processing such as ARGOS Score deductions, Pending status, or Reject.This page lists the 11 WarningOccurred values produced by the liveform, grouped by the mechanism that generates them, the field combination each value exposes in warning[], and the dashboard option that controls it.

​
warning[] Field Schema

For the full response field definitions, see GET Submission response fields.

​
Group A — ID Liveness Upload-mode Warnings

In the ID Liveness policy, when a pipeline (Screen replay / Paper printed / Replace portraits) is set to Retry and the sub-option “Apply Warning on Upload” is enabled, the Retry decision is converted to a Warning only when the user submitted via Upload mode. Upload mode does not allow re-capture, so the flow continues with a Warning instead of forcing a Retry.
See the April 2026 update — ID Liveness Upload-mode automatic Warning conversion — and the Anti-Fraud & Forgery Prevention dashboard guide for configuration details.

​
Group B — Expiry-validation Warnings

When the dashboard option for ID expiry / passport stay expiry is set to Warning, the submission is not auto-rejected; instead it is Approved with a Warning record.
For the Retry / Warning behavior of the Expired ID option, see the April 2026 update — Expired ID post-processing options. For the stay-period expiry field, see expiryDateOfStayKor.

​
Group C — Engine-error Warning Conversion

For ID Liveness · Selfie Passive Liveness · Korean government verification engines, the dashboard provides an Error Handling Method setting. When this is set to Warning the flow does not redirect to the engine-specific error page (SE-5002x / SE-5003x); the affected check is skipped and a Warning record is left instead.
Face Compare engine errors (SE-50022) are Error-only and cannot be converted to Warning. Matching the selfie to the ID photo is core to KYC integrity, so no skip branch is provided.
For configuration, see the May 2026 update — Error Handling Method — Warning conversion & Custom Policy integration — and the Anti-Fraud & Forgery Prevention dashboard guide. For the full SE error code mapping, see Error codes and pages.

​
Using Warnings in Custom Policy

Each item recorded in warning[] can be picked up by the Custom Policy → Trigger → “Warning Occurred” condition in the KYC Process dashboard, and acted on with a post-processing step.

​
Matching conditions

Conditions are built from combinations of userDataType and relatedEngine. Examples:

​
Applicable post-actions

  • ARGOS Score deduction (e.g. -10 to -30)
  • Switch the result to Pending for manual admin review
  • Reject the submission
  • Default pass-through (when no policy applies)
The Trigger list, operators, and action composition in Custom Policy are documented in the KYC Process dashboard guide.