Device Verification analyzes the information of devices accessing KYC authentication and preemptively blocks access from non-mobile devices (desktops, virtual environments, automated bots, etc.). Starting with the 2026-04 update, Fingerprint-based detection and Device Duplicate Check have been added to the existing Static check (Browser / Graphics / Screen), and the feature has been reorganized under the Device Info tab.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.
This is the first verification performed upon liveform entryDevice Info verification runs first among all pre-verification steps the moment a user enters the KYC liveform. If blocked at this stage, the user cannot proceed to Turnstile, Proxy & VPN detection, or the KYC process itself.
How to ActivateConfigure Device Verification and Fingerprint option in the Device Info tab under Project Management > Policy and Authentication > Authentication Enhancement and Forgery Prevention.
Verification Types
The Device Verification page shows results for two types of verification.| Type | Description | Error code on failure |
|---|---|---|
| Device | Static check — 3 checks: Browser check, Graphics check, Screen check. Determines whether the device is a mobile device. | DE-20000 |
| Fingerprint | Fingerprint option — Virtual machine, Emulator, Malicious bot, Browser tampering detection and Device Duplicate Check. | DE-30000 (detection) / DE-40000 (duplicate exceeded) |
Device (Static check)
Analyzes device information to determine whether it is a mobile device. If determined to be a non-mobile device, the check results in FAIL.| Verification Item | Target | Description |
|---|---|---|
| Browser check | User-Agent | Analyzes the browser’s UserAgent value and blocks the request if the accessing device is identified as a desktop PC or automation tool (bot). |
| Graphics check | WebGL Renderer | Detects the device’s GPU/graphics card through WebGL information and blocks the request if a desktop-only GPU or virtual environment is detected. |
| Screen check | Touch Points | Analyzes the device’s touchscreen support and blocks the request if the multitouch level falls below what is supported by mobile devices. |
Fingerprint 2026-04 New
Detects virtual environments, emulators, malicious bots, and tampered browsers based on device Fingerprint (Visitor ID), and limits repeated approvals from the same device.| Verification Item | Blocked target | On failure |
|---|---|---|
| Virtual machine | Virtualized environments such as VMware or Parallels | DE-30000 |
| Emulator | Android app players that simulate mobile devices | DE-30000 |
| Malicious bot | Automated scripts and browser automation tools | DE-30000 |
| Browser tampering | Browsers with manipulated or forged API signatures | DE-30000 |
| Device Duplicate Check | New requests from the same Visitor ID that exceed the allowed count | DE-40000 (when policy is “Fail if duplicate”) |
Detection criteria are continuously updated, and specific detection logic is not disclosed for security reasons.
Verification Results List
When Device Verification is activated, you can view device verification results for each KYC access attempt in the list. Both Device and Fingerprint types are displayed together in one list, and you can select which columns to show usingTable Columns at the top.
Common Columns
| Item | Description |
|---|---|
| Submission Time (UTC+9) | Time of submission attempt |
| Submitter’s email | |
| Validation ID | Pre-verification common identifier |
| Type | Verification type (Device / Fingerprint) |
| Visitor ID | Device unique identifier based on Fingerprint. Value is only shown for Fingerprint type rows; displayed as - for Device rows. |
| Status | Overall verification result (Pass / Fail) |
Device (Static check) Additional Columns
Activate these inTable Columns to view Static check raw data and detailed results alongside.
| Item | Description |
|---|---|
| UA Device | Original UserAgent data |
| GPU Renderer | Original WebGL GPU Renderer data |
| Touch Pts | Original touch point value |
| UA Check | Browser check result (Pass/Fail) |
| Detected UA | Keyword detected by Browser check |
| WebGL Check | Graphics check result (Pass/Fail) |
| Detected WebGL | Keyword detected by Graphics check |
| Touch Check | Screen check result (Pass/Fail) |
| Detected TP | Touch point count detected by Screen check |
Static check raw columns are shown as
- for Fingerprint type rows; the Visitor ID and Status fields contain values. Fingerprint detail values can be viewed in the detail modal.Verification Detail View
Click on each data entry in the list to display a detail modal for that verification record.
Basic Information
| Field | Description |
|---|---|
| Submission Time | Time when verification occurred |
| Submitter’s email | |
| Validation ID | Pre-verification common identifier |
| Submission ID | Linked submission ID (if available) |
| Type | Verification type (Device) |
Device Verification Status
You can check whether each verification item passed or failed.| Item | Description |
|---|---|
| UA Verification | Whether the device’s User-Agent string was verified |
| WebGL Verification | Whether the device’s WebGL renderer was verified |
| Touch Verification | Whether the device’s touch points were verified |
Device Detection Info
Blacklist keywords detected during actual verification.| Item | Description |
|---|---|
| Detected UA | Actual User-Agent keyword detected during UA verification |
| Detected WebGL | Actual renderer keyword detected during WebGL verification |
| Detected Touch Points | Actual touch point count detected during Touch verification |
Additional Info
Original data collected from the device.| Item | Description |
|---|---|
| UA Device | Full original UserAgent string |
| GPU Renderer | Original GPU Renderer string collected via WebGL |
| Touch Points | Original simultaneous touch point count |
Checking from Submission Detail View
In the user submission detail view, you can directly access the Device Verification result for that submission through the Pre-verification List dropdown.
Error Page on Block
When a FAIL occurs in Device Verification, a different error page is displayed to the user depending on which verification type failed. All error pages show the error code and definition so that clients can quickly diagnose the cause.| Error Code | Trigger condition |
|---|---|
DE-20000 | Device Verification (Static check) — one or more of Browser / Graphics / Screen check failed |
DE-30000 | Fingerprint option — one or more of virtual machine / emulator / malicious bot / browser tampering detected |
DE-40000 | Device Duplicate Check — duplicate device detected exceeding allowed count + policy is Fail if duplicate |
- Access from a mobile device
- Use the latest browser version
- Disable incognito mode/extensions (ad blockers, etc.) and retry
Verification Process Flow
Device Info verification runs first the moment a user enters the KYC liveform, preceding Turnstile, Proxy & VPN detection, and the KYC process itself.Enter liveform
The user enters the KYC liveform. Device Info verification runs automatically immediately after clicking the Start button.
Device Verification (Static check) execution
Three items — Browser check, Graphics check, and Screen check — are verified sequentially.
Fingerprint option execution
After passing Static check, Fingerprint-based detection (virtual machine / emulator / malicious bot / browser tampering) and Device Duplicate Check are performed.
Related Documentation
VPN & Proxy
View VPN & Proxy detection results.
Authentication Enhancement and Forgery Prevention
Learn how to configure Device Verification option settings.
User Submissions
Manage submission list and view detailed information.
Error Codes and Pages
View the complete error code list.