Reduce Abandonment in Identity Verification: Top Causes and Effective Solutions
Bob Long
President, Americas
Bob is a tenured veteran in the Identity and eKYC global markets. In his present role at Daon, he has operational oversight for the Americas Region as President, including a seat on the Daon Board of Directors. Operational requirements include sales, business development, customer success, marketing, and operations for the region encompassing North America, South America, and Latin America.
Bob has over 25 years of experience in financial services, payments, fraud and risk management, and technology. Prior to Daon, he’s held the positions of Interim CEO and Chief Revenue Officer at a Seattle-based payment solutions company and led one of the largest payment and technology providers to an Initial Public Offering on the NYSE (2012). He has also held several leadership roles including Senior Vice President of Financial Services at Vantiv/WorldPay and leadership roles at both First Data Corporation and US Bancorp.
Bob received his education from the University of The Pacific in Stockton, CA.
October 15, 2026
Abandoned identity verification flows are treated as UX footnotes when they should be P&L line items. Every dropout represents acquisition spend that converted interest but not a customer. The four fixable causes are document capture failures, intrusive liveness checks, redundancies that ignore established identity, and friction so absent it signals insufficient protection to customers who expect to see security before moving their money.
Every abandoned verification is a customer an organization already won and then lost because of one confusing screen before the finish line. Usually, this occurs because no one explained what to expect or why. A prospect clicks through, uploads a document, angles a phone camera at their face, and quits. That moment gets treated as a UX footnote. It should be treated as a P&L line. Identity verification exists to protect a business, but if the process drives away legitimate customers before it ever assesses risk, the organization has traded fraud exposure for lost revenue. Neither outcome is acceptable, and most organizations don’t realize they’re choosing between them until the abandonment data forces the conversation.
The good news is that abandonment isn’t a mystery. It has identifiable causes, and each one has a corresponding fix.
Where the Process Breaks Down
The most common failure point is document capture. Poor lighting, glare on a laminated card, a cropped edge, an unsupported document type. Any of these forces a retry, and every retry is a chance for a customer to give up. This problem compounds globally. A verification system built to recognize a handful of document formats will fail constantly outside its home market, and each failure looks identical to the customer: rejection, with no clear explanation of what to fix.
Biometric checks introduce a second failure point. Older liveness detection methods ask users to turn their head, blink on command, or read a number aloud. These prompts feel intrusive, and they fail legitimate users regularly due to device quality, lighting, or simple unfamiliarity with the instructions. A real customer, rejected by their own verification system, doesn’t conclude the system made an error. They conclude the business doesn’t want their signup.
The third and most overlooked cause is structural: treating every interaction as a fresh checkpoint. Most identity verification vendors are built to confirm identity once, typically at onboarding, and offer little beyond that first transaction. Every subsequent login, transaction, or account change starts the verification process over, as if the institution has no memory of who the customer is. Customers who verified their identity last week shouldn’t have to prove it again from scratch this week. When they do, abandonment isn’t a UX defect. It’s the predictable result of asking someone to solve a problem that’s already solved.
There’s a fourth cause that runs counter to conventional wisdom: verification that’s too smooth. When an authentication process removes all friction, some customers interpret that absence not as convenience but as insufficient protection. A payment journey with zero visible security checks can trigger the same abandonment as one with too much friction, because customers reasonably wonder why nothing is checking their identity before moving their money. Friction, deployed at the right moments, builds confidence. Its total absence can do the opposite.
What Abandonment Actually Costs
Each of these failure points carries a business cost that goes beyond a frustrated user. Every abandoned onboarding session represents wasted acquisition spend: marketing dollars, ad clicks, and sales effort that converted interest but not a customer. Multiply that across a large onboarding funnel, and abandonment becomes one of the most expensive line items an organization never tracks directly.
There’s a second cost that cuts the other way. Organizations that respond to abandonment by stripping out verification steps entirely reduce friction, but they also reduce their ability to catch fraud and satisfy compliance requirements. For regulated industries, from banking to gaming to healthcare, that tradeoff invites regulatory exposure that dwarfs whatever conversion gains it produces. Getting verification wrong isn’t a UX problem contained to the product team. It’s a risk and revenue problem that belongs on the CISO’s and compliance leader’s desk as much as the CX team’s.
Effective Solutions
Each cause identified above has a direct, implementable fix.
Document capture failures shrink dramatically with broader document support. Daon’s document verification technology processes more than 12,000 distinct identity document types from nearly every sovereign entity in the world, which means fewer customers hit a wall simply because their passport or license format falls outside a narrow supported list.
Liveness friction has a modern answer: passive liveness detection. Rather than asking users to perform an action on command, passive methods verify a live human being through the natural interaction of taking a selfie, with no head turns or spoken prompts required. The result is a check that’s harder to spoof and easier for legitimate users to pass on the first try.
The redundant re-verification problem calls for a structural shift, not a UX patch. This is where Identity Continuity changes the calculation. Instead of treating every interaction as an isolated event, Identity Continuity frontloads verification effort into enrollment, then lets that verified identity carry forward across the customer relationship. Through biometric-based re-authentication, a customer who securely enrolled once can confirm their identity later with a selfie rather than repeating document uploads or step-up procedures. Abandonment drops because the system stops asking already-verified customers to prove something it already knows.
The friction-calibration problem has a similarly direct answer: place friction where genuine risk exists, and remove it everywhere else. A confirmation prompt before a large transfer, a visible security check before a high-risk action, tells customers the institution is paying attention at the moments that matter. Routine interactions, by contrast, should move through with minimal interruption. Organizations no longer need to guess at this balance manually. No-code orchestration platforms let teams configure and adjust verification workflows, combining biometrics, document checks, and fraud signals through a visual interface rather than a lengthy development cycle. That flexibility matters because abandonment patterns shift over time, by geography, by channel, by customer segment, and a verification workflow that can’t be adjusted quickly will keep losing the same customers for the same fixable reasons.
The Strategic Shift
None of these fixes work in isolation as a one-time patch. Document support solves capture failures. Passive liveness solves biometric friction. Orchestration solves the speed of adjustment. But the deeper shift is architectural: verification stops being a gate customers pass through repeatedly and becomes a relationship the organization maintains continuously. Organizations that make that shift will find abandonment isn’t something to manage quarter over quarter. It becomes a problem they’ve already engineered out of the system.