免费
每月 $0。无需信用卡。
- 免费 KYC 套件(身份验证 + 被动活体检测 + 人脸匹配 + 设备与 IP 分析), 每月 500 次,永久有效
- 黑名单用户
- 重复检测
- 每次会话 200+ 欺诈信号
- Didit 网络中可重复使用的 KYC
- 案件管理平台
- 工作流构建器
- 公开文档、沙盒、SDK、MCP(模型上下文协议)服务器
- 社区支持


全球2,000多家组织信赖。

零工平台应尽的责任
被停用的司机和被禁的快递员每天都在用新名字重新注册。Didit 在单次会话中提供身份验证 + AML,每位工作人员仅需 $0.53(每个国家/地区增加驾照注册额外收取 $0.20),Face Search 1:N 在 200 毫秒内即可识别同一张面孔, 即使是新证件、新名字、新邮箱。每月免费提供 500 次验证。
选择您需要的检查项, 身份、活体、人脸匹配、制裁、地址、年龄、电话、邮箱、自定义问题。在控制台中将它们拖入流程,或通过 API 发布相同流程。支持条件分支、A/B 测试,无需代码。
通过我们的 Web、iOS、Android、React Native 或 Flutter SDK 进行原生嵌入。重定向到托管页面。或者直接通过邮箱、短信、WhatsApp 等任何方式向用户发送链接。选择最适合您技术栈的方案。
Didit 负责托管摄像头、光线提示、移动端切换和无障碍功能。在用户进行流程时,我们实时评估 200 多个欺诈信号,并根据权威数据源验证每个字段。两秒内即可得出结果。
实时签名的 Webhook 可在用户通过、拒绝或需要审核时,立即同步您的数据库。按需轮询 API。或打开控制台,检查每个会话、每个信号,并按您的方式管理案例。
Didit · 零工注册
步骤 3 / 5
保持静止进行活体检测
Didit · 数据库验证
Didit · 持续 AML
Didit · 人脸搜索 1:N
新申请人
Didit · 覆盖范围
$ 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_gig_rideshare",
"vendor_data": "driver-9241"
}'{ "session_url": "verify.didit.me/..." }// X-Signature-V2 verified upstream
if (payload.status === "Approved") {
activateWorker(payload.vendor_data);
indexFace(payload.face);
} else if (payload.status === "Declined") {
blockReapplication(payload.aml.hits);
}状态:已批准 · 已拒绝 · 审核中 · KYC 已过期You are integrating Didit into a gig marketplace to onboard drivers, couriers, freelancers, or creators. ONE Didit session, five checks:
Verify the worker's identity (KYC) — ID document, liveness, face match, device + IP, AML against 1,300+ sanctions / Politically Exposed Person (PEP) / adverse-media lists — plus Face Search 1:N against your private worker index to block previously-banned workers re-applying under a new name. Add an OPTIONAL licence-registry cross-check when you onboard drivers.
Bundle pricing (verified live, 2026-05-17):
- Full KYC bundle: $0.33 per worker (ID + Liveness + Face Match + Device & IP)
- AML Screening: $0.20 per worker
- Face Search 1:N against your private worker index: Free
- Baseline total: $0.53 per worker — public price, no minimums
- Optional Database Validation (licence registry): $0.20 per call, only billed when used
- First 500 verifications free every month, forever
- Ongoing AML on active workforce: $0.07 per worker per year (automatic)
PRE-REQUISITES
- Production API key from https://business.didit.me (sandbox key in 60s, no card).
- Webhook endpoint with HMAC SHA-256 verification using the X-Signature-V2 header and your webhook secret.
- A workflow_id from the Workflow Builder that bundles ID Verification + Passive Liveness + Face Match 1:1 + Device & IP + AML Screening. For drivers, ALSO add Database Validation and branch on country_of_work.
STEP 1 — Open the worker session at signup
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<wf id with KYC + AML (and Database Validation if driver)>",
"vendor_data": "<your worker id, max 256 chars>",
"callback_url": "https://<your-app>/gig/onboarding/callback",
"metadata": {
"gig_category": "rideshare",
"country_of_work": "ES",
"license_number": "<worker's licence number, OCR'd or self-entered>"
}
}
Response: 201 Created with a hosted session URL on the `url` field. Redirect the worker (web or in-app webview). Sub-2-second median verdict on completion.
STEP 2 — Read the signed webhook when the worker finishes
Didit POSTs to your callback. Session statuses are Title Case With Spaces:
Body (excerpted, with optional Database Validation included for a driver):
{
"session_id": "<uuid>",
"vendor_data": "<your worker id>",
"status": "Approved",
"id_verification": { "status": "Approved", "document_type": "Driver License" },
"liveness": { "status": "Approved" },
"face": { "status": "Approved", "similarity_score": 0.94 },
"ip_analysis": { "status": "Approved" },
"aml": { "status": "Approved", "hits": [] },
"database_validation": { "status": "Approved", "registry": "DGT" }
}
Status enum (exact case): Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned.
Verify the X-Signature-V2 header BEFORE reading the body — HMAC SHA-256 of the raw body bytes with your webhook secret. Re-serialising the parsed JSON breaks the signature.
STEP 3 — Branch on the verdict
Approved → activate the worker; let them pick up jobs.
In Review → route to ops queue; hold first job until disposition.
Declined → block; log the hit detail for compliance.
Resubmitted → applicant retried after a soft rejection — re-read.
Kyc Expired → session went stale; send a new session URL.
STEP 4 — Re-application defence (Face Search 1:N)
Every onboarded worker is indexed in your app's private Face Search 1:N index. A banned worker re-applying under a different name + a different document + a different IP is caught in under 200ms on the same /v3/ call (Face Search runs as a workflow step). Set the action on duplicate match to Block, Review, or Approve per app.
STEP 5 — Ongoing AML on the active workforce is automatic
Every Approved worker is re-screened DAILY by Didit's continuous AML monitoring at $0.07 per worker per year. NO separate endpoint to call — the original session is what gets monitored.
When a previously-clean worker crosses an AML threshold (new sanction listing, new adverse-media hit, PEP status change), the session status changes to "In Review" or "Declined" automatically and your webhook fires the update. Disable the worker, route to ops.
STEP 6 — Optional licence registry for drivers
For ride-share and delivery onboardings only, enable Database Validation in the workflow and branch on country_of_work:
ES → DGT
UK → DVLA
US → state DMV (per state)
BR → DENATRAN
The check costs $0.20 and is only billed when the workflow step runs. If the country isn't supported yet, the step is skipped — no spurious decline.
WEBHOOK EVENT NAMES
- Sessions: status changes flow through the standard session webhook.
- Ongoing AML updates: same session webhook fires when the verdict flips post-onboarding.
Verify X-Signature-V2 on every payload.
CONSTRAINTS
- Session statuses use Title Case With Spaces (Approved, In Review). Do not lowercase or snake_case them.
- Database Validation is country-specific — 20+ countries live for driver licences. If the country isn't live, the check is skipped (no spurious decline).
- 200+ fraud signals are evaluated on every KYC session at no extra cost.
- The session URL is single-use; if a worker abandons mid-flow, create a new session for the retry.
Read the docs:
- https://docs.didit.me/sessions-api/create-session
- https://docs.didit.me/core-technology/aml-screening/overview
- 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.每月 $0。无需信用卡。
按实际用量付费。25+模块。公开的模块定价,无每月最低费用。
定制MSA和SLA。适用于大批量和受监管项目。
免费开始 → 仅在检查运行时付费 → 解锁企业版以获取定制合约、SLA 或数据驻留。
Didit 是身份和欺诈基础设施, 是我们自己构建产品时希望存在的平台:开放、灵活、对开发者友好,因此它能真正融入您的技术栈,而不是一个您需要围绕其集成的黑盒。
一个 API 即可涵盖人员验证(KYC,了解您的客户)、企业验证(KYB,了解您的企业)、加密钱包筛选(KYT,了解您的交易)以及实时交易监控, 构建在以下技术栈之上:
底层支持:14,000 多种证件类型,支持48 种以上语言,1,000 多个数据源,每个会话200 多个欺诈信号。Didit 基础设施从每个会话中动态学习,并日益完善。
每个零工平台对每位新员工的四项义务:
Didit 将这四项功能捆绑到一个 /v3/session/ 调用中。
两个结构性原因:
针对您的私人员工索引进行人脸搜索 1:N 可堵住这两个漏洞。
整个流程通常在 30 秒内完成, 拿起身份证件,拍下证件照,再拍一张自拍照,搞定。这是市场上最快的速度。传统的 KYC 服务商完成同样流程通常需要超过 90 秒。
在后端,Didit 在用户完成自拍到您的 webhook 触发之间,p99 响应时间低于两秒。移动端捕获针对慢速手机和慢速网络进行了优化:渐进式图像压缩、延迟加载 SDK,以及如果用户从网页端开始,可通过二维码一键从桌面端切换到手机端。
每位获批员工的注册自拍都会被索引到您应用程序的私人一对多 (1:N) 人脸索引中, 以您的 vendor_data 为键,每个 Didit 应用程序独立隔离,静态完全加密。新入职人员的自拍会在 200 毫秒内与索引进行交叉检查。
被禁司机重新申请时:
Maria L. → M. A. Lopez)。…仍然会呈现相同的面孔。人脸搜索会返回被禁记录的原始 vendor_data,并将结果判定为“阻止”。此功能免费,包含在每个工作流中。
每个会话都会落入七种明确状态之一,因此您的代码始终知道如何处理:
Approved, 所有检查通过。让用户继续。Declined, 一项或多项检查失败。您可以允许用户重新提交特定的失败步骤(例如,重新拍摄自拍),而无需重新运行整个流程。In Review, 标记为合规审查。在控制台中打开案例,查看所有信号,决定批准或拒绝。In Progress, 用户正在进行中。Not Started, 链接已发送,用户尚未打开。如果长时间未打开,发送提醒。Abandoned, 用户打开了链接但未及时完成。重新激活或使其过期。Expired, 会话链接已过期。创建新会话。每次状态更改都会触发一个带签名的 webhook,因此您的数据库始终保持同步。放弃和拒绝的会话是免费的。
生产数据默认在欧盟的 Amazon Web Services 上处理和存储。企业合同可根据监管机构要求,申请在其他区域存储。
全程加密。 所有数据库、对象存储和备份均采用 AES-256 静态加密。所有 API 调用、webhook 和业务控制台会话均采用传输层安全协议 1.3 (TLS 1.3) 进行传输加密。生物识别数据使用单独的客户主密钥加密。
保留期限由您控制。 默认保留期限为无限期(无限制),除非您配置更短的期限, 每个应用程序可在30 天到 10 年之间设置, 您可以随时通过仪表板或 API 删除任何单个会话。
认证:SOC 2 Type 1(Type 2 审计进行中)、ISO/IEC 27001:2022、iBeta Level 1 PAD,以及西班牙 Tesoro / SEPBLAC / CNMV 的公开证明,表明 Didit 的远程身份验证比现场验证更安全。完整报告请访问 /security-compliance。
Didit 默认符合身份基础设施相关的重要监管机构要求:
详细备忘录、所有证书、所有监管机构函件:/security-compliance。
三种集成路径, 选择最适合您技术栈的方式:
所有三种方式都使用相同的仪表板、相同的计费、相同的按成功付费价格。分步指南请访问 docs.didit.me/integration/integration-prompt。
取决于工人就业国家的要求:
Didit 的分类器支持220 多个国家/地区的 14,000 多种文件。工作流构建器根据工作国家进行分支,因此英国司机进行 DVLA 检查,西班牙司机进行 DGT 检查, 流程相同,注册机构不同。
设备和 IP 分析在相同的 /v3/session/ 调用中运行,每次检查费用为 $0.03。每次会话都会免费显示 200 多个欺诈信号:
vendor_data 使用同一设备。当信号堆栈超过您在工作流构建器中配置的阈值时,结果会变为 In Review。
三种集成模式:
session_url 重定向工人。无需前端工作,这是最常见的路径。/v3/id-verification/。所有这三种模式都使用相同的工作流,返回相同的按功能报告结构,并触发相同的 webhook。可根据不同的零工类别进行混搭。