Skip to main content
Didit 融资 750 万美元，打造身份与欺诈基础设施
Didit
无代码身份工作流

无需编写代码即可构建身份流程。无需重新部署即可更改规则。

拖放式 KYC、AML、KYB、生物识别升级。根据信号分支。A/B 测试。安全版本控制。仅为已完成的模块付费, 工作流构建器本身免费。

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

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

一幅电影般的深色抽象无代码可视化工作流构建器插图, 四块浮动的半透明玻璃面板以 3D 透视方式呈现在纯黑色背景上，由一条发光的 Didit 蓝色线条串联，并由四个发光的扫描支架框住。每个面板都带有一个微小的浅白色抽象图案，代表工作流画布（节点和边缘图片段、拖动手柄、分支分叉、画布网格）。

产品负责人应尽的职责

规则每周都在变。您的应用不应如此。

将模块拖放到画布上，用边连接，添加分支，发布版本，然后将 workflow_id 传递给您的应用。当规则变更时，产品经理只需编辑草稿并发布即可, 无需工程工单，无需重新部署。集成始终只需一个 `POST /v3/session/` 调用。

工作原理

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

  1. 步骤 01

    创建工作流

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

  2. 步骤 02

    集成

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

  3. 步骤 03

    用户完成流程

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

  4. 步骤 04

    接收结果

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

专为产品负责人打造 · 基础设施级定价

六个基本元素。工作流构建器免费。

只为您每个会话实际运行的模块付费。画布、分支、模板、A/B 测试、版本控制, 全部包含在内。
阅读文档获取 API 密钥
01 · 拖放式画布

每个 Didit 模块都是一个节点。

将 ID、活体检测、人脸比对、人脸搜索、设备 + IP、AML、NFC、地址证明、KYB、钱包筛选、问卷拖放到画布上。连接边缘。完成。
工作流编排器
02 · 条件分支

如果这样，就那样。可无限嵌套。

根据任何信号进行分支, VPN / Tor 检测、签发国家、年龄、AML 命中、回访用户、欺诈评分、文档类型。无深度限制。无需重新部署应用即可编辑分支。
用户验证模块
03 · 11 个预设模板

从现有流程开始。

ID + 人脸比对、ID + 活体检测 + 人脸比对（$0.33 KYC）、ID + 基于 IP 风险、基于电话风险、高风险国家审查、双 ID、驾驶员验证、欧盟公司验证 (KYB) 等, 可切换模块的开启或关闭。
工作流编排器
04 · 内置 A/B 测试

衡量不同方案 · 推广最佳方案。

将流量分配到不同的工作流变体, 被动活体检测 vs 主动活体检测、登录界面开启 vs 关闭、申请时 AML vs 首次交易时 AML。每个 webhook 都附带变体 ID，以便分析将结果与变体关联起来。
Webhooks 文档
05 · 版本控制

草稿可编辑。已发布版本不可更改。

自由编辑草稿；发布会创建不可变版本。会话始终引用其确切版本，因此过去的会话可完全重现以供审计。历史版本永久保留。
AML 筛选模块
06 · 一个 /v3/ 合约

SDK、MCP 服务器、托管 UI, 均使用相同的 `workflow_id`。

将 workflow_id 传递给 POST /v3/session/。Didit 在服务器端处理编排并返回签名的 webhook。Didit MCP (Model Context Protocol) 服务器允许 AI 代理以编程方式创建和编辑工作流。
AI 代理身份解决方案
集成

一个会话。一个 workflow_id。处理所有分支。

一次性编排工作流。发布。将 workflow_id 传递给您的应用。Didit 负责协调。
POST /v3/session/工作流
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "workflow_id": "wf_signup_v12",
    "vendor_data": "user-42",
    "callback": "https://app/cb"
  }'
201已创建Didit 在服务器端引导用户完成每个分支。
在控制台中编辑工作流, 您的应用无需重新部署。文档 →
POST /v3/workflows/组合
$ curl -X POST https://verification.didit.me/v3/workflows/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workflow_label": "注册 KYC",
    "features": [
      { "feature": "OCR" },
      { "feature": "活体检测" },
      { "feature": "人脸匹配" },
      { "feature": "AML" }
    ]
  }'
201已创建返回工作流 UUID · 可直接用作 `workflow_id`。
线性功能顺序。与控制台构建器形状相同。文档 →
代理就绪集成

通过一个提示，快速部署无代码身份工作流。

粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent 中。填入您的模块和分支。代理将编排工作流、发布版本，并将签名 webhook 连接到您的应用。
didit-integration-prompt.md
You are integrating Didit's no-code Workflow Builder into a product. The product manager, the compliance officer, or the founder can change identity rules in the Business Console; your app only ever hands Didit a workflow_id, gets a verdict back, and routes the user.

