Skip to main content
Didit 融资 750 万美元，打造身份与欺诈基础设施
Didit
账户盗用保护

通过人脸验证阻止账户盗用。在风险飙升时立即升级验证。

在攻击者瞄准的关键时刻（转账、密码重置、新设备登录）进行生物识别升级。2秒内出结果，每次事件约 $0.13。每月免费验证500次。

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

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

一个深色抽象的账户盗用堆栈, 在纯黑色背景上，四个浮动的半透明深色玻璃面板呈3D透视，由一条发光的Didit蓝色垂直线贯穿，并由四个发光的扫描支架框住。每个面板都带有一个微小的浅白色抽象图案，代表升级验证的步骤。

攻击者如何攻击

密码被盗。会话被劫持。选择人脸验证。

撞库、SIM 卡劫持和会话劫持攻击都能绕过密码和一次性验证码。 在操作发生时，用 Didit 升级验证取代它们, 每次调用 $0.10，2秒内出结果，每月免费500次。

工作原理

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

  1. 步骤 01

    创建工作流

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

  2. 步骤 02

    集成

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

  3. 步骤 03

    用户完成流程

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

  4. 步骤 04

    您收到结果

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

为解决方案而生 · 基础设施定价

六项功能。一次二次验证。每次事件 约 $0.13。

账户盗用 (ATO) 防御是一个组合方案，而非单一检查。您可以在工作流构建器中为每个工作流切换各项功能，或通过 API 将它们组合起来。
阅读文档获取 API 密钥
01 · 二次验证触发器

您选择时机。Didit 执行检查。

二次验证策略存在于工作流构建器中, 高价值转账、密码重置、向新目的地付款、新设备登录、地理异常。如果网络信号存在风险，您可以使用设备和 IP 分析进行预门控，仅在必要时进行人脸检查。无需重新部署即可更改规则。
工作流编排模块
02 · 生物识别二次验证

一次二次验证。不到两秒出结果。

与用户注册时通过的生物识别引擎相同, iBeta Level 1 活体攻击检测 (PAD) 以及与存储照片的 1:1 人脸比对。每次会话 $0.10。防钓鱼和防 SIM 卡交换。入门级 Android 设备端到端处理时间低于两秒。
生物识别认证模块
03 · 人脸比对 1:1 vs 注册

比对目标是用户存储的照片。

人脸比对 1:1 将每次二次验证自拍与用户存储的注册照片进行比对。返回 0-1.0 的相似度分数和警告；阈值可根据工作流进行调整。被盗的自拍无法通过, 目标锁定为原始注册照片，而非新捕获的图像。
人脸比对 1:1 模块
04 · 深度伪造防御

打印。回放。面具。深度伪造。全部阻止。

经 iBeta 独立测试，并获得 Level 1 PAD 认证，符合 ISO/IEC 30107-3 完整目录标准。可有效阻止打印照片、屏幕回放、纸质/硅胶/乳胶面具、换脸攻击以及账户所有者的 AI 生成深度伪造。每年重新测试。
活体检测模块
05 · IP + 设备预检查

VPN、数据中心、Tor, 在人脸检查前标记。

在二次验证触发前，对用户的 IP（互联网协议）地址和设备指纹进行评分。返回 0-100 的风险分数以及 VPN、代理、Tor、数据中心、国家和 ASN 标志。每次检查 $0.03，耗时低于 100 毫秒。在受信任设备 + 低风险网络上跳过二次验证。
设备与 IP 分析模块
06 · Webhook 决策

一个 Webhook。三个分支。搞定。

一个签名 Webhook 会带着结果（通过、拒绝、审核中、未完成）到达。在读取正文之前，使用 HMAC SHA-256 验证 X-Signature-V2。每次二次验证的负载相同；相应地分支原始操作。免费提供 200 多个欺诈信号。
Webhook 参考
集成

一个会话。一个签名 Webhook。三个分支。

针对生物识别工作流开启二次验证。读取签名结果。分支执行操作。
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_ato_step_up",
    "vendor_data": "user-42",
    "metadata": { "trigger": "high_value_transfer" },
    // base64 KYC enrolment selfie, ≤ 1MB
    "portrait_image": "/9j/4AAQSkZJRgABAQE..."
  }'
