Non-Document Lookup - Didit Documentation

Non-doc lookup is one of the three ID Verification methods. Instead of photographing a document, the user types their national ID number plus a few personal details, and Didit checks them against the authoritative source for that country. The result carries the assurance tier data_match: the details the user gave matched a record that source holds. No document was inspected, so nothing about a document’s authenticity is being claimed.

Which source is queried

Most countries are a government register — the Department of Home Affairs in South Africa, RENAPER in Argentina, UIDAI in India, the CPR register in Denmark. Some are not. In Canada, France, Indonesia, the Netherlands, Norway, Singapore, the United Kingdom and the United States the authoritative record Didit can reach is a credit-bureau, financial-services, utility or residential-records file rather than a state register. That distinction is not cosmetic. It changes what the match proves, which consent regime the query runs under, and what you can tell a regulator about provenance, so this page never generalises: the Source queried column below names the exact source for every country, and it is the only statement of provenance to rely on. Read it before you enable a country.

The end user never sees the source name. It is on the session payload (id_lookup.source), in the console and in exports, for you and your auditors.

What the user does

Picks their country in the ID step.
Types the fields that country asks for — always the identifier, usually a name, sometimes a date of birth or an address.
Where the country’s lookup asks for one, takes a selfie.
Gets a result: verified and moved on, asked to correct the number, retried, sent to document capture, or declined.

The whole step is typing and, for five countries, one selfie. There is no upload, no camera framing and no document at all.

Selfies, portraits and a later Face Match step

A lookup establishes the identity from a record. What it leaves behind decides what a Face Match step later in the workflow can compare the user’s live capture against. Every source does one of three things, and the Selfie, liveness and face match column in the table below says which, per country:

What the source does	What a later Face Match step compares against
Returns the holder’s photograph	The registry photograph, as long as the workflow keeps the `registry_portrait` response field
Checks the selfie against the face on record itself and returns a verdict	The selfie the source verified
Returns data only	Nothing

Where the source returns a photograph, the user is asked for a selfie, passive liveness runs on it, and it is face-matched to the registry portrait. All three happen inside the lookup and inside the lookup price: there is no separate Liveness or Face Match charge. Because the lookup already proved a live person matching the register’s photograph, the country’s skip_liveness_and_face_match switch (on by default) lets the workflow skip its own Liveness and Face Match steps after a match. Turn it off to run them anyway. Where the source checks the selfie itself, as Brazil, Argentina (RENAPER), Nigeria and Panama (the Tribunal Electoral’s biometric service) do, the check returns a verdict, not a portrait. That is not a liveness check, so the switch is normalised off on save and any Liveness and Face Match steps in the workflow still run. On a match, Face Match compares the live capture with the selfie the lookup verified. In Nigeria the user chooses the ID type, and the selfie is checked against the face on record for a NIN and for a BVN alike. Every other source returns data only, as do the Argentine sources that take no selfie. No selfie is taken and the switch is normalised off on save.

A Face Match step after a method that leaves no photo

A data-only lookup leaves a Face Match step nothing to compare, and so does a digital identity wallet sign-in: even where a wallet shares a portrait, it is not used as the Face Match reference. A Face Match step reached that way cannot pass anyone automatically: every user it sees goes to review or is declined. The workflow editor, and the graph validation every client uses, tell you before you publish:

The workflow cannot be published when, for a country, every path into the Face Match step verifies its users only with methods that leave no photo, and every route out of that ID Verification step leads to the Face Match step. A branch whose outcomes all lead back to Face Match does not change that. Allow document capture for that country, pick a source that returns a photograph or checks the selfie, or remove the Face Match step.
A warning when it depends on the user: document capture or a source that leaves a photo is offered as well, or a branch after the ID Verification step can send those users to an outcome without Face Match. Users who finish with the data-only method still reach Face Match with nothing to compare.

In the console, a note beside each such source and wallet in the ID Verification step’s Countries tab says the same whenever a Face Match step follows. A workflow that collects a reference face when the session is created (Biometric Authentication, or a Face Match step that can run before any ID Verification step, with portrait_image) always has something to compare and is never flagged. If nothing else in the workflow provides one, Face Match has no reference to compare the live capture against after a data-only match. It reports that the comparison could not be computed (FACE_MATCH_NOT_COMPUTED, with a null score) rather than declining automatically. The Face Match step’s face_match_not_computed_action then decides the outcome: In Review by default, or Declined if you set it to DECLINE. See Face match warnings.

