Question 1

What is Didit?

Accepted Answer

Didit is **infrastructure for identity and fraud** — the platform we wished existed when we were building products ourselves: **open, flexible, and developer-friendly**, so it works as a real part of your stack instead of a black box you integrate around.

One API covers verifying people (**KYC**, *know your customer*), verifying businesses (**KYB**, *know your business*), screening crypto wallets (**KYT**, *know your transaction*), and monitoring transactions in real time — on a stack built to be:

- **Fast** — sub-2-second p99 on every session
- **Reliable** — in production with **1,500+ companies** across **220+ countries**
- **Secure** — SOC 2 Type 1, ISO 27001, GDPR-native, and formally attested by Spain's financial regulator as safer than verifying someone in person

The footprint underneath: **14,000+ document types** in **48+ languages**, **1,000+ data sources**, and **200+ fraud signals** on every session. The Didit infrastructure dynamically learns from every session and gets better every day.

Question 2

What is Didit, and where does it work?

Accepted Answer

Didit is **infrastructure for identity and fraud** — one API that verifies people (**KYC**, know your customer), verifies businesses (**KYB**, know your business), screens crypto wallets (**KYT**, know your transaction), and monitors transactions in real time.

It works **everywhere your users are**:

- **220+ countries and territories**
- **14,000+ document types**
- **48+ user-facing languages** with capture in **130+ document-recognition languages** across 50+ scripts (Latin, Arabic, Cyrillic, CJK, Devanagari, Hebrew, Thai, Georgian)

Same `$0.33` Full KYC bundle in every country, **500 verifications free every month**, and the only identity-verification platform formally attested by Spain's **Tesoro**, **Banco de España**, and **SEPBLAC** as safer than in-person verification.

Question 3

How does Didit cover so many countries?

Accepted Answer

Three layers stacked into one Application Programming Interface (API):

- **Document recognition** — the same OCR (Optical Character Recognition) + Machine-Readable Zone (MRZ) + Near-Field Communication (NFC) chip-read pipeline runs on every passport, national ID, driver's license, residence permit, refugee document, and voter card in the **14,000+ document catalogue**.
- **Government-registry validation** — direct connections to **18+ national registries** (Spain DNI, Brazil CPF, Mexico CURP, Argentina RENAPER, India Aadhaar, Singapore MyInfo, Australia DVS, UAE Pass, and more) for cross-check beyond the document scan.
- **Local-script capture** — the hosted UI renders in 48+ languages and **right-to-left auto-flips** for Arabic and Hebrew.

New countries and document variants ship continuously — Didit's research agents monitor government registries every day and the data feed updates within hours of a new variant going live.

Question 4

How fast is the verification for my end user?

Accepted Answer

**The full flow normally takes under 30 seconds end-to-end** — pick up the ID, snap the document, snap the selfie, done. **That is the fastest in the market**. Legacy KYC providers usually take **more than 90 seconds** for the same flow.

On the back end, Didit returns the result in **under two seconds at p99**, measured from the moment the user finishes the selfie to the moment your webhook fires. Mobile capture is tuned for slow phones and slow networks: progressive image compression, lazy software development kit load, and a one-tap hand-off from desktop to phone via QR code if the user starts on web.

Question 5

Where is my data stored, by region?

Accepted Answer

By default, **all data is processed in the European Union** on Amazon Web Services (AWS) — encrypted in transit with TLS 1.3 and at rest with AES-256. The default holds whether your users are in São Paulo, Lagos, Mumbai, or Tokyo.

If you need a **specific region or in-country residency** (e.g. Brazil under LGPD, India under DPDP, Singapore under PDPA, UAE under PDPL, or U.S. under CCPA), that's available on Enterprise contracts — so teams in any market can run Didit compliantly.

The full data inventory, retention windows, sub-processor list, and Data Processing Addendum (DPA) live on `/security-compliance`.

Question 6

What happens if a user fails, abandons, or expires?

Accepted Answer

Every session lands on one of seven clear statuses, so your code always knows what to do:

- `Approved` — every check passed. Move the user forward.
- `Declined` — one or more checks failed. You can allow the user to **resubmit** the specific failed step (for example, re-take the selfie) without re-running the whole flow.
- `In Review` — flagged for compliance review. Open the case in the console, see every signal, decide approve or decline.
- `In Progress` — user is mid-flow.
- `Not Started` — link sent, user has not opened it yet. Send a reminder if it sits too long.
- `Abandoned` — user opened the link but did not finish in time. Re-engage or expire.
- `Expired` — the session link aged out. Create a new session.

**A signed webhook fires on every status change**, so your database always stays in sync. Abandoned and declined sessions are free.

Question 7

Where does my customer data live and how is it protected?

Accepted Answer

**Production data is processed and stored in the European Union by default**, on Amazon Web Services. Enterprise contracts can request alternative regions for jurisdictions whose regulators require it.

**Encryption everywhere.** AES-256 at rest across every database, object store, and backup. Transport Layer Security 1.3 in transit on every API call, webhook, and Business Console session. Biometric data is encrypted under a separate Customer Master Key.

**Retention is yours to control.** Default retention is **indefinite (unlimited)** unless you configure shorter — between **30 days and 10 years per application** — and you can delete any individual session at any time from the dashboard or the API.

Certifications: **SOC 2 Type 1** (Type 2 audit in progress), **ISO/IEC 27001:2022**, **iBeta Level 1 PAD**, and a public attestation from **Spain''s Tesoro / SEPBLAC / CNMV** that Didit''s remote identity verification is **safer than verifying someone in person**. Full report at [/security-compliance](/security-compliance).

Question 8

Is Didit compliant for my industry?

Accepted Answer

Didit ships compliant by default for the regulators that matter to identity infrastructure:

- **GDPR + UK GDPR** — controller / processor split, full Data Processing Agreement published, lead supervisory authority named (Spain''s AEPD).
- **AMLD6 + EU AML Single Rulebook** — 1,300+ sanctions, politically exposed person, and adverse-media lists screened in real time.
- **eIDAS 2.0** — EU Digital Identity Wallet aligned; reusable-identity ready.
- **MiCA (Markets in Crypto-Assets)** — ready for crypto on-ramps, exchanges, and custodians.
- **DORA** — Digital Operational Resilience Act, EU financial-services operational resilience.
- **BIPA, CUBI, Washington HB 1493, CCPA / CPRA** — US biometric privacy (Illinois, Texas, Washington) and California consumer privacy.
- **UK Online Safety Act** — age-gating and child-safety obligations.
- **FATF Travel Rule** — originator and beneficiary data on crypto transfers, IVMS-101 interoperable.

Detailed memo, every certificate, every regulator letter: [/security-compliance](/security-compliance).

Question 9

How fast can I integrate and start verifying users?

Accepted Answer

