Skip to main content
Didit 融资 750 万美元,打造身份与欺诈基础设施
Didit
生物识别认证

取代短信 2FA
刷脸,一秒搞定。

面向回访用户的即插即用无密码二次认证。告别短信费用、SIM 卡交换风险和运营商往返延迟。与注册时采用相同的 iBeta Level 1 PAD(演示攻击检测)引擎。每次认证 $0.10,每月免费 500 次。

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

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

Didit 生物识别认证, 两秒内完成被动活体二次认证。

防钓鱼登录

固有因素。
Android 端低于 1 秒。

复用注册时已验证的身份,对回访用户进行身份验证。 防SIM卡互换、防钓鱼,每次调用仅需$0.10, 比市场上典型的短信往返验证更经济。

工作原理

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

  1. 步骤 01

    创建工作流

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

  2. 步骤 02

    集成

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

  3. 步骤 03

    用户完成流程

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

  4. 步骤 04

    接收结果

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

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

六大功能。一个工作流。biometric_authentication

以下所有功能都是同一工作流类型中的可选项。没有升级层级,没有单独的SKU,也没有额外的调用费用。您可以按工作流启用这些功能,然后通过一次调用创建会话。
01 · 增强型2FA

短信双因素认证的即插即用替代方案。

在每次敏感操作时触发生物识别认证, 高价值转账、密码重置、大额提现、新设备登录。无需运营商账单,无SIM卡互换风险,无OTP钓鱼。与您的注册流程采用相同的托管UI, 用户无需学习新操作。每次认证$0.10,比短信更便宜,且免疫所有短信攻击。
增强认证POST /v3/session/
短信双因素认证
6位验证码
  • SIM 卡互换
  • 运营商账单
  • 钓鱼
生物识别认证
人脸核验
  • 无 SIM 卡暴露风险
  • 每次认证 $0.10
  • 防钓鱼
即插即用。与您注册时使用的 iBeta 认证引擎相同。
02 · 两种模式

仅活体检测或活体检测加人脸匹配。按工作流选择。

仅活体检测用于低摩擦的存在验证,或活体检测加人脸匹配用于与存储的注册照片进行完整身份绑定。两者都返回相同的JSON。通过编辑工作流切换模式, 无需客户端更改,无需新端点,每次认证仍为$0.10。
两种模式 · 一个工作流biometric_authentication
  • 仅活体检测存在性检查
    功能: [活体检测]
    确认是真实人类。摩擦最小。
  • 活体检测 + 人脸匹配身份绑定
    功能: [活体检测, 人脸匹配]
    将人像图片绑定到注册信息。安全性最高。
每个工作流可切换。相同的 workflow_id。每次认证 $0.10。
03 · 不到2秒出结果

登录时感知延迟不到一秒。

边缘服务推理, 无需模型下载,不依赖设备加速,廉价安卓设备上也不会降低体验。捕获约0.3秒,活体检测不到1秒,人脸匹配约0.5秒,Webhook端到端输出不到2秒。比短信验证码更快,且用户无需离开您的应用。
登录延迟端到端 < 2 秒
  • Capture · auto-frame0.32 s
  • Liveness · passive0.81 s
  • Face match · 1:10.42 s
  • Approved · webhook out1.65 s
边缘推理。无需模型下载。无需运营商往返。
04 · 账户盗用防御

iBeta一级认证,可抵御所有已知攻击。

通过iBeta的PAD(演示攻击检测)一级独立认证, 这是NIST和开放身份交换组织引用的标准。可抵御被盗自拍重放、深度伪造、纸质面具、硅胶和乳胶面具、变形攻击。无论您的设置如何,硬拒绝触发器(黑名单人脸、未检测到人脸、攻击特征、无参考图像)始终有效。
账户盗用防御iBeta L1 PAD
  • 账户所有者的深度伪造已拦截
  • 硅胶或纸质面具已拦截
  • 被盗自拍 · 重放攻击已拦截
  • 黑名单人脸自动拒绝
05 · 照片复用

复用注册照片。无需额外存储。

您已经拥有用户注册KYC时的参考照片, 在每次生物识别认证会话中传递它,我们将进行相似度评分。相同的模板存储,相同的欧盟默认基础设施(企业版支持特定区域驻留),相同的数据保护官。无需重新入职,无需额外的存储决策。
复用 KYC 人像portrait_image
sign-up
KYC 人像
每次登录
人脸比对 1:1
  • 相似度得分96.2
  • 与 KYC 模板存储相同欧盟 AWS
