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

使用 Face Search 1:N 识别女巫攻击。一人一账户。

将每个新注册的自拍照与先前已批准的自拍照库进行比对。匹配意味着同一人已拥有账户。人脸搜索免费；每月免费 500 次验证。

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

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

一个深色抽象的女巫攻击检测堆栈, 四个浮动的半透明深色玻璃面板以3D透视方式呈现在纯黑色背景上，由一条发光的Didit蓝色垂直线贯穿，并由发光的扫描支架框住。每个面板上都有一个微小的浅白色抽象图案（单张脸、重复的脸、节点网络、关联账户集群）。

电子邮件和电话无法识别的

廉价邮箱。廉价手机。一张人脸，始终如一。

电子邮件别名和一次性SIM卡成本低廉。而人脸是女巫攻击者无法轮换的唯一标识符。 Face Search 1:N 对比您之前的自拍图库，让同一个人无处遁形。每次搜索免费，每月免费验证 500 次。

工作原理

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

  1. 步骤 01

    创建工作流

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

  2. 步骤 02

    集成

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

  3. 步骤 03

    用户完成流程

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

  4. 步骤 04

    接收结果

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

为配方而生 · 基础设施定价

六项检查。一个签名判决。免费人脸搜索。

多账户防御是一个组合, 搜索、活体检测、跨账户关联、审计追踪。在工作流构建器中为每个工作流切换每个模块。
阅读文档获取 API 密钥
01 · 问题形态

同一用户重复出现。

女巫空投、推荐奖励周期、规避自我排除的 iGaming 多账户、市场虚假评论集群、DAO 投票操纵、新银行或券商注册时的欢迎奖金堆叠。相同的工作流构建器工作流可保护所有变体。
工作流编排器模块
02 · 人脸搜索门槛

将每张新面孔与图库进行比对。

Face Search 1:N 会索引注册时捕获的自拍，并将其与您账户下先前批准的自拍图库进行搜索。返回具有相似度得分的最高匹配项。每次搜索免费, 无按次调用费用。向量搜索在两秒内返回结果。
人脸搜索 1:N 模块
03 · 匹配集群

同一张面孔，已存档。

当搜索找到匹配项时，Webhook payload 会携带每个先前的 session_id、匹配的用户引用和相似度得分。根据工作流调整硬/软阈值, 默认 0.85 = 拒绝，0.75–0.85 = 审核中，< 0.75 = 批准。
人脸搜索工作原理
04 · 跨账户关联信号

相同设备。相同 IP。相同支付方式。

在同一工作流中组合设备和 IP 分析（$0.03 / 次调用）。决策 payload 会显示设备指纹、Internet Protocol (IP) 地址、自治系统号 (ASN) 和国家/地区。结合您后端支付工具的哈希值，在人脸搜索确认之前对女巫攻击进行聚类。
设备与 IP 分析模块
05 · 可复用身份锚点

一个身份。多个产品。杜绝克隆。

可复用 KYC 允许合法用户以零成本使用先前验证的凭证重新进入您的其他产品, 这是有意的复用，而非滥用。女巫攻击者无法在新的账户中重放相同的凭证，因为人脸搜索仍然锚定到已发行的身份。
可复用 KYC 模块
06 · 签名 Webhook 决策

签名判决。完整匹配列表作为审计追踪。

一个签名的 Webhook 会带着判决, 批准、审核中、拒绝, 以及匹配的 session_id 和相似度得分的完整列表。在读取之前，使用基于哈希的消息认证码 (HMAC) SHA-256 验证 X-Signature-V2。匹配列表是任何争议的审计追踪。
Webhook 参考
集成

一个会话。一个签名判决。匹配列表随之而来。

开放注册。读取签名判决。人脸搜索匹配列表就在 payload 中, 阻止重复账户，记录集群。
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_sybil_gate",
    "vendor_data": "signup-A4",
    "metadata": { "surface": "airdrop_claim" }
  }'
