Skip to main content
Didit 融资 750 万美元,打造身份与欺诈基础设施
Didit
白标

您的品牌
我们的基础设施。

在您的域名下运行验证流程,使用您的 Logo、您的颜色和您的发件人, 用户看到的任何地方都没有 Didit 品牌。在模块价格之上,每次会话 $0.20。

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

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

Didit 白标, 在您自己的品牌和域名下运行验证流程。

您的品牌,我们的判断

自定义域名。
自定义 UI。自定义 Logo。

在您的域名下托管流程。替换 Logo、颜色、文案和链接 预览卡片。模块定价不变, 每次会话 $0.20 是唯一附加费用。

工作原理

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

  1. 步骤 01

    创建工作流

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

  2. 步骤 02

    集成

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

  3. 步骤 03

    用户完成流程

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

  4. 步骤 04

    您收到结果

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

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

六大功能。一次配置。您的品牌

以下所有功能都是控制台设置, 无需额外套餐,无需单独调用。您可以为每个工作流切换这些功能,并发布一个完全品牌化的流程,而无需修改您的代码库。
01 · 自定义域名

在您的子域名上托管流程。而非我们的。

在 `verify.acme.com` 而非 `verify.didit.me` 上运行验证 UI。我们提供 DNS 目标,您指向它,证书自动配置。几分钟内即可上线, 无需采购证书,无需密钥轮换。
02 · 品牌化

Logo、颜色、字体。每个可见界面。

支持方形和矩形 Logo。按钮、文本、面板和背景均可使用完整调色板。品牌字体、可配置的圆角半径、登录界面可开启或关闭。在控制台中实时预览并编辑所有内容, 无需工程师介入。
03 · 自定义发件人邮箱

每个流程中邮件都来自您的品牌。

一次性设置您的发件人姓名和回复地址。我们提供 DKIM 和 SPF 记录供您的安全团队添加,Didit 发送的每封邮件都将以您的品牌从您验证过的域名发出, 发件人、主题或页脚中均无 Didit 字样。
04 · 品牌移除

用户看到的任何地方都没有 Didit Logo。

每个捕获、同意、加载、成功和错误界面都带有您的 Logo。浏览器标签页标题、收藏夹图标和 URL 都是您的。唯一提及 Didit 的地方是隐私声明中法律要求的披露链接, 无论品牌如何,数据保护法都强制要求。
05 · 证书

TLS 自动配置。自动续订。永久有效。

我们处理每个自定义域名的证书生命周期, 自动续订、自动轮换、无按域名收费、收件箱中无过期提醒。根据您的租户数量添加任意子域名。每个子域名都在相同的固定附加费用下获得自己的证书。
06 · 经销商定价

附加费 `$0.20`。一份合同。一张发票。

在模块价格基础上,每会话固定收取 `$0.20`, 一个完整的 KYC 套餐从 `$0.33` 变为 `$0.53`。无论您运行多少租户,每月 500 次免费验证仍计入您的用量。与产品合规咨询公司和集成商转售给其客户的定价相同。
集成

一次配置。一次调用。您的品牌。

白标是一个控制台设置,而不是一个独立的端点。在样式编辑器中配置一次,然后像调用任何其他 Didit 流程一样调用工作流。相同的 JSON,相同的 Webhook,您的品牌出现在每个屏幕上。
控制台 · 样式编辑器无需代码
# 控制台 -> 白标 -> 样式编辑器
colors: 品牌调色板
logos: 方形 + 矩形
typography: 品牌字体 + 字重
domain: verify.acme.com
发件人邮箱: verify@acme.com

# 工作流 -> 设置 -> 选项
包含自定义样式: true
已保存实时预览您的品牌 · `verify.acme.com` · TLS 自动
一次配置。在每个工作流上切换 include_custom_style文档 →
POST /v3/session/相同 API
$ 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_acme_kyc",
    "vendor_data": "user-42"
  }'
201已创建{ "session_url": "verify.acme.com/..." }
相同的调用,相同的 JSON。session_url 位于您的域名下。文档 →
代理就绪集成

一键部署白标方案。

将以下代码块粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent 中。填写您的技术栈(框架、语言、用例),代理将配置样式编辑器、指向自定义域名并切换每个工作流的开关。
didit-integration-prompt.md
# Didit White Label — integrate in 5 minutes

You are integrating Didit's White Label (custom branding + custom domain)
into <my_stack>. White Label is a CONFIGURATION on top of any workflow —
not a separate API endpoint. Follow these steps exactly. Every URL,
header, and field 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. Configure White Label in the console
White Label settings live at Console -> White Label -> Style Editor. Five
groups, every one is customizable:

- Colors           — buttons, text, panels, backgrounds (every color element)
- Typography       — upload a brand font, set heading + body weights
- Logos            — square + rectangular variants, served on every screen
- Layout           — border radius for panels, buttons, inputs
- Login screen     — show or skip the user-login step entirely
- Custom domain    — host the verification UI on your own subdomain
                     (e.g. verify.acme.com) instead of verify.didit.me

Custom-domain setup:
1. Console -> White Label -> Custom Domain -> Add domain
2. We return a CNAME target. Point your subdomain CNAME at it.
3. Click Verify. We provision a TLS certificate via Let's Encrypt /
   ACME (automatic renewal, no action required from you).
