> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/identity-verification/non-doc-verification/overview.md). # 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
eIDVerify through a national or bank-issued electronic identity scheme (eIDAS, BankID, itsme, and similar)/pages/5C0VSM3beKI5vxDV7Awa
SSN verificationValidate a US Social Security Number against authoritative sources and confirm name/DOB binding./pages/wl139DDX164O45tPPrlc
Phone-based verificationUse carrier intelligence and possession checks to confirm identity through the user's mobile number./pages/gkyb9mIyS8rfYENASTTK
### How non-document methods differ from document verification | | Document verification | Non-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 ](/identity-verification/verification-methods.md)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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.1kosmos.com/identity-verification/non-doc-verification/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.