2026 Q2 ARGOS Identity Update: From Device Security to Session Journey

Stronger Security for Smarter Identity Verification

Digital identity verification has evolved far beyond simply checking an ID document and matching a user's face.

Today, organizations need to ensure not only that submitted identity information is authentic, but also that the environment where verification takes place is trustworthy, authentication failures can be diagnosed quickly, and sensitive personal information is accessible only to authorized administrators.

For industries such as financial services, fintech, ticketing, gaming, and e-commerce, identity verification has become increasingly complex. Fraudsters attempt to bypass verification using virtual machines, emulators, and automated bots, while operators must also deal with expired IDs, authentication failures, and increasingly sophisticated security and compliance requirements.

To address these challenges, ARGOS Identity introduced a series of enhancements throughout Q2 2026, focusing on stronger fraud prevention, greater policy flexibility, enterprise-grade access control, and improved operational visibility.

In this article, we'll walk through the key product updates released between April and June 2026.

April Highlights: Verifying Not Only the User, but Also the Device

Identity fraud today extends far beyond forged documents.

Attackers increasingly rely on virtual machines, mobile emulators, browser manipulation, and automated scripts to create multiple accounts or repeatedly attempt identity verification.

To better defend against these threats, ARGOS Identity strengthened its Device Info and Fingerprint-based verification capabilities in April.

Device Info performs a security check before users even begin the KYC process. Instead of validating only the user's identity, the platform first evaluates whether the device and execution environment can be trusted.

With this update, organizations can detect and block environments such as:

• Virtual Machines (VMs)

• Mobile Emulators

• Malicious Bots

• Browser Tampering

• Repeated verification attempts from the same device (Device Duplicate Check)

One of the most significant additions is Device Duplicate Check, which allows organizations to limit how many successful KYC approvals can originate from a single device.

For example, if the same device repeatedly attempts to create multiple accounts, administrators can choose to either block the request immediately or simply record the event and allow verification to continue, depending on their operational policy.

This feature is particularly valuable for industries where preventing duplicate accounts and automated abuse is critical, including ticketing platforms, financial services, online gaming, and digital marketplaces.

While traditional identity verification answers the question:

"Is this person who they claim to be?"

Device Info expands that question to:

"Can the environment this person is using also be trusted?"

This additional verification layer helps organizations stop suspicious activity before users even enter the main verification flow, reducing unnecessary processing and strengthening overall platform security.

May Highlights: Smarter Error Handling with Flexible Verification Policies

A modern KYC workflow relies on multiple verification engines working together, including ID liveness detection, passive selfie liveness, face comparison, and government database verification.

Previously, if one of these verification engines repeatedly failed, users could become stuck in a retry loop or abandon the verification process altogether. At the same time, customer support teams often struggled to determine exactly why a verification had failed.

To improve both user experience and operational efficiency, ARGOS Identity introduced Error Handling Method along with more granular error pages.

Instead of continuously prompting users to retry the same verification step, the platform now displays dedicated error pages after repeated failures, making the cause of the issue much clearer for both users and administrators.

More importantly, organizations can now define how each verification engine should respond when an error occurs.

Two handling methods are available:

• Error – Redirect users to a dedicated error page and terminate the verification flow.

• Warning – Skip the failed verification step and continue with the remaining KYC process.

Choosing Warning allows users to continue their verification journey without being forced to restart the entire process.

At the same time, every warning event is recorded and can be incorporated into Custom Policy, enabling organizations to automate follow-up actions based on their own operational requirements.

For example, if a face comparison engine experiences a temporary issue, a business may choose not to reject the user immediately. Instead, the submission can be marked with a warning, routed to Pending for manual review, or assigned a lower ARGOS Score before a final decision is made.

This approach helps organizations strike a better balance between security and user experience. Rather than treating every verification error as a failed identity check, businesses can apply policies that best fit their own compliance and operational needs.

Enterprise Access Control with Enhanced RBAC

As organizations grow, identity verification is rarely managed by a single administrator.

