Skip to main content
Didit 融资 750 万美元,打造身份与欺诈基础设施
Didit
地址证明

验证任意地址
来自账单、银行或信函。

通过水电费账单、银行对账单、政府信函或租赁协议验证居住地。我们读取文件,提取地址,将姓名与已验证的身份匹配,并返回结构化结果。每次检查 $0.20,每月免费 500 次。

投资方
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

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

Didit 地址证明, 上传水电费账单或对账单;我们进行服务器端 OCR。

账单 + 银行对账单

提取地址。
匹配姓名。

我们读取文件,提取地址和姓名,并与已验证的身份进行交叉核对。 水电费账单、银行对账单、租赁协议、税务信函, 每次检查 $0.20。

工作原理

从注册到验证用户,仅需四步。

  1. 步骤 01

    创建工作流

    选择您需要的检查项, 身份、活体检测、人脸匹配、制裁名单、地址、年龄、电话、电子邮件、自定义问题。在仪表板中将它们拖入工作流,或通过我们的 API 发布相同的工作流。根据条件进行分支,运行 A/B 测试,无需代码。

  2. 步骤 02

    集成

    使用我们的 Web、iOS、Android、React Native 或 Flutter SDK 进行原生嵌入。重定向到托管页面。或者直接通过电子邮件、短信、WhatsApp 等任何方式向您的用户发送链接。选择适合您技术栈的方式。

  3. 步骤 03

    用户完成流程

    Didit 托管摄像头、灯光提示、移动设备切换和辅助功能。在用户进行流程时,我们实时评估 200 多个欺诈信号,并根据权威数据源验证每个字段。两秒内即可获得结果。

  4. 步骤 04

    您收到结果

    实时签名 Webhook 可确保用户批准、拒绝或发送审核时,您的数据库立即同步。按需轮询 API。或者打开控制台检查每个会话、每个信号,并按您的方式管理案例。

专为开发者打造 · 专为防欺诈设计 · 开放式设计

六大功能。一个功能标志。PROOF_OF_ADDRESS

以下所有功能都是同一模块上的一个开关。没有升级层级,没有单独的 SKU,没有附加调用。您可以根据工作流开启它们,或在 API 调用中内联传递。
01 · 支持的文档

账单、银行对账单、政府信函、租赁合同。

四类文档:水电煤气网费账单、银行对账单(账户、信用卡、抵押贷款、借贷)、政府签发文件(纳税评估、选民证、居住证明)以及其他(租赁合同、雇主信函、保险、公证宣誓书)。支持 JPG、PNG、TIFF 或 PDF 格式,最大 15 MB。多页文档一次性处理。
02 · 提取与真实性

读取所有地址字段。识别所有伪造。

OCR(光学字符识别)提取原始地址并将其标准化为结构化对象, 街道、城市、地区、邮政编码、地址类型。包含经纬度。同时进行文档真实性鉴定:像素级篡改检测、复制粘贴/克隆图章残留、字体和字距不一致、AI 生成合成图像信号以及元数据不匹配。篡改文档将进入 `In Review` 状态并附带警告,而非静默批准。
03 · 时效性检查

可配置有效期。默认 90 天。

可为每个应用程序设置文档有效期, 30、60、90 天或您选择的任何期限。默认值为 90 天。我们提取签发日期并与提交时间戳进行比较;任何超过阈值的文档将自动拒绝并显示 `EXPIRED_DOCUMENT`。无法解析签发日期或签发日期在未来的文档将触发警告,您可以将其路由到人工审核。
04 · 与 KYC 姓名匹配

账单与身份信息匹配。或不匹配。

当文档姓名与已验证身份、您通过 API 发送的值或同一会话中的其他地址证明不符时,将触发三个姓名不匹配警告。可配置的匹配阈值(通常为 90-95%)可容忍中间名和拼写差异。每个警告可根据应用程序映射到拒绝、审核或批准。
05 · 解析结构化地址

OCR 返回字符串。Didit 返回结构化数据。

