> ## Documentation Index
> Fetch the complete documentation index at: https://developers.argosidentity.com/llms.txt
> Use this file to discover all available pages before exploring further.
# KYC Process
> Learn how to fine-tune identity authentication processes including ARGOS score threshold, ID recognition guarantee mode, universal ID support, age limits, automated processing only, blacklist countries, and custom policy rules.
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.
**Function Application by Identity Authentication Method**
* 🪪 **ID document**: ID photo-based
* 🧠**Knowledge-based**: User input information-based
## Use Cases
Banks can optimize automatic processing rates by adjusting ARGOS score thresholds, provide 24-hour unmanned KYC services by activating automated processing only option, accept only reliable IDs with ID recognition guarantee mode, and comply with legal requirements by setting age limits.
Platforms providing international services can manage service restrictions for specific regions through blacklist country settings and improve user convenience with universal ID support. Various countries' IDs can be automatically recognized to improve user experience.
In alcohol or adult content services, legal requirements can be complied with through age limit functions. Users below the set age are automatically rejected, ensuring regulatory compliance.
With custom policy rules, you can cap ARGOS Score when low OCR confidence is detected, apply score penalties when users edit specific fields, or automatically override KYC status to rejected when forgery warnings occur — enabling business-specific verification logic.
Since setting options interact with each other, balanced settings considering business goals and user experience are important. It is recommended to **start with conservative settings** and gradually adjust based on operational data.
***
## 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.
**ARGOS Score Threshold Selection Guide**
* **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.
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.
| 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. |
**ID Recognition Score Usage**
When ID recognition score is 80 or above and all fields recognized during ID photo are normal value recognition, the **ID photo result confirmation page is omitted** in the user view.
***
## 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.
If you want to be able to select only specific ID types as valid identity verification means, please contact customer support. Currently, only ARGOS administrators can configure this per project.
***
## 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](/dashboard/en/project-management/policy-and-authentication/anti-fraud-and-forgery-prevention#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.
**Age Limit Usage**
Can be used in services requiring age restrictions according to legal requirements (alcohol, adult content, gambling, etc.). Users are automatically rejected based on their date of birth, ensuring compliance.
***
## 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.
**Automated Processing Only Precautions**
When the automated processing only option is activated, all submissions requiring manual review are rejected. It is important to appropriately set the ARGOS score threshold to optimize automatic processing rate.
**Automated Processing Only Usage**
Can be used when providing 24-hour unmanned KYC services or when manual review exclusion is not needed. Optimal automatic processing rate can be achieved by adjusting together with ARGOS score threshold.
***
## 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.
**Blacklist Country Usage**
Can be used when user access from specific countries must be restricted due to regulations or policies. For example, users from sanctioned countries or regions where service provision is restricted can be preemptively blocked.
***
## Custom Policy Rules
Control ARGOS Score calculation and KYC Status decision logic with custom rules. You can create up to **5** policies per project.
This section is saved directly within the policy editor, separately from other settings.
### 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.
| 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
Click the **+ Add Policy** button in the **Custom Policy Rules** area on the KYC Process page.
Drag a condition from the **Triggers** area in the left Tools panel onto the canvas. Click the trigger node to display the detail settings panel on the right.
* **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.
Drag an action from the **Actions** area onto the canvas. Click the action node to configure its values.
* **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.
Connect nodes in the order: `Start` → Trigger → Action → `End`.
Enter a policy name, verify the active/inactive state, and click the **Save** button.
After saving, return to the KYC Process page to confirm the policy appears in the Custom Policy Rules area.
### 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.
When multiple policies have **Override Status** actions, the **last** Override Status result in the policy order is used as the final KYC Status. Arrange your policies carefully considering their priority order.
### 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 |
When setting up a policy for the first time, save it in **Inactive** state to thoroughly review the intended conditions and actions before activating. Activated policies are immediately applied to new KYC submissions.
**Configuration:**
* 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
**Processing flow:**
1. Original ARGOS Score: 96 points → Auto-approved (Approved)
2. Policy 1 applied: 96 - 40 = 56 points (still above Threshold 40, so Approved maintained)
3. Policy 2 applied: Status overridden to Rejected
4. 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.
**Which method should you choose?**
* **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.
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.
Global settings only apply to ID Types that are **originally supported** in each country. For example, even if you enable Residence Permit globally, it will not be added for countries that do not support Residence Permits.
### Per Country
Configure ID Types individually per country through a CSV file.
Click the **Download Current Settings** button to download the template CSV file. The CSV contains all supported countries and the ID types available for KYC in each country.
In the downloaded CSV file, set a value for each country and ID type combination.
| Value | Description |
| ------- | --------------------- |
| `TRUE` | Allow this ID Type |
| `FALSE` | Disallow this ID Type |
Upload the modified CSV file using the **CSV Upload** button. After uploading, search by country code in **Per-Country Settings Lookup** to verify the settings were applied correctly.
**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`.
If all ID Types are set to `FALSE` for a country, the ID Types for that country will not be displayed.
### 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.
The per-country settings lookup is not where you change settings — it is an area that displays the **current state** reflecting the results configured in global or per-country settings.
***
## Related Documentation
View authentication data related settings.
View selfie process and forgery prevention settings.
View KYC status codes.
View rejection codes and reasons.