Topic starter
11/11/2026 6:05 pm
TL;DR: Thin-file users are often misclassified by identity verification systems that expect familiar documents, address history, or credit signals, according to Socure's profile and example-based analysis. For practitioners, the control problem is evidence breadth and decision logic, not simply higher friction.
Editorial analysis by NHI Mgmt Group, based on content published by Socure: “Meet The Identity Disruptors: Deepanker Saxena is Building Identity for The People Systems Overlook”.
Key questions
Q: What causes legitimate users to fail identity verification?
A: Legitimate users fail when the verification model assumes they will have stable documents, consistent personal data and clean capture conditions.
Q: How should organisations reduce identity data collection without weakening assurance?
A: Start by defining the exact claim needed for each journey, then design verification so only that claim is disclosed and retained.
Q: How should identity proofing handle thin-file applicants?
A: Use multiple evidence paths, so applicants with thin files can prove identity through alternative combinations of documents, database checks, device signals and out-of-wallet questions.
Practitioner guidance
- Broaden accepted evidence sets Map the document, address, institutional, and credit signals your proofing workflow will accept for thin-file users, then test which combinations support a decision without forcing manual escalation.
- Separate unfamiliar from suspicious Review rejection and review reasons to find cases where the system treats absence of familiar records as fraud rather than as incomplete but legitimate evidence.
- Reduce data collection to the minimum proof Use threshold-based disclosure for cases like age assurance so the workflow returns only the fact needed for authorisation, not unnecessary identity detail.
Bottom line: Identity verification fails when proofing logic assumes every legitimate person will present the same records and address history.
Glossary terms: Thin-File Identity, Identity proofing, Age Verification, Liveness Detection
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/11/2026 6:07 pm
Thin-file exclusion is a governance failure, not a user failure: The decisive problem is that identity systems often assume a stable, locally legible evidence trail before they will trust a person. That assumption breaks for newcomers, renters, students, and people without long credit histories. The result is not just friction but systematic exclusion, which turns proofing policy into a barrier to access rather than a trust control. Practitioners should treat this as a design flaw in the decision model, not a customer exception.
A question worth separating out:
Q: What is the best way to test capture flows for fairness?
A: Test capture flows with a demographically varied panel, controlled lighting and device conditions, then compare completion rates, rejection reasons and retry patterns across groups. Check for bias in face detection, image quality thresholds and liveness prompts, and review whether manual fallback paths treat all users consistently when automated capture fails.
👉 Read our full editorial: Identity verification fails when thin-file users fall outside fixed evidence