Skip to main content
Didit 融资 750 万美元，打造身份与欺诈基础设施
Didit
一人一票

一人一票。真实可信，而非空谈。

验证每位投票者都是真实、唯一的个体，并发现同一人重复投票的情况。每位投票者 $0.33，免费检测重复项。每月 500 次免费验证。

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

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

一幅电影般的深色抽象反女巫投票插画, 在纯黑色背景上，四个半透明的玻璃面板以3D透视浮动，由一条发光的Didit蓝色线条贯穿，并由四个发光的扫描支架框住。每个面板上都有一个微小的浅白色抽象图案，代表一人一票（投票箱、指纹环、计票符号、单个人形剪影）。

治理的责任

钱包不是人。人才是人。

一个人可以创建上百个钱包、邮箱或临时手机号。但这并不能证明他们是上百个不同的人。Didit 将投票与真实面孔和真实证件绑定, 免费的 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。$0.33 每位投票者。

反女巫身份验证并非单一检查，而是一套组合拳。对投票者进行 KYC，与现有群体进行比对，强制执行资格，签署审计包，并在下一轮中重复使用。
阅读文档获取 API 密钥
01 · 唯一投票者

一人一票，身份核实。

iBeta Level 1 反欺诈认证的 KYC 套件, 身份验证、被动活体检测、人脸 1:1 比对、AML 筛选。两秒内出结果，支持 220 多个国家/地区的 14,000 多种证件。
用户验证模块
02 · 重复检测

在您的用户群中进行 1:N 人脸搜索。

每次注册都会与所有之前注册的投票者进行比对。相似度超过阈值 → 在记录投票前阻止。免费，仅限于您的数据集。
Face Search 1:N
03 · 隐私保护

证明唯一性，不泄露其他信息。

投票平台仅能看到 `unique: true`、一个匿名 PID（假名标识符）、年龄段和地区。证件和生物识别数据保留在 Didit 内部，静态加密。符合 GDPR、ISO/IEC 27001、SOC 2 Type 1 标准。
身份隐私声明
04 · 可复用凭证

一次验证，处处投票。

可复用 KYC（免费，已包含）允许已验证的投票者在每次后续投票中仅通过自拍证明其唯一性, 无需重新捕获证件。适用于所有由 Didit 提供支持的平台。符合 eIDAS2 标准。
可复用 KYC
05 · 管辖区规则

每位投票者都具备区域资格。

国家白名单、最低年龄、制裁/PEP 排除、证件有效期、相似度阈值, 所有这些都在一个工作流中强制执行。在无代码工作流构建器中编辑规则，无需重新部署。
AML 筛选模块
06 · 审计包

加密投票完整性证明。

签名注册收据 (X-Signature-V2, HMAC SHA-256)、匿名投票者 PID、防篡改日志，默认保留 5 年。可导出到您的透明度门户或 DAO 的快照。
Webhook 文档
集成

一个会话。一个群体。一个签名裁决。

注册投票者。读取签名 Webhook。阻止重复。记录投票。
POST /v3/session/注册
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "workflow_id": "wf_voter_enrol",
    "vendor_data": "voter-12871",
    "metadata": { "cohort_id": "round-2026-05" }
  }'
201已创建返回托管会话 URL。2 秒内完成裁决。
在 webhook 返回 status: Approved 之前，阻止投票。文档 →
GET /v3/session/{sessionId}/decision/裁决
$ curl https://verification.didit.me/v3/session/$SID/decision/ \
  -H "x-api-key: $DIDIT_API_KEY"

# Returns:
{
  "status": "Approved",
  "face_search": { "matches": [] }
}
200OKstatus Approved · Declined · In Review · Resubmitted · Expired
匹配度高于 0.85 且非空 → 重复，阻止。文档 →
代理就绪集成

一键部署反女巫投票系统。

粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent 中。填写您的技术栈。代理将构建注册工作流，阻止重复项，签署裁决，并准备下一轮。
didit-integration-prompt.md
You are integrating Didit anti-Sybil identity into a voting / governance / survey / airdrop / quadratic-funding platform. The recipe ensures each real human can be counted exactly once — no duplicates, no bots, no farmed accounts.

