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


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

账单 + 银行对账单
我们读取文件,提取地址和姓名,并与已验证的身份进行交叉核对。 水电费账单、银行对账单、租赁协议、税务信函, 每次检查 $0.20。
选择您需要的检查项, 身份、活体检测、人脸匹配、制裁名单、地址、年龄、电话、电子邮件、自定义问题。在仪表板中将它们拖入工作流,或通过我们的 API 发布相同的工作流。根据条件进行分支,运行 A/B 测试,无需代码。
使用我们的 Web、iOS、Android、React Native 或 Flutter SDK 进行原生嵌入。重定向到托管页面。或者直接通过电子邮件、短信、WhatsApp 等任何方式向您的用户发送链接。选择适合您技术栈的方式。
Didit 托管摄像头、灯光提示、移动设备切换和辅助功能。在用户进行流程时,我们实时评估 200 多个欺诈信号,并根据权威数据源验证每个字段。两秒内即可获得结果。
实时签名 Webhook 可确保用户批准、拒绝或发送审核时,您的数据库立即同步。按需轮询 API。或者打开控制台检查每个会话、每个信号,并按您的方式管理案例。
document_type 枚举 · 4个类别
存储桶
文件格式
每次上传
页面支持
OCR · 司法鉴定
真实性信号
issue_date · 可配置 · 默认90天
对比已验证的 KYC 主体
结构化响应 · 各国形状相同
AMLD6 · FATF 建议10 · 审计就绪
$ 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_poa_eu",
"vendor_data": "user-42"
}'{ "session_url": "verify.didit.me/..." }$ curl -X POST https://verification.didit.me/v3/poa/ \
-H "x-api-key: $DIDIT_API_KEY" \
-F "document=@utility-bill.pdf" \
-F "full_name=John A. Smith"{ "status": "已批准", "document_type": "BANK_STATEMENT" }# Didit Proof of Address — integrate in 5 minutes
You are integrating Didit's Proof of Address (PoA) 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 document capture, multi-page upload,
auto-capture, mobile handoff, and accessibility for you.
1. Create a workflow that contains the PROOF_OF_ADDRESS feature:
POST https://verification.didit.me/v3/workflows/
Authorization header: x-api-key: <your-api-key>
Body: workflow_label, features array with the single entry
{ feature: "PROOF_OF_ADDRESS" } (UPPERCASE — strict enum)
Optional config: accepted document_type filters
(UTILITY_BILL, BANK_STATEMENT, GOVERNMENT_ISSUED_DOCUMENT,
OTHER_POA_DOCUMENT) and per-warning threshold overrides.
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 a captured document image or PDF (mobile SDK
capture, native onboarding app, reseller pipeline).
POST https://verification.didit.me/v3/poa/
Content-Type: multipart/form-data
Body fields:
- document (required, file — JPG, JPEG, PNG, TIFF, or PDF, <= 15 MB)
- vendor_data (optional string, your user id)
- full_name (optional string, name to cross-check against the document)
- address (optional string, address to cross-check against the document)
Response: JSON report with the parsed address, document_type, issuer,
issue_date, name_on_document, and a warnings array.
## 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 poa object includes:
- status: "Approved" | "Declined" | "In Review" | "Not Finished"
- issuing_state: ISO 3166-1 alpha-3 country code
- document_type: "UTILITY_BILL" | "BANK_STATEMENT" |
"GOVERNMENT_ISSUED_DOCUMENT" | "OTHER_POA_DOCUMENT" |
"UNKNOWN"
- issuer: string (the issuing institution or company)
- issue_date: YYYY-MM-DD
- expiration_date: YYYY-MM-DD or null
- document_language: ISO 639-1 language code
- name_on_document: string (full name extracted from the document)
- poa_address: raw extracted address string
- poa_formatted_address: normalized human-readable address string
- poa_parsed_address: structured object with street_1, street_2, city,
region, postal_code, address_type, and raw_results.geometry.location
(lat / lng for geocoding)
- document_file: signed URL to the captured document (expires in 60 minutes)
- document_metadata: optional file_size, content_type, creation_date,
modified_date, and overlay_manipulation forensic block for PDFs (detected
flag, signals such as duplicate_font_subset or glyph_fragmentation, and
manipulated_regions in PDF page coordinates)
- warnings: Array<{ risk, additional_data, log_type, short_description,
long_description }>
Auto-decline risks (always enforced by Didit, not configurable):
- POA_DOCUMENT_NOT_SUPPORTED_FOR_APPLICATION
- EXPIRED_DOCUMENT
- INVALID_DOCUMENT_TYPE
- MISSING_ADDRESS_INFORMATION
Configurable risks (action per workflow — Decline, Review, or Approve):
- NAME_MISMATCH_WITH_PROVIDED
- NAME_MISMATCH_ID_VERIFICATION
- POA_NAME_MISMATCH_BETWEEN_DOCUMENTS
- POOR_DOCUMENT_QUALITY
- DOCUMENT_METADATA_MISMATCH
- SUSPECTED_DOCUMENT_MANIPULATION
- UNSUPPORTED_DOCUMENT_LANGUAGE
- ADDRESS_MISMATCH_WITH_PROVIDED
- UNABLE_TO_EXTRACT_ISSUE_DATE
- UNPARSABLE_OR_INVALID_ADDRESS
- ISSUER_NOT_IDENTIFIED
- UNABLE_TO_VALIDATE_DOCUMENT_AGE
- FUTURE_ISSUE_DATE
## 5. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: PROOF_OF_ADDRESS, ID_VERIFICATION, LIVENESS,
FACE_MATCH, AML, IP_ANALYSIS.
- document_type enum is UPPERCASE_SNAKE: UTILITY_BILL, BANK_STATEMENT,
GOVERNMENT_ISSUED_DOCUMENT, OTHER_POA_DOCUMENT, UNKNOWN.
- 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).
- Documents must be issued within 90 days of submission — older documents
trigger the EXPIRED_DOCUMENT auto-decline regardless of policy.
- The PoA document must be different from the document submitted for ID
Verification — same image triggers POA_DOCUMENT_NOT_SUPPORTED.
## 6. Accepted document types (do not paraphrase to users)
- Utility Bill — Electricity, Water, Gas, Internet, Phone, Cable TV,
Satellite TV, Trash Collection, Sewage, Heating, Combined Utilities,
Municipal Services.
- Bank Statement — Account Statement, Credit Card Statement, Bank Letter
Confirming Address, Mortgage Statement, Loan Statement, Savings,
Checking, Investment, Business Account, Credit Union, Debit Card,
Line of Credit.
- Government-Issued Document — Tax Assessment, Voter Registration Card,
ID document, Residency Certificate, Government Letter, Census Letter,
Property Tax Bill, Vehicle Registration, Social Security Statement,
Unemployment Benefits Letter, Pension Statement, Court Summons,
Municipal Permit, Immigration Document.
- Other Proof of Address — Lease Agreement, Rental Agreement, Employer
Letter Confirming Address, Insurance Policy, School Enrollment Letter,
Notarized Affidavit, Solicitor Letter, Payroll Stub, Employment
Verification Letter, Retirement / Brokerage Account Statement.
Image requirements: JPG, JPEG, PNG, TIFF, or PDF. Maximum file size 15 MB.
Full-color, all corners visible, no digital editing, all pages included
for multi-page documents.
## 7. Pricing reference (public)
- Standalone /v3/poa/ call: $0.20 per check.
- Bundled inside a Didit workflow (KYC plus PoA): $0.20 per check on top
of the bundle base.
- 500 free verifications every month, forever, on every account.
## 8. Verify your integration
- Sandbox starts on signup at https://business.didit.me — no separate flag.
- Test documents: deterministic synthetic bills returned in sandbox
(Approved by default; trigger Declined by submitting the canonical
"expired" test bill from the sandbox sample pack).
- Switch to live: flip the application's environment toggle in console.
When in doubt: https://docs.didit.me/core-technology/proof-of-address/overview
每月 $0。无需信用卡。
按实际用量付费。25+模块。公开的模块定价,无每月最低费用。
定制MSA和SLA。适用于大批量和受监管项目。
免费开始 → 仅在检查运行时付费 → 解锁企业版以获取定制合约、SLA 或数据驻留。
Didit 是身份和欺诈基础设施, 一个我们自己在构建产品时就希望存在的平台:开放、灵活、对开发者友好,因此它可以真正融入您的技术栈,而不是一个需要您围绕其进行集成的黑盒。
一个 API 即可覆盖人员验证(KYC,了解您的客户)、企业验证(KYB,了解您的业务)、加密钱包筛选(KYT,了解您的交易)以及实时交易监控, 所有这些都建立在以下技术栈之上:
其底层支持:14,000 多种文档类型,支持48 种以上语言,1,000 多个数据源,以及每次会话的200 多个欺诈信号。Didit 基础设施从每次会话中动态学习,并日益完善。
地址证明 (PoA) 是通过水电费账单、银行对账单、政府信函或租赁协议来验证个人居住地址的服务, 捕获、光学字符识别 (OCR) 提取、验证,并在几秒钟内以结构化地址的形式返回。
Didit 处理文档捕获,解析签发机构和签发日期,运行篡改检测取证,将姓名与已验证的身份文档进行交叉核对,将地址标准化为结构化字段(street_1、city、region、postal_code),并进行地理编码。
每次检查 $0.20。 完整参考:docs.didit.me/core-technology/proof-of-address。
每次独立的 POST /v3/poa/ 调用费用为 $0.20,或者当捆绑到 Didit 工作流中时,在基础捆绑包之上额外收取 $0.20。
无月度最低消费,无合同,无意外超额费用, didit.me/pricing 上的价格即为发票价格。随着业务增长,批量折扣会自动生效。
整个流程通常在 30 秒内完成, 拿起身份证,拍摄文档,拍摄自拍,完成。这是市场上最快的速度。传统的 KYC 提供商完成相同流程通常需要90 秒以上。
在后端,Didit 在 p99 情况下两秒内返回结果,从用户完成自拍到您的 webhook 触发。移动端捕获针对慢速手机和慢速网络进行了优化:渐进式图像压缩、延迟加载软件开发工具包 (SDK),以及如果用户从网页端开始,通过二维码实现从桌面到手机的一键切换。
会话报告和独立应用程序编程接口 (API) 上会有一个单独的 poa JavaScript 对象表示法 (JSON) 对象:
status, Approved(已批准)、Declined(已拒绝)、In Review(审核中)、Not Finished(未完成)。document_type(文档类型)、issuer(签发机构)、issue_date(签发日期,YYYY-MM-DD)、expiration_date(有效期)、document_language(文档语言)。name_on_document(文档上的姓名)、poa_address(原始光学字符识别 (OCR) 字符串)、poa_formatted_address(标准化地址)。poa_parsed_address, 结构化的 street_1(街道 1)、street_2(街道 2)、city(城市)、region(地区)、postal_code(邮政编码)、address_type(地址类型),以及用于地理编码的 raw_results 几何坐标。document_file 统一资源定位符 (URL),60 分钟后过期。可移植文档格式 (PDF) 提交还包括一个 document_metadata.overlay_manipulation 取证块。完整参考:docs.didit.me/core-technology/proof-of-address/report-proof-of-address。
每个会话都会落入七种明确状态之一,因此您的代码始终知道如何处理:
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。