Skip to main content
Didit 融资 750 万美元，打造身份与欺诈基础设施
Didit
一次验证，重复使用身份

一次验证。永久复用。相同品牌。信任伙伴。相同身份。

首次验证 $0.33，每次返回免费自拍重新认证，通过短期加密令牌进行跨合作伙伴共享。每月免费 500 次验证。

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

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

一张电影风格的深色抽象可复用身份凭证插画, 四个半透明玻璃面板以3D透视效果浮在纯黑色背景上，由一条发光的Didit蓝色线条串联，并由四个发光扫描支架框住。每个面板上都有一个微小的浅白色抽象图案，代表可复用身份（分层凭证卡、循环复用箭头、链条图标、钥匙轮廓）。

身份验证的未来

用户只需验证一次。无需重复验证。

一旦用户通过Didit验证, iBeta一级防欺诈、2秒内出结果、支持14,000多种证件, 该验证结果即可复用。同一品牌，不同应用：免费自拍即可重新认证。信任伙伴，新用户注册：通过短期加密共享令牌即时完成入驻。用户拥有凭证，符合eIDAS2标准。

工作原理

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

  1. 步骤 01

    创建工作流

    选择您需要的验证项, 身份、活体、人脸比对、制裁名单、地址、年龄、电话、邮箱、自定义问题。在控制面板中拖拽构建流程，或通过API发布相同流程。支持条件分支、A/B测试，无需代码。

  2. 步骤 02

    集成

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

  3. 步骤 03

    用户完成流程

    Didit负责托管摄像头、灯光提示、移动端切换和无障碍功能。在用户进行流程时，我们实时评估200多项欺诈信号，并根据权威数据源验证每个字段。两秒内即可出结果。

  4. 步骤 04

    接收结果

    实时签名webhook确保用户通过、拒绝或送审的瞬间，您的数据库同步更新。可按需轮询API。或打开控制台检查每个会话、每个信号，并按您的方式管理案例。

为复用而生 · 基础设施定价

一次验证。多次入驻。

可复用身份并非单一功能，而是两项：同平台可复用KYC（免费）和跨伙伴共享会话API。您可以选择使用其中一项或两项。
阅读文档获取API密钥
01 · 用户拥有凭证

用户拥有并重新呈现。

首次验证结果存储在Didit内部，静态加密。用户通过自拍重新认证或同意共享，即可在每个由Didit提供服务的平台（同一品牌或信任伙伴）重新出示凭证。
可复用KYC模块
02 · 跨伙伴共享

可信伙伴间的令牌交换。

伙伴A通过 `POST /v3/session/[id]/share/` 生成短期共享令牌。伙伴B通过 `POST /v3/session/import-shared/` 导入。端到端加密，仅限指定受众，每个伙伴仅可导入一次。
共享会话文档
03 · 信任策略

每个伙伴的信任审查。

伙伴B选择：信任伙伴A的验证结果（即时入驻）或复制数据并转入人工审核（受监管的升级路径）。可在业务控制台按工作流配置。
工作流编排器
04 · 仅自拍返回

回访用户 · 仅自拍 · 免费。

可复用KYC工作流运行无证件重新认证, 用户开启会话，自拍，Didit与已验证模板重新匹配，两秒内返回“已批准”。免费，无需重新采集证件。
人脸比对1:1模块
05 · 隐私与同意

同意 · 范围 · 保留 · 每次共享。

每次共享都会记录用户的同意、目的、受众、范围和有效期。Didit记录所有信息, 符合GDPR (General Data Protection Regulation)、ISO/IEC 27001、SOC 2 Type 1。默认保留5年。
身份隐私声明
06 · 网络

Didit 生态系统中的统一身份。

可复用身份适用于所有由Didit提供支持的平台, 金融科技、加密货币、市场、iGaming、先买后付、医疗保健、出行。相同的 `/v3/` 契约，相同的工作流构建器，符合eIDAS2标准。
生物识别认证
集成

首次一次会话。返回时自拍或共享。

一次验证用户。通过可复用KYC或共享会话API复用凭证。
POST /v3/session/{sessionId}/share/共享
$ curl -X POST https://verification.didit.me/v3/session/$SID/share/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "audience": "partner_b",
    "expires_in": 900
  }'
201已创建返回 share_token + expires_at · 默认 15 分钟。
将令牌带外传输给伙伴 B。每个伙伴一次导入。文档 →
POST /v3/session/import-shared/导入
$ curl -X POST https://verification.didit.me/v3/session/import-shared/ \
  -H "x-api-key: $PARTNER_B_KEY" \
  -d '{
    "share_token": "eyJhbGci…",
    "workflow_id": "partner_b_wf",
    "vendor_data": "user-on-partner-b",
    "trust_review": true
  }'
201已创建导入会话状态遵循 trust_review。
trust_review=true → 立即批准；false → 审核中。文档 →
代理就绪集成

