Hello, this is ARGOS Identity. Here are the new features and improvements we delivered in May.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.
Error page segmentation & infinite retry loop prevention
Feature Improvement When key engine processes — such as ID liveness, selfie (Passive) liveness, face comparison, or Korean government authenticity verification — fail consecutively, users were previously caught in an infinite retry loop. With this improvement, if the same error accumulates 3 times, the user is now directed to a dedicated error page for that specific error type instead of being offered another retry. Fewer than 3 occurrences are still handled with a recapture prompt or notification.New error codes
| Error code | Category | Trigger condition |
|---|---|---|
SE-50020 ~ SE-50025 | Engine error | Engine processing (ID liveness, selfie liveness, face comparison, government verification, etc.) fails 3 consecutive times |
LO-30001 ~ LO-30005 | Capture/step retry loop | The same error accumulates 3 times during the ID capture stage, blocking the loop |
LO-99999 | Fallback | Fallback for loop-blocking cases not covered by the codes above |
Warning handling option and Custom Policy integration
Engine errors (SE-50020~50025) can be configured in the dashboard to be treated as Warning instead of Error. When set to Warning, the user does not land on a dedicated error page — instead, the subsequent KYC process continues and the condition can be used as a Custom Policy trigger. This follows the same pattern as the Expired ID Warning handling.
For the full error code mapping and error page definitions, see the Error Codes and Pages reference.
Unsupported browser and device notification improvements
Feature Improvement When users access the liveform from unsupported environments — including older browsers, environments without WebAssembly support, or devices running Android OS below version 9 — they previously received only a generic notice with no error code. This improvement assigns the error codeRT-60002 and includes a link to the supported environment guide. Clients can now immediately identify the reason for the block and provide users with specific guidance.
Administrator permission management (RBAC) improvements
New Feature Permissions (roles) for ARGOS internal administrators and project external administrators are now separated, with each role independently controlling which items can be viewed, modified, or deleted on the dashboard. Roles are divided into Owner, Leader, Member, and Guest.
Personal information display control
Depending on the assigned role, data fields in a user’s submission are displayed masked. In the Personal Info Visibility by Role setting, you specify per item which roles (Owner·Leader·Member·Guest) can see each piece of personal information (PII) — such as resident registration numbers, document numbers, identification numbers, and ID card images — and any unchecked item appears masked to administrators with that role.Masking applies to on-screen display only; the actual stored data and API response data are not changed. (e.g., Name
John Doe → ***, Date of Birth 1990-01-15 → ****-**-**)
Permission-based feature control
Actions that exceed a role’s permission scope — such as saving options, deleting records, or canceling administrator invitations — are handled consistently: the relevant button is either hidden entirely or accompanied by a permission notice. This prevents unauthorized operations at the source.ARGOS continues to improve its identity verification service for stronger security and a better user experience. Thank you for using ARGOS Identity. The ARGOS Identity team