Skip to main content
Didit 融资 750 万美元，打造身份与欺诈基础设施
Didit
被动活体检测

验证任何 人脸。
无需用户进行任何操作。

证明摄像头前的人是真实活体。iBeta 认证防欺诈, 在 2 秒内击败深度伪造、面具、回放和变形攻击。被动检测 $0.10，主动检测 $0.15。每月免费 500 次。

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

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

Didit 活体检测, 被动活体捕获，设备端2秒内出结果。

iBeta 认证

被动。闪光。
主动。全部认证。

识别 3D 面具、深度伪造、回放攻击和打印照片。 iBeta 认证，2秒内出结果，每次检查 $0.10，每月免费 500 次。

工作原理

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

  1. 步骤 01

    创建工作流

    选择您需要的检查项, 身份、活体、人脸比对、制裁名单、地址、年龄、电话、邮箱、自定义问题。在控制台中拖拽到流程里，或通过 API 调用。支持条件分支、A/B 测试，无需代码。

  2. 步骤 02

    集成

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

  3. 步骤 03

    用户完成流程

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

  4. 步骤 04

    接收结果

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

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

六大功能。一个特性开关。活体检测。

以下所有功能都是同一模块上的开关。没有加价层级，没有单独的 SKU，没有附加调用。在控制台中按工作流开启，或在独立端点上内联传递。
阅读文档获取 API 密钥
01 · 方法

被动式、3D 闪光、3D 动作。根据风险选择。

一个模块支持三种方法。被动式（单帧，零用户操作）适用于低摩擦注册。3D 闪光（短光序列通过反射捕获深度）适用于高价值被动流程。3D 动作与闪光（动作 + 闪光）适用于受监管市场和高价值用户注册。
02 · 认证防欺诈

针对所有呈现攻击目录进行测试。

经过独立测试并获得 iBeta 认证, 这是 NIST 和 Open Identity Exchange 引用的标准。可阻挡打印照片、屏幕回放、纸质面具、硅胶面具、乳胶面具、变形攻击和 AI 生成的深度伪造。随着攻击目录的增长，每年重新测试。
03 · 2秒内出结果

端到端推理在两秒内完成。

边缘推理服务。无需模型下载，不依赖设备端加速，入门级 Android 设备上也不会降低体验。大多数设备上被动式活体检测在一秒内完成。闪光式增加约 600 毫秒。主动 3D 式增加约 1.5 秒, 端到端仍低于 2 秒。
04 · 警告

每个工作流可调的风险策略。

七种可配置警告, 低分、可能重复、重复人脸、多张人脸、人脸质量低、光线不足、光线过强, 每种都可根据应用映射到拒绝、审核或批准。三种自动拒绝触发器（无人脸、检测到攻击、黑名单人脸）无论如何都会强制执行。
05 · 年龄估算

一次捕获，两个信号。

在活体检测工作流中开启年龄估算，同一张自拍将返回活体检测结果和估算年龄段。专为英国在线安全法案和欧盟年龄门槛设计, 无需用户上传身份证明，即可验证真人且年龄符合要求。每次检查 $0.10。
06 · 生物识别认证

您在注册时使用的引擎，现在每次登录都可用。

活体检测是生物识别认证的基础, 重复使用相同的防欺诈模型，在每次敏感操作时验证回访用户：高价值转账、密码重置、大额提款。每次认证 $0.10，可替代短信 2FA，无运营商费用，无 SIM 卡交换风险。
集成

两个端点。相同的 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_liveness_3d",
    "vendor_data": "user-42"
  }'
201已创建{ "session_url": "verify.didit.me/..." }
我们托管捕获 UI。FLASHING 和 ACTIVE_3D 模式必需。文档 →
POST /v3/passive-liveness/服务器到服务器
$ curl -X POST https://verification.didit.me/v3/passive-liveness/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -F "image=@selfie.jpg"
200OK{ "status": "Approved", "score": 98 }
您掌控捕获过程，我们即时返回结果。文档 →
代理就绪集成

一键部署活体检测。

将以下代码块粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent 中。用您的框架、语言和用例填充 my_stack 占位符。代理将配置 Didit，构建启用活体检测的工作流，连接 webhook，并完成部署。
didit-integration-prompt.md
# Didit Liveness — integrate in 5 minutes

You are integrating Didit's Liveness (presentation-attack detection) 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 camera, motion prompts, low-light
fallback, mobile handoff, and accessibility for you.

1. Create a workflow that contains the LIVENESS 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: "LIVENESS" }   (UPPERCASE — strict enum)
   Optional config: liveness_method ("PASSIVE" | "FLASHING" | "ACTIVE_3D")
   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 selfie image (mobile SDK capture, native
onboarding app, reseller pipeline). Standalone is single-frame
PASSIVE only — for ACTIVE_3D or FLASHING you must use Path A.

