EUDI wallet friction is driving customer drop-off in verification flows

At a glance

What this is: IDnow says nearly half of surveyed consumers abandoned transactions because identity verification was too difficult, showing that onboarding friction is now a conversion problem as much as a compliance one.

Why it matters: For IAM and identity verification teams, the finding shows that slow, repeated checks can directly reduce revenue, so verification design must balance assurance with a lower-friction user journey.

By the numbers:

• 46% of European consumers abandoned a transaction because identity verification was too difficult or too time-consuming.
• 54% of Millennials abandoned a transaction because identity verification was too difficult or too time-consuming.
• 56% of Gen Z consumers abandoned a transaction because identity verification was too difficult or too time-consuming.
• The survey questioned 2,000 consumers in France and Germany.

Context

Identity verification fails when assurance is built as a one-off compliance step instead of a reusable trust layer. In this article, the primary issue is not whether identity checks exist, but whether they force customers to repeat document uploads, selfies, and manual review across every service.

The EUDI Wallet changes that model by allowing a verified credential to be presented across services without rebuilding the check each time. That shift matters because repeated friction is now directly affecting conversion, especially in regulated sectors where onboarding volume and customer trust are tightly linked Digital Identity, eID and Identity Wallets Guide.

Key questions

Q: How can organisations reduce repeated identity verification without losing assurance?

A: By standardising identity evidence across systems so the same subject is not forced to re-prove identity at every touchpoint. Centralised proofing policy, shared assurance signals, and tighter lifecycle governance reduce friction while keeping the trust decision consistent across onboarding, access, and recovery.

Q: Why do customers abandon identity verification even when they intend to transact?

A: Customers abandon verification when the process takes too long, repeats across providers, or asks for more data than the transaction requires. In regulated journeys, friction becomes a decision point in itself. If identity proofing feels like a barrier rather than a service, prospects often leave before the business can convert them.

Q: Why do identity verification controls affect customer conversion?

A: Identity controls affect conversion because every extra step adds friction to the onboarding journey. If verification is slow, confusing or repetitive, customers abandon the process. The governance challenge is to reduce avoidable effort without lowering assurance, which is why pre-filled data, biometric checks and real-time APIs matter.

Q: What changes when identity proofing is portable across services?

A: Portable proofing changes the model from repeated, provider-specific verification to a reusable trust artefact that can be presented to multiple relying parties. That reduces duplication, shortens onboarding, and creates a better user experience. It also shifts governance toward credential acceptance rules, exception handling, and ongoing assurance rather than repeated evidence gathering.

Technical breakdown

Why repeated identity checks create conversion loss

Traditional verification stacks authenticate a person for one transaction, then discard the result instead of turning it into a reusable assurance artefact. That means each provider re-establishes trust independently, often through document upload, selfie capture, and manual review. The architectural weakness is not that verification happens, but that the evidence is not portable across relying parties. In practice, the customer experiences a sequence of separate checkpoints rather than a single trusted credential lifecycle. Practical implication: design onboarding so verified identity evidence can be re-used across services instead of re-collected from scratch. See the NHI Lifecycle Management Guide.

Practical implication: move from isolated checks to reusable identity evidence in onboarding design.

How selective disclosure changes the verification model

Selective disclosure lets a user reveal only the attributes required for a specific transaction, rather than presenting an entire identity payload. That reduces unnecessary data exposure while preserving the assurance value of the credential. For regulated services, this is important because the business can still verify the person, but the user does not have to overshare every field each time. The technical shift is from broad data collection to cryptographically constrained attribute release. Practical implication: treat selective disclosure as an assurance control, not just a privacy feature. See the Digital Identity, eID and Identity Wallets Guide.

Practical implication: use attribute minimisation as part of the assurance design, not as an afterthought.

Why wallet-native onboarding still needs lifecycle governance

A wallet credential can speed up identity proofing, but it does not remove the need for ongoing KYC, fraud signal analysis, and lifecycle governance. The receiving organisation still has to decide when the credential is sufficient, when step-up checks are needed, and how to manage exceptions over the customer lifecycle. The real operational question is how to combine authoritative credential acceptance with continuous risk assessment. Practical implication: build wallet acceptance into a broader identity governance model rather than treating it as a one-time front-door shortcut. Read the Ultimate Guide to NHIs: Regulatory and Audit Perspectives.