Coverage and pricing

Prices below are public retail USD per answered attempt, checked against the anonymous Database Validation pricing feed on September 11, 2026. They use the services configured for the country. A price is not a production-launch announcement: enable only the methods your application catalog offers. The existing availability snapshot is retained separately from this price refresh. For a country using multiple sources, the table shows their sum when all answer. An answered attempt charges only its billable source responses; a source that did not answer is excluded. Nigeria uses NIN or BVN, not their sum. Custom contract rates can differ and are shown in your console. These are ID-step lookup prices, not a quote for every other Database Validation service offered in that country.

Country	USD / attempt	Code	Source queried	Availability	Selfie, liveness and face match	Consent regime
Argentina	$0.20	`ARG`	RENAPER	Available	Selfie checked by the lookup; Liveness and Face Match still run	Ley 25.326
Bolivia	$0.20	`BOL`	SEGIP	Available	Not applicable — data only	—
Brazil	$0.40	`BRA`	Receita Federal	Available	Selfie checked by the lookup; Liveness and Face Match still run	LGPD
Cambodia	$0.35	`KHM`	Ministry of Interior voter register	Available	Not applicable — data only	Explicit consent required
Canada	$3.95	`CAN`	Canadian credit bureau records (FINTRAC dual-process)	Available	Not applicable — data only	PIPEDA
Chile	$0.20	`CHL`	Servicio de Registro Civil e Identificación	Available	Not applicable — data only	—
China	$0.30	`CHN`	NCIIC (National Citizen Identity Information Center)	Available	Not applicable — data only	Explicit consent required
Colombia	$0.20	`COL`	Registraduría General de la Nación / ANI	Available	Not applicable — data only	—
Costa Rica	$0.20	`CRI`	Tribunal Supremo de Elecciones	Available	Not applicable — data only	—
Denmark	$1.39	`DNK`	CPR register	Available	Not applicable — data only	—
Dominican Republic	$0.05	`DOM`	Junta Central Electoral	Available	Not applicable — data only	—
Ecuador	$0.20	`ECU`	Registro Civil del Ecuador	Available	Not applicable — data only	—
El Salvador	$0.20	`SLV`	RNPN	Available	Not applicable — data only	—
Finland	$2.10	`FIN`	DVV population register	Available	Not applicable — data only	Explicit consent required
France	$1.54	`FRA`	French residential and utility records	Available	Not applicable — data only	GDPR
Guatemala	$0.20	`GTM`	SAT	Available	Not applicable — data only	—
Honduras	$0.20	`HND`	CNE	Available	Not applicable — data only	—
India	$0.25	`IND`	UIDAI (Aadhaar)	Available	Not applicable — data only	Aadhaar consent
Indonesia	$0.35	`IDN`	Indonesian population register via residential records	Available	Not applicable — data only	UU PDP
Kenya	$0.65	`KEN`	IPRS (Integrated Population Registration System)	Available	Not applicable — data only	—
Malaysia	$0.35	`MYS`	JPN (National Registration Department)	Available	Not applicable — data only	Explicit consent required
Mexico	$0.20	`MEX`	RENAPO	Available	Not applicable — data only	—
Netherlands	$0.90	`NLD`	Dutch residential records	Available	Not applicable — data only	GDPR
Nigeria	NIN $0.35 / BVN$ 0.35	`NGA`	NIMC / NIBSS	Available	Selfie checked by the lookup; Liveness and Face Match still run	NDPR
Norway	$2.42	`NOR`	Norwegian residential records	Available	Not applicable — data only	GDPR
Panama	$0.75	`PAN`	Tribunal Electoral / SIB	Available	Selfie checked by the lookup; Liveness and Face Match still run	—
Paraguay	$0.20	`PRY`	Registro del Estado Civil	Available	Not applicable — data only	—
Peru	$0.20	`PER`	RENIEC	Available	Not applicable — data only	—
Singapore	$4.30	`SGP`	Singapore credit bureau and utility records	Available	Not applicable — data only	PDPA
South Africa	$2.20	`ZAF`	Department of Home Affairs	Available	Included in the lookup	POPIA
Sweden	$0.35	`SWE`	Skatteverket population register	Available	Not applicable — data only	—
Thailand	$0.35	`THA`	DOPA civil registration	Available	Not applicable — data only	Explicit consent required
United Kingdom	$1.85	`GBR`	UK credit bureau and financial services records	Available	Not applicable — data only	UK GDPR
United States	$0.27	`USA`	US credit bureau and financial services records	Available	Not applicable — data only	GLBA permissible purpose
Uruguay	$0.20	`URY`	Dirección Nacional del Registro de Estado Civil	Available	Not applicable — data only	—
Venezuela	$0.20	`VEN`	CNE	Available	Not applicable — data only	—
Zambia	$0.20	`ZMB`	Zambia Revenue Authority	Available	Not applicable — data only	—