Two pillars:

  1. Verify the voter is a real human with a real identity. ONE call to POST /v3/session/ with ID Verification + Liveness + Face Match.
  2. Check the voter has not already been enrolled in this cohort. Face Search 1:N runs the voter's face against every previously-enrolled voter and returns a similarity score. Above threshold → duplicate, block.

Cost:
  - Voter Know Your Customer (KYC) bundle: $0.33 per voter (Sessions API)
  - Face Search 1:N: free (included)
  - Re-vote / next round with Reusable KYC: free (the user proves uniqueness without re-doing KYC)
  - 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.
  - A workflow_id from the Workflow Builder that bundles ID Verification + Passive Liveness + Face Match 1:1 + Face Search 1:N + your jurisdiction rules (age, country, sanctions).

STEP 1 — Enrol the voter with the Sessions API

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<wf id with KYC + Face Search 1:N>",
      "vendor_data": "<your voter id, max 256 chars>",
      "callback": "https://<your-app>/vote/enrolment/callback",
      "metadata": {
        "purpose": "vote_enrolment",
        "cohort_id": "<your election / round / airdrop id>"
      }
    }

  Response: 201 Created with the hosted session URL. Redirect the voter to it. Sub-2-second median verdict on completion.

STEP 2 — Read the signed webhook on enrolment completion

  Didit POSTs to your callback. Session statuses are Title Case With Spaces:

  Body (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your voter id>",
      "status": "Approved",
      "id_verification": { "status": "Approved" },
      "liveness": { "status": "Approved" },
      "face": { "status": "Approved", "similarity_score": 0.94 },
      "face_search": { "status": "Approved", "matches": [] }
    }

  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.

STEP 3 — Block duplicates

  When face_search.matches is non-empty AND the top match's similarity is above your threshold (typical: 0.85), DO NOT add the voter to the cohort. The voter has likely been enrolled already, possibly under a different document or alias.

  Recommended handling:
    similarity ≥ 0.95  → block automatically, log the match
    similarity 0.85–0.95 → route to manual review
    similarity < 0.85  → enrol normally

STEP 4 — Privacy-preserving storage

  The platform stores ONLY:
    - voter_pid (pseudonymous identifier — a UUID, NOT the raw document number)
    - unique (boolean)
    - age_band (e.g. "18+", "25-34") — never the raw birth date unless your eligibility rule needs it
    - region (e.g. "EU", "ES") — never the raw address

  Documents, biometrics, and full names stay inside Didit, encrypted at rest. Default retention 5 years post-relationship; configurable per workflow.

STEP 5 — Read the decision on demand

  GET https://verification.didit.me/v3/session/{sessionId}/decision/
  Headers:
    x-api-key: <your api key>

  Returns the full decision JSON. Use this when the tally service needs to confirm a voter is still eligible at vote time.

STEP 6 — Reusable KYC for subsequent rounds

  Once a voter is verified, the next vote / round / airdrop can reuse the verification at no extra cost. The user proves uniqueness with a selfie only — no document re-capture. Same workflow, different cohort id.

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.
  - Face Search 1:N is scoped to YOUR cohort by default — Didit doesn't share faces across customers.
  - Always check the duplicate score BEFORE recording the ballot, never after.
  - The platform never sees the raw ID document or the raw face template — only the verdict and the pseudonymous PID.
  - Default record retention is 5 years post-relationship per the EU AML package; extend per your governing body's rules.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/sessions-api/retrieve-session
  - https://docs.didit.me/integration/webhooks
  - https://docs.didit.me/core-technology/reusable-kyc/overview

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
原生符合欧盟标准

证明数据

证明数据
  • $0.00
    每位投票者, 包含完整的 KYC 捆绑包，以及用户群内的 1:N 人脸搜索。
  • Free
    可重复使用的 KYC, 后续轮次只需通过自拍即可证明唯一性。
  • <0s
    每位投票者的端到端注册裁决，适用于入门级 Android 设备。
  • 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 the anti-Sybil problem, in plain English?

