Skip to main content
Didit 融资 750 万美元，打造身份与欺诈基础设施
Didit
市场卖家KYB

一次调用即可验证所有卖家。注册信息、所有者、AML, 一站式搞定。

拉取公司记录，识别所有受益所有人，并对每个受益所有人进行 KYC。每位卖家 $2.00，每位受益所有人 $0.33。每月免费 500 次验证。

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

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

一张电影风格的深色抽象市场KYB插画, 四个半透明玻璃面板垂直堆叠在纯黑色背景上，由一条发光的Didit蓝色线条贯穿，并由四个扫描支架框住。每个面板上都有一个微小的抽象浅白色图案（店面、注册文件、所有权图表、印章）。

平台应尽的责任

了解公司。了解其所有者。在商品上线之前。

欧盟数字服务法案和新的AML（反洗钱）一揽子计划，使卖家验证成为一项法律义务。Didit将其整合为一个工作流：注册信息查询、所有者提取、对每个所有者进行KYC（了解您的客户）以及文档OCR（光学字符识别）, 所有这些都与同一卖家记录关联。每个卖家$2.00，每个所有者$0.33。每月免费提供500次验证。

工作原理

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

  1. 步骤 01

    创建工作流

    选择您需要的验证项, 身份、活体检测、人脸比对、制裁名单、地址、年龄、电话、邮箱、自定义问题。在控制面板中拖拽即可创建流程，或通过API发布相同流程。支持条件分支和A/B测试，无需代码。

  2. 步骤 02

    集成

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

  3. 步骤 03

    用户完成流程

    Didit负责托管摄像头、光线提示、移动端切换和无障碍功能。在用户进行流程时，我们实时评估200多项欺诈信号，并根据权威数据源验证每个字段。两秒内即可获得结果。

  4. 步骤 04

    接收结果

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

专为平台打造 · 基础设施定价

一个工作流。每个卖家$2.00。

受监管的平台卖家验证并非单一检查，它是一套组合拳：注册信息查询、所有者提取、每个所有者的KYC、AML筛选、文档OCR和持续监控。每个工作流可按需启用模块。
阅读文档获取API密钥
01 · 注册信息查询

卖家的法律记录。实时更新。

直接从各国权威来源获取, 英国公司注册处（Companies House）、西班牙商业登记处（Mercantil）、德国商业登记处（Handelsregister）、巴西商业委员会（Junta Comercial）以及200多个其他注册机构。包括法定名称、注册号、状态、成立日期。无抓取，无过期数据。
企业验证模块
02 · 实际受益人提取

所有持股25%以上的受益人。

实际受益人（UBO）提取功能可识别拥有卖家四分之一或以上股权的每个个人，以便进行闭环KYC。从注册来源提取董事和股东信息，确保名单可验证，而非自证。
企业验证模块
03 · 每个所有者的KYC

所有受益人的闭环身份验证。

每个实际受益人都会获得一个托管的KYC会话, 身份验证、被动活体检测、1:1人脸比对、设备+IP分析、AML, 每个所有者$0.33。结果会回溯到父级KYB记录中，因此一次批准即可通过整个卖家验证。
用户验证模块
04 · 实体AML

在1300多个名单中筛选公司。

制裁名单、政治公众人物（PEP）和负面媒体名单, 每日更新，支持14种语言。命中后自动创建案例，并在通过前阻止卖家。覆盖公司和每个所有者。
AML筛选模块
05 · 文档收集 + OCR

一份已签名的证据包。

公司注册证书、税务登记、营业地址证明, 通过托管流程收集并使用OCR读取。与注册记录进行交叉核对，确保篡改的上传文件在进入您的审计日志之前就被识别。
数据库验证模块
06 · 持续监控

入驻后持续验证。

对卖家和每个所有者进行每日持续AML（反洗钱）监控（$0.07/用户/年），监控注册状态以防解散，当所有者股权变更超过25%阈值时发出警报，以及文档到期提醒。确保卖家在经营期间始终合规。
工作流编排器
集成

一个会话。一个Webhook。每个卖家。

开启KYB会话。读取签名结果。激活卖家。
POST /v3/session/KYB
$ 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_kyb_marketplace",
    "vendor_data": "seller-42",
    "expected_country": "GB"
  }'