Availability comes from the capability catalog the backend serves; the API rejects a workflow that enables a lookup the catalog does not mark Available for that country. Prices marked On request are not published yet — non-document methods are priced per country and quoted by your account team.

Format rules

Identifier fields carry a client-side format check before anything is sent — a length, a digit-only rule, a checksum or a pattern, depending on the country. A number that fails it never reaches the source, which means it is never billed and never counted against max_attempts: the user is shown a country-specific message and asked to correct it. The per-country tables below list the rule for each field. A field with no rule is free text — a name, a date the interface collects, or an image capture. Get the format right in your own pre-fill and you spend nothing on typos.

Per-country fields

Argentina (`ARG`)

Source: RENAPER. The lookup also takes a selfie and compares it with the face on record for that identity; that check returns a verdict, not a portrait. It is not a liveness check, so the skip switch stays off: any Liveness and Face Match steps in the workflow still run, and Face Match compares the live capture with that verified selfie.

Asked for	Field key	Required	Format check
Argentine DNI	`document_number`	Yes	Pattern `[MFmf]?\d{7,8}`; 7-9 characters
Selfie	`selfie`	Yes	—
Gender	`gender`	Yes	One of `M`, `F`

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Bolivia (`BOL`)

Source: SEGIP. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
Bolivian CI	`document_number`	Yes	6-10 characters; digits only
Date of birth	`date_of_birth`	Yes	—

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Brazil (`BRA`)

Source: Receita Federal. The lookup also takes a selfie and compares it with the face on record for that identity; that check returns a verdict, not a portrait. It is not a liveness check, so the skip switch stays off: any Liveness and Face Match steps in the workflow still run, and Face Match compares the live capture with that verified selfie.

Asked for	Field key	Required	Format check
Brazilian CPF	`tax_number`	Yes	Exactly 11 characters; digits only
Date of birth	`date_of_birth`	Yes	—
Selfie	`selfie`	Yes	—

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Cambodia (`KHM`)

Source: Ministry of Interior voter register. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
First name	`first_name`	Yes	—
Last name	`last_name`	Yes	—
Date of birth	`date_of_birth`	Yes	—
Voter ID number	`voter_id`	Yes	Pattern `(?:\d{8,9}\|\d{2}-\d{3}-\d{3})`

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Canada (`CAN`)

Source: Canadian credit bureau records (FINTRAC dual-process). This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
First name	`first_name`	Yes	—
Last name	`last_name`	Yes	—
Date of birth	`date_of_birth`	Yes	—
Home address	`address`	Yes	—

Returned	Field key	Required
Name match (exact, partial or none)	`name_match`	Yes
Date-of-birth match	`date_of_birth_match`	Yes
Address match	`address_match`	Yes
Number of sources that confirmed the identity	`sources_confirming`	Yes
Source name	`source_name`	No
Queried at	`queried_at`	No

Chile (`CHL`)

Source: Servicio de Registro Civil e Identificación. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
Chilean RUT	`personal_number`	Yes	8-12 characters

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

China (`CHN`)

Source: NCIIC (National Citizen Identity Information Center). This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
Full name	`full_name`	Yes	—
Date of birth	`date_of_birth`	Yes	—
National ID number	`national_id`	Yes	Pattern `(\d{15}\|\d{17}[\dXx])`

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Colombia (`COL`)

Source: Registraduría General de la Nación / ANI. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
Colombian Cédula	`personal_number`	Yes	6-10 characters; digits only
Date of issue	`date_of_issue`	Yes	—

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Costa Rica (`CRI`)

Source: Tribunal Supremo de Elecciones. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
Costa Rican Cédula	`personal_number`	Yes	9-12 characters; digits only

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Denmark (`DNK`)

