



全球2,000多家组织信赖。
数据一览
- 0+支持本地化流程的国家/地区
- 0+全球支持的证件类型
- 0+捕获界面语言
- $0.00每次完整 KYC。全球统一价格
Europe — attested by Spain. Recognised across the European Union.
| 国旗 | 国家/地区 | 支持的本地 ID | 打开国家/地区页面 |
|---|---|---|---|
| 英国 | 16+ | Open | |
| 西班牙 | 13+ | Open | |
| 德国 | 14+ | Open | |
| 法国 | 13+ | Open | |
| 意大利 | 13+ | Open | |
| 荷兰 | 16+ | Open | |
| 比利时 | 16+ | Open | |
| 爱尔兰 | 10+ | Open | |
| 葡萄牙 | 12+ | Open | |
| 瑞士 | 11+ | Open | |
| 奥地利 | 16+ | Open | |
| 瑞典 | 16+ | Open | |
| 挪威 | 14+ | Open | |
| 丹麦 | 11+ | Open | |
| 芬兰 | 14+ | Open | |
| 波兰 | 16+ | Open | |
| 爱沙尼亚 | 12+ | Open | |
| 拉脱维亚 | 14+ | Open | |
| 立陶宛 | 12+ | Open | |
| 马耳他 | 13+ | Open | |
| 直布罗陀 | 5+ | Open | |
| 卢森堡 | 14+ | Open | |
| 捷克 | 15+ | Open | |
| 罗马尼亚 | 11+ | Open | |
| 希腊 | 11+ | Open | |
| 匈牙利 | 18+ | Open | |
| 乌克兰 | 12+ | Open | |
| 保加利亚 | 18+ | Open | |
| 克罗地亚 | 14+ | Open | |
| 斯洛伐克 | 13+ | Open | |
| 斯洛文尼亚 | 14+ | Open | |
| 塞浦路斯 | 10+ | Open | |
| 格鲁吉亚 | 14+ | Open | |
| 塞尔维亚 | 10+ | Open | |
| 冰岛 | 12+ | Open | |
| 阿尔巴尼亚 | 11+ | Open | |
| 北马其顿 | 10+ | Open | |
| 黑山 | 20+ | Open | |
| 摩尔多瓦 | 10+ | Open | |
| 波斯尼亚和黑塞哥维那 | 12+ | Open | |
| 亚美尼亚 | 10+ | Open | |
| 阿塞拜疆 | 13+ | Open | |
| 白俄罗斯 | 14+ | Open | |
| 列支敦士登 | 10+ | Open | |
| 安道尔 | 6+ | Open |
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.
| 国旗 | 国家/地区 | 支持的本地 ID | 打开国家/地区页面 |
|---|---|---|---|
| 阿拉伯联合酋长国 | 13+ | Open | |
| 沙特阿拉伯 | 10+ | Open | |
| 卡塔尔 | 14+ | Open | |
| 巴林 | 9+ | Open | |
| 科威特 | 6+ | Open | |
| 阿曼 | 11+ | Open | |
| 以色列 | 10+ | Open | |
| 土耳其 | 13+ | Open | |
| 埃及 | 7+ | Open | |
| 摩洛哥 | 8+ | Open | |
| 南非 | 10+ | Open | |
| 肯尼亚 | 13+ | Open | |
| 尼日利亚 | 13+ | Open | |
| 加纳 | 11+ | Open | |
| 埃塞俄比亚 | 18+ | Open | |
| 坦桑尼亚 | 12+ | Open | |
| 乌干达 | 10+ | Open | |
| 卢旺达 | 12+ | Open | |
| 约旦 | 6+ | Open | |
| 塞内加尔 | 10+ | Open | |
| 安哥拉 | 14+ | Open | |
| 科特迪瓦 | 12+ | Open | |
| 突尼斯 | 5+ | Open | |
| 伊拉克 | 14+ | Open | |
| 黎巴嫩 | 13+ | Open | |
| 利比亚 | 7+ | Open | |
| 阿尔及利亚 | 7+ | Open | |
| 毛里塔尼亚 | 8+ | Open | |
| 马里 | 9+ | Open | |
| 尼日尔 | 5+ | Open | |
| 乍得 | 9+ | Open | |
| 喀麦隆 | 11+ | Open | |
| 刚果(金) | 9+ | Open | |
| 南苏丹 | 6+ | Open | |
| 厄立特里亚 | 4+ | Open | |
| 吉布提 | 9+ | Open | |
| 索马里 | 7+ | Open | |
| 毛里求斯 | 4+ | Open | |
| 佛得角 | 9+ | Open | |
| 几内亚 | 12+ | Open | |
| 塞拉利昂 | 10+ | Open | |
| 利比里亚 | 10+ | Open | |
| 纳米比亚 | 11+ | Open | |
| 博茨瓦纳 | 8+ | Open | |
| 莫桑比克 | 12+ | Open | |
| 赞比亚 | 8+ | Open | |
| 津巴布韦 | 9+ | Open | |
| 马达加斯加 | 7+ | Open | |
| 马拉维 | 10+ | Open |
一键开启新国家/地区业务。 我们为您解决难题。
关于国家/地区覆盖范围的常见问题
What is Didit?
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.
What is Didit, and where does it work?
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.
How does Didit cover so many countries?
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.
How fast is the verification for my end user?
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.
Where is my data stored, by region?
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.
What happens if a user fails, abandons, or expires?
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.
Where does my customer data live and how is it protected?
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.
Is Didit compliant for my industry?
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.
How fast can I integrate and start verifying users?
- 60 seconds to a sandbox account at 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.