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 source returns a portrait, takes a selfie.
- Gets a result: verified and moved on, asked to correct the number, retried, sent to document capture, or declined.
Sources that return a portrait
Four sources return the person’s photograph: South Africa, Nigeria, Argentina and Panama — all four government registers. For those countries 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 (all four are government registers), the country’sskip_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.
Every other source returns data only. There is no portrait to compare against, so no selfie is taken and the switch is normalised off on save. Add Liveness and Face Match as their own workflow steps if a biometric check matters in those countries — Face Match then needs a portrait from somewhere else in the workflow.
Coverage and sources
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 againstmax_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 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.
Bolivia (BOL)
Source: SEGIP. This source returns data only, so there is no portrait to face-match against.
Brazil (BRA)
Source: Receita Federal. This source returns data only, so there is no portrait to face-match against.
Cambodia (KHM)
Source: Ministry of Interior voter register. This source returns data only, so there is no portrait to face-match against.
Canada (CAN)
Source: Canadian credit bureau records (FINTRAC dual-process). This source returns data only, so there is no portrait to face-match against.
Chile (CHL)
Source: Servicio de Registro Civil e Identificación. This source returns data only, so there is no portrait to face-match against.
China (CHN)
Source: NCIIC (National Citizen Identity Information Center). This source returns data only, so there is no portrait to face-match against.
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.
Costa Rica (CRI)
Source: Tribunal Supremo de Elecciones. This source returns data only, so there is no portrait to face-match against.
Denmark (DNK)
Source: CPR register. This source returns data only, so there is no portrait to face-match against.
Dominican Republic (DOM)
Source: Junta Central Electoral. This source returns data only, so there is no portrait to face-match against.
Ecuador (ECU)
Source: Registro Civil del Ecuador. This source returns data only, so there is no portrait to face-match against.
El Salvador (SLV)
Source: RNPN. This source returns data only, so there is no portrait to face-match against.
Finland (FIN)
Source: DVV population register. This source returns data only, so there is no portrait to face-match against.
France (FRA)
Source: French residential and utility records. This source returns data only, so there is no portrait to face-match against.
Guatemala (GTM)
Source: SAT. This source returns data only, so there is no portrait to face-match against.
Honduras (HND)
Source: CNE. This source returns data only, so there is no portrait to face-match against.
India (IND)
Source: UIDAI (Aadhaar). This source returns data only, so there is no portrait to face-match against.
Indonesia (IDN)
Source: Indonesian population register via residential records. This source returns data only, so there is no portrait to face-match against.
Kenya (KEN)
Source: IPRS (Integrated Population Registration System). This source returns data only, so there is no portrait to face-match against.
Malaysia (MYS)
Source: JPN (National Registration Department). This source returns data only, so there is no portrait to face-match against.
Mexico (MEX)
Source: RENAPO. This source returns data only, so there is no portrait to face-match against.
Netherlands (NLD)
Source: Dutch residential records. This source returns data only, so there is no portrait to face-match against.
Nigeria (NGA)
Source: NIMC / NIBSS. 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.
Norway (NOR)
Source: Norwegian residential records. This source returns data only, so there is no portrait to face-match against.
Panama (PAN)
Source: Tribunal Electoral / SIB. 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.
Paraguay (PRY)
Source: Registro del Estado Civil. This source returns data only, so there is no portrait to face-match against.
Peru (PER)
Source: RENIEC. This source returns data only, so there is no portrait to face-match against.
Singapore (SGP)
Source: Singapore credit bureau and utility records. This source returns data only, so there is no portrait to face-match against.
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.
Sweden (SWE)
Source: Skatteverket population register. This source returns data only, so there is no portrait to face-match against.
Thailand (THA)
Source: DOPA civil registration. This source returns data only, so there is no portrait to face-match against.
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.
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.
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.
Venezuela (VEN)
Source: CNE. This source returns data only, so there is no portrait to face-match against.
Consent
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.
A source that answered is billed whatever it answered — the query ran and the answer is the product. A source that never answered costs nothing. When the user falls back to document capture, that capture bills on top, because two checks ran.
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 anid_lookup evidence block:
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.
When a source does not answer, the array also carries an error row instead of a field verdict:
result before treating a row as a field comparison: error is evidence about the query, never a mismatch by the user. registry_portrait and face_match_score are present only for the four sources that return a portrait.
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.Related
- 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
methodskey reference