Three pillars:

  1. Compose the workflow in the visual builder — drag ID, Liveness, Face Match, AML, NFC, KYB modules onto the canvas, connect them with edges, add conditional branches.
  2. Publish a version — the published version is immutable; sessions reference the exact version they were created with.
  3. Open POST /v3/session/ with the published workflow_id. Didit handles every module and every branch server-side.

Cost:
  - Pay per completed module per session (e.g. ID $0.15 + Liveness $0.10 + Face Match $0.05 + AML $0.20 = $0.50, or bundle = $0.33)
  - Workflow Builder itself is free
  - MCP server (for AI coding agents to manage workflows programmatically) is free, included
  - 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.
  - Access to the Business Console's Workflow Builder (every account has it).
  - The 11 seeded templates are a good starting point:
      "ID + Face Match"
      "ID + Liveness + Face Match" (the $0.33 KYC bundle)
      "ID + IP risk-based" (extra Liveness on VPN / Tor)
      "Phone risk-based verification"
      "High-risk country review"
      "Two ID documents"
      "Driver verification"
      "EU Company Verification" (KYB)
      ... plus four more
  - Plus "Start from Scratch" for fully bespoke flows.

STEP 1 — Compose the workflow

  Console → Workflows → New → pick a template OR Start from Scratch:
    - Drag modules from the sidebar onto the canvas
    - Connect them with edges (the user moves left-to-right through them)
    - Add branching conditions (right-click a node → Add condition)
    - Set per-workflow options: Include custom style (white label), retention override, callback URL

  Click Save Draft. The draft is fully editable; only published versions are immutable.

STEP 2 — Publish a version

  Click Publish on the draft. The version receives a number (v1, v2, v3…) and becomes immutable.

  Versioning rules:
    - Sessions reference the exact published version they were created with
    - You can iterate on a new draft while sessions on the old version continue to use it
    - Past versions are kept; you can inspect any past session's configuration
    - To change a published workflow, create a new draft from it, edit, publish

STEP 3 — Open a session with the workflow_id

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

  Response: 201 Created with the hosted session URL. Didit walks the user through every module and every branch defined in the workflow.

STEP 4 — Read the signed webhook on completion

  Didit POSTs to your callback when the session reaches a terminal status. Session statuses are Title Case With Spaces:

  Body (excerpted):
    {
      "session_id": "<uuid>",
      "workflow_id": "<the workflow id>",
      "workflow_version": "<v3>",
      "vendor_data": "<your user id>",
      "status": "Approved",
      "id_verification": { "status": "Approved" },
      "liveness": { "status": "Approved" },
      "face": { "status": "Approved", "similarity_score": 0.94 },
      "aml": { "status": "Approved", "hits": [] }
    }

  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.

  Each module that ran inside the workflow returns its own sub-status; the top-level status is the rolled-up verdict.

STEP 5 — Iterate without redeploying

  When the rules need to change — a new country flagged as high-risk, a tighter age threshold, a new module added to the bundle — the workflow owner edits the draft in the Console and publishes. New sessions automatically use the new version.

  Your app doesn't change. You don't redeploy. The workflow_id is the same; the underlying behaviour is updated.

STEP 6 — Run A/B tests

  Built-in A/B testing splits traffic across variant workflows. Configure variants in the Console (e.g. variant A uses Passive Liveness, variant B uses Active Liveness), set the split percentage, and read the variant id back on every session webhook.

  Measure conversion + verdict mix per variant in the Business Console's analytics. Promote the winner; the loser becomes a previous version retained for audit.

STEP 7 — Drive the Workflow Builder from AI coding agents

  The Didit MCP (Model Context Protocol) server (free, included) exposes the Workflow management primitives as MCP tools. Any MCP-compatible host — Claude Code, Cursor, Codex, Replit Agent, Devin, Aider — can list workflows, create new drafts, edit nodes, and publish versions on your behalf.

  Useful for ops teams that want to script tenant-specific workflow provisioning, A/B-variant generation, or per-customer-brand template materialisation.

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.
  - Published workflow versions are immutable. To change behaviour, publish a new version.
  - Conditional branches are unlimited in depth; keep flows readable for the next operator.
  - The cost model is pay-per-completed-module — adding a module that runs only conditionally only costs you on the branches that hit it.

Read the docs:
  - https://docs.didit.me/console/workflows
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/sessions-api/retrieve-session
  - 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
原生符合欧盟标准

数据证明

数据证明
  • Free
    工作流构建器、MCP 服务器、条件分支、A/B 测试、版本控制, 全部包含。
  • 0
    预设工作流模板，支持从零开始构建完全自定义流程。
  • $0.00
    标准 KYC 套件（身份识别 + 活体检测 + 人脸比对 + 设备 + IP + AML），按会话计费。
  • 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 no-code identity workflow, in plain English?

