免费
免费
每月 $0。无需信用卡。
- 免费 KYC 套件（身份验证 + 被动活体检测 + 人脸匹配 + 设备与 IP 分析）, 每月 500 次，永久有效
- 黑名单用户
- 重复检测
- 每次会话 200+ 欺诈信号
- Didit 网络中可重复使用的 KYC
- 案件管理平台
- 工作流构建器
- 公开文档、沙盒、SDK、MCP（模型上下文协议）服务器
- 社区支持
全球2,000多家组织信赖。
经销商的职责
以您的品牌提供 KYC 服务。省去底层技术搭建。
在样式编辑器中配置颜色、字体、方形和矩形徽标以及您的自定义域名, 在每个工作流程中切换包含自定义样式。最终用户看到的是您的品牌、您的域名、您的流程；您将继承 Didit 提供的 iBeta Level 1 PAD（演示攻击检测）、西班牙 Tesoro / SEPBLAC 认证、SOC 2 Type 1 和 ISO/IEC 27001。每月免费 500 次验证。
工作原理
从注册到验证用户，仅需四步。
- 步骤 01
创建工作流
选择您需要的检查项, 身份、活体、人脸比对、制裁、地址、年龄、电话、电子邮件、自定义问题。在仪表板中将它们拖入流程，或将相同的流程发布到我们的 API。根据条件进行分支，运行 A/B 测试，无需代码。
- 步骤 02
集成
使用我们的 Web、iOS、Android、React Native 或 Flutter SDK 进行原生嵌入。重定向到托管页面。或者直接通过电子邮件、短信、WhatsApp 等任何方式向您的用户发送链接。选择适合您技术栈的方式。
- 步骤 03
用户完成流程
Didit 负责摄像头、灯光提示、移动设备切换和辅助功能。在用户进行流程时，我们实时评估 200 多个欺诈信号，并根据权威数据源验证每个字段。结果在两秒内得出。
- 步骤 04
您收到结果
实时签名 Webhook 可确保用户获得批准、拒绝或发送审核时，您的数据库立即同步。按需轮询 API。或者打开控制台检查每个会话、每个信号，并以您的方式管理案例。
01 · 样式编辑器
无需代码，轻松换品牌。
颜色、字体、方形 + 矩形 Logo、边框圆角，可选 Didit 登录界面开关。预览将显示在您专属的托管 UI 上，而非 Didit 界面。每个账户配置一次，应用于所有工作流。
白标模块Didit · Style Editor
Swap colours, type, logo.
Your brand
Verify your identity
- Brand colours
- Typography
- Square + rect logos
- Border radius
- Login screen on / off
02 · 自定义域名
托管在 verify.yourbrand.com。
CNAME 指向 verify.didit.me，TLS 证书通过 Let's Encrypt 自动配置，HSTS 默认启用。在业务控制台内验证, 您无需任何操作。
白标文档Didit · Custom domain
Host on your domain.
DNS record
typeCNAME
hostverify.yourbrand.com
targetverify.didit.me
ttl300 s
TLS · auto
issuerLet's Encrypt
statusActive
auto_renew30 days
hstsEnabled
Verified inside the Business Console · zero ops.
03 · SDKs · 五大平台
一个品牌。全平台适用。
相同的样式编辑器配置适用于 Web、iOS (Swift)、Android (Kotlin)、React Native (TurboModules) 和 Flutter。SDK 免费；白标费用涵盖所有平台的品牌化。
工作流编排器Didit · SDKs
One brand. Five surfaces.
- Web SDKReact, Vue, vanilla
- iOS · AndroidNative Swift + Kotlin
- React NativeTurboModules
- FlutterDart package
Same Style Editor config applies across all five.
04 · 按工作流配置品牌
一个账户，品牌与非品牌混合使用。
面向客户的工作流开启“包含自定义样式”，内部管理流程关闭。非常适合多品牌经销商, 一个 Didit 账户，多个终端客户品牌，按工作流配置样式。
工作流文档Didit · Workflow Builder
Per-workflow brand on / off.
WorkflowCustom styleOutcome
- wf_signup · consumerONPass
- wf_kyc_step_upONPass
- wf_internal_adminOFFPass
- wf_partner_b · resellerON · brand BPass
- wf_sandbox · debugOFFPass
Multi-brand on one account · ideal for resellers.
05 · 经销商定价
$0.53 cost in. You pick the sticker.
Didit KYC 套餐 $0.33 + 白标费 $0.20 = 每次检查成本 $0.53。您可以以 $0.99-$1.49 的价格转售给您的客户；保留利润。达到一定规模可享批量折扣, 请联系销售。
用户验证模块Didit · Reseller margin
Cost in. Price out.
LineAmountNote
- Didit KYC bundle$0.33Floor
- White-label fee+ $0.20Per check
- Your cost$0.53Total in
- Your sticker price$0.99 - $1.49Out
- Your margin · per check$0.46 - $0.96Net
Volume discount kicks in at scale. Talk to sales.
06 · 审计留痕
您的品牌。同样的合规标准。
iBeta Level 1 PAD、西班牙 Tesoro / SEPBLAC 认证、SOC 2 Type 1、ISO/IEC 27001、GDPR 合规、默认 5 年数据保留。品牌可换，底层合规标准不变。
AML 筛选模块Didit · Audit retained
Your brand. Same compliance.
- iBeta Level 1 PADSame liveness ceiling
- Tesoro · SEPBLACEU-government attested
- SOC 2 · ISO 27001Inherited by your stack
- 5-year retentionConfigurable upward
Sub-process disclosure available on request.
集成
一次会话。您的品牌。您的域名。
开启品牌会话。读取签名结果。终端用户全程不会看到 Didit。
POST /v3/session/品牌化
$ curl -X POST https://verification.didit.me/v3/session/ \
-H "x-api-key: $DIDIT_API_KEY" \
-d '{
"workflow_id": "wf_signup_branded",
"vendor_data": "end-user-42",
"metadata": { "tenant_id": "品牌B" }
}'201已创建在您的自定义域名上返回托管 URL。
通过样式编辑器和每个工作流的切换进行品牌化。无需更改 API。文档 →
GET /v3/session/{sessionId}/decision/裁决
$ curl https://verification.didit.me/v3/session/$SID/decision/ \
-H "x-api-key: $DIDIT_API_KEY"
# Returns:
{
"状态": "已批准",
"AML": { "状态": "已批准" }
}200OK状态：已批准 · 已拒绝 · 审核中 · 已重新提交 · 已过期
无论您如何品牌化 UI，都使用相同的 /v3/ 合同。文档 →
代理就绪集成
一键发布白标 KYC 产品。
粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent 中。填写您的品牌 + 域名 + 工作流模块。代理将配置样式编辑器，连接签名 webhook，并发布品牌化流程。
didit-integration-prompt.md
You are integrating Didit white-label KYC. You're either reselling identity verification to your own customers under your brand, or embedding KYC inside your SaaS product so the end-user never sees Didit. Either way, the verification stack is Didit's; the visible brand is yours.
Three pillars:
1. Configure your brand once in the Style Editor — colours, typography, square + rectangular logos, optional custom domain.
2. Toggle Include custom style ON for every workflow that should ship under your brand. Leave it OFF for internal admin flows.
3. Open POST /v3/session/ as usual. The hosted UI returns under your brand on your domain.
Cost:
- Didit KYC bundle: $0.33 per check (Sessions API floor)
- White-label fee: $0.20 per check (adds branding + custom domain + per-workflow style toggle)
- Reseller cost in: $0.53 per check
- Mark up to your buyer as you choose — published rate at scale, custom contracts above 100k/month
- First 500 verifications free every month, forever
PRE-REQUISITES
- Production API key from https://business.didit.me (sandbox key in 60s, no card).
- White-label add-on enabled on your account (talk to sales to switch it on).
- 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 the modules you ship (typically ID Verification + Passive Liveness + Face Match 1:1 + AML Screening) with Include custom style ENABLED.
- Optional: custom domain (e.g. verify.yourbrand.com) configured in the Business Console — Didit handles the CNAME target + TLS cert via Let's Encrypt.
STEP 1 — Configure brand in the Style Editor (no code)
Console → White Label → Style Editor:
Colors: buttons, text, panels, backgrounds
Typography: fonts that match your brand
Logos: square + rectangular uploads
Layout: border radius for panels and buttons
Login: show or skip the Didit login screen
Domain: add verify.yourbrand.com (CNAME target = verify.didit.me; TLS auto-provisioned)
STEP 2 — Enable custom style on the workflow
Console → Workflows → <your workflow> → Settings → Options:
Toggle Include custom style ON. Without this, the workflow ships with default Didit branding.
Repeat per workflow. You can mix branded + unbranded workflows on the same account — useful for an internal admin flow that doesn't need the customer brand.
STEP 3 — Open a session as usual
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<wf id with Include custom style ON>",
"vendor_data": "<your end-user id, max 256 chars>",
"callback": "https://<your-app>/kyc/callback",
"metadata": {
"purpose": "white_label_onboarding",
"tenant_id": "<your reseller tenant id if multi-brand>"
}
}
Response: 201 Created with the hosted session URL — under YOUR domain if you set one. Sub-2-second median verdict on completion.
STEP 4 — Read the signed webhook on completion
Didit POSTs to your callback. Session statuses are Title Case With Spaces:
Body (excerpted):
{
"session_id": "<uuid>",
"vendor_data": "<your end-user id>",
"status": "Approved",
"id_verification": { "status": "Approved" },
"liveness": { "status": "Approved" },
"face": { "status": "Approved", "similarity_score": 0.94 },
"aml": { "status": "Approved", "hits": [] }
}
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.
On Approved → onboard the end-user. On Declined → reject. On In Review or Resubmitted → hold + route to your compliance team.
STEP 5 — Multi-brand on one account (reseller pattern)
When you serve multiple end-customer brands from a single Didit account:
- Create one workflow per end-customer brand
- Configure each workflow with the customer's brand style (or use the Style Editor presets per workflow if your account supports it)
- On POST /v3/session/, pick the workflow_id that matches the end-customer's brand
The end-customer sees their own brand; you see one consolidated invoice per month. Didit's MCP (Model Context Protocol) server is included free for programmatic per-tenant workflow management.
STEP 6 — Audit + compliance retained
Swapping the brand does not change the underlying compliance bar. Every session is still:
- iBeta Level 1 PAD (Presentation Attack Detection) certified on liveness
- Backed by Spain's Tesoro / SEPBLAC attestation (only EU member-state government attestation of safer-than-in-person verification)
- Aligned with SOC 2 Type 1 + ISO/IEC 27001 + GDPR (General Data Protection Regulation)
- Logged with X-Signature-V2 webhook signing on every event
- Retained 5 years post-relationship by default per the EU Anti-Money-Laundering package; configurable upward per your supervisor's guidance
Sub-processor disclosure available on request for your DPA (Data Processing Agreement).
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.
- The white-label add-on is a per-account feature — talk to sales to enable it. Once enabled, the Style Editor + custom-domain pipeline is no-code.
- Custom domain TLS auto-renews 30 days before expiry. Monitor the cert status in the Console.
- Some end-user browsers (mobile in-app webviews) constrain custom domains — keep verify.didit.me as a fallback for these edge cases.
Read the docs:
- https://docs.didit.me/console/white-label
- https://docs.didit.me/console/workflows
- https://docs.didit.me/sessions-api/create-session
- 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
原生符合欧盟标准
数据证明
数据证明
- $0.00每次检查成本, $0.33 KYC 套餐 + $0.20 白标费。您可以向买家加价。
- 0 SDKsWeb、iOS、Android、React Native、Flutter, 全部采用相同品牌。
- Per WF包含自定义样式切换, 同一账户下可使用品牌化和非品牌化工作流。
- 0每个账户每月免费验证。
三个层级，一份价目表
免费开始。按使用量付费。可扩展至企业级。
每月 500 次免费验证，永久有效。生产环境按量付费。企业版提供定制合约、数据驻留和 SLA (Service Level Agreements)。
最受欢迎
按用量付费
按用量计费
按实际用量付费。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 a white-label KYC, in plain English?
It's an identity-verification product that runs under your brand, your colours, your logo, your domain, but uses someone else's verification stack under the hood. The end-user never sees the underlying vendor.
Two flavours you can ship:
- Reseller, your business is identity verification (or a vertical wrapper of it). You charge customers a per-check rate that's higher than your cost, and the margin is the business model. Common for SaaS aggregators, niche compliance plays, regional resellers in markets the big vendors don't serve well.
- Embedded, you're a SaaS / fintech / platform whose product includes KYC as one feature among many. You don't want your end-users to bounce into a Didit-branded flow mid-onboarding; you want the verification to feel like part of your product.
The Didit recipe handles both with the same Style Editor + per-workflow toggle.
What can I actually customise?
Six categories, all no-code via the Business Console Style Editor:
- Colours, buttons, text, panels, backgrounds. Every colour element is a token.
- Typography, fonts that match your brand. Upload custom font files or pick from a curated list.
- Logos, square and rectangular logo uploads. Used on hosted screens, in-app SDK headers, and email confirmations.
- Layout, border radius for panels and buttons. Match your design language (sharp corners or rounded).
- Login screen, show or skip the Didit login screen at session start.
- Custom domain, host on
verify.yourbrand.cominstead ofverify.didit.me. CNAME + TLS handled inside the Console.
The Style Editor previews live as you change tokens. Once you save, toggle Include custom style on the workflow you want branded, that's the activation gate.
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.
Does the white-label cover the SDKs too?
Yes. The same Style Editor configuration applies across all five Didit SDKs, Web (React, Vue, vanilla JS), iOS (Swift), Android (Kotlin), React Native (TurboModules), and Flutter (Dart). The SDKs are free; the white-label fee covers branding across every surface.
In practice: you set colours, type, logos, and radius once. The SDK reads the same brand config from your account, the hosted flow reads the same config, and your end-user gets a consistent branded experience whether they're in a mobile app, a webview, or a desktop browser.
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.
Do I keep the underlying compliance attestations?
Yes. Swapping the brand does not change the underlying compliance posture:
- iBeta Level 1 PAD, Didit's Passive Liveness is iBeta Level 1 certified, meaning it has been independently tested against printed photos, screen replays, masks, and deepfakes
- Tesoro / SEPBLAC, Didit is the only identity provider formally attested by Spain's Tesoro (under SEPBLAC, Spain's financial-intelligence unit) as a safer-than-in-person verification mechanism, for purposes of the EU Anti-Money-Laundering package
- SOC 2 Type 1, independent audit of Didit's security controls
- ISO/IEC 27001, international security-management standard
- GDPR alignment, General Data Protection Regulation by design (data minimisation, lawful basis, DSAR support)
Under your white-label, all of these flow through to your customer. Didit provides sub-processor disclosure on request for your DPA (Data Processing Agreement).
How does this fit with Didit's MCP server and the Workflow Builder?
Both are free, both work with the white-label add-on.
- Workflow Builder, drag-and-drop composer for KYC + AML + KYB + Wallet Screening modules. Per-workflow Include custom style toggle lives here. Edit rules and module selection without redeploying your app.
- Didit MCP (Model Context Protocol) server, exposes the same Didit primitives to AI coding agents (Claude Code, Cursor, Codex, Replit Agent, Devin, Aider). Useful for a small reseller team that wants to automate per-tenant workflow provisioning, branded-flow templating, or scripted onboarding tests.
The net: you don't need a large engineering team to ship a white-label KYC product. The Style Editor handles brand, the Workflow Builder handles modules, the MCP server handles automation, and the /v3/ API handles the verification itself.
How fast can a small team launch?
Four wires, one afternoon for a vertical-slice; a week for production:
- Open
business.didit.me, sandbox key in 60 seconds, no credit card - Enable the white-label add-on (talk to sales) and open the Style Editor, configure brand, upload logos, add custom domain (CNAME at your DNS provider)
- Build the workflow in the Workflow Builder with the modules you ship (typically ID + Liveness + Face Match + AML), toggle Include custom style ON
- Wire
POST /v3/session/+ the signed webhook (X-Signature-V2HMAC SHA-256) into your onboarding flow
For a multi-tenant reseller, add: one workflow per end-customer brand, per-tenant Style Editor configuration, a routing layer that picks the right workflow_id per inbound request. The MCP server scripts these end-to-end.