Source: CPR register. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
First name	`first_name`	Yes	—
Last name	`last_name`	Yes	—
Date of birth	`date_of_birth`	Yes	—
National ID number	`national_id`	Yes	Pattern `\d{6}-?\d{4}`

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Dominican Republic (`DOM`)

Source: Junta Central Electoral. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
Dominican Cédula	`personal_number`	Yes	Exactly 11 characters; digits only

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Ecuador (`ECU`)

Source: Registro Civil del Ecuador. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
Ecuadorian Cédula	`personal_number`	Yes	Exactly 10 characters; digits only

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

El Salvador (`SLV`)

Source: RNPN. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
Salvadoran DUI	`document_number`	Yes	Exactly 9 characters; digits only
Date of birth	`date_of_birth`	Yes	—

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Finland (`FIN`)

Source: DVV population register. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
First name	`first_name`	Yes	—
Last name	`last_name`	Yes	—
Date of birth	`date_of_birth`	Yes	—
National ID number	`national_id`	Yes	Pattern `(?:\d{6}[-+A]\d{3}[0-9A-Z]\|\d{6}\d{3}[0-9A-Z])`

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

France (`FRA`)

Source: French residential and utility records. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
First name	`first_name`	Yes	—
Last name	`last_name`	Yes	—
Date of birth	`date_of_birth`	Yes	—
Home address	`address`	Yes	—

Returned	Field key	Required
Name match (exact, partial or none)	`name_match`	Yes
Date-of-birth match	`date_of_birth_match`	Yes
Address match	`address_match`	Yes
Number of sources that confirmed the identity	`sources_confirming`	Yes
Source name	`source_name`	No
Queried at	`queried_at`	No

Guatemala (`GTM`)

Source: SAT. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
Guatemalan DPI	`document_number`	Yes	Exactly 13 characters; digits only
Date of birth	`date_of_birth`	Yes	—

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Honduras (`HND`)

Source: CNE. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
Honduran DNI	`document_number`	Yes	Exactly 13 characters; digits only

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

India (`IND`)

Source: UIDAI (Aadhaar). This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
Full name	`full_name`	Yes	—
Date of birth	`date_of_birth`	Yes	—
National ID number	`personal_number`	Yes	Exactly 12 characters; digits only
PAN	`pan`	Yes	Pattern `[A-Z]{5}\d{4}[A-Z]`; uppercased

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Indonesia (`IDN`)

Source: Indonesian population register via residential records. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
First name	`first_name`	Yes	—
Last name	`last_name`	Yes	—
Date of birth	`date_of_birth`	Yes	—
Home address	`address`	Yes	—
NIK (16 digits)	`national_id`	Yes	Exactly 16 characters; digits only

Returned	Field key	Required
Name match (exact, partial or none)	`name_match`	Yes
Date-of-birth match	`date_of_birth_match`	Yes
Address match	`address_match`	Yes
Number of sources that confirmed the identity	`sources_confirming`	Yes
Source name	`source_name`	No
Queried at	`queried_at`	No

Kenya (`KEN`)

Source: IPRS (Integrated Population Registration System). This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
First name	`first_name`	Yes	—
Last name	`last_name`	Yes	—
Date of birth	`date_of_birth`	Yes	—
National ID number	`national_id`	Yes	Pattern `\d{8,9}`

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Malaysia (`MYS`)

Source: JPN (National Registration Department). This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
Full name	`full_name`	Yes	—
Date of birth	`date_of_birth`	Yes	—
National ID number	`national_id`	Yes	Exactly 12 characters; digits only

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Mexico (`MEX`)

Source: RENAPO. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
Mexican CURP	`personal_number`	Yes	Exactly 18 characters

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Netherlands (`NLD`)

Source: Dutch residential records. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
First name	`first_name`	Yes	—
Last name	`last_name`	Yes	—
Date of birth	`date_of_birth`	Yes	—
Home address	`address`	Yes	—

Returned	Field key	Required
Name match (exact, partial or none)	`name_match`	Yes
Date-of-birth match	`date_of_birth_match`	Yes
Address match	`address_match`	Yes
Number of sources that confirmed the identity	`sources_confirming`	Yes
Source name	`source_name`	No
Queried at	`queried_at`	No

Nigeria (`NGA`)