201已创建{ "url": "verify.didit.me/..." }
将此URL通过邮件发送给卖家。状态更新将通过您的webhook推送。文档 →
GET /v3/session/{id}/decision/决策
$ curl https://verification.didit.me/v3/session/$SESSION/decision/ \
  -H "x-api-key: $DIDIT_API_KEY"

# Decision payload (excerpted):
{ "session_kind": "business", "status": "APPROVED",
  "decision": { "company": { "legal_name": "Maker Goods Ltd.", "registry_status": "ACTIVE" }, 
    "key_people": [ ... kyc_session_url per owner ... ]
  } }
200OK状态 APPROVED · IN_REVIEW · DECLINED · AWAITING_USER
每个所有者的 kyc_session_url 都追溯到父级 KYB。文档 →
代理就绪集成

通过一个提示，快速上线市场卖家KYB。

粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent 中。填写您的技术栈。Agent 将构建工作流，为每个卖家启动会话，驱动每个所有者的关联 KYC，并连接 Webhook。
didit-integration-prompt.md
You are integrating Didit into a marketplace that lists third-party sellers (Etsy, Shopify, Faire, Amazon Handmade, OnBuy archetype). EU Digital Services Act Article 30 and the new EU Anti-Money Laundering (AML) package require you to verify the seller (KYB) before any listing goes live, and to keep that verification fresh while they sell.

Four obligations on every seller:

  1. Pull the company's registry record (legal name, registration number, status, incorporation date) from the authoritative government source.
  2. Extract every Ultimate Beneficial Owner (UBO) — anyone owning 25% or more — and run a closed-loop KYC on each one.
  3. Screen the company AND every UBO against sanctions, Politically Exposed Persons (PEP), and adverse-media lists.
  4. Collect the corporate evidence (certificate of incorporation, tax registration, proof of business address) and watch the seller continuously for status changes, UBO turnover, AML hits, and document expiry.

Pricing (verified live):
  - KYB session (registry + company AML + documents + key-people flow): $2.00 per seller, pay-per-call
  - Linked KYC per UBO: $0.33 per UBO (ID + Passive Liveness + Face Match + IP + AML)
  - Ongoing AML monitoring: $0.07 per user per year
  - 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 for KYB from the Workflow Builder. The workflow's type (KYC or KYB) drives the session shape — no explicit business flag is needed on the request.
  - A workflow_id for KYC bundled with ID + Passive Liveness + Face Match + IP + AML, used for the linked UBO sessions.

STEP 1 — Create the KYB session

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<your KYB workflow id>",
      "vendor_data": "<your seller id, max 256 chars>",
      "callback_url": "https://<your-app>/sellers/kyb/callback",
      "expected_country": "GB",
      "metadata": {
        "seller_id": "<your internal seller id>",
        "marketplace_segment": "handmade"
      }
    }

  Response: 201 Created with the hosted session URL. Email it to the seller or embed it in your onboarding UI. Behind the scenes, Didit runs:
    - kyb_registry — live registry lookup against the country's authoritative source
    - kyb_company_aml — sanctions / PEP / adverse media on the company
    - kyb_documents — document collection + Optical Character Recognition (OCR) (incorporation, TIN, proof of address)
    - kyb_key_people — UBO + director extraction with linked-KYC sessions