POST https://verification.didit.me/v3/passive-liveness/
Content-Type: multipart/form-data
Body fields:
  - image        (required, file — single selfie)
  - vendor_data  (optional string, your user id)

Response: JSON report with liveness score, method, and 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 liveness object includes:
- status: "Approved" | "Declined" | "In Review" | "Not Finished"
- method: "PASSIVE" | "FLASHING" | "ACTIVE_3D"
- score: number 0-100 (normalized liveness score)
- reference_image: signed URL to the captured selfie (expires in 1 hour)
- video_url: signed URL to the capture video, present only for FLASHING
  and ACTIVE_3D (expires in 1 hour)
- age_estimation: { age, age_range } when enabled in the workflow
- warnings: Array<{ risk, log_type, short_description, long_description }>

Auto-decline risks (always enforced by Didit, not configurable):
- NO_FACE_DETECTED
- LIVENESS_FACE_ATTACK
- FACE_IN_BLOCKLIST

Configurable risks (action per workflow — Decline, Review, or Approve):
- LOW_LIVENESS_SCORE
- POSSIBLE_DUPLICATED_FACE
- DUPLICATED_FACE
- MULTIPLE_FACES_DETECTED
- LOW_FACE_QUALITY
- LOW_FACE_LUMINANCE
- HIGH_FACE_LUMINANCE

## 5. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: LIVENESS, ID_VERIFICATION, FACE_MATCH, AML, IP_ANALYSIS.
- Method enum is UPPERCASE: PASSIVE, FLASHING, ACTIVE_3D.
- 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).

## 6. Pricing reference (public)
- PASSIVE method: $0.10 per check (standalone or bundled)
- FLASHING / ACTIVE_3D methods: $0.15 per check
- Bundled in a full KYC workflow: $0.33 per session (includes Liveness)
- 500 free checks every month, forever, on every account.

## 7. Verify your integration
- Sandbox starts on signup at https://business.didit.me — no separate flag.
- Test images: deterministic synthetic faces returned in sandbox (Approved
  by default; trigger Declined by sending the canonical "spoof" test image).
- Switch to live: flip the application's environment toggle in console.

When in doubt: https://docs.didit.me/core-technology/liveness/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
原生符合欧盟标准

数据证明

数据证明
  • iBeta
    独立认证的防欺诈（演示攻击检测）。
  • 0
    活体检测方法, 被动式、3D 闪光、3D 动作 + 闪光。
  • <0s
    每次验证的端到端推理。
  • $0.00
    每次被动活体检测。每月免费 500 次。
三个层级，一份价目表

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

每月 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 inputs does Liveness accept?
A single selfie. Path A, Workflow Builder: the hosted UI captures the selfie inside the user's session, passive needs no user action, 3D Flash plays a short colour sequence, 3D Action prompts a head movement. Comes for free with the session, no extra capture work on your side. Path B, Standalone API: you pass the image yourself as user_image on a multipart POST /v3/passive-liveness/. Accepted formats: JPG, JPEG, PNG, up to 5 MB. Both paths return the same liveness JSON shape.
What is the response shape?
A root-level liveness object with status (Approved, Declined, In Review, or Not Finished), a 0–100 score, the method used (PASSIVE, FLASHING, or ACTIVE_3D), an age_estimation float (optional, when bundled), a signed reference_image URL, a signed video_url for active methods, a matches array surfacing any face-search hits (each with session_id, similarity_percentage, is_blocklisted), and a warnings array. Each warning carries risk, log_type (information, warning, or error), short_description, and long_description. Same shape whether you called the Workflow Builder or the standalone API. Full reference at docs.didit.me/core-technology/liveness/report-liveness.
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.

How does Didit defeat deepfakes, masks, and replay attacks?

Three methods, one module, iBeta Level 1 Presentation Attack Detection (PAD) certified across the full attack catalogue:

  • Passive, one frame, zero user action. Catches printed photos, screen replays, and basic morph attacks. Best for low-friction sign-up.
  • 3D Flash (`FLASHING`), plays a short colour sequence on the phone screen and measures the reflection on the face. Defeats 2D screen replays and high-fidelity printed masks.
  • 3D Action (`ACTIVE_3D`), combines a head-movement prompt with the flash sequence. Defeats 3D silicone masks and AI-generated deepfake video. Best for high-value onboarding and regulator-sensitive markets.

Seven configurable warnings (low score, low light, high light, possible duplicate, duplicate face, multiple faces, low face quality) map to decline / review / approve per application. Three auto-decline triggers (no face, attack detected, blocklisted face) are always enforced.

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.

Related

相关模块

身份与欺诈基础设施。

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

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