Practical implication: align wallet acceptance with ongoing KYC and fraud monitoring controls.

NHI Mgmt Group analysis

Compliance-first identity verification creates conversion debt: The current model was built to satisfy assurance requirements in isolation, not to preserve transaction completion. When every relying party re-verifies the same person independently, the programme accumulates friction that turns into measurable customer loss. The implication is that identity teams must stop treating repeated verification as a neutral control choice; it is now a business outcome with direct revenue impact.

EUDI wallets expose the portability gap in identity governance: The article shows that organisations still operate as if trust evidence cannot be shared across relying parties. That assumption is no longer sustainable once authoritative wallet credentials can be presented cryptographically across services. The governance question is not whether to verify, but whether each verification result has a life beyond the single session in which it was collected.

Selective disclosure is becoming a governance expectation, not a feature request: Consumers are signalling that they will trade data minimisation for adoption when they understand the value. That means identity programmes have to reconcile privacy, assurance, and UX in the same control plane rather than choosing one at the expense of the others. Practitioners should expect users to compare the burden of repeated checks against the value of reusable credentials.

Wallet-native onboarding will widen the gap between prepared and unprepared institutions: The organisations that can accept portable credentials and still maintain fraud and KYC controls will remove a structural source of drop-off. Those that keep current fragmented flows will continue to lose prospects at the verification step. The practical lesson is that onboarding architecture is now a competitive differentiator, not just an operational detail.

What this signals

Conversion debt is now part of identity governance: When verification is repeated at every doorway, the organisation pays twice, once in user friction and again in lost completions. Identity programmes should treat abandonment as a control signal, not just a marketing metric.

Portable credentials shift the control point upstream: If a trusted credential can be accepted across services, the governance burden moves from repeated proofing to credential acceptance policy, exception handling, and post-issuance assurance. That changes how IAM and KYC teams design the front door.

Selectively disclosed attributes will become the expected default in customer identity journeys: Users increasingly want to prove only what the transaction requires. Programmes that keep collecting full-document payloads will look increasingly out of step with both privacy expectations and conversion goals.

For practitioners

• Standardise verification reuse across channels Map where the same customer is forced through separate identity checks and eliminate duplicate evidence collection where regulatory rules allow it.
• Design for selective disclosure Limit each transaction to the attributes actually required, so customers can complete verification without over-sharing identity data.
• Align wallet acceptance with KYC controls Treat wallet credentials as one input to onboarding, then keep fraud signal review and exception handling in place for higher-risk cases.
• Measure friction as a conversion control Track abandonment at each identity step, not just pass or fail rates, so the business impact of verification design is visible.

Key takeaways

• Identity verification friction is no longer a pure UX issue because it directly affects completion rates and customer acquisition.
• The survey shows that abandonment is especially pronounced among younger, digitally active consumers, which raises the commercial cost of slow onboarding.
• Reusable credentials and selective disclosure point to a governance model where assurance and conversion can improve together if programmes redesign the verification flow.

Related NHI Mgmt Group resources: NHI Lifecycle Management Guide · Digital Identity, eID and Identity Wallets Guide · Ultimate Guide to NHIs: Regulatory and Audit Perspectives

Key terms

• Identity Verification Friction: Identity verification friction is the delay, effort, or inconvenience added when a merchant asks a customer to prove who they are. Excessive friction can suppress conversion, frustrate travellers, and create operational overhead. The practical goal is to verify risk without interrupting the purchase journey unnecessarily.
• Selective Disclosure: Selective disclosure is the practice of sharing only the identity attributes needed for a specific decision. In credential-based systems, it reduces oversharing, lowers retention burden, and limits exposure when a verifier does not need the full record to make a trustworthy judgment.
• Reusable Identity: Reusable identity is a verification model that allows an identity proof to be used again across multiple platforms or journeys. It can reduce repeated document collection, but it also requires clear governance for revalidation, revocation, and jurisdictional boundaries so trust does not become portable without control.
• Wallet-Native Onboarding: An onboarding flow that accepts a credential from a digital identity wallet as part of the verification journey instead of forcing the customer to start from scratch. It changes the control point from repeated document collection to policy-driven credential acceptance and lifecycle-aware assurance.

Deepen your knowledge

NHI governance, identity lifecycle management, and workload identity security are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are building or maturing an IAM programme, it is worth exploring.