STEP 2 — Read the signed webhook on KYB completion

  Didit POSTs to your callback. KYB SESSION statuses are UPPER_SNAKE_CASE:

  Body (excerpted):
    {
      "session_id": "<uuid>",
      "session_kind": "business",
      "vendor_data": "<your seller id>",
      "status": "APPROVED",
      "decision": {
        "company": {
          "legal_name": "Maker Goods Ltd.",
          "registration_number": "1029847",
          "country_code": "GB",
          "registry_status": "ACTIVE"
        },
        "features": [
          { "node_id": "kyb_registry", "status": "APPROVED" },
          { "node_id": "kyb_company_aml", "status": "APPROVED", "total_hits": 0 },
          { "node_id": "kyb_documents", "status": "APPROVED" },
          { "node_id": "kyb_key_people", "status": "APPROVED",
            "key_people": [
              { "uuid": "<uuid>", "name": "Sara Ortega", "role": "director", "is_ubo": true, "ownership_percentage": 60, "kyc_status": "Approved", "kyc_session_url": "https://verify.didit.me/..." },
              { "uuid": "<uuid>", "name": "Niels Janssen", "role": "shareholder", "is_ubo": true, "ownership_percentage": 30, "kyc_status": "Approved", "kyc_session_url": "https://verify.didit.me/..." }
            ]
          }
        ]
      }
    }

  SESSION status enum (KYB · UPPER_SNAKE_CASE):
    NOT_STARTED | IN_PROGRESS | AWAITING_USER | APPROVED | DECLINED | IN_REVIEW | RESUBMITTED | ABANDONED | EXPIRED

  FEATURE status enum (inside decision.features[].status · UPPER_SNAKE_CASE):
    NOT_FINISHED | APPROVED | DECLINED | IN_REVIEW | RESUB_REQUESTED | AWAITING_USER

  Note: kyc_status on key_people IS Title Case ("Approved" / "Declined" / "Pending") — those are KYC sessions linked from inside the KYB feature, not KYB features themselves.

  Verify the X-Signature-V2 header BEFORE reading the body — HMAC SHA-256 of the raw bytes with your webhook secret.

STEP 3 — Linked KYC on each UBO is automatic

  When the seller completes the hosted KYB flow and submits the UBO list, Didit spawns a child KYC session per UBO using the KYC workflow you configured on the KYB workflow. Each child session has its own session_id and its own hosted URL on the kyc_session_url field inside the key-people block.

  You don't need to call POST /v3/session/ again for the UBOs — they're stitched to the parent KYB session automatically. You DO need to drive each UBO through their hosted KYC URL (email it, SMS it, embed it in your seller dashboard).

  Per-UBO KYC session status is Title Case With Spaces (KYC convention):
    Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned

  Linked-KYC pricing: $0.33 per UBO.

STEP 4 — Retrieve the decision

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

  Returns the full KYB decision payload — company block, AML hits, document OCR, every UBO with their kyc_status and kyc_session_url. Use this for audit-pack export and for re-rendering the seller status in your admin UI.

STEP 5 — Decide

  Branch logic:
    APPROVED       → activate the seller, allow listings.
    IN_REVIEW      → keep listings off, wait for analyst webhook update.
    DECLINED       → refuse onboarding, log the decision_reason_code.
    AWAITING_USER  → nudge the seller to complete the pending step (typically UBO list submission).

  Pre-DSA Article 30: store the trader information (legal name, registration number, address, contact) in your trader-information record alongside the decision payload.

STEP 6 — Ongoing monitoring is automatic when enabled

  Enable Ongoing AML on the seller and on each UBO ($0.07/user/year). The session status updates automatically as new sanctions hits land, dissolutions are filed in the registry, or document expirations approach. Your webhook fires on every state change.

  No separate endpoint to call — the same workflow drives it.

WEBHOOK EVENT NAMES
  - status.updated — session status changed (filter on data.session_kind === "business" for KYB).
  - data.updated — session data changed (registry refresh, key-people submission, document upload, ongoing AML hit).
  - business.status.updated — the linked Business entity changed.
  - business.data.updated — Business entity data changed.

  Verify X-Signature-V2 on every payload. The webhook secret is per-environment — sandbox key is separate from production.

CONSTRAINTS
  - KYB session statuses use UPPER_SNAKE_CASE (APPROVED, IN_REVIEW, DECLINED). KYC session statuses use Title Case (Approved, In Review, Declined). They live in different APIs — don't mix them in the same code path.
  - Default record retention is 5 years post-relationship per the EU AML package; some jurisdictions go higher.
  - You cannot replace the registry lookup with a self-attested form — DSA Article 30 requires the data to come from an authoritative source.

Read the docs:
  - https://docs.didit.me/business-verification/integration-guide
  - https://docs.didit.me/business-verification/statuses
  - https://docs.didit.me/business-verification/webhooks
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/sessions-api/retrieve-session
  - https://docs.didit.me/integration/webhooks

Start free at https://business.didit.me — sandbox key in 60 seconds, 500 KYC 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
    每次 KYB 会话, 注册、AML、文件、关键人物流程。
  • $0.00
    每个受益所有者（持股25%以上）的关联 KYC。
  • 0+
    拥有实时政府注册覆盖的国家/地区。
  • 0
    每个账户每月免费 KYC 验证。