201创建时间{ "session_url": "verify.didit.me/..." }
在 webhook 返回 status: Approved 之前阻止操作。文档 →
POST /webhooks/didit判定结果
// X-Signature-V2 verified upstream
if (payload.status === "Approved") {
  unblockAction(payload.vendor_data);
} else if (payload.status === "Declined") {
  logWarnings(payload.liveness.warnings);
  blockAndAlert(payload.vendor_data);
}
200确定状态：已批准 · 已拒绝 · 审核中 · 未完成
读取 payload 前验证 X-Signature-V2。文档 →
代理就绪集成

一键部署账户盗用防御。

粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent 中。填写您的技术栈。Agent 将连接触发器、启动升级会话、验证 Webhook 并分支原始操作。
didit-integration-prompt.md
You are integrating Didit account-takeover defence into an application that already has the user signed in. Your job: when a sensitive action fires (large transfer, password reset, payout to a new destination, new-device login, geo anomaly), gate it on a Didit biometric step-up. One API call. One signed webhook. Three branches.

WHY THIS SHAPE
  - Credential stuffing, SIM-swap, and stolen-session-cookie attacks all walk past passwords and SMS one-time codes. A face check at the moment of the sensitive action does not.
  - Didit runs Passive Liveness (the user is alive, present, not a deepfake) plus 1:1 Face Match against the portrait captured at sign-up. A stolen selfie cannot pass — the comparison target is locked to the original enrollment.
  - $0.10 per step-up (Biometric Authentication module) + $0.03 IP pre-check (optional) = around $0.13 per event. Sub-two-second verdict on entry-level Android. 500 verifications free every month.

