Skip to main content
Authentication enhancement and forgery prevention functions allow you to customize the security level and verification methods of identity authentication in ID check projects. You can build optimal identity verification processes that meet customer security requirements through ID forgery prevention, face authentication, additional authentication options, meta-information-based verification, etc.
Function Application by Identity Authentication Method
  • 🪪 ID document: ID photo-based identity authentication
  • 🧠 Knowledge-based: User input information-based identity authentication

Feature Map

The options spread across three dashboard tabs are grouped into five pages.

ID Forgery Prevention

MRZ Check · PDF417 Check · ID liveness · Expired ID · Streaming Capture · Allow ID Upload (tab: ID and Face Based)

Face Authentication

Selfie Process · Face Duplicate Check · Selfie Liveness · Face-based Age Verification (tab: ID and Face Based)

3rd party Data Sources

1 Won Account Authentication · Government Data Verification · CURP Verification · Address Proof · Residency Expiration Date Query (tab: Additional Authentication & Meta Information)

Meta Information-based Detection

Proxy & VPN Detection · Regional Pre-screening · Email Owner Verification (tab: Additional Authentication & Meta Information)

Device Info

Device Verification · Sensor Verification · Fingerprint option · Device Duplicate Check (tab: 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

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

MRZ Check Settings

Generally, when name order is changed, similarity of about 85 points is calculated. If typos are a concern, you can implement a stricter authentication system by setting a higher threshold.
What each outcome means
Threshold example: at 85, an input with only the given name and surname swapped (about 85 points) sits on the boundary. Use 80 to tolerate swapped order, or 90 to also catch typos.

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 check settings

Driver's License Barcode (PDF417) Check Settings

Supported Countries
  • United States (USA)
  • Mexico (MEX)
  • Canada (CAN)
There is no setting other than the toggle. When on, the barcode on the back of the driver’s license is read and compared with the OCR data from the front. What each outcome means

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 settings

ID liveness - ID Copy Detection Settings

Detection Processing Method per pipeline: Each pipeline (Screen Replay / Paper Print / Portrait Replacement) can have its detection processing method configured independently.
When Retry and Warning occur simultaneously in settings between pipelines, it proceeds with Retry.
Apply Warning on Upload Each pipeline with Retry selected has a sub-checkbox Apply Warning on Upload. When checked, the pipeline’s Retry is converted to Warning only when the user submitted the ID via Upload mode, because Upload-mode users have no way to recapture.
  • 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.
Error Handling Method Separate from the Detection Processing Method above (which applies when forgery is detected), this option defines how to handle cases where the engine itself returns an error. Select via the radio buttons at the bottom of each pipeline card.
For the full error code reference, see Error Codes and Pages. For how to configure Warning Triggers, see the KYC Process guide.

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 processing method setting screen

Expired ID settings

Processing Method for Expired IDs: Submissions approved in Warning state leave the following Warning data on the dashboard.
Warnings caused by expired IDs can be used as a Custom Policy Trigger condition.
Example: if expired IDs still need to be accepted for internal record-keeping, set Expired ID to Warning. The submission is not blocked; a Warning is recorded and the flow continues.
How expiry is decided
  • 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.
When the period-of-stay table has several rowsA Korean Alien Registration Card is judged by the dates in the “period of stay” table on the back. If an extension is handwritten below the printed period, the handwritten row may not be read and the ID can be treated as expired. When several expiry dates are read, the latest is used and low-confidence dates are dropped. If such rejections are a concern, set Expired ID to Warning and hold those submissions as pending with a Custom Policy for manual review.

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.
Streaming capture settings

Liveform Streaming Capture Only Settings

When streaming capture only option is activated, users cannot upload photo files and must submit ID and selfie through real-time camera capture. Must be used together when using active liveness.

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.
Image Quality Check settings

Allow ID Upload and Image Quality Check Toggle

The Image Quality Check toggle is only visible when Liveform Streaming is ON and Allow ID Upload is ON. If either condition is OFF, the toggle is not displayed.
If you encounter cases where IQC repeatedly fails due to upload environment conditions, you can switch to OFF to allow users to complete the authentication flow.

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

Selfie Process Settings

Selfie Process UsageWhen selfie process is activated, you can use additional face authentication functions such as face duplicate check, selfie liveness, face-based age verification, etc.
What each outcome means
Threshold guide
  • 85 is the usual value.
  • If retryCode face_compare_underscore repeats 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

Face Duplicate Check Settings

Duplicate Face Policy Options:
  1. Register and Proceed: Records duplicate submissions for the case and continues the process.
  2. 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.
To activate face duplicate check function, Selfie Process must be activated first.
What each outcome means
To prevent multiple accounts, a threshold of 99 with reject-on-duplicate is a common combination. If the same person legitimately verifies again (re-verification, account recovery), keep register-and-proceed and decide in a Custom Policy or manual review.

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.
Selfie liveness settings

Face Duplicate Check and Selfie Liveness inside Selfie Process

Mode Selection Guide
  • Active Mode: Can more effectively block deepfakes or presentation attacks, but user experience may become somewhat complex.
  • Passive Mode: User experience is more convenient, but detection rate may be lower than active mode for some advanced attacks.
Auto CapturePassive-mode face capture uses Auto Capture: once the user aligns their face with the guide, the photo is taken automatically after about 1 second, without any button press.
When using active liveness, streaming capture only option must be used together.
Also, recognition improves when the user sets the phone screen brightness to maximum before capturing. Low screen brightness can lead to lower scores.
Error Handling Method — Passive mode only This option appears only in Passive mode. Separate from the liveness detection result (which applies when a spoofing attack is detected), this controls how to handle cases where the Passive liveness engine itself returns an error.
For the full error code reference, see Error Codes and Pages. For how to configure Warning Triggers, see the KYC Process guide.
What each outcome means

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

Face-based Age Verification Settings

Age Range and BufferFace-based age verification does not provide exact age but provides age range (Low, High) that the person likely belongs to. When verifying, Buffer can be applied to set verification criteria considering age range errors.
Verification Condition SettingsBy combining and setting Low, Median, High conditions, customers can directly set age verification criteria suitable for service characteristics. For example, stricter conditions can be set when minor blocking is needed.
Usage ScenariosWhen using only selfie (proceeding with face authentication only without ID), it is useful for age verification to block minors. You can implement minor blocking policies by setting target image as selfie photo and reference age as fixed value.
Simulation FunctionA simulation button is provided on the face-based age verification settings screen to test if the set conditions work correctly.
Settings (screen order) Worked example — blocking minors with the selfie Settings: target image = selfie, reference age = fixed 19, LOW extension = 2, condition = LOW ≥ reference age With the condition 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.
On failure a retake is requested; once the retry limit is exceeded the submission is rejected with reason 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

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

1 Won Account Authentication Settings

1 Won Account Authentication Process
  1. 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.
  2. Before 1 won is sent, the user reviews the financial institution, account number, and account holder (name on the ID) on a confirmation screen.
  3. System deposits 1 won to the account.
  4. User checks the 3-digit number in the depositor name of the deposit in their banking app and enters it.
  5. When the code and the account holder name match, account possession confirmation is complete.
User Screen Guide
  • For security, there is no back navigation. Users move between screens only with the on-screen buttons.
  • If the user re-enters an account and 1 won is sent again, a new code is issued and the previous code can no longer be used.
  • The number of verification attempts does not reset when the account is changed.
  • The account holder name returned by the bank is not shown on screen.
  • The banking app screen and the depositor name of the 1 won deposit follow each bank’s own language and rules.
  • Applies to all projects using 1 won account authentication with no additional project settings.

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 settings

Government Data Verification - Korea (Individual switches per ID type)

Individual control switches:
Scope of the Alien Registration switchThe single Alien Registration switch controls authenticity verification for all three ID types simultaneously: alien registration card, domestic residence report for foreign nationals of Korean descent, and permanent residence card. All foreign-national-related IDs are managed under one switch.
When required values for authenticity verification are missingIf values required for authenticity verification (name, date of birth, resident registration number, etc.) are absent from the submitted data, the switch is always treated as not applied even when it is ON.
Error Handling Method The error handling method can be configured individually per ID type. Separate from forgery detection, this applies when the authenticity verification engine itself returns an error. Select via the radio buttons below each ID type switch.
For the full error code reference, see Error Codes and Pages. For how to configure Warning Triggers, see the KYC Process guide.
What each outcome means

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

CURP Third-party Verification Settings

Each verification field (full name, gender, date of birth) can be switched on or off; only full name has a similarity threshold (for example 80). What each outcome means

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

Address Information Verification Settings

There is no setting other than the toggle. When on, an address step is added to Liveform. How it works
  1. The user searches for and selects an address. Autocomplete suggestions appear while typing, and the details of the selected address are loaded.
  2. The selected address is checked against the user’s location.
  3. To add address verification to an existing submission, open Liveform with the action=addveri parameter. See the Injection guide.
Results appear in the submission detail and the submission API.

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

Residency Expiration Date Query Settings

Residency Expiration Date Query UsageWhen verifying identity for foreign residents or visa holders, you can query residency expiration date information from Korean government database to verify residency qualifications.
Settings What each outcome means

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

Proxy & VPN Detection Settings

VPN & Proxy Pre-verification List

Learn how to view Proxy & VPN detection results.
There is no setting other than the toggle. It is off by default; when off, VPN and proxy users are not blocked. How it works When the user enters Liveform (after the Device Info checks), the risk of the connecting IP is looked up. A combined risk score covering Proxy, VPN, Commercial VPN, Hosting Provider and TOR of 90 or more blocks that IP for 48 hours. Results are listed per submission in the VPN & Proxy pre-verification list. What each outcome means

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 Exception Settings

Regional pre-screening target 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: Operation Method:
  • 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.
Which method to choose
“Target designation” does not mean “block that country”For example, if you add a single country under Target designation › IP country based to stop IDs from other countries being submitted from that country’s IPs, only submissions from that country’s IPs are compared. Submissions from any other foreign IP are not checked and pass. To accept domestic residents only, turn on Exception settings and leave the exception list empty. Genuine residents who are abroad will be blocked as well, so add only the countries you want to allow as exception countries.
Exception settings and target designation cannot be used simultaneouslyRegional pre-screening can only be used by selecting one of exception settings or target designation. The two methods cannot be activated simultaneously, so select and set the method suitable for your service requirements.

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

Email Owner Verification Settings

Email Owner Verification Process
  1. User enters email address.
  2. System sends authentication code to the email.
  3. User enters the received authentication code.
  4. When code matches, email ownership verification is complete.
There is no setting other than the toggle. Under the toggle, Edit template lets you change the verification email sent to users. You can edit it even while the switch is off.
Verification email template editor

Email Owner Verification — verification email template

What each outcome means
Pass the email in the Liveform URL with the email query string so the user does not have to type it again. To limit how many times the same email can submit, use Authentication Data › Submission limit.

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 Info is the first validation upon Liveform entryPre-verification runs in the following order. If the Device Info stage fails, the user is immediately redirected to an error page and no subsequent stages are performed.Device Verification → Fingerprint option → Turnstile → Proxy & VPN Detection → KYC Process
Checks run at entry and at captureDevice Verification runs at Liveform entry. Sensor verification runs at ID and selfie capture, and Fingerprint can run again at capture through its verification triggers. Values collected at capture are compared against the values from entry to determine whether the device or environment was swapped.See Device Verification pre-verification list for how to review the results.

Device 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 settings

Device Verification — Static check

Static check — performed on Liveform entry
If even one of the enabled checks fails, the user is redirected to an error page (DE-20000) and cannot proceed with KYC.

Device Verification Pre-verification List

View the Device Verification result list and detail fields.

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

Sensor Verification settings

Legitimate users may also fail in webview (in-app browser) environmentsSome in-app browsers do not deliver device sensor signals, so Sensor verification can fail even when a real user captures with a real device. Before enabling this option, review how your users reach the Liveform and, if needed, prompt them to open it in an external browser. See the WebView integration guide for details.If you host the Liveform in a native app WebView, users cannot fall back to an external browser as they can with in-app browsers. In that case the app must grant device motion/sensor permission for Sensor verification to work. If the app does not grant sensor permission, sensor signals are never delivered and even legitimate users fail.
Detection criteria are continuously updated, and specific decision logic and threshold values are not disclosed for security reasons.

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 settings

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. At the capture stages, it only compares whether the visitorId matches the entry stage (same-device check).
Duplicate check runs only at entryEnabling ID capture or selfie capture does not run or record Device Duplicate Check at those stages. This is by design, to prevent users from being rejected because their own earlier stage was flagged as a duplicate.

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. Policy on duplicate detected:
Meaning of Detection period OFFWhen the detection period toggle is set to OFF, all past approval history accumulates. Using this setting in long-running projects may unintentionally block legitimate users, so configure carefully together with the allowed count.
For details on error codes DE-30000 and DE-40000, see the Error Codes and Pages reference.

Use Cases

Banks or securities companies can secure the highest level of security by activating multiple authentication options such as government data verification, 1 won account authentication, face duplicate check, etc. Deepfakes or presentation attacks can be effectively blocked through active mode of selfie liveness and ID attack prevention functions.
Companies providing global services can accurately authenticate IDs from each region by utilizing country-specific verification options such as MRZ check (passport), PDF417 barcode check (North American driver’s license), CURP third-party verification (Mexico), etc.
E-commerce or sharing economy platforms can preemptively block fake account creation or ID forgery attempts through forgery prevention options such as Proxy & VPN detection, ID validity verification, mandatory real-time camera capture, etc.

For recommended setting combinations by industry, see the KYC Settings Simulator. Pick an industry to see which settings to turn on, including the features on this page, in KYC step order.
Excessive security option activation may hinder user experience, so it is important to set appropriate security policy levels suitable for service characteristics.

KYC Process

View basic authentication policies.

Pre-verification List

View VPN & Proxy and Device Verification pre-verification results.

Authentication Data

Learn how to manage authentication data.

Contact Us

Email customersupport@argosidentity.com with any additional questions.