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

经验证的居住地信息来自任何支持性文件。

水电费账单、银行对账单、政府信函, 读取、解析、与ID交叉核对，并根据国家地址注册机构进行验证。每次检查 $0.20。每月免费500次验证。

免费开始阅读文档
投资方
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

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

一幅电影般的深色抽象地址证明插图, 四个漂浮的半透明玻璃面板在纯黑色背景上，由一条发光的Didit蓝色线条串联。每个面板都带有一个小的抽象图案（信封、水电费账单、地图图钉、房屋轮廓）。

受监管平台应尽的义务

不要相信手动输入的地址。读取账单，验证注册信息。

自行输入的地址无法通过审计。未与ID交叉核对的扫描水电费账单也无法通过审计。Didit 提供完整的地址证明方案, 捕获、OCR、姓名+地址与ID匹配，以及在18个以上司法管辖区的国家注册验证, 所有这些都作为一份签名的证据包，每次检查 $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。或者打开控制台，检查每个会话、每个信号，并按您的方式管理案例。

为合规而生 · 基础设施定价

六项检查。每份地址证明 $0.20。

监管级别的地址证明不仅仅是 OCR, 它是一个集捕获、解析、交叉核对、注册验证和审计包于一体的流程。您可以根据工作流切换每个模块。
阅读文档获取 API 密钥
01 · 文档捕获

接受任何支持性文件。

水电费账单、银行对账单、政府信函、租赁合同、抵押贷款、手机/互联网合同, 所有文件均需在 90 天内。托管流程引导用户完成捕获；SDK 在您的原生应用中提供相同的流程。
地址证明模块
02 · 解析 + 欺诈检查

解析字段。验证文档。

OCR 将地址提取到标准字段, 第一行、第二行、城市、邮政编码、国家、签发日期, 并对英文水电费账单、西班牙银行对账单、德国 Anmeldung 进行标准化处理。同时，我们检查真实性：像素级篡改、复制粘贴痕迹、字体/模板篡改、低分辨率重印和 EXIF 不一致。伪造或篡改的文档在进入您的审计日志之前就会被检查出来。
地址证明模块
03 · 身份交叉核对

与基础身份证明进行匹配。

解析后的地址会与基础身份证明上的地址进行交叉核对，证明上的姓名会与身份证明上的姓名进行交叉核对。这可以发现伪造的账单、姓名不匹配、过期上传以及同一地址下属于他人的账单。
身份验证模块
04 · 注册验证

根据国家权威来源进行验证。

在支持的国家/地区, 英国皇家邮政 PAF、西班牙 Catastro / Padrón、法国 BAN、德国市政 Anmeldung、美国 USPS 等, 解析后的地址会直接与权威注册机构进行查询。
数据库验证模块
05 · 全球覆盖

220 多个国家，48 种以上语言。

各地区可接受的文档有所不同, 欧洲倾向于水电费/银行/市政信函，拉丁美洲倾向于税务登记，美国倾向于银行/水电费/租赁合同，亚太地区倾向于政府信函。工作流构建器允许您根据国家/地区细分限制可接受的文档。
数据库验证模块
06 · 审计包

监管级别的审计包。

每份地址证明的裁决都经过签名和时间戳, 包括原始文档图像、解析后的地址负载、交叉核对结果和注册验证结果。可通过业务控制台或 API 按需导出。默认使用欧盟数据中心。
合规设计
集成

一次会话。标准地址。签名包。

打开会话。读取解析后的地址。归档监管级别的审计包。
POST /v3/session/POA
$ 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_proof_of_address",
    "vendor_data": "user-42",
    "expected_country": "ES"
  }'
201已创建托管 URL · 用户上传身份证 + 自拍 + 地址证明。
文件日期必须在 90 天内。文档 →
GET /v3/session/{id}/decision/决策
$ curl https://verification.didit.me/v3/session/$SESSION/decision/ \
  -H "x-api-key: $DIDIT_API_KEY"

# Decision payload (excerpted):
{ "proof_of_address": { "status": "Approved", "address": { ... } },
  "database_validation": { "service": "es_catastro_address", "result": { "registry_match": true } } }
200OKregistry_match 为 true → 高置信度地址证明。
保留规范地址信封。文档 →
代理就绪集成

一键部署地址证明。

粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent。填写您的技术栈。Agent 将构建工作流、启动会话、将地址解析为规范字段、运行注册验证并连接 Webhook。
didit-integration-prompt.md
You are integrating Didit's Proof of Address into a regulated onboarding flow (bank, fintech, lender, crypto exchange, EU payment institution). Regulators want a current address on every customer file; the legacy "ask the user to type it" approach fails audit because the typed address is unverified.

