KYC Process

KYC process settings allow you to fine-tune identity authentication processes in ID check projects. You can build customized identity verification systems that meet business requirements through various options such as automatic processing rate adjustment, ID recognition guarantee, age and country restrictions, custom policy rules, and more.

​

Use Cases

---

​

ARGOS Score Threshold

Set the ARGOS score criteria to use for KYC verification. You can select the threshold for ARGOS score that determines automatic processing rate from a dropdown. Setting Option Examples:

• Conservative (70 points)
• Standard (50 points)
• Open (40 points)

The higher this score, the higher the threshold for the comprehensive score (total authentication score of ID, selfie, and other authentication fields) required for submission approval.

• Through custom settings, you can set the ARGOS score threshold to 99, then use the client API option in Project Settings > System Operation > Reviewer Settings to enable customers to review directly.

---

​

ID Recognition Guarantee Mode

Proceeds only when ID template recognition is successful. When this function is activated, eKYC can only be submitted with IDs that OCR AI can recognize. If an unrecognized ID is submitted, users must retake photos with a different ID.

---

​

Universal ID Support

Proceeds with recognition without selecting ID type in liveform. (Korea excluded) When activated, users no longer need to select ID type. ARGOS automatically recognizes all supported ID types except South Korea. Since only the front and back of the ID need to be photographed, cases where users incorrectly select ID type are greatly reduced.

---

​

Age Limit

KYC is rejected when users below the set age submit. You can set age restrictions. This may be suitable when you want to restrict identity authentication for users below a certain age.

• This age limit function works based on the date of birth shown on the ID.
• For age limit functions through selfie, you must use Face-based Age Verification.

Configuration Method:

• Enter age in the number input field. (e.g., 13 years old)
• Users below the set age are automatically rejected when they submit.

---

​

Automated Processing Only

Submissions not automatically approved are rejected. (Manual review excluded) When activated, the project operates with 100% automated processing only. All submissions requiring manual review (Pending) are rejected, and users must resubmit eKYC to be automatically approved.

---

​

Blacklist Countries (Issuing Country)

KYC progress is restricted for IDs issued from selected countries. Set Blacklist Country based on the ID’s issuing country. Use this option when identity authentication restrictions for users from specific countries are needed. Multiple countries can be selected, and country search and additional input are possible. Configuration Method:

• Search for countries to restrict through the country search function.
• Select countries from search results to add.
• Multiple countries can be selected and added to the blacklist.

---

​

Custom Policy Rules

Control ARGOS Score calculation and KYC Status decision logic with custom rules. You can create up to 5 policies per project.

​

Policy editor

Click the + Add Policy button to open the policy editor. In the editor, you build policies by connecting triggers (conditions) and actions in a visual flow. Drag triggers and actions from the Tools panel on the left onto the canvas to build your flow. Each policy follows the Start → Trigger (condition) → Action (result) → End structure.

​

Triggers (conditions)

Triggers define the conditions under which a policy is applied. When a condition is met, the connected action is executed.

​

Actions (results)

Actions define the operations to execute when a trigger condition is met.

​

Utilities

​

Creating a policy

​

Policy application order

Custom policies run immediately after the ARGOS Score decision, and are applied in the following order during KYC processing:

1. ARGOS Score (auto-approval) decision — Compares ARGOS Score against the Threshold to determine the initial KYC Status.
2. Custom policy validation — Runs immediately after the ARGOS Score decision, validating activated policies in order and executing their actions.
3. Automated Processing Only enforcement — A step that runs after custom policies. If the “Automated Processing Only” option is enabled, any Pending status at this stage (including a Pending forced by a custom policy) is rejected (automatic_verification_fail).
4. Search-based duplicate user verification — A step that runs after custom policies, performing a final check for duplicate users.

​

Final result determination logic

After custom policy application, the final ARGOS Score and KYC Status are determined by the following rules:

---

​

Supported ID Type Management

Set the ID types allowed in your project. You can configure this in two ways — Global and Per Country — choose the method that best fits your business requirements.

​

Global

Applies the same ID Types uniformly across all countries. In the Supported Document Types area, you can add or remove allowed ID types as tags. The ID Types selected here are applied identically to all countries.

​

Per Country

Configure ID Types individually per country through a CSV file. CSV Upload Validation Rules:

• All countries included in the Preset must exist in the CSV.
• Values for ID Types supported by the Preset must not be missing.
• ID Types not supported by the Preset cannot be set to any value other than FALSE.

​

Per-Country Settings Lookup

Regardless of whether global or per-country settings are used, you can check the currently applied settings status for each country. Select a country from the dropdown to view the allowed ID types and their activation status (TRUE / FALSE) for that country.

---

​

Related Documentation