- 🪪 ID document: ID photo-based
- 🧠 Knowledge-based: User input information-based
Use Cases
Financial Institution Automated KYC System
Financial Institution Automated KYC System
Global Service Regional Customized Operations
Global Service Regional Customized Operations
Age-Restricted Service Compliance Management
Age-Restricted Service Compliance Management
Fine-grained KYC adjustment with custom policies
Fine-grained KYC adjustment with custom policies
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.
- Conservative (70 points)
- Standard (50 points)
- Open (40 points)
- 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.
- Low Score (Conservative): More submissions are automatically approved, but some risky submissions may also be included.
- High Score (Strict): Safer with stricter verification criteria, but legitimate users may also be rejected.
- Recommended: It is recommended to start with conservative settings and gradually adjust based on operational data.
ID Recognition Guarantee Mode
Proceeds only when ID template recognition is successful.
| Setting | Description |
|---|---|
| ID Recognition Score | Administrators can directly adjust the reliability score for ID authentication. If reliability below the set threshold is produced, Retry occurs. |
Universal ID Support
Proceeds with recognition without selecting ID type in liveform. (Korea excluded)
Age Limit
KYC is rejected when users below the set age submit.
- 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.
- 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)
Blacklist Countries (Issuing Country)
KYC progress is restricted for IDs issued from selected countries.
- 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.
Start → Trigger (condition) → Action (result) → End structure.
| Component | Description |
|---|---|
| Policy Name | Enter a name to identify the policy. |
| Active / Inactive | Toggle to control whether the policy is active. Inactive policies do not affect KYC processing. |
Triggers (conditions)
Triggers define the conditions under which a policy is applied. When a condition is met, the connected action is executed.| Trigger | Description |
|---|---|
| User Edited Field | Triggered when a user modifies a field value recognized by OCR. You can specify target fields for all ID Types or per specific ID Type. |
| OCR Confidence | Triggered when the OCR engine’s per-field confidence score falls below a set threshold. Fields and thresholds can be configured individually per ID Type. |
| Warning Occurred | Triggered when specific warnings such as ID liveness detection or government verification issues are detected. |
Actions (results)
Actions define the operations to execute when a trigger condition is met.| Action | Description |
|---|---|
| Cap ARGOS SCORE | Limits the maximum ARGOS Score. Set a cap value between 0–100; the score cannot exceed this value. |
| Penalty | Deducts points from the ARGOS Score. Choose between absolute (fixed point deduction) or relative (percentage deduction) methods. |
| Override Status | Forces the KYC Status to a specified state. For example, you can automatically set the status to Pending or Rejected under certain conditions. |
Utilities
| Utility | Description |
|---|---|
| Sticky Note | Add notes to the flow canvas to document the policy’s intent or reference information. |
Creating a policy
Configure trigger
- User Edited Field: Select target ID Types and fields.
- OCR Confidence: Set fields and confidence thresholds per ID Type.
- Warning Occurred: Select warning types to detect.
Configure action
- Cap ARGOS SCORE: Enter the cap value (0–100).
- Penalty: Choose the deduction method (absolute/relative) and enter the deduction value.
- Override Status: Select the KYC Status to apply.
Policy application order
Custom policies are applied in the following order during KYC processing:- Auto-approval decision logic — Compares ARGOS Score against the Threshold to determine the initial KYC Status.
- Custom policy validation — Validates activated policies in order and executes actions.
- Duplicate user verification — Performs 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:| Scenario | Policy result | Final ARGOS Score | Final KYC Status |
|---|---|---|---|
| No policy applied | — | Original Score retained | Original Status retained |
| Score changed + Status changed | Both exist | Modified Score | Modified Status |
| Status only changed | Score unchanged | Original Score retained | Modified Status |
| Score only changed | Status unchanged | Modified Score | Modified Score ↔ Threshold re-comparison |
Policy application example
Policy application example
- ARGOS Score Threshold: 40 points
- Policy 1: Deduct 40 points (absolute) when low OCR confidence detected
- Policy 2: Override status to Rejected when low OCR confidence detected
- Original ARGOS Score: 96 points → Auto-approved (Approved)
- Policy 1 applied: 96 - 40 = 56 points (still above Threshold 40, so Approved maintained)
- Policy 2 applied: Status overridden to Rejected
- Final result: ARGOS Score 56 points, KYC Status Rejected
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: Best for applying the same ID Type policy across all countries. For example, use global settings if you want to “accept only passports from all countries.”
- Per Country: Best when different countries need different ID Type policies. For example, use per-country settings if you need a targeted strategy like “accept only passports in Country A, but allow both passports and driver’s licenses in Country B.”
Global
Applies the same ID Types uniformly across all countries.
Per Country
Configure ID Types individually per country through a CSV file.
Download Preset
Edit CSV File
| Value | Description |
|---|---|
TRUE | Allow this ID Type |
FALSE | Disallow this ID Type |
- 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.