Source: NIMC / NIBSS. The lookup also takes a selfie and compares it with the face on record for that identity; that check returns a verdict, not a portrait. It is not a liveness check, so the skip switch stays off: any Liveness and Face Match steps in the workflow still run, and Face Match compares the live capture with that verified selfie.

Asked for	Field key	Required	Format check
ID type	`identifier_type`	Yes	One of `NIN`, `BVN`
The number itself	`identifier`	Yes	Exactly 11 characters; digits only
First name	`first_name`	Yes	—
Last name	`last_name`	Yes	—
Selfie	`selfie`	Yes	—

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
State of origin	`state_of_origin`	No
Phone number (masked)	`phone_number_masked`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Norway (`NOR`)

Source: Norwegian residential records. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
First name	`first_name`	Yes	—
Last name	`last_name`	Yes	—
Date of birth	`date_of_birth`	Yes	—
Home address	`address`	Yes	—

Returned	Field key	Required
Name match (exact, partial or none)	`name_match`	Yes
Date-of-birth match	`date_of_birth_match`	Yes
Address match	`address_match`	Yes
Number of sources that confirmed the identity	`sources_confirming`	Yes
Source name	`source_name`	No
Queried at	`queried_at`	No

Panama (`PAN`)

Source: Tribunal Electoral / SIB. The lookup also takes a selfie and compares it with the face on record for that identity; that check returns a verdict, not a portrait. It is not a liveness check, so the skip switch stays off: any Liveness and Face Match steps in the workflow still run, and Face Match compares the live capture with that verified selfie.

Asked for	Field key	Required	Format check
Panamanian Cédula	`personal_number`	Yes	Pattern `(?:\d{1,2}(?:-?(?:AV\|PI))?\|PE\|E\|N)[\d-]*`; at least 5 characters; uppercased
Selfie	`selfie`	Yes	—

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Paraguay (`PRY`)

Source: Registro del Estado Civil. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
Paraguayan CI	`document_number`	Yes	6-10 characters; digits only

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Peru (`PER`)

Source: RENIEC. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
Peruvian DNI	`personal_number`	Yes	Exactly 8 characters; digits only

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Singapore (`SGP`)

Source: Singapore credit bureau and utility records. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
First name	`first_name`	Yes	—
Last name	`last_name`	Yes	—
Date of birth	`date_of_birth`	Yes	—
Home address	`address`	Yes	—
NRIC / FIN	`national_id`	Yes	Pattern `[STFGM]\d{7}[A-Z]`; uppercased

Returned	Field key	Required
Name match (exact, partial or none)	`name_match`	Yes
Date-of-birth match	`date_of_birth_match`	Yes
Address match	`address_match`	Yes
Number of sources that confirmed the identity	`sources_confirming`	Yes
Source name	`source_name`	No
Queried at	`queried_at`	No

South Africa (`ZAF`)

Source: Department of Home Affairs. The source returns a portrait, so a selfie is taken, passive liveness runs on it and it is face-matched to that portrait inside the lookup.

Asked for	Field key	Required	Format check
13-digit ID number	`national_id`	Yes	Exactly 13 characters; digits only; LUHN checksum
First name	`first_name`	Yes	—
Last name	`last_name`	Yes	—
Selfie	`selfie`	Yes	—

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Citizenship	`citizenship`	No
ID status (valid, deceased or blocked)	`id_status`	Yes
Registry portrait	`registry_portrait`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Sweden (`SWE`)

Source: Skatteverket population register. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
First name	`first_name`	Yes	—
Last name	`last_name`	Yes	—
Date of birth	`date_of_birth`	Yes	—
National ID number	`national_id`	Yes	Pattern `(\d{10}\|\d{12})`; digits only

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Thailand (`THA`)

Source: DOPA civil registration. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
First name	`first_name`	Yes	—
Last name	`last_name`	Yes	—
Date of birth	`date_of_birth`	Yes	—
Thai national ID number	`national_id`	Yes	Exactly 13 characters; digits only

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

United Kingdom (`GBR`)

Source: UK credit bureau and financial services records. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
First name	`first_name`	Yes	—
Last name	`last_name`	Yes	—
Date of birth	`date_of_birth`	Yes	—
Home address	`address`	Yes	—

Returned	Field key	Required
Name match (exact, partial or none)	`name_match`	Yes
Date-of-birth match	`date_of_birth_match`	Yes
Address match	`address_match`	Yes
Number of sources that confirmed the identity	`sources_confirming`	Yes
Source name	`source_name`	No
Queried at	`queried_at`	No

