Identity check friction is driving onboarding drop-off

At a glance

What this is: NHI Mgmt Group's analysis, drawing on OneID's blog post: Customer onboarding drop-off concentrates at the identity check, where document-and-selfie flows and poor method fit push high-intent applicants to abandon signup.

Why it matters: This matters to identity verification, IAM and fraud teams because conversion problems at onboarding are also governance problems: the wrong verification path can create both customer abandonment and avoidable risk friction.

By the numbers:

• In OneID's experience, bank and wallet routes typically complete for 80 to 90% of customers.
• Passport-chip flows typically complete for 50 to 60% of customers.

Context

Customer onboarding fails most often where identity proofing asks the applicant to do the most work. In practice, document photos, selfie retries and poor lighting turn a trust step into a friction step, and that creates a direct conversion cost for any business relying on digital signup.

The core issue is not identity verification itself but method fit. When the verification route does not match the audience, even high-intent applicants abandon the process before completion, which makes verification design a growth control as much as a trust control.

Key questions

Q: How should organisations speed up customer onboarding without weakening identity assurance?

A: They should automate the primary verification path and reserve manual review for exceptions. The combination of document authentication, liveness detection, and authoritative data checks reduces waiting time while preserving assurance. The goal is not fewer controls, but a control chain that completes fast enough to support digital conversion and compliance.

Q: Why do document and selfie checks create so much abandonment?

A: They ask the customer to do the hard part of verification themselves. That means finding a document, photographing it clearly and passing a facial scan, each of which can fail for ordinary reasons such as lighting, framing or retries. Every failure adds friction at the point where the applicant is most likely to quit.

Q: What signals show that an onboarding identity flow is underperforming?

A: Low completion at the identity step, a high retry rate and a large gap between starting the check and finishing it are the clearest signs. Break the numbers down by document capture, selfie and fallback route, because aggregate completion alone hides where the friction really sits.

Q: What should teams prioritise when choosing customer onboarding software?

A: Prioritise completion evidence over feature count. The right platform should support multiple verification methods, show completion by method and by step, and make repeat verification easier for returning customers. If the flow still loses high-intent applicants, the technology list is not solving the real problem.

Technical breakdown

Why document-and-selfie verification creates drop-off

Document-and-selfie flows transfer the burden of proof to the customer. The user must locate a physical document, capture it in acceptable lighting, and then pass a facial match that can fail for quality, framing or retry reasons. Each step increases the chance of abandonment because the customer is still trying to complete a purchase or signup, not to manage a separate verification task. The issue is amplified when the system treats every failed capture as a fresh friction point rather than a recoverable path.

Practical implication: Design verification paths that minimise user effort and remove avoidable retries.

Method routing and the role of reusable credentials

The most effective onboarding designs route people to the method that fits their circumstances. Bank-based verification works for customers with online banking, reusable wallet credentials work for returning users, and international eIDs serve applicants outside the UK. A reusable credential changes the model further by allowing a returning customer to confirm identity with a tap rather than repeating a full proofing flow. That reduces friction without lowering assurance because the trust is anchored in a previously verified credential. See the NHI Lifecycle Management Guide.

Practical implication: Offer multiple verification routes and route customers to the one they can complete fastest.

Why completion metrics matter more than feature lists

Verification capability is not the same as verification performance. A provider can support several methods and still lose customers if teams only measure whether a check is technically available. Completion rate at the identity step, drop-off by stage and cost per approved customer reveal where friction actually sits. Those metrics show whether the verification design is working for the audience, not just whether it exists in the product stack.

Practical implication: Measure completion by method and stage before deciding whether the onboarding flow is fit for purpose.

NHI Mgmt Group analysis

Conversion failure is a governance signal, not just a UX issue. Identity proofing sits at the boundary between trust and abandonment, so poor completion is evidence that the verification journey is misaligned with the audience. When a business loses high-intent applicants at this point, the control design has failed as an access decision mechanism and as a commercial control. Practitioners should treat onboarding drop-off as a control-performance problem, not only a design problem.

