> 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/verification-methods/non-doc-verification.md).

# Non-Doc verification

***

## Overview

Non-document verification is the catch-all for methods that establish a user's identity without asking them to capture a passport, driver's license, or national ID card. Instead of extracting attributes from a document image, these methods rely on authoritative data sources government registries, credit bureaus, mobile network operators, national eID schemes to confirm the user is who they claim to be.

The trade-off versus document verification is straightforward: lower friction and faster completion, in exchange for narrower geographic coverage and (usually) lower assurance. For the right use cases, that's an obvious win. For others, document capture is still the right answer. This page covers when to reach for non-document methods and what's in the toolbox.

### How it works in general

The exact flow depends on the method, but the shape is consistent:

{% stepper %}
{% step %}
**The user provides an identity anchor**

The user enters one or more attributes — typically a national identifier (SSN, national ID number), a phone number, or authenticates with an existing credential (eID, bank login). No camera, no document upload. 
{% endstep %}

{% step %}
**The platform queries an authoritative source**

The submitted anchor is checked against the corresponding source of truth: the SSA for US SSNs, a credit bureau for attribute matching, a mobile network operator for phone-based intelligence, or a government/bank eID provider for federated identity assertions.
{% endstep %}

{% step %}
**The source returns a verification signal**

The response is either a yes/no match, a probabilistic match score, a signed identity assertion, or a fraud/risk signal depending on the source. The platform aggregates whatever was returned into a structured result.
{% endstep %}

{% step %}
**Optional supplementary checks run**

The flow can layer additional signals on top possession (OTP, silent network authentication), behavioural fraud indicators, or a lightweight biometric. These don't replace the primary check, but they reinforce assurance.
{% endstep %}
{% endstepper %}

### Methods in this category

| Method                       | What it checks                                                                                                                                                                      | Geographic fit                                                         |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| **eID**                      | Government-issued or bank-issued electronic identity (eIDAS, BankID, MitID, itsme, FranceConnect, and similar). Returns signed verified attributes at the scheme's assurance level. | Strong in EU, Nordics, Benelux, Baltics; limited elsewhere.            |
| **SSN verification**         | Matches a US Social Security Number plus name and DOB against authoritative sources (eCBSV from SSA, credit bureau attribute matching, death indicator, issuance-date check).       | US only.                                                               |
| **Phone-based verification** | Mobile carrier intelligence (line type, tenure, SIM-swap, port-out, subscriber name/address) combined with possession checks (OTP, silent network authentication, voice call).      | Global, with richest data in markets where MNO data sharing is mature. |


---

# 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/verification-methods/non-doc-verification.md?ask=<question>&goal=<endgoal>
```

`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.