一键部署可复用身份。

粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent 中。填写您的技术栈。代理将构建首次验证流程、可复用 KYC 重新认证流程以及跨伙伴共享 + 导入流程。
didit-integration-prompt.md
You are integrating Didit reusable identity. Your users get verified once with full KYC and then re-present that verification on every subsequent service — your own platforms (same-platform reuse via Reusable KYC) and trusted partner platforms (cross-partner Share Session API).

Three pillars:

  1. Verify once with full KYC ($0.33 bundle) via POST /v3/session/.
  2. On the SAME platform, returning users re-prove identity with a selfie only — free, via the Reusable KYC workflow.
  3. To a TRUSTED PARTNER, the first platform generates a short-lived share token (POST /v3/session/{id}/share/); the partner imports it (POST /v3/session/import-shared/) and the user lands fully onboarded.

Cost:
  - First verification: $0.33 (Sessions API)
  - Same-platform selfie-only reauth: free (Reusable KYC workflow)
  - Cross-partner import: priced per call, from $0.30 — Partner B pays the import fee
  - 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.
  - Two workflows in the Workflow Builder:
      wf_first_verification    — ID Verification + Passive Liveness + Face Match 1:1 + Device & IP Analysis + Anti-Money Laundering (AML) Screening
      wf_reusable_kyc          — Reusable KYC (selfie-only reauth)
  - For cross-partner: a pre-arranged backend channel with the partner (a webhook, a queue, or even an authenticated REST call between your services) so the share token can be transmitted out-of-band.

STEP 1 — First verification (Sessions API)

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<wf_first_verification>",
      "vendor_data": "<your user id, max 256 chars>",
      "callback": "https://<your-app>/identity/callback"
    }

  Response: 201 Created with the hosted session URL. Sub-2-second median verdict on completion.

STEP 2 — Read the signed webhook on verification 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" },
      "liveness": { "status": "Approved" },
      "face": { "status": "Approved", "similarity_score": 0.94 }
    }

  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.

  Store the (user_id, session_id, status) tuple. session_id is the handle you reuse for shares.

STEP 3 — Same-platform reuse (Reusable KYC selfie-only reauth)

  When the same user returns for a new flow:

  POST https://verification.didit.me/v3/session/
  Body:
    {
      "workflow_id": "<wf_reusable_kyc>",
      "vendor_data": "<your user id>",
      "callback": "https://<your-app>/identity/reauth-callback"
    }

  The hosted UI prompts the user for a selfie only — no document re-capture. Didit matches the selfie against the original verified template, returns Approved in under two seconds, free.

STEP 4 — Cross-partner share (Partner A generates a share token)

  Only finished sessions (Approved / Declined / In Review) can be shared.

  POST https://verification.didit.me/v3/session/{sessionId}/share/
  Headers:
    x-api-key: <Partner A's api key>
    Content-Type: application/json
  Body:
    {
      "audience": "<partner_b_identifier>",
      "expires_in": 900
    }

  Response (excerpted):
    {
      "share_token": "eyJhbGciOiJIUzI1NiJ9...",
      "session_kind": "kyc",
      "expires_at": "<ISO8601>"
    }

  Transmit the share_token to Partner B via your pre-arranged backend channel.

STEP 5 — Cross-partner import (Partner B imports the session)

  POST https://verification.didit.me/v3/session/import-shared/
  Headers:
    x-api-key: <Partner B's api key>
    Content-Type: application/json
  Body:
    {
      "share_token": "eyJhbGciOiJIUzI1NiJ9...",
      "workflow_id": "<Partner B's workflow id>",
      "vendor_data": "<Partner B's internal user id>",
      "trust_review": true
    }

  trust_review options:
    true  — Partner B trusts Partner A's verdict (Approved / Declined). The imported session keeps the original status.
    false — Partner B copies the data but sets status to "In Review" so Partner B's compliance team can apply their own thresholds.

  Constraints (verified against mintlify-docs/core-technology/reusable-kyc/share-kyc-via-api.mdx):
    - A specific session can be imported only ONCE into a given partner application.
    - The share_token is short-lived (defaults to 15 minutes).
    - End-to-end encrypted; only the named audience can import.

STEP 6 — Audit the consent + the share

  Log every share + every import with:
    - user_pid (the pseudonymous user identifier)
    - audience (which partner)
    - purpose (onboarding, lending, payments, etc.)
    - scope (kyc, kyc + aml, kyc + kyb)
    - share_token id + expiry
    - import status
  Default retention 5 years post-relationship per the EU AML package; longer under your supervisor's guidance.

WEBHOOK EVENT NAMES
  - Sessions: status changes flow through the standard session webhook.
  - Verify X-Signature-V2 on every payload.