- **60 seconds** to a sandbox account at [business.didit.me](https://business.didit.me) — no credit card.
- **5 minutes** to a working verification through Claude Code, Cursor, or any coding agent via our Model Context Protocol (MCP) server.
- **A weekend** to a production-ready integration with signed-webhook verification, retries, and a remediation flow when a user is declined.

Three integration paths — pick whichever fits your stack:

- **Embed natively** with our Web, iOS, Android, React Native, or Flutter SDK.
- **Redirect** the user to the hosted verification page — zero SDK.
- **Send a link** by email, SMS, WhatsApp, or any channel — zero front-end work.

Same dashboard, same billing, same pay-per-success price for all three. Step-by-step guide at [docs.didit.me/integration/integration-prompt](https://docs.didit.me/integration/integration-prompt).

Country	Local IDs supported	Open country page
United Kingdom	16+	Open
Spain	13+	Open
Germany	14+	Open
France	13+	Open
Italy	13+	Open
Netherlands	16+	Open
Belgium	16+	Open
Ireland	10+	Open
Portugal	12+	Open
Switzerland	11+	Open
Austria	16+	Open
Sweden	16+	Open
Norway	14+	Open
Denmark	11+	Open
Finland	14+	Open
Poland	16+	Open
Estonia	12+	Open
Latvia	14+	Open
Lithuania	12+	Open
Malta	13+	Open
Gibraltar	5+	Open
Luxembourg	14+	Open
Czechia	15+	Open
Romania	11+	Open
Greece	11+	Open
Hungary	18+	Open
Russia	16+	Open
Ukraine	12+	Open
Bulgaria	17+	Open
Croatia	14+	Open
Slovakia	13+	Open
Slovenia	14+	Open
Cyprus	10+	Open
Georgia	14+	Open
Serbia	10+	Open
Iceland	12+	Open
Albania	11+	Open
North Macedonia	9+	Open
Montenegro	20+	Open
Moldova	10+	Open
Bosnia & Herzegovina	12+	Open
Armenia	10+	Open
Azerbaijan	13+	Open
Belarus	14+	Open
Liechtenstein	10+	Open
Andorra	6+	Open

Country	Local IDs supported	Open country page
Brazil	57+	Open
Mexico	46+	Open
Argentina	10+	Open
Chile	10+	Open
Colombia	17+	Open
Peru	13+	Open
Uruguay	9+	Open
Ecuador	11+	Open
Venezuela	8+	Open
Panama	9+	Open
Costa Rica	8+	Open
Dominican Republic	7+	Open
Bolivia	8+	Open
El Salvador	9+	Open
Guatemala	7+	Open
Honduras	8+	Open
Paraguay	12+	Open
Nicaragua	8+	Open
Haiti	9+	Open
Belize	12+	Open
Guyana	6+	Open
Suriname	6+	Open
Trinidad & Tobago	6+	Open
Jamaica	9+	Open

Flag	Country	Local IDs supported	Open country page
	United States	322+	Open
	Canada	48+	Open

Country	Local IDs supported	Open country page
Australia	46+	Open
New Zealand	13+	Open
Singapore	10+	Open
Hong Kong SAR China	5+	Open
Japan	12+	Open
South Korea	17+	Open
Indonesia	16+	Open
Philippines	13+	Open
Thailand	9+	Open
Vietnam	8+	Open
Malaysia	18+	Open
India	53+	Open
Pakistan	20+	Open
Bangladesh	9+	Open
Kazakhstan	11+	Open
Cambodia	9+	Open
Nepal	13+	Open
Sri Lanka	7+	Open
Myanmar (Burma)	7+	Open
Maldives	9+	Open
Brunei	10+	Open
Taiwan	7+	Open
Mongolia	12+	Open
Uzbekistan	9+	Open
Kyrgyzstan	9+	Open
Tajikistan	9+	Open
Laos	9+	Open

Country	Local IDs supported	Open country page
United Arab Emirates	14+	Open
Saudi Arabia	10+	Open
Qatar	14+	Open
Bahrain	9+	Open
Kuwait	6+	Open
Oman	11+	Open
Israel	10+	Open
Türkiye	13+	Open
Egypt	7+	Open
Morocco	8+	Open
South Africa	10+	Open
Kenya	13+	Open
Nigeria	13+	Open
Ghana	11+	Open
Ethiopia	18+	Open
Tanzania	12+	Open
Uganda	10+	Open
Rwanda	12+	Open
Jordan	6+	Open
Senegal	10+	Open
Angola	14+	Open
Côte d’Ivoire	12+	Open
Tunisia	5+	Open
Iraq	14+	Open
Lebanon	13+	Open
Libya	7+	Open
Algeria	7+	Open
Mauritania	8+	Open
Mali	9+	Open
Niger	5+	Open
Chad	9+	Open
Cameroon	11+	Open
Congo - Kinshasa	9+	Open
South Sudan	6+	Open
Eritrea	4+	Open
Djibouti	9+	Open
Somalia	7+	Open
Mauritius	4+	Open
Cape Verde	9+	Open
Guinea	12+	Open
Sierra Leone	10+	Open
Liberia	10+	Open
Namibia	11+	Open
Botswana	8+	Open
Mozambique	12+	Open
Zambia	8+	Open
Zimbabwe	9+	Open
Madagascar	7+	Open
Malawi	10+	Open

Identity verification in 220+ countries.

Europe — attested by Spain. Recognised across the European Union.

Latin America — local registries, Portuguese and Spanish hosted UI.

North America — federal, state, and provincial registries on one API.

Asia-Pacific — Aadhaar, MyInfo, Australia's document verification service.

Middle East & Africa — FATF Travel Rule aligned.

Open a new country in one click. We do the hard work.

Common questions about country coverage

Infrastructure for identity and fraud.