United States (`USA`)

Source: US credit bureau and financial services records. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
First name	`first_name`	Yes	—
Last name	`last_name`	Yes	—
Date of birth	`date_of_birth`	Yes	—
Home address	`address`	Yes	—
Social Security number (last 4 or full)	`ssn`	No	4-9 characters; digits only

Returned	Field key	Required
Name match (exact, partial or none)	`name_match`	Yes
Date-of-birth match	`date_of_birth_match`	Yes
Address match	`address_match`	Yes
Number of sources that confirmed the identity	`sources_confirming`	Yes
Source name	`source_name`	No
Queried at	`queried_at`	No

Uruguay (`URY`)

Source: Dirección Nacional del Registro de Estado Civil. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
Uruguayan CI	`personal_number`	Yes	7-9 characters; digits only
Date of birth	`date_of_birth`	Yes	—

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Venezuela (`VEN`)

Source: CNE. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
Venezuelan Cédula	`document_number`	Yes	Pattern `[VvEe]?-?\d{7,10}`; 7-12 characters

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Zambia (`ZMB`)

Source: Zambia Revenue Authority. This source returns data only, so there is no portrait to face-match against: a Face Match step later in the workflow has nothing to compare for a user verified this way.

Asked for	Field key	Required	Format check
National ID number	`national_id`	Yes	Pattern `\d{6}/?\d{2}/?\d`; uppercased
First name	`first_name`	Yes	—
Last name	`last_name`	Yes	—

Returned	Field key	Required
Full name	`full_name`	Yes
Date of birth	`date_of_birth`	Yes
Gender	`gender`	No
Address	`address`	No
Record status	`record_status`	No
Source name	`source_name`	No
Queried at	`queried_at`	No

Several sources may only be queried with the person’s explicit consent, and the consent regime differs by country — POPIA in South Africa, NDPR in Nigeria, LGPD in Brazil, UK GDPR in the United Kingdom, GLBA permissible purpose in the United States, and so on. The regime that applies to each source is in the coverage table above. You are the controller for that consent. Collect it in your own flow, or add a questionnaire step before the ID step, and keep the record — Didit runs the query you asked for and does not judge whether you had the right to ask for it. Where a country’s source requires consent wording of its own, the verification UI shows it before the lookup runs.

Attempts, outcomes and billing

Each answered lookup counts as one attempt. max_attempts is 1 to 5, default 1.

Outcome	Counts as an attempt	Billed	What happens next
`match`	Yes	Yes	The register’s record becomes the ID Verification result and the workflow moves on.
`partial_match`	Yes	Yes	Retry while attempts remain, then `on_partial_match`.
`no_match`	Yes	Yes	Retry while attempts remain, then `on_no_match`.
`provider_error`	No	No	Retry, then `on_provider_error`.
`format_rejected`	No	No	The user is asked to correct the field. It never reached the register.

Each billable answered attempt sums the retail rates of the services that answered with a match, partial match or no match. Retries are new attempts and can add another charge. An attempt that ends in a provider error is not billed. Format rejection is not billed. The first 500 document-capture checks per organization each month do not cover lookup attempts. If lookup falls back to document capture, the completed document check is billed separately, subject to its remaining document allowance. Disabling fallback declines the session; it does not refund a completed lookup. Sandbox scenarios simulate outcomes without paid registry queries or usage charges.

What lands on the session

A lookup that matched populates the ID Verification result the same way a document read would — name, date of birth and the national identifier — and adds an id_lookup evidence block:

{
  "node_id": "feature_ocr_1",
  "status": "Approved",
  "verification_method": "id_lookup",
  "assurance": "data_match",
  "wallet_provider": null,
  "fallback_from": null,
  "id_lookup": {
    "source": "Department of Home Affairs",
    "checked_at": "2026-09-04T09:12:44Z",
    "attempts": 1,
    "max_attempts": 2,
    "outcome": "match",
    "comparison": [
      { "field": "identification_number", "label": "ID number", "provided": "9106155043088", "record": "9106155043088", "result": "match" },
      { "field": "full_name", "label": "Full name", "provided": "Thabo Mokoena", "record": "Thabo Mokoena", "result": "match" },
      { "field": "date_of_birth", "label": "Date of birth", "provided": "1991-06-15", "record": "1991-06-15", "result": "match" }
    ],
    "registry_portrait": "https://<media-host>/registry_portrait.jpg",
    "face_match_score": 96.4,
    "source_errors": []
  },
  "wallet_verification": null
}