06 · 可调阈值

每个工作流可配置相似度和活体检测阈值。

低活体和低人脸匹配警告分别带有审核阈值和拒绝阈值,您可以根据每个应用进行调整。对高价值转账严格,对新设备登录宽松, 所有这些都可以在控制台的同一工作流编辑器中完成。完整的警告目录可在文档中查看。
Didit业务控制台生物识别认证工作流编辑器,显示可配置的活体检测和人脸匹配阈值。
集成

两种配置。同一会话。同等价格。

两种配置都在同一个生物识别认证工作流中创建会话。仅活体检测是纯粹的存在验证, 摩擦最小。活体检测加人脸匹配将认证与用户存储的注册照片绑定。通过编辑工作流进行切换, 无需客户端更改。
POST /v3/session/活体检测 + 人脸匹配
$ 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_bio_auth",
    "vendor_data": "user-42",
    // base64-encoded reference selfie, ≤ 1MB
    // omit this field for liveness-only mode
    "portrait_image": "/9j/4AAQSkZJRgABAQE..."
  }'
201已创建{ "session_url": "verify.didit.me/..." }
传入 portrait_image 用于人脸匹配;若仅需活体检测则省略。文档 →
POST /webhooks/didit第二步 · 接收
// Your endpoint receives a signed payload
app.post("/webhooks/didit", (req, res) => {
  const sig = req.headers["x-signature-v2"];
  const expected = crypto.createHmac("sha256", SECRET)
    .update(req.rawBody).digest("hex");
  if (sig !== expected) return res.sendStatus(401);
  const { status, decision, vendor_data } = req.body;
  // status: Approved | Declined | In Review | ...
  res.sendStatus(200);
});
200OKwebhook_type: "status.updated", status: "Approved"
实时 HMAC 签名 webhook。验证、解析并更新您的数据库。文档 →
代理就绪集成

通过一个提示词,快速上线生物识别认证。

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

You are integrating Didit's Biometric Authentication module into <my_stack>.
This is a returning-user passwordless re-verification flow — a drop-in
replacement for SMS or email 2FA at high-value actions (large transfers,
password reset, large withdrawals, sensitive setting changes). It is NOT
the first-time KYC sign-up flow — for that, see Didit Liveness at
docs.didit.me/core-technology/liveness/overview.

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. Create the biometric_authentication workflow (one time)
Biometric Authentication is a workflow_type, not a feature flag. Create
the workflow once, reuse the workflow_id for every authentication.

POST https://verification.didit.me/v3/workflows/
Header: x-api-key: <your-api-key>
Body:
  - workflow_label   (your label, e.g. "step-up-2fa")
  - workflow_type    "biometric_authentication"  (snake_case enum)
  - features         the array
                       [{ feature: "LIVENESS" }]                    (liveness-only mode)
                     OR
                       [{ feature: "LIVENESS" }, { feature: "FACE_MATCH" }]  (face-match mode)
  - liveness_method  "PASSIVE" | "FLASHING" | "ACTIVE_3D"   (PASSIVE recommended for low-friction step-up)

Store the returned workflow_id — you will reuse it on every auth.

## 3. Authenticate a returning user

POST https://verification.didit.me/v3/session/
Header: x-api-key: <your-api-key>
Header: Content-Type: application/json
Body:
  - workflow_id     (from step 2)
  - vendor_data     (your own user id, e.g. "user-42")
  - callback        (optional URL we redirect the user to after capture)
  - metadata        (optional JSON, surfaced back on the webhook)
  - portrait_image  (Base64 JPEG, REQUIRED when the workflow has FACE_MATCH;
                     OMIT for liveness-only mode)

The portrait_image is the stored reference photo from the user's original
KYC verification (you already have it as id_verification.portrait_image in
the original session response). Send it as a Base64-encoded JPEG, max 1 MB.

Response: session_url — redirect the user to it. Didit hosts the capture
(camera, motion prompts, low-light fallback, accessibility) and posts the
verdict back via webhook.

## 4. Webhooks
- Register a webhook destination once via
  POST https://verification.didit.me/v3/webhook/destinations/
  Body: url, subscribed_events: ["session.verified", "session.declined",
                                  "session.review_started"]
