Overview
Non-Document Verification
Non-document verification establishes a user's identity using authoritative data sources and possession signals - without asking them to capture a passport, driver's license, or ID card. Instead of extracting attributes from a document image, the platform queries trusted issuers, government registries, credit bureaus, mobile network operators, or national eID schemes to confirm the user is who they claim to be.
These methods exist because document capture isn't always the right tool. For many use cases - re-verification of an existing customer, low-friction onboarding for thin-file users, regulated markets where a national eID is the de facto standard, or recovery flows where a user no longer has their original document - non-document verification is faster, cheaper, and just as defensible.
What's in this section
How non-document methods differ from document verification
User effort
Capture document + selfie
Enter a few fields or authenticate with an existing credential
Median time to complete
1–3 minutes
10–45 seconds
Source of truth
The physical document and its security features
Authoritative database, issuer, or trusted attribute provider
Coverage
Anyone with a supported document
Depends on data availability in the user's country/region
Typical assurance
Up to IAL2 with biometric binding
Varies by method — eID can reach IAL2; SSN/phone alone are typically lower
Best for
First-time onboarding, regulated KYC
Re-verification, thin checks, account recovery, regional fit
When to choose a non-document method
Non-document verification is the right fit when:
Friction matters more than maximum assurance. A high-converting onboarding flow that completes in 20 seconds is more valuable than a 3-minute document scan that 30% of users abandon.
You have a strong attribute to anchor on. A US SSN, an EU eID, or a mobile number tied to a long-tenured carrier account are all anchors strong enough to verify against without a document.
The user has already been document-verified before. Re-verification at session, transaction, or compliance refresh time rarely needs the full document flow again.
The market expects it. In the Nordics, BankID is the verification method. Asking for a driver's license scan there is unusual and feels off-brand. Match the market.
You're recovering an account. The user has lost access — making them produce a document they may not have anymore is the wrong default. A non-document path with appropriate fraud signals is usually better.
When to stick with document verification
Reach for document verification when:
You're opening a new account under a regulated KYC/AML regime that mandates documentary evidence.
The user has no usable identity attribute on file (no SSN, no eID, no consistent phone history).
You need IAL2 or IAL3 assurance and the user doesn't have an eID at the required level.
The transaction risk justifies the friction (high-value money movement, irreversible actions).
See Verification methods for the full document-based catalog.
Combining methods
Non-document and document verification are not mutually exclusive. Common patterns:
Document first, non-document for re-verification. A user verifies their passport on signup; six months later, a phone-based possession check is enough to confirm it's still them before a high-risk action.
Non-document first, document for step-up. A user opens a basic account with an SSN check, then completes document verification only when they want to enable a feature that requires higher assurance.
Parallel signals. Run a phone-based fraud check in the background while the user completes a document scan, and fail the verification if the two diverge.
The right composition depends on your risk model. Most teams converge on a tiered approach where the verification rigor scales with what the user is trying to do.
Last updated
Was this helpful?