每个响应都包含一个解析后的地址对象, 街道、城市、地区、邮政编码、地址类型, 以及原始坐标。将其放入您的客户记录、欺诈模型或配送路由中。无需正则表达式、无需后处理、无需针对每个国家的解析器。无论文档是在美国、西班牙、巴西还是新加坡签发,格式都相同。
06 · 合规就绪

AMLD6 和 FATF 建议 10 证据。每次检查 $0.20。

地址验证是 AMLD6(欧盟第六项反洗钱指令)客户尽职调查和 FATF 建议 10 的强制要求。每份裁决都附带签名的文档 URL、可供审计的警告数组以及 PDF 叠加操作取证, 您的合规官可随时获取证据包。按次付费定价,无合同。
集成

两个端点。相同的 JSON。相同的价格。

当您希望我们的托管 UI 处理捕获和多页上传时,请创建会话。当您已拥有文档时,请调用独立端点。两种方式的报告格式相同。
POST /v3/session/托管 UI
$ 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"
  }'
201已创建{ "session_url": "verify.didit.me/..." }
我们托管捕获 UI。多页 PDF + 自动捕获为您处理。文档 →
POST /v3/poa/服务器到服务器
$ 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"
200OK{ "status": "已批准", "document_type": "BANK_STATEMENT" }
您拥有捕获数据。我们将完整报告直接返回。文档 →
代理就绪集成

一键部署地址证明。

将以下代码块粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent 中。用您的框架、语言和用例填充 my_stack 占位符。代理将配置 Didit,创建工作流,连接 webhook,并完成部署。
didit-integration-prompt.md
# 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
需要更多上下文?请参阅完整的模块文档。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
    文件类型:水电费账单、银行对账单、政府文件等。
  • 0d
    自动拒绝前的最长签发日期。
  • <0s
    每次地址证明验证的端到端推理时间。
  • $0.00
    每次独立的地址证明检查。
三个层级,一份价目表

免费开始。按使用量付费。可扩展至企业级。

每月 500 次免费验证,永久有效。生产环境按量付费。企业版提供定制合约、数据驻留和 SLA (Service Level Agreements)。
免费

免费

每月 $0。无需信用卡。

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

按用量计费

按实际用量付费。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 is Proof of Address?

Proof of Address (PoA) is the verification of a person's residency using a utility bill, bank statement, government letter, or lease, captured, Optical Character Recognition (OCR)-extracted, validated, and returned as a structured address in seconds.

Didit handles the document capture, parses the issuer and issue date, runs tamper-detection forensics, cross-checks the name against the verified Identity Document, normalizes the address into structured fields (street_1, city, region, postal_code), and geocodes it.

$0.20 per check. Full reference: docs.didit.me/core-technology/proof-of-address.

What does Proof of Address cost?

$0.20 per standalone POST /v3/poa/ call, or $0.20 when bundled into a Didit workflow on top of the underlying bundle base.

No monthly minimum, no contract, no overage surprises, the price on didit.me/pricing is the price on the invoice. Volume discounts kick in automatically as you grow.

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.

What is the response shape?

A single poa JavaScript Object Notation (JSON) object on the session report and on the standalone Application Programming Interface (API):

  • status, Approved, Declined, In Review, Not Finished.
  • document_type, issuer, issue_date (YYYY-MM-DD), expiration_date, document_language.
  • name_on_document, poa_address (raw Optical Character Recognition (OCR) string), poa_formatted_address (normalized).
  • poa_parsed_address, structured street_1, street_2, city, region, postal_code, address_type, with raw_results geometry coordinates for geocoding.
  • Signed document_file Uniform Resource Locator (URL) that expires in 60 minutes.

Portable Document Format (PDF) submissions also include a document_metadata.overlay_manipulation forensic block. Full reference: docs.didit.me/core-technology/proof-of-address/report-proof-of-address.

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.

身份与欺诈基础设施。

一个 API 即可实现 KYC、KYB、交易监控和钱包筛选。5 分钟即可集成。

让 AI 总结此页面