Different team members often have different responsibilities, and not everyone should have access to sensitive customer information or administrative controls.

To address this, ARGOS Identity enhanced its Role-Based Access Control (RBAC) capabilities in May.

Administrators can now be assigned one of four roles

• Owner/ Leader/ Member/ Guest

Each role has its own permissions, determining which settings can be modified, which administrative functions are available, and what level of customer information can be viewed.

For example, high-level administrators can manage project settings or invite new administrators, while team members responsible only for operational monitoring can be restricted to viewing limited information.

RBAC also introduces more granular control over personally identifiable information (PII). Organizations can configure which administrator roles are allowed to view sensitive information such as. By limiting access to only those who require it, organizations can better align with internal security policies and regulatory compliance requirements while reducing unnecessary exposure of sensitive customer data.

These enhancements make ARGOS Identity a stronger enterprise identity platform, providing organizations with the flexibility to manage identity verification according to their own governance and security standards.

June Highlights: Visualize Every Step of the Verification Journey with Session Journey

One of the most common challenges for operations teams is understanding why a verification failed.

A user may report that their identity verification didn't go through, but support teams still need to determine where the process stopped, which verification step failed, whether the user abandoned the flow, or whether the submission was rejected due to a specific policy.

To make troubleshooting significantly easier, ARGOS Identity introduced Session Journey in June.

Session Journey provides a complete timeline of every event that occurs during a verification session from the moment a user enters the Live Form until the final verification result.

Instead of relying on logs or engineering support, operations teams can now review the entire verification process directly from the dashboard.

Administrators can quickly see:

• When the user entered the Live Form

• Every step completed throughout the verification process

• Front-end events generated by user interactions

• Back-end verification and decision events

• The most recent event in the session

• Associated error codes

• Final verification status

• Whether the user abandoned the verification process

The newly introduced DROPPED status makes it easy to identify users who leave the verification process before reaching the final result page.

For example, when a customer contacts support saying, "My verification didn't work," an operator can immediately determine whether the user:

• Left during ID capture,

• Failed Face Compare,

• Was blocked during Device Info validation,

• Or encountered a specific error page.

This dramatically reduces investigation time while giving operations teams greater visibility into where users experience friction.

Beyond customer support, Session Journey also helps organizations analyze drop-off points, identify recurring operational issues, and continuously optimize the overall verification experience.

Flexible Session Data Retention

Alongside Session Journey, ARGOS Identity also introduced configurable Session Data Retention settings.

Organizations can now define how long session history should be stored based on their operational or compliance requirements.

Available retention periods include:

• 30 days (default)/ 90 days / 180 days / 365 days

Once the configured retention period expires, session data is automatically removed.

This gives organizations greater flexibility in managing verification history while aligning with internal governance policies, privacy regulations, and audit requirements.

Businesses that only need short-term operational visibility can minimize data retention, while organizations requiring longer-term analysis or customer support records can retain session history for extended periods.

Building a More Secure and Flexible Identity Verification Platform

The Q2 2026 updates are more than just a collection of new features.

They represent ARGOS Identity's continued commitment to helping organizations solve real operational challenges in identity verification.

Across this quarter, ARGOS Identity introduced enhancements that allow organizations to:

• Detect suspicious device environments before verification begins

• Handle exceptions such as expired identity documents and verification engine errors according to their own business policies

• Apply role-based access control to protect sensitive customer information

• Trace every verification session through a complete event timeline for faster troubleshooting and operational visibility

Together, these improvements deliver stronger fraud prevention, greater operational flexibility, enhanced administrative security, and a more transparent identity verification experience.

As digital identity continues to evolve, ARGOS Identity remains committed to providing organizations with the tools they need to build secure, scalable, and user-friendly verification experiences.

Want to Learn More?

This article highlights the major product updates introduced during Q2 2026.

For detailed implementation guides, API specifications, dashboard configuration, error codes, and integration references, please visit the ARGOS Identity Developer Guide.

We will continue to improve the ARGOS Identity platform to help organizations build safer, smarter, and more efficient digital identity verification experiences.