KR (South Korea) region support
New feature Starting October 1, 2026, ID check supports the KR (South Korea) region. You can now place a project in either the US (United States) region or the KR region. The region is set per project. Dashboard features, policies, and options are the same in both regions — only the API and Liveform access addresses (endpoints) and the webhook sender IP differ.Existing customers do not need to take any action. All existing projects stay in the US region, and the existing API and Liveform endpoints and the webhook sender IP do not change.
Using the KR region
Please ask the sales team to create a KR region project. To move an existing US region project to the KR region, you need to create a new project in the KR region and migrate your data. Please contact the sales team or customer support.Integration values for KR region projects
KR region projects use the values below. Use the values that match the region your project belongs to.The firewall of the server that receives webhooks must allow the sender IP of the region your project belongs to. If you use projects in both the US and KR regions, please allow both IPs.
Dashboard
The dashboard address (https://idcheck.argosidentity.com) is the same regardless of region. After you log in, the Project List shows US (United States) / KR (South Korea) tabs, and each tab lists the projects in that region. If you have projects in both regions, you can see each of them in its own tab, and a member invited to a project enters the region the project belongs to.

Region tabs in the Project List
Where data is processed
KYC processing and data storage take place in the region the project belongs to. Some third-party integrations, such as IP lookup, use the US region; apart from these, users’ personal information (PII) is always processed in the project’s region.Documentation changes
Most endpoints and request examples in the API Reference can be switched betweenUS / KR tabs. For examples without tabs, replace only the host with the one for your project’s region.
- Regions how to check a project’s region, endpoints by region, and where data is processed
Dashboard UI redesign
Improvement Starting October 20, 2026, the dashboard uses a new design based on the ARGOS Identity Design System. Color, typography, and common elements such as buttons, input fields, tables, dialogs, and date pickers now appear in the new design.Features and menu locations have not changed. Only the look of the screens is different, so you can keep your existing settings and ways of working.
FaceAuth return URL — error code delivery
New feature Error code (errorCode) has been added to the dynamic fields of the FaceAuth add-on’s AddOn Return URL. The error code feature already available in the main pipeline’s return URL now works the same way in FaceAuth.- When you select Error code, the failure reason code is sent to the return URL when authentication fails. You can use this code to tell failure causes apart and handle retries or guidance.
- When you select Error code, users can return to the return URL even after reaching an error page.
- When both Skip result page and Error code are enabled, the error page is also skipped and the user goes straight to the return URL.
- FaceAuth Guide dashboard guide
- FaceAuth Getting Started developer guide
Allowed nationalities for Liveform — WhiteListNationality
New feature
You can set WhiteListNationality in the Liveform query string to choose which nationalities are allowed to verify. You can specify one or more nationalities, and the setting applies to the ID document and Knowledge-based pipelines.
- If the nationality the user enters is not on the allowed list, the submission is rejected at Step 2 with the reason White List Nationality Mismatch. The user sees the message “The selected nationality is not supported in the current process.”
- If the user enters a Korean Resident Registration Number, ARGOS also checks whether the number matches the allowed nationalities. If it does not match, a guidance modal is shown.
- query string and Token Guide developer guide
Improved 1 won account authentication screens
Improvement The 1 won account authentication screens have changed. Users now enter the account number first instead of choosing a bank, and can fix the account or name directly from the code screen.- While the account number is typed, matching financial institutions are suggested. If the right one is not listed, users can open the full list (banks and securities firms) from the Financial institution field.
- If the account number has the wrong number of digits or a card number is entered, users are notified before 1 won is sent. They are also notified when the selected institution does not match the account number format.
- Before 1 won is sent, a confirmation screen shows the financial institution, account number, and account holder (name on the ID).
- The code screen shows the 3-digit number with an example of how the deposit appears in the banking app, plus the remaining time and remaining attempts.
- Re-enter account number returns users to the account entry screen to fix the account number or institution. Previously entered values are kept.
- If verification fails because the account holder name differs from the name on the ID, Edit name lets users check and fix the ID name.
No project settings need to change. This applies to all projects that use 1 won account authentication, starting with submissions made after the release. Results of submissions already processed do not change.
- Anti-fraud and forgery prevention — 1 Won Account Authentication dashboard guide
ARGOS continues to improve its identity verification service for stronger security and a better user experience. Thank you for using ARGOS ID check. The ARGOS Identity team