- 🪪 ID document: ID photo-based identity authentication
- 🧠 Knowledge-based: User input information-based identity authentication
Feature Map
- By dashboard screen
- By verification flow
ID Forgery Prevention
Face Authentication
3rd party Data Sources
Meta Information-based Detection
Device Info
Option Dependencies
Some options can only be enabled after another option is on.ID Forgery Prevention
ID forgery prevention options on the ID and Face Based tab. They block forgery and fraud attempts during identity verification.
ID and Face Based Settings Tab
MRZ Check
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “ID and Face Based” tab › ID Forgery Prevention Scans MRZ (Machine Readable Zone) existing on IDs to verify information accuracy. (e.g., bottom of passport)
MRZ Check Settings
Driver’s License Barcode (PDF417) Check
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “ID and Face Based” tab › ID Forgery Prevention Scans barcodes of US, Mexico, and Canada driver’s licenses to verify information accuracy.
Driver's License Barcode (PDF417) Check Settings
- United States (USA)
- Mexico (MEX)
- Canada (CAN)
ID liveness - ID Copy Detection
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “ID and Face Based” tab › ID Forgery Prevention Can specifically detect forgery methods (presentation attacks) that frequently occur in ID-based authentication.
ID liveness - ID Copy Detection Settings
- The checkbox can be configured independently per pipeline (e.g., enabled for Screen Replay and Paper Print but not for Portrait Replacement).
- The checkbox appears only when Retry is selected. It is hidden when Warning is selected.
- Submissions auto-converted to Warning under Upload mode appear in the Custom Policy list with the following values.
Expired ID
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “ID and Face Based” tab › ID Forgery Prevention Choose whether submissions with an expired identification document go to Retry or Warning.
Expired ID settings
- Decided at Step 1 (ID recognition). It applies only when OCR adopted the expiry date as a valid value, and the ID counts as expired when that date is before today in UTC. An ID that expires today passes.
- A Korean Alien Registration Card has no expiry date on the front, so the dates in the “period of stay” table on the back are used.
- With Retry, the user goes straight to a retake and cannot edit the expiry date. The submission is rejected once the retry limit (default 3) is exceeded.
Liveform Streaming Capture Only
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “ID and Face Based” tab › ID Forgery Prevention Allows only real-time capture for both ID and selfie and blocks photo uploads to configure a live capture-based submission environment. Click the allow ID upload button to allow ID uploads.
Liveform Streaming Capture Only Settings
Allow ID Upload — Image Quality Check
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “ID and Face Based” tab › ID Forgery Prevention › inside the “Liveform streaming capture only” card When the Liveform streaming capture only option is ON and Allow ID Upload is turned ON, users can upload an image as an alternative to camera capture to submit their ID document. The Image Quality Check toggle appears alongside this option, allowing you to decide whether to apply the same frontend quality checks as the camera capture.
Allow ID Upload and Image Quality Check Toggle
Face Authentication
Face authentication options on the ID and Face Based tab. Every option in this section requires Selfie Process to be enabled.Selfie Process
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “ID and Face Based” tab › Face Authentication You can register user face information through face recognition. When used in ID document pipeline, it compares the portrait on the ID with the user’s Selfie.
Selfie Process Settings
- 85 is the usual value.
- If retryCode
face_compare_underscorerepeats in submission details and the final rejection is for exceeding retries, check whether the threshold is too high for your user base.
Face Duplicate Check
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “ID and Face Based” tab › Face Authentication › inside the “Selfie Process” card You can check for duplicates with already approved person photos. Requires selfie process to be activated.
Face Duplicate Check Settings
- Register and Proceed: Records duplicate submissions for the case and continues the process.
- Reject if Duplicate: Enter a count (for example 1) in the box next to the radio button. Authentication is rejected when a match with an already approved person occurs that many times or more. With 1, a single match with an approved face is enough to reject.
Selfie Liveness
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “ID and Face Based” tab › Face Authentication › inside the “Selfie Process” card You can choose between Active mode (deepfake detection) and Passive mode (texture-based detection). Requires selfie process to be activated.
Face Duplicate Check and Selfie Liveness inside Selfie Process
Face-based Age Verification
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “ID and Face Based” tab › Face Authentication A function that analyzes face images to estimate age range and verifies by comparing with set reference age. Provides age range (Low, High) rather than exact age, and verification criteria can be set by applying Buffer.
Face-based Age Verification Settings
LOW ≥ reference age
MEDIAN ≥ reference age, user B passes (23 ≥ 19). A LOW condition means “even the youngest plausible age is above the bar”, so it is strict; a MEDIAN condition is lenient. A larger extension makes LOW conditions stricter and HIGH conditions more lenient.
AGE_VERIFICATION. The estimates and per-condition results are available in the submission API under verification.faceAge (usedValues, conditionResults). Use the Simulation button on the settings screen to test numbers before going live.3rd party Data Sources
External data source verification options on the Additional Authentication & Meta Information tab.
Additional Authentication & Meta Information Settings Tab
1 Won Account Authentication - Korea
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “Additional Authentication & Meta Information” tab › 3rd party Data Sources Confirms account possession through 1 won authentication.
1 Won Account Authentication Settings
- User enters the account number. While typing, matching financial institutions are suggested. If the right one is not listed, the user opens the full list (banks and securities firms) from the Financial institution field.
- Before 1 won is sent, the user reviews the financial institution, account number, and account holder (name on the ID) on a confirmation screen.
- System deposits 1 won to the account.
- User checks the 3-digit number in the depositor name of the deposit in their banking app and enters it.
- When the code and the account holder name match, account possession confirmation is complete.
Government Data Verification - Korea
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “Additional Authentication & Meta Information” tab › 3rd party Data Sources Performs government data verification for IDs issued in Korea. Individual switches per ID type let you choose which Korean ID types to verify.
Government Data Verification - Korea (Individual switches per ID type)
CURP Third-party Verification - Mexico
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “Additional Authentication & Meta Information” tab › 3rd party Data Sources Performs Mexico CURP number verification through official external sources.
CURP Third-party Verification Settings
Address Proof
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “Additional Authentication & Meta Information” tab › 3rd party Data Sources Performs location-based address verification.
Address Information Verification Settings
- The user searches for and selects an address. Autocomplete suggestions appear while typing, and the details of the selected address are loaded.
- The selected address is checked against the user’s location.
- To add address verification to an existing submission, open Liveform with the
action=addveriparameter. See the Injection guide.
Residency Expiration Date Query - Korea
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “Additional Authentication & Meta Information” tab › 3rd party Data Sources Queries and verifies Korean government’s residency expiration date information for passports from other countries.
Residency Expiration Date Query Settings
Meta Information-based Detection
Meta information-based detection options on the Additional Authentication & Meta Information tab. Risk is detected from IP address, region, and similar metadata.Proxy & VPN Detection
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “Additional Authentication & Meta Information” tab › Meta Information-based Detects IP-based risk and blocks the IP for 48 hours when risk score is 90 or above.
Proxy & VPN Detection Settings
VPN & Proxy Pre-verification List
Regional Pre-screening
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “Additional Authentication & Meta Information” tab › Meta Information-based A function that controls access by comparing user’s IP country with ID issuing country. By default, it blocks access when user’s IP country differs from issuing country, and detailed policies can be configured through exception settings and target designation.
Regional Pre-screening Exception Settings