三个层级，一份价目表

免费开始。按使用量付费。可扩展至企业级。

每月 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 does KYB actually mean for a marketplace?

Know Your Business (KYB) is the process of verifying that a company is real, that it's still trading, and that you know who actually owns and controls it. For a marketplace it has three pieces:

  • Verify the company, name, registration number, status, and incorporation date pulled from the country's official registry
  • Find the beneficial owners, every person owning 25% or more of the company
  • Run KYC on each owner, same identity check you'd run on a consumer signup, just multiplied by the number of owners

It's the business-side equivalent of KYC (Know Your Customer). On a marketplace that lists third-party sellers, you owe it before any listing goes live. Didit ships the whole recipe as one workflow for $2.00 per seller + $0.33 per owner.

Who actually has to do this?

Any marketplace that lets a third party offer goods or services to consumers and takes payment for it. That covers:

  • Goods marketplaces, Etsy, Shopify, Faire, Amazon Handmade, OnBuy archetype
  • Service marketplaces, Fiverr, Upwork, Bark, ClassPass for studios
  • Travel and stays, Booking, Airbnb hosts who operate as businesses
  • Food and delivery, restaurant partners on Uber Eats, DoorDash, Deliveroo
  • Mobility, drivers and operators on Uber, Bolt, Cabify

In the European Union the Digital Services Act (the EU's online-platform rulebook) makes seller verification a hard requirement, with material fines for non-compliance. The UK, US, and most of Latin America have parallel obligations under their own consumer-protection and anti-money-laundering rules.

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.

What goes wrong if I skip KYB?

Three things, in order of how often they bite a marketplace:

  • Fraud sellers, fake businesses listing real goods they don't have, collecting payment, vanishing. The marketplace eats the chargebacks and the brand damage.
  • Sanctioned counterparties, selling on behalf of a designated entity or person. In the EU and US this is strict liability; the marketplace owes the fines regardless of intent.
  • Regulator enforcement, under the EU Digital Services Act the European Commission can fine a very-large online platform up to 6% of global turnover. National regulators have parallel enforcement under consumer-protection law.

The historical record on this is unforgiving. Almost every major marketplace has been fined for letting unverified sellers operate. KYB is the standard control.

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.

How do statuses work?

Two enum sets, one per session kind:

  • KYB session, APPROVED, IN_REVIEW, DECLINED, AWAITING_USER, plus the resubmitted / abandoned / expired states the docs cover
  • Linked KYC session per owner, Approved, In Review, Declined, Resubmitted, Expired, Not Finished, Kyc Expired, Abandoned

The casing difference is deliberate, UPPER_SNAKE for the KYB session, Title Case for the KYC session. They sit in different APIs; don't mix them in the same code branch.

For a webhook handler, switch on the parent KYB status. AWAITING_USER is the most common interim state, it usually means the seller still has to submit the owner list or re-upload a document. The state transitions to IN_REVIEW or APPROVED automatically once they do.

What does ongoing monitoring look like?

Verification at signup is necessary but not sufficient, sellers change over time, owners move in and out, and sanctions lists update daily. Didit's ongoing monitoring catches all of it:

  • Ongoing AML on the company and every owner, daily delta refresh at $0.07 per user per year
  • Registry status watch, dissolutions, strike-offs, and adverse filings trigger a webhook the day they hit the source
  • Ownership change detection, if a new UBO crosses the 25% threshold, the seller is automatically queued for re-KYB
  • Document expiry, passport, ID card, and address proof expirations fire a 30-day-out reminder

Everything flows through the same status.updated webhook you already wired for onboarding. No new endpoint, no extra integration.

How does Didit compare on price?

Most KYB providers price between $8 and $50 per check, often with floor commits in the thousands of dollars per month and per-country surcharges. The Middesk / Persona KYB / Onfido Business archetype.

Didit's published price is $2.00 per KYB session + $0.33 per linked KYC. No floor, no commit, no per-country surcharge, no hidden registry fees. Pay only for what runs.

That's 3–5× cheaper than the incumbent stack on the same regulatory output. The economics matter because seller verification is a per-listing cost, at scale the difference between $2 and $25 is the difference between accepting a seller and refusing them. Full pricing at /pricing.

Related

相关模块 + 工作流

身份与欺诈基础设施。

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

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