A Sybil attack is when one human pretends to be many, by spinning up wallets, email addresses, burner phones, or fake IDs, to game a system that counts each account as one vote, one entry, one share.

It shows up everywhere voting or scarcity matter:

  • DAO governance, a whale opens 1,000 wallets and skews every proposal
  • Airdrops, a farmer creates 50,000 accounts and drains the token allocation
  • Quadratic funding, fake identities multiply a single donor's matched funds
  • Citizen surveys and polls, coordinated brigading manufactures consent
  • Content-moderation votes, sock-puppet accounts swing what gets boosted or removed

The only durable defence is to bind each vote to a real human. That's what this recipe ships.

Why do wallets and email addresses fail as identity?

They prove control of a resource, not control of a body.

  • A wallet proves you hold a private key. You can hold a hundred private keys.
  • An email address proves you registered with an SMTP provider. SimpleLogin, gmail.com, and a thousand others mint addresses in seconds.
  • A phone number proves a SIM card. SIM farms and virtual-number providers sell them in bulk.
  • An IP address proves a network connection. VPNs, residential proxies, and datacenter pools rotate them on demand.

A face plus a government document is harder. There is exactly one face per body, and one valid government ID per face per country. Forging at scale costs orders of magnitude more than spinning up a wallet.

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 Face Search 1:N actually catch duplicates?

When a voter enrols, Didit creates a privacy-preserving face template (a vector, not the image) and compares it against every other voter template in your cohort. The output is a list of matches, each with a similarity score from 0 to 1.

A typical policy:

  • ≥ 0.95 similarity, almost certainly the same person, block automatically
  • 0.85 – 0.95, likely the same person, route to manual review
  • < 0.85, different person, enrol normally

The cohort is scoped to YOUR dataset, Didit does not share faces across customers. The template is encrypted at rest, never exposed to the voting platform, and falls under the privacy notice the user agreed to at enrolment.

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.

What about voters across multiple rounds, do they pay every time?

No. Once a voter is verified by Didit, Reusable KYC (free, included) lets them prove uniqueness on every subsequent round with a selfie only, no document re-capture.

In practice:

  • Round 1, full KYC bundle at $0.33
  • Round 2, 3, 4, …, the user opens a new session against the next cohort id, takes a selfie, and Didit re-matches against the original verified template. Free.

The credential is portable across every Didit-powered platform, aligned with eIDAS2 (the EU's digital-identity regulation). The voter owns the credential, they re-present it on demand, you never re-pay.

What does the audit trail look like for a regulator or a transparency portal?

Every enrolment produces a signed receipt you can export to your audit log or your DAO's transparency portal:

  • session_id, Didit's verifiable identifier for the enrolment
  • voter_pid, your pseudonymous voter id
  • verdict, Approved, Declined, In Review, etc. (status enum: Approved, Declined, In Review, Resubmitted, Expired, Not Finished, Kyc Expired, Abandoned)
  • cohort_id, which round / election / airdrop
  • signature, X-Signature-V2 HMAC SHA-256 of the payload with your webhook secret
  • timestamp

Pair with the on-chain attestation (if used) and you have a tamper-evident trail from "this real human enrolled" to "this ballot was cast". Default retention 5 years, extendable per your governing body's rules.

What does the integration look like for a small team?

Four steps, one afternoon:

  • Open the sandbox at business.didit.me, sandbox key in 60 seconds, no credit card
  • Build a workflow in the Workflow Builder that bundles ID + Liveness + Face Match + Face Search 1:N + your eligibility rules
  • Wire POST /v3/session/ to enrol voters and the signed webhook to receive verdicts
  • Block the ballot until the webhook says status: Approved and face_search.matches is empty (or below your threshold)

The Didit MCP (Model Context Protocol) server is included free, paste the integration prompt above into Claude Code, Cursor, Codex, Replit Agent, Devin, or Aider and the agent scaffolds the whole thing against the live /v3/ API.

Related

相关模块 + 工作流

身份与欺诈基础设施。

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

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