Four obligations on every Proof of Address:

  1. Capture an acceptable document — utility bill, bank statement, government letter, lease, mortgage, mobile / internet contract — dated within the last 90 days.
  2. Read the address fields with Optical Character Recognition (OCR) and parse them into the canonical address envelope (line 1, line 2, city, postal code, country).
  3. Cross-check the address against the address on the underlying ID document AND against the name on both — a mismatched address or a mismatched name fails the check.
  4. Where the country supports it, validate the parsed address against the authoritative address registry (UK Royal Mail PAF, Spain Catastro / Padrón, France BAN, Germany DATEV, US USPS).

Pricing (verified live):
  - Proof of Address: $0.20 per check
  - ID Verification (required as the cross-check anchor): $0.15 per check
  - Database Validation (per-country registry validation, optional): variable per service
  - Combined bundle (ID + Liveness + Face Match + Proof of Address): $0.55 per user
  - 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 HMAC SHA-256 verification using the X-Signature-V2 header and your webhook secret.
  - A workflow_id from the Workflow Builder bundling ID Verification + Passive Liveness + Face Match 1:1 + Proof of Address. Add a Database Validation node for the country-specific address registry where available.

STEP 1 — Create the session

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<your proof-of-address workflow id>",
      "vendor_data": "<your user id, max 256 chars>",
      "callback_url": "https://<your-app>/onboarding/poa/callback",
      "expected_country": "ES",
      "metadata": {
        "purpose": "regulatory_address_capture",
        "user_id": "<your internal id>"
      }
    }

  Response: 201 Created with the hosted session URL. SMS or email the URL to the user; they complete ID capture + selfie + Proof of Address upload on their phone in under five minutes.

STEP 2 — Read the signed webhook on completion

  Didit POSTs to your callback. Session statuses are Title Case With Spaces:

  Body (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your user id>",
      "status": "Approved",
      "id_verification": { "status": "Approved", "document_type": "passport", "country_code": "ES" },
      "liveness": { "status": "Approved" },
      "face": { "status": "Approved", "similarity_score": 0.94 },
      "proof_of_address": {
        "status": "Approved",
        "document_type": "utility_bill",
        "issuer": "Iberdrola",
        "issued_at": "2026-04-12",
        "address": {
          "line1": "C. Diagonal 612",
          "line2": "3a",
          "city": "Barcelona",
          "postal_code": "08021",
          "country": "ES"
        },
        "cross_check": {
          "name_match": true,
          "address_match_with_id": true,
          "within_90_day_window": true
        }
      },
      "database_validation": {
        "status": "Approved",
        "service": "es_catastro_address",
        "result": { "registry_match": true }
      }
    }

  Session 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 bytes with your webhook secret.

STEP 3 — Decide

  Branch logic:
    Approved    → file the canonical address payload on the customer record.
    In Review   → hold the onboarding, wait for analyst webhook update.
    Declined    → refuse onboarding, log the decline reason (typically: document over 90 days old, name mismatch, address mismatch with the ID).
    Resubmitted → user updated the upload; re-read the decision.

  The Proof of Address sub-result is independent of the parent session — even if the parent session is Approved, the proof_of_address.status might be In Review if the cross-check flagged a different city. Switch on proof_of_address.status when you persist the address.

STEP 4 — Persist the canonical address envelope

  When proof_of_address.status === "Approved", save the entire address object to your customer record as the regulatory current address. Use the canonical fields (line1, line2, city, postal_code, country) — Didit normalises across document layouts so the same shape works for an English utility bill, a Spanish bank statement, and a German Anmeldung.

  Keep the issuer + issued_at fields for your audit log — they prove the document type and the recency window the regulator audited.

STEP 5 — Registry validation result

  When the workflow includes a Database Validation node, the database_validation block returns the per-country registry-validation outcome:
    - es_catastro_address — Spanish Catastro property registry
    - uk_royal_mail_paf — UK Postcode Address File
    - fr_ban — France Base Adresse Nationale
    - de_anmeldung — German municipal registration check
    - us_usps — US Postal Service address validation

  A registry-match-false result on a country that supports validation is a signal worth manual review even if the OCR pass succeeded — most fake addresses fail registry validation immediately.

STEP 6 — Refresh on a cadence (optional)

  Most regulators ask for the address on file to be re-confirmed every 1-3 years (longer for low-risk customers, shorter for high-risk). Add a periodic Proof of Address session to your account-refresh cadence — same workflow, same hosted URL flow.

WEBHOOK EVENT NAMES
  - status.updated — session status changed.
  - data.updated — session data changed (resubmission, document re-upload).

  Verify X-Signature-V2 on every payload. The webhook secret is per-environment — sandbox key is separate from production.

CONSTRAINTS
  - Session statuses use Title Case With Spaces (Approved, In Review).
  - Acceptable documents must be dated within the last 90 days by default; some workflows extend to 180 days for low-risk customer segments.
  - The address on the Proof of Address document MUST cross-check against the address on the underlying ID OR against a previously-Approved address on file. If neither match, the proof flips to In Review automatically.
  - Default record retention is 5 years post-relationship per the EU AML package.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/sessions-api/retrieve-session
  - https://docs.didit.me/core-technology/proof-of-address/overview
  - https://docs.didit.me/core-technology/database-validation/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.