PRE-REQUISITES
  - Production API key from https://business.didit.me (sandbox key in 60 seconds, no credit card).
  - A webhook endpoint with HMAC SHA-256 verification of the X-Signature-V2 header using your webhook secret.
 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.  - A Workflow Builder workflow that bundles Passive Liveness + Face Match 1:1 (with the user's stored sign-up portrait as the comparison target). Optionally compose Device & IP Analysis ahead of the step-up to pre-gate the check.
  - Persist the user's sign-up portrait — either base64 on your side, or rely on Didit's stored enrollment via vendor_data lookup.

STEP 1 — Decide WHEN to step up (your code, not Didit's)
  Run your usual fraud signals. Common triggers worth a biometric step-up:
    - Wire / crypto transfer above the user's daily limit
    - Password / email reset on a session less than 24h old
    - Payout to a bank account or wallet seen for the first time
    - Login from a new device or new country
    - Velocity anomaly — N actions of type T within window W

  Cheap pre-check (optional, ~100ms, $0.03):
    - Score the user's IP via Device & IP Analysis. If the IP is a residential trusted address with a low risk score AND the device fingerprint matches the user's trusted device, skip the step-up. Otherwise run Step 2.

STEP 2 — Create a biometric step-up session
  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<wf id bundling Passive Liveness + Face Match 1:1>",
      "vendor_data": "<your user id, max 256 chars>",
      "callback": "https://<your-app>/ato/step-up/callback",
      "metadata": {
        "trigger": "high_value_transfer",
        "action_id": "<your internal action reference>"
      },
      "portrait_image": "<base64 JPEG of the user's stored sign-up portrait, ≤ 1 MB — REQUIRED when the workflow has FACE_MATCH active; the step-up matches the new live selfie against this stored reference>"
    }

  Response: 201 Created with a hosted session URL. Redirect the user there inline (or open it in a webview / Didit mobile SDK). The action stays BLOCKED on your side until the signed webhook lands.

STEP 3 — Read the signed webhook on completion
  Didit POSTs the decision to your callback. Verify X-Signature-V2 (HMAC SHA-256 of the raw request body using your webhook secret) BEFORE reading the JSON.

  Payload (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your user id>",
      "status": "Approved",
      "liveness": { "status": "Approved" },
      "face":     { "status": "Approved", "similarity_score": 0.94 },
      "ip_analysis": { "status": "Approved", "score": 11 }
    }

  Session status enum (exact case, Title Case With Spaces): Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned.

STEP 4 — Branch the original action on status
  Approved      → unblock the sensitive action. Log session_id + similarity score on the audit trail.
  In Review     → hold the action, route to a human review queue.
  Declined      → block the action, log liveness warnings (mask / deepfake / replay / morph), alert the user.
  Not Finished  → invite the user to retry with a fresh session URL.
  Expired       → resend the link; the original session has timed out.
  Abandoned     → the user closed the flow before completing; resend the link.

STEP 5 — (Optional) Pull the full decision payload
  GET https://verification.didit.me/v3/session/{session_id}/decision/
  Headers:
    x-api-key: <your api key>
  Returns the same payload as the webhook plus the structured signals (liveness warnings, face-match similarity, IP / device flags). Use for analyst review.

WEBHOOK EVENT NAMES
  - Sessions: standard session webhook (one endpoint, status field tells you where in the lifecycle).
  - Verify X-Signature-V2 (HMAC SHA-256) on every payload.

CONSTRAINTS
  - Session statuses use Title Case With Spaces (Approved, In Review). Never use UPPER_SNAKE_CASE for session verdicts — that's the Transactions API and lives in a different surface.
  - 1:1 face match's comparison target is the user's STORED sign-up portrait, not a freshly captured one. A stolen selfie cannot pass.
  - iBeta Level 1 Presentation Attack Detection (PAD) certified against the full ISO/IEC 30107-3 catalogue — print, replay, paper / silicone / latex mask, deepfake, morph.
  - The Workflow Builder is where you choose the modules in the step-up — change them in the console without redeploying.
  - 200+ fraud signals are surfaced on every session at no extra cost — read them off the decision payload, don't re-query.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/core-technology/biometric-auth/overview
  - https://docs.didit.me/core-technology/ip-analysis/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
原生符合欧盟标准

数据证明

数据证明
  • iBeta L1
    独立认证的演示攻击检测, 每年重新测试。
  • <0s
    入门级 Android 设备上的端到端升级验证。
  • ~$0.13
    每次事件, $0.10 生物识别升级，外加 $0.03 可选 IP 预检查。
  • 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 an account takeover attack?

An account takeover (ATO) happens when an attacker gains control of a legitimate user account, usually with stolen credentials, a hijacked session cookie, or a SIM-swap that intercepts the One-Time Password (OTP). From there they drain wallets, move funds, change payout details, or reset email and lock the real owner out.

The attack walks past the password because the password is already correct. It walks past the Short Message Service (SMS) code because the attacker controls the phone number. The defence is to interrupt the moment of action with something the attacker does not have, the legitimate user's face.

Why don't SMS one-time codes stop ATO anymore?

Because SIM-swap fraud puts the Short Message Service (SMS) code in the attacker's pocket. The attacker convinces the carrier to port the victim's number to a new Subscriber Identity Module (SIM); from then on, every code the bank sends arrives on the attacker's phone.

Phishing kits in 2026 also proxy the code in real time, the user types it into a fake page, the kit replays it to the real site, the session opens. SMS gives a single shared secret per channel; biometrics give a per-action proof tied to the human in front of the camera.

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 is biometric step-up different from biometric sign-up?

Sign-up captures the user's identity for the first time, government identity document, Optical Character Recognition (OCR), Passive Liveness, and a portrait that becomes the enrollment baseline. It is a one-off, heavy-weight flow.

Step-up is the lightweight, repeatable version. The same liveness engine runs on a new selfie; Face Match 1:1 compares the new selfie against the stored sign-up portrait. No identity document, no OCR. Sub-two-second, $0.10 per session.

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 do I pre-check the network before the face check fires?

Compose Device & IP Analysis ahead of the step-up. $0.03 per check, under 100ms, returns a 0–100 risk score plus Virtual Private Network (VPN), proxy, The Onion Router (Tor), datacenter, country, and Autonomous System Number (ASN) flags.

If the network looks clean (residential Internet Service Provider (ISP), trusted device fingerprint, no country flip), skip the face check. If the score is high or any flag fires, run the step-up. That keeps the biometric budget on the events that actually need it.

How much does it cost per protected action?

Two line items:

  • Biometric Authentication step-up: $0.10 per session
  • Device & IP Analysis pre-check (optional): $0.03 per call

Around $0.13 per fully-screened sensitive action. The first 500 verifications every month are free on every account, most teams find their step-up volume sits inside that allowance for the first few weeks.

No minimums, no annual commitment, no per-seat pricing.

Which industries run this recipe?

The recipe applies to any team handling high-value actions. Common live patterns:

  • Fintech / neobank: step up on transfers above the daily limit and on payout-account changes
  • Crypto exchange: step up on withdrawals to a wallet not on the allowlist
  • Marketplace: step up on payouts to a new bank account and on bulk-listing actions
  • iGaming: step up on withdrawals and on responsible-gaming-limit overrides
  • Telecom / utilities: step up on SIM-port-out and address-change requests

Same Workflow Builder, different triggers, one integration, one pricing line.

Related

相关模块 + 工作流

身份与欺诈基础设施。

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

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