It's a way to design what your KYC / AML / KYB flow checks, in what order, and under which conditions, all in a visual drag-and-drop canvas instead of code.

In practice:

  • A product manager drags ID Verification, Passive Liveness, Face Match 1:1, and AML Screening onto the canvas
  • They draw a branch: if Device & IP signals say the user is on a VPN, add Active Liveness
  • They draw another branch: if the AML check returns a hit, block and open a case
  • They publish the workflow and hand the workflow_id to the engineering team
  • The engineering team passes that workflow_id into POST /v3/session/, done

When the rules need to change, the product manager edits the draft and publishes. The app doesn't redeploy.

Why does this matter? Couldn't we just code the flow ourselves?

You could. Most teams that try learn three lessons:

  • Rules change faster than deploys, a new country flags as high-risk, regulator tightens an age threshold, fraud team needs a new step-up. Every change is an engineering ticket, a PR, a review, a release.
  • State machines are fiddly, "if VPN then liveness else face match, unless returning user in which case skip to reusable KYC, but only when document was issued before 2020" gets ugly fast in application code
  • A/B testing your verification flow requires shipping two versions, splitting traffic at your edge, joining the variant id to the verdict for analytics, non-trivial infra

The Workflow Builder collapses all three into one drag-drop canvas. The rules become product configuration; the code becomes one POST /v3/session/ call.

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 modules can I drag onto the canvas?

Every Didit primitive ships as a node:

  • Identity & document, ID Verification ($0.15), NFC Reading ($0.15), Proof of Address ($0.20), Database Validation (variable), Custom Questionnaires ($0.10)
  • Biometric, Passive Liveness ($0.10), Active Liveness ($0.15), Face Match 1:1 ($0.05), Face Search 1:N (free), Age Estimation ($0.10), Biometric Authentication ($0.10)
  • Risk & fraud, AML Screening ($0.20, 1,300+ lists), Ongoing AML ($0.07/user/yr), Device & IP Analysis ($0.03)
  • Contact, Email Verification ($0.03), Phone Verification (from $0.03)
  • Business (KYB), Registry Lookup, UBO (Ultimate Beneficial Owner) Extraction, Officer Data, Entity AML, KYB Documents

Plus branching nodes (if/else, switch) and terminal nodes (Approve, Decline, Review).

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 workflow versioning work?

Two states per workflow:

  • Draft, fully editable. Add, remove, restructure nodes freely. Doesn't affect any live session.
  • Published, immutable. Receives a numeric version (v1, v2, v3...). Live sessions use the latest published version at the time the session was created.

To change a published workflow, you create a new draft from it, edit, publish. The new published version becomes v3 (or whatever); v2 stays in place forever as the historical record. Past sessions are fully reproducible, the session payload includes the exact workflow_version it ran on.

This matches what a regulator wants for audit: "show me the exact configuration of the workflow this user ran on, on this date". Every Didit account gets it for free, no setup.

How does this fit with the SDKs and the MCP server?

Everything ships under the same /v3/ contract.

  • SDKs, Web (React, Vue, vanilla), iOS (Swift), Android (Kotlin), React Native (TurboModules), Flutter (Dart). All five accept a workflow_id and walk the user through the same orchestration server-side. Free.
  • Hosted UI, branded or unbranded via the White Label add-on. Same workflow_id, same orchestration.
  • Didit MCP (Model Context Protocol) server, free, included. Exposes the Workflow management primitives as MCP tools so AI agents (Claude Code, Cursor, Codex, Replit Agent, Devin, Aider) can list workflows, create drafts, edit nodes, and publish versions on your behalf.

The net: one workflow_id flows from the Console → into your app → into the SDK or hosted UI → server-side orchestration → signed webhook. Zero glue code beyond the single POST /v3/session/.

What does the integration look like for a small team?

Three wires, one afternoon:

  • Open business.didit.me, sandbox key in 60 seconds, no credit card
  • Open the Workflow Builder, pick a template (e.g. "ID + Liveness + Face Match"), add or remove modules, save the draft, publish
  • In your app, call POST /v3/session/ with the published workflow_id and wire the signed webhook (X-Signature-V2, HMAC SHA-256) into your decision logic

That's the entire integration. When rules change, the workflow owner edits the draft in the Console and publishes, your app doesn't change.

For scripted workflow management, the Didit MCP server is free and lets any MCP-compatible agent host (Claude Code, Cursor, etc.) drive the Workflow Builder programmatically.

Related

相关模块 + 工作流

身份与欺诈基础设施。

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

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