需要更多上下文？请参阅完整的模块文档。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.00
    每份地址证明, OCR + 交叉核对 + 注册验证。
  • 0+
    内置权威地址注册验证的国家/地区。
  • 0+
    支持的国家/地区总数，包含各地区可接受的文档。
  • 0
    每个账户每月免费验证。
三个层级，一份价目表

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

每月 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's a Proof of Address and why do regulators want one?

Proof of Address is exactly what it sounds like, evidence that the person you're onboarding actually lives at the address they claim. The conventional artefacts are:

  • Utility bill, electricity, gas, water, internet, mobile contract
  • Bank statement, from a regulated bank, with the user's name and address on it
  • Government letter, tax demand, council letter, voter registration
  • Lease or mortgage agreement, signed contract for the address

Why regulators care: an address on file is the anchor for anti-money-laundering record-keeping, tax-residency reporting (FATCA / CRS), and the legal jurisdiction of any future enforcement. A typed self-attested address is unverifiable; a Proof of Address backed by a recent document + a cross-check against the ID is the standard. Didit ships the full recipe for $0.20 per check.

Why isn't a typed address enough?

Three reasons regulators consistently reject self-attested addresses:

  • Fraud, anyone can type any address. Mules and synthetic identities use this routinely to spread the same address across many opened accounts.
  • No audit anchor, when the regulator audits the file, there's nothing to point to. A signed Proof of Address is the artefact you can put in the audit pack.
  • Tax-residency reporting, under FATCA and the OECD's Common Reporting Standard, banks have to report account-holders' tax residency based on documentary evidence. A typed address doesn't qualify as documentary.

The Proof of Address recipe, capture, OCR, cross-check, registry validation, produces a regulator-grade artefact in under five minutes on the user's phone. $0.20 per check end-to-end.

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's wrong with just asking for a utility bill?

If you stop at "upload your utility bill", a determined attacker can:

  • Photoshop the address on a bill belonging to someone else
  • Reuse a bill from a previous tenant at the same address
  • Submit a bill from a different person at the same address
  • Submit an expired bill (from before they moved)

The Didit recipe catches all four by stacking three layers of validation on top of the OCR:

  • Name cross-check, the name on the bill has to match the name on the ID
  • Address cross-check, the address on the bill has to match the address on the ID (or the previous Approved address)
  • Registry validation, the address is looked up against the country's authoritative address registry (UK Royal Mail PAF, Spain Catastro, France BAN, Germany DATEV, US USPS, etc.)

All three run server-side. The agent never sees a raw upload, only the validated result.

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.

How does the 90-day window work?

Most regulators want the Proof of Address document to be dated within the last 90 days at the moment of verification, anything older is treated as stale on the assumption that the user might have moved since.

Didit's OCR reads the document date and checks it against the verification timestamp automatically:

  • Within 90 days → within_90_day_window: true → proof passes the recency check
  • Older than 90 days → within_90_day_window: false → session flips to In Review and the user is prompted to upload a more recent document

For low-risk customer segments you can configure the workflow to extend the window to 180 days, or drop it to 60 days for high-risk segments. The configuration is per workflow, not per session, so changes apply uniformly. UK Right to Rent uses 90 days; EU AML guidance generally accepts 90-180 days depending on the supervisor.

How does refresh work for long-tenured customers?

Most regulators ask for the address on file to be re-confirmed periodically:

  • Low-risk customers, every 3 years is typical
  • Standard customers, every 1-2 years
  • High-risk / EU-PEP customers, annually
  • On material event, significant transaction pattern change, address change reported by the customer, new product onboarded

Didit's refresh is the same POST /v3/session/ against your Proof-of-Address workflow with the existing customer's vendor_data. The new document supersedes the previous one in the customer file; both are kept in the audit trail. Schedule the refresh from your customer-data pipeline, Didit doesn't auto-trigger refreshes because the cadence belongs to your risk policy.

How does Didit compare on price?

Most KYC providers price Proof of Address between $0.50 and $2.00 per check, often as a separate line item on top of a higher KYC base, with per-country surcharges for any registry validation. The Onfido / Jumio / Veriff archetype.

Didit's published price is $0.20 per Proof of Address + $0.15 for the underlying ID Verification (required as the cross-check anchor) = $0.35 for the combined recipe. Database Validation adds variable per-country cost, typically $0.05-$0.20. No floor, no minimum, no per-country surcharge.

That's roughly 3-5× cheaper than the incumbent stack on the same regulatory output. At a 50,000-user month, the saving versus a $1.50-per-POA incumbent is around $65,000 per year. Full pricing at /pricing.

Related

相关模块 + 工作流

身份与欺诈基础设施。

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

免费开始联系我们
让 AI 总结此页面