Identity verification can cut fraud and onboarding friction

At a glance

What this is: Prove Identity describes how identity verification can reduce onboarding friction while pushing fraudsters into a smaller, more reviewable exception path.

Why it matters: For identity verification teams, the key issue is not speed alone but whether onboarding design can separate low-risk users from accounts that need deeper scrutiny.

By the numbers:

• Company A reported a 78.7% decrease in average onboarding completion time, from 47 seconds to 10 seconds.
• Company A also reported a 28.8% increase in total applications approved, from 73% to 94%.
• Company C experienced a 151% increase in new patient registrations after Prove Pre-Fill was implemented.
• Several customers reported that fraudsters were concentrated into a smaller review bucket of about 7%.

Context

Identity verification is not only a fraud control. In onboarding flows, it also shapes how much effort legitimate users must spend before they can complete registration, which means the control directly affects conversion, abandonment, and downstream trust decisions. The article’s core point is that firms are using verification design to separate routine users from higher-risk applicants instead of treating every applicant the same.

That matters for identity teams because fraud controls often fail when they create more friction for good users than for bad ones. In this case, the operational gain comes from making risky users self-select into a harder path, which gives reviewers a smaller exception set and makes the identity control more usable across banking, payments, and healthcare. The starting position is typical for digital onboarding programmes that need both assurance and low friction.

Key questions

Q: What breaks when identity verification is too slow or fragmented across onboarding steps?

A: When verification is slow or fragmented, applicants abandon the process, staff create manual workarounds, and risky cases can slip through inconsistent review paths. Fragmentation also makes it harder to enforce a single compliance standard across KYC, KYB, and AML checks. The result is more operational friction, weaker control consistency, and less reliable fraud prevention.

Q: Why do fast onboarding and low-friction payment flows create more fraud risk?

A: Fast onboarding and low-friction payment flows create fraud risk because they reduce the signals teams can use to distinguish a trusted customer from an organised fraudster. Criminals can mimic legitimate behaviour, use fake information, or exploit exemption paths. The more seamless the experience, the more important it becomes to add layered verification and adaptive controls.

Q: How do teams know if identity security controls are actually working?

A: Identity security controls are working when teams can show a current view of high-risk entitlements, detect privilege drift quickly, and remove access before exposure spreads. A useful sign is reduced time between entitlement change and policy review. Another is fewer unresolved conflicts between approved access and actual production permissions.

Q: When should teams prioritise fraud review over pure onboarding speed?

A: Prioritise fraud review when the identity flow shows signs of mismatch, manual entry, or repeated refusal of automation. Those are the points where risk is being expressed, and they are more valuable than adding friction across the entire population. Good governance focuses review effort where behaviour suggests the claim and the claimant may not align.

Technical breakdown

How identity verification changes onboarding economics

Identity verification in onboarding is not just an authentication check. It is a decision layer that determines whether a user can proceed through a low-friction flow or is diverted into additional review. Pre-fill and similar methods reduce manual data entry, which lowers abandonment while preserving enough identity signal to detect mismatches. The important mechanism is not speed alone, but selective friction. Good users encounter less work, while suspicious users are more likely to reveal themselves by refusing automated pre-population or by failing consistency checks. Practical implication: design verification so routine applicants move quickly, but exception handling is triggered by identity behaviour, not by blanket friction.

Practical implication: tune onboarding controls so low-risk users stay fast while mismatched identities are routed to review.

Why self-selection can expose fraud risk

Self-selection works because fraudsters often avoid anything that increases the chance of detection. If a process auto-populates known identity data, a fraudster impersonating someone else may be forced to reject the automation and type details manually, which creates a measurable signal. That signal is useful because it shrinks the population that needs deeper inspection and concentrates risk into a smaller queue. This does not eliminate fraud, and it does not prove innocence for the larger group. It simply turns user behaviour into a screening mechanism. Practical implication: treat opt-out and manual-entry events as risk signals, not as neutral UX choices.

Practical implication: classify manual-entry and opt-out behaviour as part of fraud triage.

What the case study says about identity assurance and conversion

The case study shows that identity assurance and conversion do not have to compete if the workflow is designed well. A cleaner identity path can raise approval rates because fewer legitimate users abandon the process, while fraud review becomes more focused because suspicious users drift into a separate bucket. In practice, this is a governance problem as much as a product problem: the organisation decides how much trust to assign at each step and what evidence is sufficient to continue. For identity programmes, the lesson is that assurance should be embedded in journey design, not bolted on after abandonment appears. Practical implication: align fraud controls with onboarding metrics, not just security metrics.

Practical implication: measure identity controls by both risk separation and completion outcomes.

Threat narrative

Attacker objective: Complete fraudulent account opening without triggering the higher-friction identity review path.