201已创建{ "session_url": "verify.didit.me/..." }
在 webhook 返回 status: Approved 之前，请勿创建账户。文档 →
POST /webhooks/didit匹配列表
// X-Signature-V2 verified upstream
if (payload.status === "Declined") {
  logCluster(payload.face_search.matches);
  blockSignup(payload.vendor_data);
} else if (payload.status === “审核中”) {
  queueForAnalyst(payload);
}
200OK状态：已批准 · 已拒绝 · 审核中 · 未完成
读取 payload 前，请验证 X-Signature-V2。文档 →
代理就绪集成

一键部署人脸搜索 1:N 女巫攻击检测。

粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent 中。填写您的技术栈。代理将连接工作流、打开会话、读取匹配列表并阻止重复项。
didit-integration-prompt.md
You are integrating Didit Face Search 1:N to catch the same human opening many accounts on your platform — sybil airdrops, referral payout cycles, sign-up bonus stacking, iGaming multi-accounting that bypasses self-exclusion, marketplace fake-review clusters. One API call. One signed webhook. One decision.

WHY THIS SHAPE
  - Email, phone, device, IP can all be rotated cheaply. A human face cannot.
  - Every new sign-up captures one Passive Liveness selfie. Didit searches that selfie against the gallery of prior approved selfies under your account. A high-similarity match means the same person already has an account.
  - Face Search 1:N itself is FREE on every session — no per-search fee. Only the surrounding bundle (ID + Passive Liveness + AML) carries the usual cost. Use the full Know Your Customer (KYC) bundle on sign-up or the Passive Liveness + Face Search subset, depending on what the product needs.

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.
  - A Workflow Builder workflow that contains the Face Search 1:N module. Compose it with Passive Liveness so an attacker cannot upload a still photo of the target.
  - Define what a "match" means for your product. Default: similarity ≥ 0.85 = Declined. 0.75–0.85 = In Review. < 0.75 = Approved.

STEP 1 — Open the sign-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 with Face Search 1:N + Passive Liveness>",
      "vendor_data": "<your new-account id, max 256 chars>",
      "callback": "https://<your-app>/sybil-gate/callback",
      "metadata": {
        "surface": "airdrop_claim",
        "campaign": "<your campaign id>"
      }
    }

  Response: 201 Created with a hosted session URL. Redirect inline (web) or open in a Software Development Kit (SDK) webview (mobile). The new account stays UNCREATED on your side until the signed webhook lands.

STEP 2 — Read the signed webhook
  Didit POSTs the verdict. Verify X-Signature-V2 (HMAC SHA-256 of the raw body) BEFORE reading the JSON.

  Payload (excerpted, match case):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your new-account id>",
      "status": "Declined",
      "face_search": {
        "matches": [
          { "session_id": "sess-9182", "similarity": 0.96, "vendor_data": "user-A1" },
          { "session_id": "sess-7733", "similarity": 0.94, "vendor_data": "user-A2" }
        ]
      }
    }

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

STEP 3 — Branch the sign-up
  Approved   → no gallery match. Create the account.
  In Review  → soft match (similarity in your grey-zone band). Queue for human review.
  Declined   → hard match (similarity above your hard threshold). Block, log the matched session_id list as the audit trail.

STEP 4 — Cross-account link signals (optional but cheap)
  Compose Device & IP Analysis ($0.03 / call) in the same workflow. The decision payload surfaces device fingerprint, IP, Autonomous System Number (ASN), country, and city. Combine with your own payment-instrument hash and you can cluster sybils even before the face search confirms.

STEP 5 — Reusable KYC for legitimate cross-product re-entry
  If the user is supposed to reuse one identity across multiple products you own, Reusable KYC lets them replay a previously verified credential at no cost. That is different from sybil abuse — reuse is intentional and you control the issuance.

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

WHAT IT BLOCKS
  - Sybil airdrop / token claims (one person · many wallets)
  - Self-referral payout cycles (sign-up bonus farms)
  - iGaming multi-accounting that bypasses self-exclusion
  - Marketplace fake-review clusters from a single human
  - DAO and community-vote stuffing
  - Welcome-bonus stacking on neobank / brokerage sign-ups

