> ## Documentation Index
> Fetch the complete documentation index at: https://docs.didit.me/llms.txt
> Use this file to discover all available pages before exploring further.

# September 2026

> ID Verification gets three methods: photograph a document, check a national ID number against an authoritative source, or sign in with a digital ID wallet.

### Three ways to verify an identity

ID Verification is still one feature and one price line, but a document photograph is no longer the only way through it. You now choose, country by country, which methods a person may use.

* **Document capture, unchanged** — every document type, capture rule and threshold you already configure keeps working exactly as before, and a workflow that says nothing about methods stays document capture only
* **Non-document lookup, available now** — the user types their national ID number plus a few personal details and we check them against the authoritative source for that country. No photograph, no upload. That source is a government register in most countries and a credit-bureau, financial-services, utility or residential-records file in some, so [the coverage table](/core-technology/id-verification/non-doc-lookup) names the exact source per country
* **Digital ID wallets, not live yet** — the roadmap is published and configurable in the console as **Coming soon**, but no wallet can be enabled or offered to an end user in production yet. MitID, BankID, itsme, Vipps, iDIN, UAE PASS, gov.br and the EUDI Wallet are on [the wallet page](/core-technology/id-verification/digital-id-wallets); talk to your account team about being in the first cohort
* **Choose per country** — the **Countries** tab on the ID Verification step turns each method on or off for each country, and the same settings are available through the API

### Sources that return a photograph verify the person too

Where a government register returns the person's portrait — South Africa, Nigeria, Argentina and Panama — the lookup also takes a selfie, runs passive liveness on it and matches it to that portrait. All of it is included in the lookup price, and the workflow can skip its own Liveness and Face Match steps afterwards because they would repeat work already done.

### You decide what happens when a method does not land

Every non-document method has a switch for each way it can fail: a partial match, no match, no response from the source, or a wallet sign-in that was cancelled or timed out. Each one either sends the user to document capture or declines the session.

* **Retries are yours to set** — one to five attempts, two by default, and only lookups the source actually answered are counted
* **A typo costs nothing** — a number that fails the format check never reaches the source, so it is neither counted nor billed
* **The console shows the bill before you save** — each switch spells out what that configuration costs

### Every result says how it was verified

Sessions, the decision API and the `status.updated` webhook now carry the method that produced each ID Verification and the assurance tier that goes with it — **Documentary** for a document, **Data match** for a lookup, **Cryptographic** for a wallet. The tiers describe different evidence; they are not a ranking.

* **Registry comparison** — every compared field with what the user provided, what the source held, and whether it matched, plus an error row when a source did not answer
* **Credential details** — the wallet, its issuing authority, the level of assurance it asserted, and whether the signature checked out
* **Existing integrations are untouched** — a document session reports `document` and `documentary` and leaves the new fields empty

### Pricing

Document capture is unchanged: \$0.15 per check with the first 500 checks each month free. Non-document methods are priced per country and per wallet — [talk to us](mailto:hello@didit.me) for the figures that apply to your countries.

* A source that answered bills the lookup, whether it matched or not
* A source that never answered is not billed
* An abandoned or failed wallet sign-in is not billed
* A user who falls back to document capture pays for that capture on top

Read more in [ID Verification methods](/core-technology/id-verification/verification-methods), [Non-document lookup](/core-technology/id-verification/non-doc-lookup) and [Digital ID wallets](/core-technology/id-verification/digital-id-wallets).