4. Domain becomes live within minutes.

Custom email-from:
- Console -> White Label -> Email -> set the "From" name + reply-to address.
- DKIM / SPF records returned for you to add to DNS.

## 3. Enable White Label on each workflow
The customization does NOT auto-apply. You enable it per workflow:

1. Console -> Workflows -> open the workflow you want to brand.
2. Click Settings (gear icon).
3. Under Options, find "Include custom style".
4. Enable the toggle. Save.

Workflows without the toggle keep the default Didit branding — useful for
sandbox flows you do not want to brand yet.

## 4. Use the white-labeled workflow from your stack
Once the workflow has white-label enabled, you call it the same way as any
other Didit workflow:

POST https://verification.didit.me/v3/session/
Authorization header:  x-api-key: <your-api-key>
Body:
  - workflow_id   (required, your white-labeled workflow id)
  - vendor_data   (optional, your own user id)
  - callback      (optional, URL we redirect to after the flow)

Response: { session_url } — redirect the user there. The UI they see is
your brand (your logo, your colors, your typography), on your domain
(verify.acme.com), with your "From" name on every email we send to the
user mid-flow.

## 5. Webhooks
- 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", "session.kyc_expired"]
- 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.

## 6. Hard rules - do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Auth header is x-api-key (lowercase, hyphenated).
- Webhook signature header is X-Signature-V2 (NOT X-Signature).
- Status casing matches exactly: "Approved", "Declined", "In Review",
  "Not Finished" (title-cased, space-separated).
- White Label is a configuration on a workflow — there is NO standalone
  /v3/white-label/ endpoint. Do not invent one.
- Removing visible Didit branding does NOT remove your obligations as the
  controller of the user journey. You still surface your privacy notice,
  link Didit's Verification Privacy Notice + End User Terms, and collect
  explicit consent before document + biometric capture where the law
  requires it. See https://docs.didit.me/console/white-label for the full
  controller-side checklist.

## 7. Reseller / OEM positioning
White Label is the same product your agency, integrator, or compliance-
consulting firm uses to resell Didit under your own name to your own
customers:

- Pricing: $0.20 per session on top of the underlying module price (e.g.
  full Know Your Customer (KYC) bundle at $0.33 + $0.20 white label = $0.53 per session, or
  standalone ID at $0.15 + $0.20 = $0.35).
- 500 free verifications per month stay applied to your own meter,
  regardless of how many resold tenants you have.
- One contract with Didit, one invoice — your customers see only your
  brand and your support address.
- Custom email-from + custom domain mean your customers never see Didit
  branding mid-flow. We still surface the legally-required disclosures
  per the controller-side checklist above.

## 8. Pricing reference (public)
- White Label add-on: $0.20 per session, on top of the underlying module
  price. A full KYC bundle goes from $0.33 to $0.53 per white-labeled
  session; a standalone $0.15 ID Verification goes to $0.35.
- 500 free verifications every month, forever, on every account — applies
  regardless of whether the flow is white-labeled.
- No setup fee, no certificate cost, no per-domain charge.

## 9. Verify your integration
- Sandbox starts on signup at https://business.didit.me - no separate flag.
- Test custom domain locally by adding a /etc/hosts entry pointing your
  brand subdomain at our CNAME target before DNS is live.
- Switch to live: flip the application's environment toggle in console.

When in doubt: https://docs.didit.me/console/white-label
需要更多上下文?请参阅完整的模块文档。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
    每个白标会话,在模块价格之上。
  • 0
    任何用户可见界面上的 Didit 标志。
  • minutes
    从 DNS 指向到实时自定义域名。
  • 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 White Label?

White Label runs the entire Didit verification flow under your brand, your custom domain (verify.acme.com), your logo, your color palette, your typography, your email sender, your favicon. Zero Didit branding visible to your users.

Same /v3/ Application Programming Interface (API). Same hosted capture flow. Same X-Signature-V2 Hash-based Message Authentication Code (HMAC) webhook contract. Same Spain Tesoro / Banco de España (BdE) / Spanish Financial Intelligence Unit (SEPBLAC)-attested pipeline underneath.

$0.20 per session on top of the underlying module price. Full reference: docs.didit.me/console/white-label.

What does White Label cost?

$0.20 per session, on top of the underlying module price.

  • A full Know Your Customer (KYC) bundle goes from $0.33 to $0.53 per white-labeled session.
  • A standalone $0.15 Identity Document Verification goes to $0.35.

No setup fee, no certificate cost, no per-domain charge. Public pricing: didit.me/pricing.

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 the custom-domain setup work?

Three minutes, zero certificate work.

1. In the Business Console go to White LabelCustom DomainAdd domain. 2. We return a Canonical Name (CNAME) target. 3. Point your brand subdomain CNAME at it. 4. Click Verify.

We provision a Transport Layer Security (TLS) certificate via Let's Encrypt and the Automatic Certificate Management Environment (ACME) protocol, set up automatic renewal, and the domain goes live within minutes.

No certificate procurement, no key rotation, no Domain Name System (DNS) round-trip with your security team. Renewal is automatic for the lifetime of the domain.

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 总结此页面