CONSTRAINTS
  - Session statuses use Title Case With Spaces. Never UPPER_SNAKE_CASE for session verdicts — that's the Transactions API.
  - Face Search 1:N WITHOUT Passive Liveness lets an attacker upload a still photo of the target. Always compose them together.
  - Thresholds are tunable per workflow. Start at 0.85 hard / 0.75 soft and adjust based on your false-positive tolerance.
  - The gallery is scoped to your account — no cross-customer leakage by design.

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

数据证明

数据证明
  • Free
    每次人脸搜索 1:N, 无按次收费。仅其周边捆绑服务收费。
  • <0s
    入门级 Android 设备上的端到端向量搜索判决。
  • iBeta L1
    每次自拍都进行被动活体检测, 无静态照片绕过。
  • 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 a sybil attack?

A sybil attack is when one human creates many accounts to pretend to be many humans. The name comes from a 1973 case study of a patient with dissociative identity disorder. In product terms it shows up as one person claiming an airdrop ten times, stacking ten sign-up bonuses, or stuffing a leaderboard with ten "different" wins.

The attack works because every other identifier, email, phone, device, Internet Protocol (IP) address, can be rotated for cents. The one identifier that cannot be cheaply rotated is the attacker's own face.

Why is email and phone defence not enough?

A sybil farmer in 2026 can buy:

  • 10,000 throwaway email aliases for under \$50
  • 10,000 Subscriber Identity Module (SIM) cards or virtual numbers for under \$200
  • A residential-proxy Virtual Private Network (VPN) subscription for under \$100 / month
  • A second-hand or virtualised device pool for a few hundred dollars

The whole operation pays back if a single sybilled airdrop or bonus is worth more than the kit. Face Search 1:N takes the face, the one thing the farmer cannot cheaply duplicate, and turns it into the unique key.

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 Face Search 1:N different from Face Match 1:1?

Different question, different math.

  • Face Match 1:1 asks "is this the same person as the one selfie I have on file?" Used at account-takeover step-up, where the comparison target is the user's own enrollment portrait.
  • Face Search 1:N asks "is this person already in my gallery of N enrolled humans?" Used at sign-up, to surface duplicates across all prior accounts.

The 1:1 check costs \$0.05 per match. Face Search 1:N is free per search, only the surrounding bundle (ID Verification, Passive Liveness) carries cost.

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 tune the match thresholds?

Face Search 1:N returns a similarity score between 0 and 1 per match. You set two thresholds per workflow:

  • Hard threshold (default 0.85): scores at or above → Declined. Auto-block the sign-up.
  • Soft threshold (default 0.75): scores between soft and hard → In Review. Queue for analyst.
  • Below soft: Approved. No duplicate found.

Start at the defaults. If you see too many false positives (real twins, real strong family resemblance), raise the hard threshold. If duplicates slip through, lower it. Tune in the Workflow Builder, no redeploy needed.

What does the recipe cost?

Two line items per new sign-up:

  • Passive Liveness: \$0.10 per check
  • Face Search 1:N: \$0.00 per search (free, no per-call fee)

Around \$0.10 per protected sign-up. Add Device & IP Analysis at \$0.03 if you want device + IP link signals for clustering. The first 500 verifications every month are free on every account.

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

Which industries run this recipe?

Anywhere multiplying accounts has economic value:

  • Web3 / crypto airdrops, to keep one human from claiming an allocation N times
  • Marketplace + creator-economy referral programs, to kill self-referral payout cycles
  • iGaming, to enforce self-exclusion that the user themselves requested
  • Fintech / neobank welcome bonuses, to prevent the same human stacking ten sign-up rewards
  • DAO / community voting, to make one-vote-per-human stick
  • Marketplace review systems, to kill 5-star clusters from one human

One integration, every surface.

Related

相关模块 + 工作流

身份与欺诈基础设施。

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

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