Skip to main content
Didit 融资 750 万美元，打造身份与欺诈基础设施
Didit
加密货币入口

验证买家。筛选钱包。一站式工作流。

Didit 工作流一站式处理买家身份和目标钱包验证，确保加密货币交易安全。每月免费提供 500 次验证。

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

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

入口的责任

了解买家。了解钱包。资金转移前完成。

每个受监管的入口都必须同时处理两部分：买家 KYC 和目标钱包 KYT，适用于每笔购买。Didit 将它们整合为一个工作流： $0.33 KYC + $0.17 交易（含托管钱包筛选）= 每笔购买 $0.50。如果使用您自己的钱包提供商 (BYOK)，则降至 $0.37。每月免费提供 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.50 每笔购买。

受监管的入口购买并非单一检查, 它是一个配方。每个工作流程可切换每个模块，通过BYOK替换您自己的钱包筛选提供商，将每次购买费用降至 $0.37。
阅读文档获取 API 密钥
01 · 买家 KYC 套件

五项检查，一次调用。

身份、活体、人脸比对、设备 + IP、AML, 打包价每位买家 $0.33。通过 iBeta Level 1 反欺诈认证，两秒内出结果，支持 220 多个国家/地区的 14,000 多种证件。
用户验证模块
02 · 钱包筛选 (KYT)

加密货币转出前，先评估目标地址。

识别受制裁钱包、混币器、高风险交易所、被盗资金。托管检查每笔 $0.15，或使用您自己的提供商密钥每笔 $0.02。支持 EVM、Bitcoin、TRON、Solana 和主要 L2。
钱包筛选模块
03 · AML 筛选

针对 1300 多个列表筛选每位买家。

制裁、政治公众人物 (PEP)、负面媒体, 每日更新，支持 14 种语言。命中后自动创建案例，并在清除前阻止购买。
AML 筛选模块
04 · 旅行规则 (TFR)

每笔转账都包含发起人 + 受益人信息。

通过 TRP、Sumsub Travel Rule、Notabene、Veriscope 交换 IVMS-101 数据包。欧盟 TFR 下无 €1,000 最低限额, 每笔转账都包含发起方 + 受益方数据。
加密货币旅行规则概览
05 · 交易限额

限额随买家风险动态调整。

每个工作流的实时速度、金额、链和地理阈值。自动识别结构化模式。在无代码工作流构建器中编辑规则，无需重新部署。
交易监控模块
06 · 出口覆盖

出入金，一个工作流搞定。

相同的 /v3/ 会话处理提款：KYC 卖家，KYT 源钱包，AML 买家，提交旅行规则数据包。一份合同，一份发票，一份审计包，双向适用。
加密行业工作流
集成

一个会话。一次预检查。一个 Webhook。

开启 KYC 会话。预检查目标钱包。读取签名结果。放行加密货币。
POST /v3/session/KYC
$ 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_onramp_kyc",
    "vendor_data": "buyer-42",
    "metadata": { "destination_wallet": "0x2dc1...81f9" }
  }'
201已创建{ "session_url": "verify.didit.me/..." }
在签名 webhook 返回 status: Approved 之前，阻止购买。文档 →
POST /v3/transactions/KYT
$ curl -X POST https://verification.didit.me/v3/transactions/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "transaction_id": "buy-42",
    "transaction_details": { "direction": "OUTBOUND", "currency_kind": "crypto" },
    "subject": { "vendor_data": "buyer-42", "full_name": "Jamie Example" },
    "counterparty": { "full_name": "Destination wallet", "payment_method": { "account_id": "0x2dc1...81f9" }}
  }'
201创建时间{ 状态 APPROVED · IN_REVIEW · DECLINED · AWAITING_USER }
当 currency_kind: "crypto" 时，钱包筛选在服务器端运行。无需二次调用。文档 →
代理就绪集成

通过一个提示，快速上线加密货币入口的 KYC + KYT 流程。

粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent 中。填写您的技术栈。代理将构建工作流，在钱包界面设置购买门槛，注册持续监控，并连接 Webhook。
didit-integration-prompt.md
You are integrating Didit into a fiat-to-crypto on-ramp. Two obligations on every buy:

  1. Verify the buyer (KYC) — identity, liveness, face match, device + IP, AML against 1,300+ sanctions / PEP / adverse-media lists. ONE call to the Sessions API.
  2. Screen the destination wallet (KYT) — risk-score the address against sanctioned wallets, mixers, high-risk counterparties BEFORE the crypto leaves. ONE call to the Transactions API with currency_kind: "crypto".

Bundle pricing (verified live against POST /v3/transactions/, 2026-05-16):
  - KYC bundle: $0.33 per buyer (Sessions API)
  - Transactions API call: $0.02 base (transaction-monitoring) + $0.15 wallet screening (Didit's default managed provider) = $0.17 per buy
  - Total managed: $0.33 + $0.17 = $0.50 per fully-screened buy
  - Total with BYOK on the wallet provider: $0.33 + $0.04 = $0.37 per buy
  - First 500 KYC 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 + Device & IP Analysis + AML Screening.
  - Transaction Monitoring enabled in the Business Console (Transactions > Settings) with crypto screening turned on.

STEP 1 — Verify the buyer 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 buyer id, max 256 chars>",
      "callback": "https://<your-app>/onramp/kyc/callback",
      "metadata": {
        "purpose": "crypto_onramp_buy",
        "buy_id": "<your internal tx reference>"
      }
    }

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

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 buyer 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 — Screen the destination wallet BEFORE crediting the buy

  POST https://verification.didit.me/v3/transactions/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body (required fields verified live 2026-05-16):
    {
      "transaction_id": "<your internal buy 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 buyer id>",
        "full_name": "<buyer 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: a 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.

  Response shape (excerpted from a real successful 201):
    {
      "uuid": "<server transaction uuid>",
      "txn_id": "<your transaction_id echoed back>",
      "status": "APPROVED",
      "score": 0,
      "severity": null,                       // null when score is 0; LOW | MEDIUM | HIGH | CRITICAL | UNKNOWN otherwise
      "props": {
        "wallet_risk_score": 0,
        "sanctions_hit": false,
        "pep_counterparty": false,
        "aml_provider": "<provider slug>",    // identifies the screening provider used on this call
        "aml_screening_type": "WALLET_SCREENING",
        "aml_screening_status": "COMPLETED"
      },
      "provider_results": [{ "provider": "<provider slug>", "result_type": "WALLET_SCREENING", "status": "SCREENED", ... }],
      "cost_breakdown": {
        "total_price": 0.17,
        "items": [
          { "usage_type": "transaction_aml_monitoring", "price": 0.15 },
          { "usage_type": "transaction_monitoring", "price": 0.02 }
        ]
      }
    }

  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.

  Real per-transaction cost (verified live):
    - Plain fiat transaction monitoring: $0.02
    - Crypto transaction with managed wallet screening: $0.17 ($0.02 TM base + $0.15 wallet screen on Didit's managed flow)
    - Crypto transaction with BYOK wallet screening: $0.04 ($0.02 TM base + $0.02 wallet screen)

  Branch logic:
    APPROVED       → send the crypto.
    IN_REVIEW      → hold the buy, route to analyst queue.
    DECLINED       → refund the fiat, block the address.
    AWAITING_USER  → redirect the buyer to the remediation session URL.

STEP 4 — Ongoing AML monitoring is automatic

  Any session with AML enabled is rescreened DAILY by Didit's continuous monitoring at $0.07 per user per year. There is NO separate endpoint to call — the same workflow does it.

  When a previously-approved buyer crosses an AML threshold, the session status changes to "In Review" or "Declined" automatically and your webhook fires the update.

STEP 5 — Off-ramp uses the same two endpoints

  Selling crypto for fiat:
    - KYC the seller via POST /v3/session/ (same as Step 1).
    - Screen the source wallet via POST /v3/transactions/ with direction: "INBOUND" and the source wallet address on subject.payment_method.account_id.

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.

CONSTRAINTS
  - Session statuses use Title Case With Spaces (Approved, In Review). Transaction statuses use UPPER_SNAKE_CASE (APPROVED, IN_REVIEW). They live in different APIs — don't mix them in the same code path.
  - Wallet Screening MUST run BEFORE the crypto leaves — a post-transfer screen is useful for audit but useless for blocking.
  - Default record retention is 5 years post-relationship per the EU AML package; 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, don't re-query.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/transaction-monitoring/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.
合规性设计

一键开启新国家/地区业务。 我们为您解决难题。

我们负责设立当地子公司、获取许可证、进行渗透测试、获得认证，并与所有新法规保持一致。要在新国家/地区发布验证服务，只需轻点开关。已覆盖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 捆绑包 + 带有钱包筛选的交易。
  • 0+
    对每位买家进行制裁、政治公众人物 (PEP) 和负面媒体名单筛选。
  • <0s
    入门级 Android 设备上，每次会话的端到端 KYC 结果。
  • 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 a crypto on-ramp, and why does it need two checks?

An on-ramp is the service that lets someone pay with a card or bank transfer and receive crypto in their wallet. Think MoonPay, Ramp, Transak, and Didit customers like AhoraCrypto and GBTC Finance.

Two things can go wrong on every buy, so you need two checks:

  • Verify the buyer, are they real, are they who they say they are, are they on a sanctions list
  • Screen the destination wallet, has that address shown up in a mixer, a hack, or a sanctioned cluster

A clean buyer can still send funds to a bad wallet, and a clean wallet can still be funded by a bad buyer. Both checks, every buy. Didit ships them as one workflow for $0.50 per buy ($0.33 KYC + $0.17 transaction with managed wallet screening), or $0.37 when you bring your own wallet-screening key.

KYC versus KYT, what's the difference?

KYC is about the person: name, document, face, sanctions, where they're logging in from. You run it once at signup and refresh it later.

KYT is about the wallet: where it sits in the on-chain graph, who it's transacted with, whether it's been flagged. You run it on every transaction.

A regulated on-ramp owes both. Didit gives you one workflow that runs the KYC on the buyer and the KYT on the destination wallet in the same flow, no extra moving parts.

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.

Off-ramp too?

Same two checks, reverse direction:

  • Verify the seller, same KYC flow as the buyer
  • Screen the source wallet, where is the crypto coming FROM, before you accept it. Catches mixers, ransomware proceeds, sanctioned addresses

One workflow handles buy and sell. One contract, one invoice, one audit trail for both directions.

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 cover the Travel Rule?

Yes. The EU Travel Rule (the Transfer of Funds Regulation) says CASPs must exchange originator and beneficiary data on every crypto transfer, no minimum threshold for crypto in the EU.

Didit handles it with:

  • IVMS-101 payloads, the standard every major Travel Rule protocol speaks
  • Interoperability with TRP, Sumsub Travel Rule, Notabene, and Veriscope
  • Transaction Monitoring flags transfers where originator or beneficiary data is missing or mismatched

One workflow, both halves, KYC on the user, Travel Rule data on the transfer.

What if a buyer is flagged after the buy?

Didit re-checks every approved buyer daily against the same 1,300+ lists used at signup. It's automatic, there's no separate endpoint to call, no extra setup, no extra cost on most plans (and $0.07 per user per year on heavy-volume accounts).

When a previously-clean buyer crosses an AML threshold:

  • The session status changes to In Review or Declined automatically
  • A signed webhook lands on your back-end with the new hits
  • A case opens in the Business Console with the original onboarding evidence one click away
  • Your compliance team can file a Suspicious Activity Report (SAR) from inside the case

For a million-buyer base that's single-digit dollars per buyer per year, orders of magnitude cheaper than a manual review queue.

How long does it take to ship?

Sandbox in 5 minutes. Production in a weekend.

  • Sign up at the Business Console, sandbox key in 60 seconds, no card
  • Build the workflow in the no-code Workflow Builder, pick KYC modules + turn on crypto screening in Transactions settings
  • Drop one call into your KYC step (POST /v3/session/) and one into your buy step (POST /v3/transactions/)
  • Verify the signed webhook, approved unlocks the buy, declined holds the funds

If you'd rather have an AI agent build it (Claude Code, Cursor, Codex, Devin, Aider, Replit Agent), paste the integration prompt from the section above and the agent scaffolds the flow. Native SDKs for Web, iOS, Android, React Native, and Flutter all share the same session model.

Related

相关模块 + 工作流

身份与欺诈基础设施。

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

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