Topic starter
06/11/2026 6:39 pm
TL;DR: Abandoned identity verification flows create revenue leakage, compliance risk, and fraud exposure when document capture fails, liveness checks feel intrusive, identity is re-checked unnecessarily, or security disappears entirely, according to Daon. The control problem is not just conversion tuning: verification has to become risk-calibrated and continuity-based, or every retry becomes another opportunity to lose a legitimate customer.
Editorial analysis by NHI Mgmt Group, based on content published by Daon: “Reduce Abandonment in Identity Verification: Top Causes and Effective Solutions”.
Key questions
Q: How should security teams reduce form abandonment without weakening identity verification?
A: Security teams should move verification earlier but make it less visible to the user.
Q: Why do repeated identity checks increase customer drop-off?
A: Repeated identity checks increase drop-off because each extra re-entry, document capture or challenge adds friction and creates a new failure point.
Q: How does passive liveness detection reduce friction in onboarding?
A: Passive liveness detection reduces friction by confirming that the person is physically present without asking them to perform extra actions such as blinking or head turns.
Practitioner guidance
- Define abandonment as a control metric Track drop-off by document type, device class, geography, and step in the journey so verification failures are visible as governance data, not just UX noise.
- Expand document coverage before tightening thresholds Review which passports, licenses, and national IDs your flow can actually validate, then prioritise the document classes that cause the highest legitimate-user rejection rates.
- Use passive liveness for lower-risk journeys Replace command-based biometric prompts with passive checks where the risk model allows, and keep higher-friction challenges for exceptional cases only.
Bottom line: Identity verification abandonment is often a design and governance failure, not a simple user-experience problem.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:41 pm
Identity verification abandonment is an assurance design problem, not a usability nuisance. When the process rejects legitimate customers, the organisation has not only lost a conversion event, it has also signalled that its trust model is too brittle for real-world onboarding. The right lens is governance of the identity journey, where false rejection, repeated retries, and customer confidence all count as control outcomes. Practitioners should manage abandonment as a policy and assurance metric, not just a product metric.
A few things that frame the scale:
- Gartner predicts that by 2026, 30% of enterprises will consider identity verification solutions unreliable in isolation because of AI-driven attacks.
A question worth separating out:
Q: What should teams do first when identity verification abandonment rises?
A: First, teams should identify where applicants are failing, then separate genuine document rejection from UX problems such as unclear instructions, image capture errors or unsupported document types. Document rejection should be measured by step, device and reason code, then tested with a simpler capture flow, clearer guidance or alternate evidence before adding more checks.
👉 Read our full editorial: Identity verification abandonment is a risk and revenue problem