免费
免费
每月 $0。无需信用卡。
- 免费 KYC 套件（身份验证 + 被动活体检测 + 人脸匹配 + 设备与 IP 分析）, 每月 500 次，永久有效
- 黑名单用户
- 重复检测
- 每次会话 200+ 欺诈信号
- Didit 网络中可重复使用的 KYC
- 案件管理平台
- 工作流构建器
- 公开文档、沙盒、SDK、MCP（模型上下文协议）服务器
- 社区支持
全球2,000多家组织信赖。
英国 Ofcom · 法国 SREN · 欧盟 DSA
1秒内完成年龄验证。仅在必要时才需提供证件。
强制每位访客上传文档会使完成率下降25-40%。 Didit 的自适应流程首先运行年龄估算，仅将临界情况 路由到文档回退。自拍验证结果不到2秒，每次检查 $0.10， 每位用户的综合成本接近 $0.115。每月免费500次验证。
工作原理
从注册到验证用户，仅需四步。
- 步骤 01
创建工作流
选择您需要的检查项, 身份、活体、人脸匹配、制裁、地址、年龄、电话、电子邮件、自定义问题。在仪表盘中将它们拖入流程，或将相同的流程发布到我们的 API。根据条件进行分支，运行 A/B 测试，无需代码。
- 步骤 02
集成
使用我们的 Web、iOS、Android、React Native 或 Flutter SDK 进行原生嵌入。重定向到托管页面。或者直接通过电子邮件、短信、WhatsApp 等任何方式向您的用户发送链接。选择适合您技术栈的方式。
- 步骤 03
用户完成流程
Didit 负责托管摄像头、灯光提示、移动设备切换和辅助功能。当用户在流程中时，我们实时评估200多个欺诈信号，并根据权威数据源验证每个字段。结果在两秒内得出。
- 步骤 04
您接收结果
实时签名 Webhook 可在用户被批准、拒绝或发送审核时立即同步您的数据库。按需轮询 API。或者打开控制台检查每个会话、每个信号，并以您的方式管理案例。
01 · 仅自拍初审
通过一张被动自拍估算年龄。
单帧，无需动作挑战，无需上传文档。入门级安卓设备上，2 秒内出结果，每次检查 $0.10。这是对英国《在线安全法》和法国 SREN 的最低数据响应。
年龄估算模块Didit · Age Estimation
Estimate age in one passive selfie.
Step 1 / 1
Centre your face
Estimate27 yrs
ConfidenceHigh
LivenessPass
Sub-2-second verdict on entry-level Android.
02 · 临界范围路由
调整范围。Didit 负责其余路由。
为每个工作流设置临界范围。明确通过和明确失败的验证在自拍阶段完成；临界范围内的用户则升级到文档回退。在无代码工作流构建器中编辑切入点，无需重新部署。
工作流编排器Didit · Workflow Builder
Route only the borderline cases to ID.
Estimated bandPathVerdict
- 30+ yrsSelfie onlyApproved
- 22 - 29 yrsSelfie onlyApproved
- 16 - 21 yrsSelfie + documentReview
- 13 - 15 yrsDocument requiredReview
- Under 13Document requiredBlock
Edit the band in the no-code Workflow Builder.
03 · 文档回退
14,000+ 种文档。220+ 个国家/地区。
只有临界范围内的用户才需要上传文档。支持护照、国民身份证、驾驶执照、居留许可，并提供完整的光学字符识别 (OCR) 和机器可读区 (MRZ) 解析。约 10% 的典型流量会触及此步骤。
身份验证模块Didit · ID Verification
14,000+ documents. Only when needed.
- PassportMRZ + photo page
- National identity cardFront + back, OCR
- Driving licencePer-state rules in US, CA, AU
- Residence permitSchengen + UK BRP
220+ countries · 48+ languages~10% traffic
04 · 各国年龄规则
美国 21 岁可饮酒。欧盟 18 岁。韩国 19 岁。
设置每个国家的最低年龄，并在必要时提供州级覆盖（密西西比州 21 岁，阿拉巴马州 19 岁，美国默认 18 岁）。文档回退会自动根据签发国的规则验证出生日期。
国家/地区参考Didit · Country Rules
Per-country minimum age, out of the box.
CountryRuleMin age
- United KingdomOSA, adult content18
- FranceSREN, adult content18
- GermanyJuSchG / JMStV18
- United StatesAlcohol (federal)21
- South KoreaAlcohol / gaming19
State-level overrides (Mississippi 21, Alabama 19) included.
05 · 符合监管要求
英国 Ofcom、法国 CNIL、欧盟 DSA、德国 JuSchG。
专为高效的年龄保障标准而构建。西班牙 Tesoro 和 SEPBLAC 已正式证明 Didit 的远程流程比现场验证更安全, 这是目前欧盟成员国政府唯一此类认证。审计包包括 iBeta Level 1 PAD、ISO/IEC 27001、SOC 2 Type 1。
合规文档Didit · Compliance Matrix
Regulator-ready out of the box.
RegulatorMethod acceptedDidit
- UK Ofcom (OSA)Estimation or documentShips
- France CNIL / Arcom (SREN)Estimation or documentShips
- EU DSA, VLOPsRisk-proportionateShips
- Germany JuSchGDocument or KYCShips
Tesoro / SEPBLAC attestation included in the audit pack.
06 · 公开定价
$0.10 selfie. $0.15 document. Only when needed.
$0.10 的年龄估算覆盖了约 90% 通过自拍验证的用户。文档检查费用为 $0.15，仅针对约 10% 的临界少数。每用户平均成本接近 $0.115。每月免费提供 500 次验证，永久有效。
查看定价Didit · Public pricing
Blended cost: ~$0.115 per user.
Selfie age estimation~90% · $0.10
Document fallback~10% · $0.15
Blended per user~$0.115
500 verifications free every month, forever.
集成
一个工作流。一个会话。一个 Webhook。
针对自适应工作流开启一个会话。Didit 运行验证流程。签名后的结果将发送到您的回调地址。
POST /v3/session/自适应
$ curl -X POST https://verification.didit.me/v3/session/ \
-H "x-api-key: $DIDIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"workflow_id": "wf_age_gate_uk_fr",
"vendor_data": "user-42",
"callback": "https://app/age-gate/cb"
}'201创建时间{ "session_url": "verify.didit.me/..." }
工作流在临界情况下链式调用
AGE_ESTIMATION 和 ID_VERIFICATION。文档 →GET /v3/session/{sessionId}/decision/验证结果
$ curl https://verification.didit.me/v3/session/<id>/decision/ \
-H "x-api-key: $DIDIT_API_KEY"
# Returns the path taken
{
"status": "Approved",
"liveness": { "age_estimation": 27.3 }
}200OK状态：已批准 · 审核中 · 已拒绝 · 未完成
签名 webhook 具有相同结构。请先验证
X-Signature-V2。文档 →代理就绪集成
一键集成年龄验证功能。
将其粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent 中。填写您的技术栈。代理将构建自适应工作流、开启会话、连接 Webhook，并在五分钟内完成部署。
didit-integration-prompt.md
You are integrating Didit's Age Verification recipe into <my_stack>. Selfie-first age estimation with an adaptive document fallback for the borderline tail. One Didit workflow. Two real endpoints.
1. Verify age on a selfie. ONE call to the Sessions API runs Age Estimation + Passive Liveness on the same passive frame.
2. Fall back to a document check ONLY when the estimate sits in the borderline band you define. Same Sessions API workflow handles the fallback automatically.
Bundle pricing (public):
- Age Estimation: $0.10 per check (Sessions API or standalone)
- ID Verification fallback: $0.15 per check, only when triggered
- Typical blended cost lands near $0.115 per user (~90% finish on the selfie, ~10% touch the document fallback)
- First 500 verifications free every month, forever
PRE-REQUISITES
- Production API key from https://business.didit.me (sandbox key in 60s, no card).
- Webhook endpoint with Hash-based Message Authentication Code (HMAC) SHA-256 verification using the X-Signature-V2 header and your webhook secret.
- A workflow_id from the Workflow Builder. The workflow must contain the AGE_ESTIMATION feature, and (recommended) the ID_VERIFICATION feature with adaptive_id_verification enabled so the borderline tail routes through automatically.
STEP 1 — Build the adaptive workflow once
POST https://verification.didit.me/v3/workflows/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_label": "age_gate_uk_fr",
"features": [
{ "feature": "AGE_ESTIMATION" },
{ "feature": "ID_VERIFICATION" }
],
"age_estimation_decline_threshold": 18,
"face_liveness_score_decline_threshold": 30,
"adaptive_id_verification": true
}
Notes:
- "AGE_ESTIMATION" and "ID_VERIFICATION" are exact, case-sensitive feature names.
- age_estimation_decline_threshold defaults to 18; set 21 for US alcohol, 19 for South Korea, etc.
- adaptive_id_verification = true tells Didit to invoke the document fallback automatically when the estimate sits inside the borderline band.
STEP 2 — Open an age-verification session per user
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<the workflow_id from step 1>",
"vendor_data": "<your internal user id>",
"callback": "https://<your-app>/age-gate/callback",
"metadata": {
"purpose": "age_gate",
"surface": "<the page or feature being gated>"
}
}
Response: 201 Created with the hosted session_url. Redirect the user to it. The hosted flow opens the front camera, captures one passive frame, runs Age Estimation + Passive Liveness in sub-2-seconds, and either returns a verdict or routes the user into the document fallback automatically.
STEP 3 — Read the signed webhook on session completion
Didit POSTs to your callback. Session statuses are exact Title Case With Spaces.
Body (excerpted for an Age Estimation only finish):
{
"session_id": "<uuid>",
"vendor_data": "<your user id>",
"status": "Approved",
"liveness": {
"status": "Approved",
"method": "PASSIVE",
"score": 92,
"age_estimation": 27.3,
"warnings": []
}
}
Body (excerpted when the document fallback fired):
{
"session_id": "<uuid>",
"vendor_data": "<your user id>",
"status": "Approved",
"liveness": { "status": "Approved", "age_estimation": 17.9, "warnings": [{ "code": "AGE_NOT_DETECTED" }] },
"id_verification": {
"status": "Approved",
"date_of_birth": "1998-03-21",
"age": 27,
"document_type": "Passport",
"issuing_state": "GBR"
}
}
Verify X-Signature-V2 BEFORE trusting the body — HMAC SHA-256 of the raw bytes with your webhook secret.
Session status enum (exact case): Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned.
Warning catalog:
- AGE_BELOW_MINIMUM estimated or computed age below the threshold
- AGE_NOT_DETECTED unable to estimate age (lighting / quality)
- LOW_LIVENESS_SCORE passive-liveness score below threshold
- NO_FACE_DETECTED no face in the capture
- LIVENESS_FACE_ATTACK presentation attack suspected
- POSSIBLE_DUPLICATED_FACE same face previously verified
STEP 4 — Branch your surface on the final verdict
Approved → grant access to the gated surface.
Declined → render the regulator-required age-gate notice.
In Review → hold; an analyst case is open in the Business Console.
Not Finished → user abandoned; safe to re-prompt.
STEP 5 — Alternate path (server-to-server, when you already have the selfie)
POST https://verification.didit.me/v3/age-estimation/
Headers:
x-api-key: <your api key>
Body (multipart/form-data):
user_image <single passive selfie>
age_estimation_decline_threshold 18 (optional, integer)
face_liveness_score_decline_threshold 30 (optional, integer)
Branch on the borderline band yourself, then optionally call:
POST https://verification.didit.me/v3/id-verification/
Body (multipart/form-data):
front_image <required>
back_image <optional>
vendor_data <optional, your user id>
This path is useful for native onboarding apps that capture the selfie locally.
CONSTRAINTS
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: AGE_ESTIMATION, ID_VERIFICATION, LIVENESS, FACE_MATCH, AML, IP_ANALYSIS.
- Method enum is UPPERCASE: PASSIVE, FLASHING, ACTIVE_3D.
- Auth header is x-api-key (lowercase, hyphenated).
- Webhook signature header is X-Signature-V2 (NOT X-Signature).
- Status casing matches exactly: Approved, Declined, In Review, Expired, Not Finished, Resubmitted, Kyc Expired, Abandoned.
- Reference image URLs are signed and expire in 60 minutes. Store only the verdict + score; never the biometric media unless retention is explicitly enabled for fraud defence.
- 200+ fraud signals are evaluated on every session at no extra cost — surface the score via the session decision payload, do not re-query.
WEBHOOK EVENT NAMES
- Sessions: status changes flow through the standard session webhook.
- Verify X-Signature-V2 on every payload.
Read the docs:
- https://docs.didit.me/core-technology/age-estimation/overview
- https://docs.didit.me/sessions-api/create-session
- https://docs.didit.me/integration/webhooks
Start free at https://business.didit.me — sandbox key in 60 seconds, 500 verifications free every month, no credit card.需要更多上下文？请参阅完整的模块文档。docs.didit.me →
合规性设计
一键开启新国家/地区业务。 我们为您解决难题。
我们负责设立当地子公司、获取许可证、进行渗透测试、获得认证，并与所有新法规保持一致。要在新国家/地区发布验证服务，只需轻点开关。已覆盖220多个国家/地区，每个季度进行审计和渗透测试, 是唯一一个被欧盟成员国政府正式认定比线下验证更安全的身份提供商。
阅读安全与合规性档案欧盟金融沙盒
Tesoro · SEPBLAC · BdE
ISO/IEC 27001
信息安全 · 2026
SOC 2 · Type I
AICPA · 2026
iBeta Level 1 PAD
NIST / NIAP · 2026
GDPR
EU 2016/679
DORA
EU 2022/2554
MiCA
EU 2023/1114
AMLD6 · eIDAS 2.0
原生符合欧盟标准
数据证明
数据证明
- $0.000每位用户的综合成本, 包括自拍和 10% 的临界文档回退。
- ~90%用户仅通过被动自拍即可完成验证, 无需上传证件。
- <0s入门级安卓设备上每次会话返回的年龄段。
- 0每月免费验证，永久有效。
三个层级，一份价目表
免费开始。按使用量付费。可扩展至企业级。
每月 500 次免费验证，永久有效。生产环境按量付费。企业版提供定制合约、数据驻留和 SLA (Service Level Agreements)。
最受欢迎
按用量付费
按用量计费
按实际用量付费。25+模块。公开的模块定价，无每月最低费用。
- 完整KYC $0.33（身份+生物识别+IP/设备）
- 10,000+ AML数据集, 制裁、PEP、负面媒体
- 1,000+ 政府数据源用于数据库验证
- 交易监控 $0.02/笔交易
- 实时KYB $2.00/家企业
- 钱包筛选 $0.15/次检查
- 白标验证流程, 您的品牌，我们的基础设施
企业版
企业版
定制MSA和SLA。适用于大批量和受监管项目。
- 年度合同
- 定制MSA、DPA和SLA
- 专属Slack和WhatsApp频道
- 按需人工审核员
- 经销商和白标条款
- 独家功能和合作伙伴集成
- 指定CSM、安全审查、合规支持
免费开始 → 仅在检查运行时付费 → 解锁企业版以获取定制合约、SLA 或数据驻留。
FAQ
常见问题
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 does "age verification" actually require?
Most regulators ask for highly effective age assurance on adult content, online gambling, alcohol, and sometimes social platforms. That means a method good enough that the average minor can't trivially pass, not a self-declared birth-date checkbox.
The two methods almost every regulator accepts are age estimation (a selfie scored by a model) and age verification by document (the user uploads a passport or national identity card). Most teams ship both, with the estimation step gating the cheaper, lower-friction selfie path.
Which laws drive age-gating in 2026?
The two new rules pulling teams in are the UK Online Safety Act (Ofcom started enforcement in July 2025 for any service that lets users in the UK encounter pornography) and France's SREN law (CNIL + Arcom rules in force for sites accessed from France).
Alongside those, the EU Digital Services Act asks very-large platforms to mitigate risks to minors, and several US states (Utah, Texas, Louisiana) have age-gate statutes for adult content. They all accept the same toolkit: selfie age estimation, government identity document upload, or a third-party identity wallet.
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.
Why pair age estimation with a document fallback?
Two reasons. First, regulators care about the tail, not the median. A model is statistically fine at 17 vs 19 but the regulator wants you to be confident on the 16-year-old who looks 20. The document check is your evidence on those cases.
Second, conversion. Forcing every visitor to upload a passport drops finish rates by 25-40%. A selfie-first flow with document fallback typically routes 90% of users through the cheaper, friction-free path and 10% to the document step, far better business outcomes, same compliance posture.
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.
What attestations should I show my regulator?
Didit ships with the certifications UK Ofcom and CNIL most often ask to see on a vendor questionnaire:
- iBeta Level 1 PAD on the passive-liveness module (the NIST-referenced anti-spoof bar).
- ISO/IEC 27001 information-security certification.
- SOC 2 Type 1 on the platform.
- Spain's Tesoro / SEPBLAC formal attestation that Didit's remote flow is safer than in-person verification, currently the only EU member-state government attestation of this kind for any identity provider.
All four sit in the audit pack, ready to attach to the platform's transparency notice.
How do you handle the user's biometric data?
Data minimisation by default. The selfie is processed in memory, the age verdict and a liveness score are persisted, and the raw image is deleted unless retention is explicitly enabled for fraud defence. The retention window is per-workflow and per-region, and an end user can request deletion via the standard data-subject-request path.
We never sell, share, or train third-party models on a customer's biometric data. The full data-processing terms live at didit.me/terms/business.
What if a user fails the age check?
The selfie returns one of three outcomes:
- Approved, clearly above the threshold. Continue.
- Declined, clearly below. Block the surface; show the regulator-required age-gate notice.
- In Review, borderline, low liveness, or no face detected. The flow auto-routes to the document fallback. The user uploads a passport or national identity card; Didit returns the date-of-birth read off the document and verdict in under two seconds.
A signed webhook lands at every state change so you only render the gate against the latest verdict, not a guess.