1. Entry occurs when fraudsters attempt account opening or onboarding through a digital registration flow that expects clean identity data.
2. Credential or identity misuse follows when the attacker cannot safely accept auto-filled details and instead has to deviate from the legitimate path.
3. The attacker’s objective is to complete fraudulent onboarding while avoiding the stronger identity checks that are triggered by manual entry or inconsistent data.

Breaches seen in the wild

• Coupang Signing Key Breach: Unrevoked signing key credentials expose 33.7 million records after employee offboarding failure at Coupang.

Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.

NHI Mgmt Group analysis

Selective friction is the real control here: the article shows that identity verification is most effective when it routes trustworthy users quickly and forces suspicious applicants into a narrower review path. That changes the economics of onboarding because the system no longer treats every applicant as equally trustworthy. For practitioners, the question is whether identity controls separate risk, not merely whether they collect data.

Fraud detection improves when the workflow encourages self-selection: the smaller review bucket described in the article is not a side effect, it is the control effect. When a fraudster has to opt out of automation to avoid revealing a mismatch, the process itself becomes a screening mechanism. This is a strong example of identity governance shaping adversary behaviour rather than only reacting to it.

Identity assurance and conversion should be governed together: the article reinforces that onboarding design is a control surface, not just a user experience problem. A programme that optimises only for fraud blocking often creates abandonment, while a programme that optimises only for speed can widen exposure. The governance goal is to align assurance thresholds, review queues, and conversion targets so both outcomes are measured together.

Identity verification is becoming a journey-level control, not a point check: the useful distinction is that the control sits in the onboarding flow, where it can influence both trust decisions and user effort. That makes it relevant to IAM-adjacent governance, especially where customer identity proofing and fraud prevention overlap. Practitioners should treat onboarding design as part of the identity control plane.

Faster onboarding does not weaken assurance when the exception path is well designed: the case study suggests that speed gains are sustainable only when higher-risk users are pushed into a more visible review channel. That is the governance pattern worth copying, because it reduces the false trade-off between security and conversion. The practical conclusion is to measure where risk is being separated, not just how quickly forms are completed.

From our research library:

• Nearly 60% of companies reported that fraud losses were still increasing in 2025.

What this signals

Identity verification is moving toward journey-level governance: the useful control point is no longer only the proofing step itself, but the way the onboarding path sorts users into trusted, reviewable, and suspicious segments. That means identity teams should design for selective friction and measure whether exception handling is getting cleaner over time.

Risk separation is the named concept worth watching: this article illustrates how a verification flow can create a smaller, higher-signal review population without breaking conversion. For programmes that combine identity proofing with fraud prevention, the practical challenge is to keep the trusted lane fast while making the exception lane sufficiently visible to investigators.

For practitioners

• Map onboarding friction to risk tiers Separate low-risk applicants from higher-risk applicants before manual review so the default path stays fast without removing scrutiny from edge cases.
• Treat opt-out behaviour as a risk signal Flag users who refuse auto-fill or abandon identity automation for investigation, because that behaviour can indicate a mismatch between claimed and actual identity.
• Measure conversion and assurance together Track completion time, approval rate, and fraud review yield in one dashboard so fraud controls are judged by both trust and journey outcomes.
• Redesign exception queues for smaller risk populations Use identity verification outcomes to shrink the number of cases sent to deeper inspection, so reviewers spend time on the most suspicious applicants.

Key takeaways

• Identity verification can improve both fraud control and onboarding efficiency when it separates routine users from higher-risk applicants.
• The key operational signal is not only faster completion, but whether suspicious users are pushed into a smaller review bucket that investigators can manage.
• Identity teams should judge onboarding controls by the quality of risk separation, not by friction reduction alone.

Key terms

• Identity verification: Identity verification is the process of confirming that a user, workload, or agent is the entity it claims to be before access is granted. In AI-heavy environments, that verification must include the requester, the system acting on its behalf, and the sensitivity of the action.
• Selective Friction: Selective friction is a control strategy that adds verification or delay only where risk signals justify it. In returns, it preserves a smooth experience for low-risk customers while using tighter checks, evidence demands, or manual review for claims with stronger abuse indicators.
• Risk Separation: Risk separation is the ability of a control to route ordinary users and suspicious users into different paths based on evidence. In identity programmes, it is valuable because it turns onboarding into a triage process, making fraud review smaller, clearer, and easier to manage.
• Exception Queue: An exception queue is the set of cases that fail the normal automated path and require human or enhanced review. In identity verification, the queue should contain a smaller share of higher-risk applicants, otherwise the control is creating work without improving decision quality.

Deepen your knowledge

NHI Mgmt Group covers identity security, NHI governance, and agentic AI through independent research, practitioner guides, and the NHI Foundation Level course. It is a good fit for practitioners who need to connect identity assurance, lifecycle control, and governance across programmes.