Regional Pre-screening Target Settings
Exception Settings
You can set countries to process as exceptions in regional pre-screening.Pre-screening Exception Countries
When IP address belongs to the country, pre-screening passes even if IP country and issuing country differ. Operation Method:- If user’s IP address is included in the exception country list, access is allowed even if IP country and issuing country do not match.
- For example, if “United States” is added to exception countries, pre-screening passes when accessing from US IP regardless of issuing country.
Issuing Country Pre-screening Exception
When ID issuing country belongs to the country, pre-screening passes even if IP country and issuing country differ. Operation Method:- If the issuing country of the ID submitted by the user is included in the exception country list, access is allowed even if IP country and issuing country do not match.
- For example, if “Korea” is added to exception countries, pre-screening passes when using IDs issued in Korea regardless of IP country.
Target Designation
You can designate targets to apply regional pre-screening. It is not an OR condition, but selects one of IP country based or Issuing country based to designate targets. On screen, choose Target designation, then pick Apply pre-screening by IP country or Apply pre-screening by issuing country, and select the target countries below. As the tooltip puts it, pre-screening runs only when the user connects from a designated IP country or holds an ID from a designated issuing country. Setting Options:- When accessing from IP addresses of countries designated as screening targets or using IDs issued from those countries, always compares IP address and issuing country and blocks access if they do not match.
- For countries not designated as screening targets, pre-screening check is not performed.
Email Owner Verification
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “Additional Authentication & Meta Information” tab › Meta Information-based Performs email ownership verification by sending code during Liveform process.
Email Owner Verification Settings
- User enters email address.
- System sends authentication code to the email.
- User enters the received authentication code.
- When code matches, email ownership verification is complete.

Email Owner Verification — verification email template
Device Info
A dedicated tab for configuring device-based pre-blocking options. Device Info verification is performed first when entering the Liveform. If blocked at this stage, the user cannot proceed to subsequent pre-verification steps (Turnstile, Proxy & VPN) or the KYC process itself.Device Verification → Fingerprint option → Turnstile → Proxy & VPN Detection → KYC ProcessDevice Verification
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “Device Info” tab A Static check that analyzes browser, GPU, and touch information to preemptively block access from non-mobile devices (desktops, virtual environments, automated bots, etc.).
Device Verification — Static check
Device Verification Pre-verification List
Sensor Verification
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “Device Info” tab An option that verifies the device’s sensor signals at the moment of capture to detect attempts to forge the camera path and inject pre-prepared images (media injection). Toggled on or off as a single switch.
Sensor Verification settings
Fingerprint option
📍 Menu location Project Management › Policy and Authentication › Authentication Enhancement and Forgery Prevention › “Device Info” tab Advanced threat detection options based on device fingerprinting. Detects virtual environments, emulators, malicious bots, and tampered browsers, and controls repeated approvals from the same device through Device Duplicate Check.
Fingerprint option and Device Duplicate Check settings
Detection items
Select the items to block using individual checkboxes. If any checked item is detected, the user is redirected to an error page (DE-30000).
Verification triggers
Select the stages where Fingerprint is additionally called.Device Duplicate Check
Limits the number of times a KYC approval can occur from the same device. Can be toggled ON/OFF independently while the Fingerprint option is enabled.Use Cases
Financial Institution High-Security KYC Process
Financial Institution High-Security KYC Process
International Service Multi-country ID Verification
International Service Multi-country ID Verification
Online Platform Fraud Prevention System
Online Platform Fraud Prevention System