Question 1

How do you add a brand-new document type you have never seen?

Accepted Answer

Research agents monitor PRADO (the EU Public Register of Authentic Documents Online), the U.S. Department of State document library, and 220+ per-country government registries every day. When a new variant ships — a new German Personalausweis, a redesigned Brazilian CNH, a freshly-issued Estonian eID — the agent diffs it against the certified database, files the specimen, and routes it through one of two pipelines depending on capture quality.

**No customer redeploy required** — the new variant appears on the searchable table on this page the moment it ships.

Question 2

What decides auto-add versus manual review?

Accepted Answer

Capture quality. Two paths:

- **Auto-add via PRADO** — low-resolution variants (thumbnails under 600 px on the long edge, the size PRADO publishes for most documents) flow straight into the classifier. They teach the model to recognise the document on sight but are too small to read security features from.
- **Manual review** — high-fidelity specimens (full-resolution captures with visible Optical Character Recognition (OCR) fields, Machine-Readable Zone (MRZ) zones, and security features) go through compliance review before they ship.

Both paths land on the same `/v3/` session API and return the same JSON shape — you do not see the difference downstream.

Question 3

How do you handle expired documents?

Accepted Answer

**Document Monitoring** tracks every user's document expiry date after the initial verification. When a document expires, the user status flips automatically from `Approved` to `Kyc Expired` and the platform fires a webhook so your app can prompt re-verification.

The same monitoring layer powers ongoing Know Your Customer (KYC) for regulated workflows. Full reference at `docs.didit.me/core-technology/id-verification/document-monitoring-id-verification`.

Question 4

How does NFC reading work, and which documents support it?

Accepted Answer

Near-Field Communication (NFC) reads the cryptographic chip embedded in **eMRTDs** — Electronic Machine-Readable Travel Documents, the ICAO 9303 standard. That covers virtually every modern e-passport plus EU national eID cards and EU residence permits.

The phone reads the chip wirelessly, verifies the Document Signer Certificate against the issuing country's Country Signing Certificate Authority (CSCA), and returns a tamper-proof copy of the document data. NFC ships in the **iOS and Android native Software Development Kits (SDKs)** — browser-based flows fall back to standard ID Verification + selfie because the Web NFC API is unstable on Android and absent on iOS.

Question 5

How accurately do you parse the Machine-Readable Zone (MRZ)?

Accepted Answer

The Machine-Readable Zone (MRZ) is the two- or three-line code at the bottom of every ICAO 9303 passport and most EU national ID cards.

Didit parses it with **full check-digit validation** — every field (document number, date of birth, date of expiry, nationality, document type) is mathematically validated against its check digit before the response returns. The MRZ also acts as a structured fallback whenever Optical Character Recognition (OCR) confidence drops below threshold, so name, document number, and dates always have a deterministic recovery path even on imperfect captures.

Question 6

Do you verify document authenticity, security features, and holograms?

Accepted Answer

Yes. Every session runs:

- **Template matching** against the certified specimen.
- **Security-feature validation** — holograms, watermarks, Optically Variable Ink (OVI), kinegrams, microprint.
- **Document liveness** — defeats screen replays, printed copies, and photographs of screens.
- **Portrait tamper detection**.
- **Machine-Readable Zone (MRZ) check-digit validation**.
- **Country Signing Certificate Authority (CSCA) chain check** when Near-Field Communication (NFC) is available.

Full catalog of warnings — what each one means and how it surfaces — at `docs.didit.me/core-technology/id-verification/warnings-id-verification`.

Question 7

How fast does document inference complete?

Accepted Answer

**Every session completes in under 2 seconds, end to end.** Most complete inside 1.2 seconds. The infrastructure has held 100% uptime over the last 6 months across millions of verifications a month — track it live at `status.didit.me`.

Question 8

How do you handle low-quality or blurry captures?

Accepted Answer

Every side of the document carries a `front_image_quality_score` and `back_image_quality_score` in the report — each scoring 0-100 across focus, glare, occlusion, and crop.

The intelligent-capture flow surfaces real-time visual cues during capture (positioning, lighting, focus) and only auto-captures when conditions are ideal — so most low-quality submissions never reach the model. When a captured image still scores low, the session emits a warning and either auto-retries the user or routes to manual review, depending on your workflow.

Question 9

What is the difference between ID Verification and Database Validation?

Accepted Answer

- **ID Verification ($0.15)** reads the document itself — Optical Character Recognition (OCR), Machine-Readable Zone (MRZ), Near-Field Communication (NFC), security features, document liveness. It answers *is this a real document, and what does it say?*
- **Database Validation (from $0.05)** takes the data ID Verification extracted and queries it against the **authoritative government registry** that issued the document — RENAPER (Argentina), Receita Federal (Brazil), Tribunal Electoral (Panama), RENAPO (Mexico), and 60+ others. It answers *does that data actually match the official record, and is the photo on file the same person as the selfie?*

Run them together for the strongest defence against synthetic-identity fraud.

Question 10

What does a document check cost?

Accepted Answer

**Run ID Verification standalone at $0.15.** Bundle it into the recommended **$0.33 KYC (Know Your Customer)** workflow with ID Verification ($0.15) + Passive Liveness ($0.10) + Face Match 1:1 ($0.05) + Device & IP Analysis ($0.03) on a single API call.

**Get 500 verifications free every month**, every workspace, forever — no credit card required. No minimum commit, no overage surprise: the price on `didit.me/pricing` is the price on the invoice.

Question 11

How do I request a document or a language you do not yet support?

Accepted Answer

Contact us on WhatsApp at `https://wa.me/+19544659728` or ping the team from the Business Console. **We ship a new document — or a new language — to production in 1 day when you request it.** The research agent pulls every available specimen, the model retrains, manual-review compliance signs off, and the new variant lands on the same `/v3/` API with no customer redeploy on your side.

The verification flow already ships in **49 languages** out of the box. Need one we do not have? Ask — same 1-day turnaround, with full localised capture, retry prompts, and error states from day one.

14,000+ documents in 220+ countries.

Search every country, every document.

Research agents read every government registry every day.

Common questions

ID Verification

NFC Reading

Database Validation

Passive Liveness

Public pricing on every module

Supported documents reference

Infrastructure for identity and fraud.