Method diversity is the real answer to onboarding friction. The article shows that one path does not fit every applicant, especially when the audience includes domestic banking users, returning customers and international applicants. NHI lifecycle processes are relevant here because identity verification should behave like a governed journey, not a single static checkpoint. Practitioners should build method selection into the flow rather than forcing every customer through the same proofing route.

Reusable credentials shift verification from repeated proofing to trusted reuse. That matters because the highest-friction step in onboarding is often repeated unnecessarily for customers who have already been verified once. The named concept here is verification friction gap: the difference between the assurance a business wants and the effort it makes the customer absorb. Practitioners should close that gap by reducing repeated proofing for returning users.

Identity verification is increasingly a conversion control as well as an assurance control. The business consequence is straightforward: friction at proofing time changes who reaches account creation, payment or regulated onboarding. That means identity teams need to work with product and growth teams, not just compliance, because the verification path directly shapes both trust and revenue. Practitioners should evaluate proofing flows using the same discipline they use for other critical journey controls.

What this signals

Verification friction gap: the gap between the assurance a business wants and the effort it makes the customer absorb is now a measurable conversion risk. Teams that treat onboarding as a proofing-only problem miss the operational reality that friction changes who completes signup, who abandons, and where the business pays for avoidable retries.

Identity journeys should be designed like routed controls, not fixed hurdles. When one proofing path serves every audience, completion falls because customers are forced to adapt to the system instead of the system adapting to the customer.

For identity, fraud and IAM teams, the forward-looking implication is clear: reusable credentials and method routing will matter more as customer journeys become more fragmented across devices, geographies and regulated use cases.

For practitioners

• Measure drop-off at each verification step Track completion rate, retries and abandonment separately for document capture, selfie matching and any fallback path so you can see exactly where applicants leave.
• Route customers to the right proofing method Offer bank-verified identity, reusable wallet credentials, mobile-number age checks and international eIDs, then send each audience to the route most likely to complete.
• Reduce repeat proofing for returning users Use passkey-secured reusable credentials so customers who have already been verified can confirm identity with a tap instead of repeating a full onboarding check.
• Judge providers on conversion evidence Ask for completion by method, drop-off by step and cost per approved customer, not just a list of supported verification features.

Key takeaways

• Identity proofing can become a conversion bottleneck when the verification path asks customers to do too much work at the moment they are most likely to complete.
• The most effective response is not to weaken the check but to match the method to the customer and reduce repeat proofing where trust already exists.
• Completion rate, retry rate and cost per approved customer are the metrics that show whether onboarding security is helping or hurting the journey.

Related NHI Mgmt Group resources: NHI Lifecycle Management Guide · IAM and IGA Basics · Ultimate Guide to NHIs: What are Non-Human Identities

Key terms

• Identity proofing: The process of verifying that a person is who they claim to be before granting or restoring access. In higher-risk recovery paths, proofing can include stronger evidence checks such as government ID validation or liveness-based facial verification so the assurance level matches the sensitivity of the request.
• Verification Friction: Verification friction is the extra effort, delay, or confusion a user or system faces during identity checks. In IAM and identity verification, it appears when authentication, proofing, or approval steps are too complex, too frequent, or poorly matched to risk, reducing completion rates and weakening security outcomes.
• Reusable credential: An identity credential that can be presented more than once across different services or transactions. Reuse changes the control problem from a single verification event to ongoing lifecycle governance, including issuance, acceptance, revocation, and offboarding.
• Method Routing: Method routing is the practice of directing different users to different verification methods based on their circumstances, such as location, device or account history. It helps maintain completion rates by matching the proofing route to the audience instead of forcing one universal path.

Deepen your knowledge

The NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, machine identity security and identity lifecycle control. It is designed for practitioners who need to connect identity governance to operational security decisions across modern programmes.