CONSTRAINTS
  - Session statuses use Title Case With Spaces (Approved, In Review). Don't transform them.
  - Share tokens are scoped to the named audience and the named purpose — they're not bearer tokens for free reuse.
  - The user must consent before a share happens. Capture explicit consent in your UI; Didit logs the consent against the session.
  - Reusable KYC selfie-only reauth is free; cross-partner imports are priced at Partner B's account.
  - 200+ fraud signals are evaluated on every fresh session at no extra cost.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/sessions-api/share-session/share
  - https://docs.didit.me/sessions-api/share-session/import
  - https://docs.didit.me/core-technology/reusable-kyc/overview
  - https://docs.didit.me/core-technology/reusable-kyc/share-kyc-via-api
  - 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
    首次验证, 完整的 KYC 捆绑包。同平台回访免费。
  • Free
    可复用 KYC, 每次同品牌会话仅需自拍重新认证。
  • 0 min
    默认共享令牌有效期 · 加密、受众绑定、仅限一次导入。
  • 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 is reusable identity, in plain English?

It's an identity verification you do once, full document + face + AML, that the user can then re-present on every future service without redoing the document capture.

Two flavours:

  • Same brand · second app, the user signs up to your savings product, then to your trading product. Same Didit verification, free selfie-only reauth on the second app via Reusable KYC.
  • Trusted partner · fresh signup, the user is verified on Partner A and signs up to Partner B. Partner A mints a short-lived encrypted share token; Partner B imports it; the user lands fully onboarded with no re-capture.

The credential lives with the user, they consent to each reuse. The shape of the data they share is auditable, scoped, and time-bound.

Why does "verify once" matter? What does it actually change?

Three things drop:

  • Drop-off, every additional document re-capture loses 15-30% of conversions. Removing the friction recovers most of that.
  • Cost, the second verification is free instead of another $0.33. At any meaningful scale this becomes a line item your CFO notices.
  • Time-to-onboard, sub-2-second selfie reauth versus several minutes of re-capturing IDs from the start.

For the user, the benefit is just "I already did this". For the platform, it's higher activation, lower CAC (Cost of Acquisition), and a competitive moat against any flow that doesn't reuse.

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 eIDAS 2 and why does the page mention it?

eIDAS 2 (officially Regulation (EU) 2024/1183) is the EU's updated digital-identity regulation, it mandates that every EU citizen gets access to a European Digital Identity Wallet by late 2026.

The wallet's defining property is exactly what reusable identity delivers: the user holds verified credentials in a wallet they control, and re-presents them on demand to public and private services. Didit's reusable-identity recipe is aligned with eIDAS 2, same shape, same user-ownership principle, so platforms building on it today are also building toward the EU's official-wallet world.

Outside the EU, the same recipe still works. The legal anchor is local (UK FCA, US state lender rules, etc.); the technical shape is the same.

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.

What does the user have to consent to?

Two consent moments:

  • At first verification, standard KYC consent: data processed for verification + screening, retention, sub-processors, etc. (the privacy notice you ship today)
  • At reuse, for cross-partner shares, explicit consent before the share token is generated. Your UI shows: "You will be onboarded on Partner B using the identity you verified with Partner A. The shared data covers ID, face match, AML status. The share expires in 15 minutes."

Didit logs the consent against the session, purpose, audience, scope, expiry, and the log is exportable to your data-subject-access-request (DSAR) and audit tools. Default retention 5 years post-relationship per the EU Anti-Money-Laundering package. Aligned with the General Data Protection Regulation (GDPR), ISO/IEC 27001, and SOC 2 Type 1, all of which Didit holds.

What are the limits on a share token?

Three load-bearing limits:

  • Finished sessions only, a share token can only be generated for sessions with a terminal status (Approved, Declined, In Review). Pending sessions can't be shared.
  • One import per partner, a specific session can be imported only once into a given partner application. Subsequent imports are rejected. (If the partner needs to re-import, the user must verify fresh or Partner A must mint a new token.)
  • Short-lived + audience-bound, the token defaults to a 15-minute expiry and is only valid for the named audience. Stolen tokens can't be re-targeted at a different partner.

The token is signed and end-to-end encrypted. The only thing that travels between Partner A and Partner B is the opaque token; the underlying data fields stay inside Didit until Partner B's authenticated import call.

What does this cost, who pays for what?

Pricing breakdown:

  • First verification, $0.33 per user (Sessions API), paid by the verifier
  • Same-platform Reusable KYC reauth, free, included
  • Cross-partner import, Partner B pays the import fee, from `$0.30` per call, on Partner B's account
  • Workflow Builder + MCP server, free, included
  • 500 verifications free every month, forever, on every account

The model rewards reuse: the verifier pays once, the user re-uses many times on the same brand for free, and the only paid step at a partner is the import call, which is materially cheaper than the partner running fresh KYC themselves.

Related

相关模块 + 工作流

身份与欺诈基础设施。

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

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