- 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.

## 5. Reading the report
The webhook payload (and the GET /v3/session/{id}/decision/ response)
returns the combined biometric_authentication shape:

  status               "Approved" | "Declined" | "Not Finished"
  workflow_id          string
  session_id           uuid
  session_number       integer
  vendor_data          your user id
  liveness:
    status             "Approved" | "Declined" | "Not Finished"
    method             "PASSIVE" | "FLASHING" | "ACTIVE_3D"
    score              number 0-100
    reference_image    signed URL to the captured selfie (expires in 1 hour)
    video_url          signed URL (FLASHING and ACTIVE_3D only, expires in 1 hour)
    warnings           array
  face_match:                     (only present in face-match mode)
    status             "Approved" | "Declined" | "Not Finished"
    score              number 0-100 (similarity %)
    source_image       signed URL to the captured selfie
    target_image       signed URL to the supplied portrait_image
    warnings           array

Overall status is "Approved" only when liveness.status == "Approved" AND
(face_match is absent OR face_match.status == "Approved").

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

Configurable risks (action per workflow — Decline, Review, or Approve):
  LOW_LIVENESS_SCORE, LOW_FACE_MATCH_SIMILARITY

## 6. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- workflow_type is snake_case: biometric_authentication.
- Feature enums inside the workflow are UPPERCASE: LIVENESS, FACE_MATCH.
- Liveness 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).
- portrait_image is Base64 JPEG, max 1 MB, required only in face-match mode.

## 7. Pricing reference (public)
- Biometric Authentication: $0.10 per authentication (passwordless re-auth).
- 500 free authentications every month, forever, on every account.
- For the original sign-up KYC, see https://didit.me/pricing (full KYC
  bundle is $0.33 per onboarded user, which includes Liveness + Face Match +
  ID Verification + Device & IP Analysis).

## 8. When to use this versus Liveness directly
- First-time KYC sign-up: use Liveness (the feature) inside an ID
  Verification workflow. See docs.didit.me/core-technology/liveness/overview.
- Step-up at sensitive actions (transfer, password reset, large
  withdrawal): use this Biometric Authentication workflow.
- High-volume passive monitoring (any login): use this workflow with
  liveness-only mode (no portrait_image) — fastest, lowest friction.

## 9. 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/biometric-auth/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 L1
    经独立认证的演示攻击检测。
  • <0s
    每会话端到端认证结果,边缘服务。
  • $0.00
    每次认证成本低于短信,且免疫所有短信攻击。
  • 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 Biometric Authentication and how is it different from Liveness?
Biometric Authentication is the returning-user re-auth surface, a drop-in replacement for SMS or email two-factor authentication (2FA) at sensitive actions (high-value transfer, password reset, large withdrawal, new-device login). It is a workflow_type (snake-case: biometric_authentication) that composes the LIVENESS feature with an optional FACE_MATCH feature. Liveness on its own is the sign-up capability, see /products/liveness for the first-time know-your-customer (KYC) flow. Both use the same iBeta Level 1 Presentation Attack Detection (PAD)-certified engine, so the model your user passed at onboarding is the same model checking them at every login.
What is the response shape?
The combined report returns status (Approved, Declined, Not Finished), a liveness block with status, method (PASSIVE, FLASHING, or ACTIVE_3D), score 0-100, reference_image, video_url, and warnings, plus a face_match block (only present when the workflow has FACE_MATCH) with status, score 0-100, source_image, target_image, and warnings. The signed image and video URLs expire after 60 minutes. Overall status is Approved only when liveness is approved AND (face match is absent OR face match is approved).
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 account-takeover attacks does it block?
Didit Biometric Authentication is iBeta Level 1 PAD certified against the full ISO/IEC 30107-3 attack catalog, printed photos, screen replays, paper masks, silicone masks, latex masks, morph attacks, AI-generated deepfakes of the account owner, and stolen-selfie replays. Four risks are auto-decline regardless of your settings: FACE_IN_BLOCKLIST, NO_FACE_DETECTED, LIVENESS_FACE_ATTACK, and NO_REFERENCE_IMAGE. Configurable warnings, LOW_LIVENESS_SCORE and LOW_FACE_MATCH_SIMILARITY, let you tune the review and decline thresholds per application.
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 总结此页面