免费
免费
每月 $0。无需信用卡。
- 免费 KYC 套件（身份验证 + 被动活体检测 + 人脸匹配 + 设备与 IP 分析）, 每月 500 次，永久有效
- 黑名单用户
- 重复检测
- 每次会话 200+ 欺诈信号
- Didit 网络中可重复使用的 KYC
- 案件管理平台
- 工作流构建器
- 公开文档、沙盒、SDK、MCP（模型上下文协议）服务器
- 社区支持
全球2,000多家组织信赖。
MiCA 的要求
验证用户。筛选钱包。保留证据。
每个欧盟加密平台都必须大规模地对每位客户执行这三项操作。 Didit 将它们整合为一个工作流程，每次检查仅需 $0.33，每月免费提供 500 次。
工作原理
从注册到验证用户，仅需四步。
- 步骤 01
创建工作流程
选择您需要的检查项, 身份、活体、人脸匹配、制裁、地址、年龄、电话、电子邮件、自定义问题。在仪表板中将它们拖入流程，或通过我们的 API 发布相同的流程。根据条件进行分支，运行 A/B 测试，无需代码。
- 步骤 02
集成
使用我们的 Web、iOS、Android、React Native 或 Flutter SDK 进行原生嵌入。重定向到托管页面。或者直接通过电子邮件、短信、WhatsApp 等任何方式向您的用户发送链接。选择适合您技术栈的方式。
- 步骤 03
用户完成流程
Didit 负责托管摄像头、灯光提示、移动设备切换和辅助功能。当用户在流程中时，我们实时评估 200 多个欺诈信号，并根据权威数据源验证每个字段。两秒内即可获得结果。
- 步骤 04
您收到结果
实时签名 Webhook 可确保用户获批、拒绝或发送审核的瞬间，您的数据库保持同步。按需轮询 API。或者打开控制台检查每个会话、每个信号，并按您的方式管理案例。
Didit · MiCA bundle
One session. Five checks.
Step 3 / 5
Hold still for liveness
- ID Verification$0.15
- Passive Liveness$0.10
- Face Match 1:1$0.05
- Device & IP Analysis$0.03
- AML Screening$0.20
Didit · AML
Sanctions · PEP · adverse media.
HitSource listScoreStatus
- OFAC SDN, Specially Designated NationalOFAC96Block
- PEP · Foreign government officialDow Jones PEP78Review
- Adverse media, financial sanctionEU adverse41Pass
14 languages · daily delta refresh$0.20 / check
03 · 钱包筛选
资金到账前，对每笔存款进行评分。
识别受制裁钱包、混币器、被盗资金。每次检查 $0.15，或使用您自己的提供商密钥仅需 $0.02。支持 EVM、Bitcoin、TRON、Solana。
钱包筛选模块Didit · Wallet Screening
Score every deposit. Block what doesn't belong.
AddressCategoryScoreAction
- 0x6c2b…f49aSanctioned98Block
- bc1q9a…0vw3Mixer84Review
- 0xa11e…12ccExchange · high risk62Review
- 0x2dc1…81f9Clean8Pass
$0.15 managed · $0.02 BYOKEVM · BTC · TRON · SOL
$0.07 / user / year
Catch sanctions drift after onboarding.
- user_42New PEP hit · Tier 2today · 09:14
- user_117Sanctions list updated · still Approvedtoday · 03:00
- user_31Adverse media · score 28 → 12yesterday
- user_88Re-screen complete · no changeyesterday
Hits open a case + fire a webhook automatically.
05 · 欧盟认证
唯一获得欧盟政府认证的KYC平台。
西班牙财政部、西班牙银行和 SEPBLAC 联合证明 Didit 比面对面验证更安全。下载报告并将其与您的 MiCA 第 16 条文件包一起提交。
安全与合规Spain · Tesoro / Banco de España / SEPBLAC
EU-attested verification depth.
The only KYC (Know Your Customer) platform formally attested by an EU member-state government as safer than in-person verification.
- Tesoro
- Banco de España
- SEPBLAC
Report downloadable from your Business Console.
EU Crypto-Asset Service Providers
Same MiCA bundle. Every CASP archetype.
- Spot exchangesListing + trade flow
- On-rampsFiat → crypto deposits
- Custodial walletsAccount-level CDD
- Tokenisation / RWAInvestor verification
Article 60 audit pack, every CASP archetype.
集成
一次调用。一个 Webhook。外加监控。
一次调用即可开启会话。从 Webhook 读取签名结果。将已批准的用户纳入监控。
POST /v3/session/MiCA
$ 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_mica_user_verification",
"vendor_data": "user-42",
"metadata": { "purpose": "mica_onboarding" }
}'201已创建{ "session_url": "verify.didit.me/..." }
在签名 webhook 返回
status: Approved 之前，阻止存款。文档 →POST /webhooks/didit裁决
// X-Signature-V2 verified upstream
if (payload.status === "Approved") {
unlockDeposits(payload.vendor_data);
enrollOngoingAml(payload.id_verification);
} else if (payload.status === "Declined") {
logHits(payload.aml.hits);
blockAndReview(payload.vendor_data);
}200确定状态：已批准 · 已拒绝 · 审核中
读取 payload 前，验证
X-Signature-V2。文档 →代理就绪集成
一键部署 MiCA 合规入驻流程。
粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent。填写您的技术栈。AI 代理将构建工作流，限制存款，注册监控，并预检查钱包。
didit-integration-prompt.md
You are integrating Didit's MiCA-aligned crypto user-verification workflow. MiCA is the EU's crypto rulebook; a regulated Crypto-Asset Service Provider (CASP) owes three things on every new customer:
1. Customer Due Diligence (CDD) — verify identity, screen for sanctions, file the evidence.
2. Ongoing monitoring — re-screen approved users as watchlists update.
3. Wallet screening for any crypto outflow — score the destination address before the transfer.
Didit ships all three on one workflow:
- KYC bundle at $0.33 per user (Sessions API)
- Continuous AML monitoring at $0.07 per user per year (automatic on any session with AML enabled)
- Wallet screening at $0.17 per crypto transaction managed, or $0.04 BYOK (Transactions API)
- 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 bundling ID Verification + Passive Liveness + Face Match 1:1 + Device & IP Analysis + AML Screening.
- Transaction Monitoring enabled in the Business Console (Transactions > Settings) with crypto screening on, if you handle crypto outflows.
STEP 1 — Verify the user 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 + AML modules>",
"vendor_data": "<your user id>",
"callback": "https://<your-app>/casp/kyc/callback",
"metadata": {
"purpose": "mica_onboarding",
"casp_reference": "<your internal reference>"
}
}
Response: 201 Created with a hosted-flow URL. Redirect the user. Sub-2-second median verdict.
STEP 2 — Read the signed webhook on KYC completion
Didit POSTs to your callback. Session statuses are Title Case With Spaces.
Body (excerpted):
{
"session_id": "<uuid>",
"vendor_data": "<your user id>",
"status": "Approved",
"id_verification": { "status": "Approved" },
"liveness": { "status": "Approved" },
"face": { "status": "Approved", "similarity_score": 0.94 },
"ip_analysis": { "status": "Approved" },
"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.
STEP 3 — Continuous AML monitoring is automatic
Every approved user is re-screened daily against the same 1,300+ sanctions, PEP, and adverse-media lists used at onboarding. There is NO separate endpoint to call.
When a previously-clean user crosses a threshold, the session status updates to "In Review" or "Declined" and your webhook fires the same payload shape as the original onboarding event with the new AML hits. A case opens automatically in the Business Console.
STEP 4 — Wallet screening on crypto outflows (Transactions API)
Required only if you transfer crypto on behalf of the user. Run BEFORE the crypto leaves.
POST https://verification.didit.me/v3/transactions/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body (required fields verified live):
{
"transaction_id": "<your internal reference>",
"transaction_category": "finance",
"include_crypto_screening": true,
"transaction_details": {
"direction": "OUTBOUND",
"amount": "0.25",
"currency": "ETH",
"currency_kind": "crypto",
"action_type": "withdrawal"
},
"subject": {
"entity_type": "individual",
"vendor_data": "<your user id>",
"full_name": "<user full name>"
},
"counterparty": {
"entity_type": "unhosted_wallet",
"full_name": "<destination wallet label>",
"payment_method": {
"method_type": "crypto_wallet",
"account_id": "<destination wallet address>"
}
}
}
REQUIRED fields the API rejects if missing:
- subject.vendor_data + subject.full_name
- counterparty.full_name
- transaction_details.direction + currency + currency_kind + amount
- For crypto: wallet address on counterparty.payment_method.account_id (OUTBOUND) or subject.payment_method.account_id (INBOUND post-transfer)
Wallet screening runs server-side when currency_kind = "crypto" and there is a wallet address in the right participant. No separate endpoint.
Transaction status enum (exact case, UPPER_SNAKE_CASE): APPROVED | IN_REVIEW | DECLINED | AWAITING_USER.
When a transaction enters AWAITING_USER, Didit creates a linked remediation session automatically and returns a verification URL on the response.
Branch logic:
APPROVED → ship the crypto.
IN_REVIEW → hold, route to analyst queue.
DECLINED → block, refund, log.
AWAITING_USER → redirect the user to the remediation session URL.
WEBHOOK EVENT NAMES
- Sessions: status changes flow through the standard session webhook.
- Transactions: transaction.created · transaction.updated · transaction.status.changed · transaction.alert.generated.
Verify X-Signature-V2 on every payload.
EVIDENCE + RECORD RETENTION
Every approved user comes with a signed evidence pack (document, biometric match, AML hits, device + IP) stored in the EU. Default retention 5 years post-relationship; configurable per workflow.
Didit holds the only formal EU-government attestation for a KYC platform — issued jointly by Spain's Tesoro, Banco de España, and SEPBLAC. The report files directly into the MiCA evidence pack.
CONSTRAINTS
- Session statuses use Title Case With Spaces (Approved, In Review). Transaction statuses use UPPER_SNAKE_CASE (APPROVED, IN_REVIEW). Don't mix them in the same code path.
- Default record retention is 5 years post-relationship; extend per your supervisor's guidance.
- 200+ fraud signals are evaluated on every KYC session at no extra cost — surface the score via the session decision payload.
Read the docs:
- https://docs.didit.me/sessions-api/create-session
- https://docs.didit.me/core-technology/aml-screening/overview
- https://docs.didit.me/transaction-monitoring/aml-screening
- 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
原生符合欧盟标准
证明数字
数据证明
- EU-attested唯一获得欧盟政府（西班牙财政部、西班牙银行和 SEPBLAC）认可的 KYC 平台。
- 0+对每位用户进行制裁、政治公众人物 (PEP) 和负面媒体名单筛选。
- <0s入门级 Android 设备上的端到端会话结果。
- 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 is MiCA, in one sentence?
MiCA, Regulation (EU) 2023/1114, the Markets in Crypto-Assets Regulation, is the European Union's first uniform rulebook for crypto-asset issuance, public offerings, admission to trading, and the services around them. It replaces 27 different national Virtual Asset Service Provider (VASP) regimes with one harmonised licence valid across the entire EU single market.
Supervision is layered:
- Each member state's National Competent Authority (NCA) issues the licence and runs day-to-day supervision
- The European Securities and Markets Authority (ESMA) publishes Level 2/3 standards and supervises significant CASPs
- The European Banking Authority (EBA) supervises significant stablecoin issuers and writes Anti-Money Laundering (AML) guidance
Didit ships every piece a Crypto-Asset Service Provider (CASP) needs to satisfy MiCA's customer-due-diligence, ongoing-monitoring, and evidence-retention duties, one workflow, $0.33 per user, 500 verifications free every month, integrate in 5 minutes.
Which crypto businesses are in scope?
Any business offering one of the ten CASP services defined in Article 3(1)(15) to EU clients:
- Custody and administration of crypto-assets on behalf of clients
- Operation of a trading platform for crypto-assets
- Exchange of crypto-assets for funds (on/off-ramp)
- Exchange of crypto-assets for other crypto-assets
- Execution of orders for crypto-assets on behalf of clients
- Placing of crypto-assets
- Reception and transmission of orders
- Advice on crypto-assets
- Portfolio management of crypto-assets
- Transfer services for crypto-assets on behalf of clients
In practice that captures centralised exchanges, on/off-ramps, custodial wallets, brokers, OTC desks, advisory services, payment institutions handling crypto, and tokenisation platforms. Truly decentralised protocols with no identifiable operator and pure peer-to-peer transfers sit outside the regime.
Didit customers across the MiCA perimeter: AhoraCrypto (Bank-of-Spain-registered on/off-ramp), GBTC Finance (exchange + 20+ physical stores), TucanPay (EU↔LatAm payments), Agape Smart Money (international money transfers in 30+ countries). Same workflow, same /v3/ API, different deposit + trade flows downstream.
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 MiCA different from 6AMLD and the EU Travel Rule?
Three regulations, three jobs, all of them apply to a CASP at once:
- MiCA, Regulation (EU) 2023/1114. Conduct regulation. Licenses the crypto business; sets capital, governance, custody, market-abuse, and disclosure duties.
- The EU AML package, Directive (EU) 2018/1673 (AMLD6) + the new Anti-Money-Laundering Regulation (EU) 2024/1624 + the new AMLA Regulation (EU) 2024/1620. Anti-money-laundering / counter-terrorist-financing. Sets Customer Due Diligence (CDD), Politically Exposed Persons (PEP) checks, sanctions screening, Suspicious Activity Reports (SARs), ongoing monitoring.
- The TFR, Regulation (EU) 2023/1113. The Travel Rule for crypto. The EU's implementation of Financial Action Task Force (FATF) Recommendation 16, originator + beneficiary data must travel with every crypto transfer.
Didit covers all three in one workflow:
- Conduct (MiCA): evidence pack, Article 60 CDD, EU-resident storage, attestation
- AML / 6AMLD: AML Screening against 1,300+ sanctions / PEP / adverse-media lists, Ongoing Monitoring at $0.07 per user per year, signed webhooks for new hits
- Travel Rule (TFR): IVMS-101 payloads, TRP / Sumsub TR / Notabene / Veriscope interop
One contract, one invoice, one audit pack.
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.
Does it screen incoming deposit wallets too?
Yes. Wallet Screening (Know-Your-Transaction) scores every deposit address before you credit the user.
Returns:
- 0-100 risk score + categorical labels:
sanctioned,mixer,exchange-high-risk,stolen funds,darknet,ransomware,phishing,scam - Counterparty cluster + attribution to the upstream entity where known
- Daily delta refresh against the underlying provider feeds
Pricing:
- $0.15 per check on the managed flow (Didit handles the underlying on-chain-analytics contract for you)
- $0.02 per check when you Bring Your Own Key (BYOK) from your existing on-chain-analytics provider, Didit becomes the routing + normalisation layer over the API key you already paid for
Chain coverage: Ethereum + EVM-compatible chains (Polygon, BNB, Arbitrum, Optimism, Base), Bitcoin, TRON, Solana, plus the major Layer 2s. New chains added as provider coverage expands.
Hits route into the same Case Management surface as AML hits, one queue, one reviewer workflow, one audit trail.
What records do I need to keep, and for how long?
MiCA Article 67-68, CASPs must retain records of services, activities, orders, and transactions for at least 5 years (extendable to 7 on competent-authority request).
The EU AML package, CDD records must be retained for 5 years after the end of the business relationship, with member-state discretion to extend up to 10 years.
The TFR, Travel Rule data must travel with the transfer and be retained per the same AML retention timeline.
Didit's retention model:
- All evidence stored in the European Union, regulated EU data centres, no cross-border transfer for EU customers
- Signed + timestamped, every payload carries an HMAC signature so chain-of-custody is provable for an examiner
- Retained indefinitely while your subscription is active, no per-record retention bill, no expiry surprises
- Configurable per workflow if your NCA mandates a specific duration (e.g. extend to 10 years for high-risk client categories)
- Export anytime via
GET /v3/session/...or bulk ZIP from the Console
When a user closes their account, evidence retention starts ticking from the off-boarding date, same model regulators expect from traditional financial institutions.
Is there an attestation I can show our MiCA examiner?
Yes, Didit is the only KYC provider with a formal EU member-state government attestation.
The Spanish Financial Sandbox, run jointly by:
- Tesoro (the Spanish Treasury)
- Banco de España (the Spanish central bank)
- SEPBLAC (Servicio Ejecutivo de la Comisión de Prevención del Blanqueo de Capitales, Spain's Financial Intelligence Unit)
…jointly attested Didit's NFC + active-biometric verification as safer than in-person verification. The report is downloadable from your Business Console and slots directly into your MiCA Article 16 (CASP authorisation) and Article 60 (CASP conduct) packs.
Additional third-party certifications kept current:
- ISO/IEC 27001, Information Security Management System
- SOC 2 Type 1, service-organisation controls
- iBeta Level 1 PAD, Presentation Attack Detection (the standard for face-liveness anti-spoof)
- finReg360 EBA memo, independent legal review against the EBA's MiCA guidelines
Every certificate is reachable from /security-compliance and downloadable on demand.