comparison carries one row per comparable field, with result of match, partial or no_match, so a reviewer can see exactly which field disagreed. The row names are normalised — identification_number, full_name, date_of_birth, address — not the country’s request field keys, because a first name and a last name are compared as one name and every identifier alias is compared as one number. The current staging response keeps source failures in a separate source_errors array. Its entries can contain service_id, code, message, details and outcome_detail when supplied. Treat these as query diagnostics, not identity mismatches. Earlier releases may represent source failures as comparison rows with result: "error"; confirm the contract deployed in your target environment. registry_portrait is present only for a source that returns a portrait, when the selected response fields retain it; face_match_score is then the comparison of the selfie with that portrait. A source that checks the selfie itself (RENAPER in Argentina, Nigeria) returns no portrait, and face_match_score is the score it reported for its own check. Full field types are in the ID verification data model.

Retention

The source record that produced a match is stored as the ID Verification result and follows your organization’s data retention settings, exactly like a document read. Deleting a session deletes it; see Delete session.

The current staging implementation applies id_lookup.response_fields to comparison output, optional gender and retained registry portraits. Required identity fields remain part of the verification record. This is not a guarantee that every intermediate provider payload is excluded from processing. Production rollout has not been verified for this change; confirm the behavior in your target environment before relying on field selection for retention requirements.

ID Verification methods — the three methods, fallback and billing
Digital ID wallets — the cryptographic method
Database Validation — the standalone feature for checking a document you already captured against a source
Workflow feature configs — the methods key reference

​Which source is queried

​What the user does

​Selfies, portraits and a later Face Match step

​A Face Match step after a method that leaves no photo

​Coverage and pricing

​Format rules

​Per-country fields

​Argentina (ARG)

​Bolivia (BOL)

​Brazil (BRA)

​Cambodia (KHM)

​Canada (CAN)

​Chile (CHL)

​China (CHN)

​Colombia (COL)

​Costa Rica (CRI)

​Denmark (DNK)

​Dominican Republic (DOM)

​Ecuador (ECU)

​El Salvador (SLV)

​Finland (FIN)

​France (FRA)

​Guatemala (GTM)

​Honduras (HND)

​India (IND)

​Indonesia (IDN)

​Kenya (KEN)

​Malaysia (MYS)

​Mexico (MEX)

​Netherlands (NLD)

​Nigeria (NGA)

​Norway (NOR)

​Panama (PAN)

​Paraguay (PRY)

​Peru (PER)

​Singapore (SGP)

​South Africa (ZAF)

​Sweden (SWE)

​Thailand (THA)

​United Kingdom (GBR)

​United States (USA)

​Uruguay (URY)

​Venezuela (VEN)

​Zambia (ZMB)

​Consent

​Attempts, outcomes and billing

​What lands on the session

​Retention

​Related

Which source is queried

What the user does

Selfies, portraits and a later Face Match step

A Face Match step after a method that leaves no photo

Coverage and pricing

Format rules

Per-country fields

Argentina (`ARG`)

Bolivia (`BOL`)

Brazil (`BRA`)

Cambodia (`KHM`)

Canada (`CAN`)

Chile (`CHL`)

China (`CHN`)

Colombia (`COL`)

Costa Rica (`CRI`)

Denmark (`DNK`)

Dominican Republic (`DOM`)

Ecuador (`ECU`)

El Salvador (`SLV`)

Finland (`FIN`)

France (`FRA`)

Guatemala (`GTM`)

Honduras (`HND`)

India (`IND`)

Indonesia (`IDN`)

Kenya (`KEN`)

Malaysia (`MYS`)

Mexico (`MEX`)

Netherlands (`NLD`)

Nigeria (`NGA`)

Norway (`NOR`)

Panama (`PAN`)

Paraguay (`PRY`)

Peru (`PER`)

Singapore (`SGP`)

South Africa (`ZAF`)

Sweden (`SWE`)

Thailand (`THA`)

United Kingdom (`GBR`)

United States (`USA`)

Uruguay (`URY`)

Venezuela (`VEN`)

Zambia (`ZMB`)

Consent

Attempts, outcomes and billing

What lands on the session

Retention

Related