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


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

同人检查
亚秒级相似度评分,带防欺诈回退。每次检查 $0.05, 市场上最便宜的人脸比对服务。
选择您需要的检查项, 证件、活体、人脸比对、制裁名单、地址、年龄、电话、邮箱、自定义问题。在控制面板中拖拽构建流程,或通过 API 发布相同流程。支持条件分支、A/B 测试,无需代码。
通过我们的 Web、iOS、Android、React Native 或 Flutter SDK 进行原生嵌入。重定向到托管页面。或者直接通过电子邮件、短信、WhatsApp 等方式向用户发送链接。选择最适合您技术栈的方式。
Didit 负责托管摄像头、灯光提示、移动设备切换和辅助功能。在用户进行流程时,我们实时评估 200 多个欺诈信号,并根据权威数据源验证每个字段。两秒内出结果。
实时签名 Webhook 可确保用户批准、拒绝或发送审核后,您的数据库立即同步。按需轮询 API。或打开控制台检查每个会话、每个信号,并按您的方式管理案例。
source_image · target_image
POST /v3/face-match/
边缘服务 · 嵌入模型
LOW_FACE_MATCH_SIMILARITY
wf_face_match_kyc
按成功付费 · 无最低消费
$ 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_face_match_kyc",
"vendor_data": "user-42"
}'{ "session_url": "verify.didit.me/..." }$ curl -X POST https://verification.didit.me/v3/face-match/ \
-H "x-api-key: $DIDIT_API_KEY" \
-F "source_image=@selfie.jpg" \
-F "target_image=@portrait.jpg"{ "status": "Approved", "score": 87 }# Didit Face Match 1:1 — integrate in 5 minutes
You are integrating Didit's Face Match 1:1 (selfie vs. reference image)
module into <my_stack>. Follow these steps exactly. Every URL, header,
and enum value below is canonical — do not paraphrase or "improve" them.
## 1. Provision an account
- Sign up: https://business.didit.me (no credit card required).
- Or provision programmatically: POST https://apx.didit.me/auth/v2/programmatic/register/
(returns an API key bound to the workspace + application).
## 2. Two integration paths — pick one
### Path A — Workflow Builder (hosted UI)
Best when you want Didit to handle selfie capture, real-time framing,
mobile handoff, and accessibility for you. Inside a Know Your Customer (KYC) workflow,
Face Match runs automatically against the portrait extracted from the
ID document the user uploads in the same session.
1. Create a workflow that contains the FACE_MATCH feature:
POST https://verification.didit.me/v3/workflows/
Authorization header: x-api-key: <your-api-key>
Body: workflow_label, features array with FACE_MATCH plus any
other features the same session needs (typically
ID_VERIFICATION and LIVENESS for full KYC). Feature names
are UPPERCASE — strict enum.
Optional config: review_threshold and decline_threshold for the
LOW_FACE_MATCH_SIMILARITY warning (numbers 0–100).
2. Create a verification session for an end user:
POST https://verification.didit.me/v3/session/
Body: workflow_id (from step 1), vendor_data (your own user id).
Response: session_url — redirect the user to it.
3. Listen for webhook callbacks (see "Webhooks" below).
### Path B — Standalone server-to-server API
Best when you already have two face images and just need a similarity
score (re-auth at sensitive actions, employee badge access, cross-app
identity binding, periodic re-verification).
POST https://verification.didit.me/v3/face-match/
Content-Type: multipart/form-data
Body fields:
- source_image (required, file — the live selfie)
- target_image (required, file — the reference image, e.g. ID portrait
or a stored enrollment frame)
- vendor_data (optional string, your user id)
Response: synchronous JSON report with the similarity score and warnings
array. No webhook needed.
## 3. Webhooks (Path A only — Path B returns synchronously)
- Register a webhook destination once via
POST https://verification.didit.me/v3/webhook/destinations/
Body: url, subscribed_events: ["session.verified",
"session.review_started",
"session.declined"]
- Response includes secret_shared_key — store it.
- Every webhook delivery carries an X-Signature-V2 header you MUST verify
before trusting the payload. HMAC-SHA256 verification MUST run against the raw body bytes (the raw payload as Didit sent it) BEFORE any JSON parsing — re-serialising the parsed body changes whitespace and key order, which invalidates the signature.Algorithm:
1. sortKeys(payload) recursively
2. shortenFloats (truncate trailing zeros after the decimal point)
3. JSON.stringify the result
4. HMAC-SHA256 with the secret_shared_key
5. Hex-encode, compare to the X-Signature-V2 header.
## 4. Reading the report (both paths return the same shape)
The face_match object includes:
- status: "Approved" | "Declined" | "In Review" | "Not Finished"
- score: number 0-100 (normalized similarity score)
- source_image_session_id: the verification session that produced the
live selfie (Path A) or null (Path B)
- source_image: signed URL to the live selfie (expires in 1 hour)
- target_image: signed URL to the reference image (expires in 1 hour)
- warnings: Array<{ risk, log_type, short_description, long_description }>
Auto-decline risks (always enforced by Didit, not configurable):
- NO_REFERENCE_IMAGE (no reference image available to compare against)
Configurable risks (action per workflow — Decline, Review, or Approve):
- LOW_FACE_MATCH_SIMILARITY
Tune two thresholds per application:
review_threshold → score below this goes to "In Review"
decline_threshold → score below this is auto-declined
## 5. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: FACE_MATCH, ID_VERIFICATION, LIVENESS, AML, IP_ANALYSIS.
- Auth header is x-api-key (lowercase, hyphenated).
- Webhook signature header is X-Signature-V2 (NOT X-Signature).
- Always verify webhook signatures before trusting payload data.
- Status casing matches exactly: "Approved", "Declined", "In Review",
"Not Finished" (title-cased, space-separated).
- Reference and source image URLs in the response expire in 60 minutes.
Persist only the score and status; re-fetch images on demand if your
audit policy needs them.
## 6. Pricing reference (public)
- Standalone POST /v3/face-match/: $0.05 per match.
- Bundled inside a full KYC workflow with ID Verification + Passive
Liveness + Device & IP Analysis: $0.33 per session (Face Match included).
- 500 free checks every month, forever, on every account.
## 7. Verify your integration
- Sandbox starts on signup at https://business.didit.me — no separate flag.
- Test images: deterministic synthetic faces returned in sandbox
(Approved by default; trigger Declined by sending a mismatched pair).
- Switch to live: flip the application's environment toggle in console.
When in doubt: https://docs.didit.me/core-technology/face-match/overview
每月 $0。无需信用卡。
按实际用量付费。25+模块。公开的模块定价,无每月最低费用。
定制MSA和SLA。适用于大批量和受监管项目。
免费开始 → 仅在检查运行时付费 → 解锁企业版以获取定制合约、SLA 或数据驻留。
Didit 是身份和欺诈基础设施, 一个我们自己在构建产品时曾渴望拥有的平台:开放、灵活且对开发者友好,因此它能真正融入您的技术栈,而不是一个需要您围绕其进行集成的黑盒。
一个 API 即可涵盖人员验证(KYC,了解您的客户)、企业验证(KYB,了解您的企业)、加密钱包筛选(KYT,了解您的交易)以及实时交易监控, 所有这些都建立在一个旨在实现以下目标的堆栈上:
底层支持:14,000 多种证件类型,支持 48 种以上语言,1,000 多个数据源,每个会话包含 200 多个欺诈信号。Didit 基础设施通过每个会话动态学习,并日益完善。
source_image 和 target_image 传递给 multipart POST /v3/face-match/。接受的格式:JPG、JPEG、PNG,每张图像最大 5 MB。两种路径都返回相同的 face_match JSON 结构。face_match 对象,包含 status(Approved、Declined、In Review 或 Not Finished)、一个 0-100 的 score、一个将结果与生成实时自拍的验证会话关联起来的 source_image_session_id、60 分钟后过期的签名 source_image 和 target_image URL,以及一个 warnings 数组。每个警告包含 risk、log_type(information、warning 或 error)、short_description 和 long_description。无论是通过工作流构建器还是独立 API 调用,结构都相同。整个流程通常在 30 秒内完成, 拿起证件,拍下证件,拍下自拍,完成。这是市场上最快的速度。传统的 KYC 提供商完成相同流程通常需要超过 90 秒。
在后端,Didit 在 p99 指标下,两秒内返回结果,这个时间是从用户完成自拍到您的 Webhook 触发为止。移动端捕获针对慢速手机和慢速网络进行了优化:渐进式图像压缩、延迟加载软件开发工具包,以及如果用户从网页端开始,可通过二维码一键从桌面端切换到手机端。
LIVENESS 结合使用,确保源图像始终是经过验证的活体人类,而不是演示攻击。活体检测已通过 iBeta Level 1 演示攻击检测 (PAD) 认证,可有效防御打印照片、屏幕回放、面具、变形攻击和 AI 深度伪造。此外,人脸嵌入模型经过训练,对姿态、光照、发型、眼镜和正常范围内的老化具有鲁棒性, 因此即使证件照片已是多年前的,真实人脸仍能匹配成功。每个会话都会落入七种明确状态之一,因此您的代码始终知道如何处理:
Approved, 所有检查通过。让用户继续。Declined, 一项或多项检查失败。您可以允许用户重新提交特定的失败步骤(例如,重新自拍),而无需重新运行整个流程。In Review, 标记为合规审查。在控制台中打开案例,查看所有信号,决定批准或拒绝。In Progress, 用户正在进行中。Not Started, 链接已发送,用户尚未打开。如果长时间未打开,发送提醒。Abandoned, 用户打开了链接但未及时完成。重新激活或使其过期。Expired, 会话链接已过期。创建新会话。每次状态更改都会触发签名 Webhook,因此您的数据库始终保持同步。放弃和拒绝的会话是免费的。
生产数据默认在欧盟的亚马逊云服务(AWS)上处理和存储。企业客户可根据监管要求,申请在其他区域存储。
全面加密。 所有数据库、对象存储和备份均采用 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,以及西班牙财政部/SEPBLAC/CNMV的公开证明,表明 Didit 的远程身份验证比现场验证更安全。完整报告请访问 /security-compliance。
Didit 默认符合身份基础设施相关监管机构的合规要求:
详细备忘录、所有证书、所有监管机构函件:/security-compliance。
三种集成方式, 选择最适合您技术栈的:
所有三种方式均使用相同的控制面板、相同的计费方式和按成功次数付费的价格。分步指南请访问 docs.didit.me/integration/integration-prompt。