Skip to main content
Didit 融资 750 万美元，打造身份与欺诈基础设施
Didit
BNPL 承保

申请时承保。监控每期付款。

借款人入驻费用 $0.33，每期付款收取 $0.02，包含持续 AML。每月免费 500 次验证, 60 秒内即可使用沙盒。

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

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

一张电影风格的深色抽象“先买后付”承保插图, 四个半透明玻璃面板以3D透视浮动在纯黑色背景上，由一条发光的Didit蓝色线条贯穿，并由四个发光扫描支架框住。每个面板上都有一个微小的浅白色抽象图案，代表分期承保（四点分期时间线、信用卡轮廓、上升的条形图、圆形进度环）。

BNPL 的责任

申请时的借款人。此后每笔分期付款。

BNPL 计划并非一次性决策，而是一个连续过程。Didit 在结账时对借款人进行承保， 将每笔分期付款记录到 Transactions API，并在计划的整个生命周期内自动 重新筛查制裁或 PEP（政治公众人物）命中。申请时 $0.33，每期 $0.02， 包含持续的 AML。每月免费 500 次验证。

工作原理

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

  1. 步骤 01

    创建工作流

    选择您需要的检查项, 身份、活体、人脸匹配、制裁、地址、年龄、电话、电子邮件、自定义问题。将它们拖入仪表盘中的流程，或将相同的流程发布到我们的 API。根据条件进行分支，运行 A/B 测试，无需代码。

  2. 步骤 02

    集成

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

  3. 步骤 03

    用户完成流程

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

  4. 步骤 04

    您接收结果

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

专为 BNPL 打造 · 基础设施定价

六个基本功能。申请时 $0.33，每期 $0.02。

BNPL 合规并非单一检查，而是一套组合拳。申请时承保，记录每笔分期付款，在整个计划中刷新 AML，并构建审计包。
阅读文档获取 API 密钥
01 · BNPL 套件

一次调用，五重核查。

身份、活体、人脸匹配、设备 + IP、AML, 打包后每位借款人 $0.33。iBeta Level 1 反欺诈认证，两秒内出结果，覆盖 220 多个国家/地区的 14,000 多种证件。
用户验证模块
02 · 设备 + IP 风险

申请时识别200+欺诈信号。

VPN / Tor / 代理检测、数据中心暴露、账单与 IP 地理位置不匹配、每设备多账户、结账时速度, 所有这些都加权计入每个申请的风险评分。
设备与 IP 分析
03 · 持续监控

整个计划期间持续更新AML，而非仅在申请时。

持续 AML 每日监控借款人，以发现新的制裁、PEP（政治公众人物）和负面媒体命中, 每年每用户 $0.07。无需单独端点，任何启用 AML 的会话均自动进行。
AML 筛选模块
04 · 负担能力 + 审计包

每位借款人一个数据包 · 支持FCA导出。

已验证的借款人字段加上承保信号栈（KYC、AML、设备 + IP、计划参数）打包成一份签名记录, 可导出至英国 FCA (Financial Conduct Authority)、澳大利亚 ASIC 或任何其他进行 BNPL 检查的机构。
Webhooks 文档
05 · 首次付款违约

在申请时捕获FPD模式。

同类群组模式, 被盗证件集群、BNPL 计划间的身份重用、每设备速度、一次性电子邮件 + 新设备, 每日刷新并在计划批准前阻止。可按商户编辑阈值。
账户盗用用例
06 · 跨境

一套堆栈，覆盖全球。

英国 FCA BNPL 规则 (2026)、欧盟消费者信贷指令 II、美国各州贷款机构许可、澳大利亚 ASIC，以及各地区的 AML 观察名单。覆盖 220 多个国家/地区的 14,000 多种证件。
交易监控
集成

申请时一次会话。每期一次交易。

承保借款人。收取分期付款。读取签名裁决。在整个计划中重复。
POST /v3/session/申请
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "workflow_id": "wf_bnpl_apply",
    "vendor_data": "borrower-42",
    "metadata": { "plan_id": "plan-9182" }
  }'
201已创建返回托管会话URL。
在 webhook 返回 status: Approved 之前，暂停该计划。文档 →
POST /v3/transactions/分期付款
$ curl -X POST https://verification.didit.me/v3/transactions/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "transaction_id": "plan-9182-inst-1",
    "transaction_details": { "direction": "INBOUND", "amount": "125.00", "currency": "GBP", "currency_kind": "fiat" },
    "subject": { "vendor_data": "borrower-42", "full_name": “Jamie Example” },
    “交易对手”: { “full_name”: “Merchant Ltd” }
  }'
201创建时间状态 APPROVED · IN_REVIEW · DECLINED · AWAITING_USER · $0.02
内置速度与结构化检测，覆盖每一笔分期付款。文档 →
代理就绪集成

一键部署 BNPL 承保流程。

粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent。填写您的技术栈。代理将构建申请工作流，记录每笔分期付款，签署 webhook，并连接审计包。
didit-integration-prompt.md
You are integrating Didit into a Buy-Now-Pay-Later (BNPL) checkout flow — Klarna / Affirm / Clearpay / Tabby / Tamara / Kueski archetype. The recipe handles three obligations on every BNPL plan:

  1. Verify the borrower at checkout — identity, liveness, face match, device + IP, AML against 1,300+ sanctions / PEP / adverse-media lists. ONE call to the Sessions API.
  2. Log every instalment charge — Transaction Monitoring catches velocity, structuring, and chargeback patterns. ONE call to the Transactions API per instalment.
  3. Continuous AML — the borrower is rescreened automatically across the lifetime of the plan. NO separate endpoint to call.

Cost:
  - Borrower Know Your Customer (KYC) bundle: $0.33 per application (Sessions API)
  - Transaction monitoring per instalment charge: $0.02 (Transactions API)
  - Ongoing AML monitoring: $0.07 per user per year (automatic on any session with AML enabled)
  - 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 that bundles ID Verification + Passive Liveness + Face Match 1:1 + Device & IP Analysis + AML Screening.
  - Transaction Monitoring enabled in the Business Console (Transactions > Settings).

STEP 1 — Underwrite the borrower at checkout

  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 bundle>",
      "vendor_data": "<your borrower id, max 256 chars>",
      "callback": "https://<your-app>/bnpl/apply/callback",
      "metadata": {
        "purpose": "bnpl_application",
        "plan_id": "<your internal plan reference>",
        "merchant_id": "<merchant id>",
        "principal_amount": "500.00",
        "currency": "GBP"
      }
    }

  Response: 201 Created with the hosted session URL. Embed the URL inline in the BNPL widget at checkout. Sub-2-second median verdict on completion.

STEP 2 — Read the signed webhook on application completion

  Didit POSTs to your callback. Session statuses are Title Case With Spaces:

  Body (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your borrower 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.

  On Approved + clean AML + acceptable Device & IP, approve the plan and schedule the instalments. On Declined or AML hit, decline. On In Review or AWAITING_USER, hold the plan and route to your underwriting analyst queue.

STEP 3 — Log every instalment charge

  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": "<plan-id>-instalment-1",
      "transaction_category": "finance",
      "transaction_details": {
        "direction": "INBOUND",
        "amount": "125.00",
        "currency": "GBP",
        "currency_kind": "fiat",
        "action_type": "deposit"
      },
      "subject": {
        "entity_type": "individual",
        "vendor_data": "<your borrower id>",
        "full_name": "<borrower full name>"
      },
      "counterparty": {
        "entity_type": "individual",
        "full_name": "<merchant or BNPL settlement counterparty>"
      }
    }

  REQUIRED fields the API rejects if missing:
    - subject.vendor_data + subject.full_name
    - counterparty.full_name
    - transaction_details.direction + currency + currency_kind + amount

  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,
      "cost_breakdown": {
        "total_price": 0.02,
        "items": [{ "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.

  Per-instalment cost: $0.02 (transaction-monitoring base).

  Branch logic:
    APPROVED       → charge the card / pull the bank transfer.
    IN_REVIEW      → hold the instalment, route to analyst queue.
    DECLINED       → hard-fail the instalment, mark the plan delinquent.
    AWAITING_USER  → redirect the borrower to the remediation session URL.

STEP 4 — Continuous 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.

  When a previously-approved borrower crosses an AML threshold, the session status changes to "In Review" or "Declined" automatically and your webhook fires the update. Hold the remaining instalments and route the case to your collections / fraud team.

STEP 5 — Returning borrowers re-use the verified identity

  When a borrower comes back for a second plan, open a new session against their existing vendor_data — Didit reuses the previously verified document and face match where policy allows, and you avoid paying for the full bundle again. Pair with Reusable KYC for the lightest path.

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.
  - Never approve a BNPL plan before the X-Signature-V2 webhook lands with status Approved + AML clear.
  - 200+ fraud signals are evaluated on every session at no extra cost — surface the score via the session decision payload, don't re-query.
  - Default record retention is 5 years post-relationship per the EU AML package; UK FCA rules and similar national rules sit on top.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/transaction-monitoring/overview
  - https://docs.didit.me/transaction-monitoring/transactions
  - https://docs.didit.me/core-technology/aml-screening/continuous-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
原生符合欧盟标准

数据证明

数据证明
  • $0.00
    每位借款人申请时：KYC + 设备 + IP + AML，一次 API 调用。
  • $0.00
    每笔分期付款费用，内置速度与结构化检测。
  • <0s
    端到端 KYC 裁决，适用于入门级 Android 设备上的每份申请。
  • 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 Buy-Now-Pay-Later (BNPL), in plain English?

BNPL lets a shopper take goods home today and pay for them in instalments, typically four payments over six weeks, sometimes longer plans with interest.

The industry shape:

  • Klarna · Affirm · Clearpay (Afterpay) · Tabby · Tamara · Kueski · Atome are the major standalone providers
  • Apple Pay Later, PayPal Pay in 4, Shopify Installments are payment-network-embedded variants
  • The merchant gets paid in full at checkout; the BNPL provider takes the credit risk

The regulatory shift: BNPL used to sit in a soft-touch consumer-credit grey zone. As of 2025-2026, the UK FCA (Financial Conduct Authority) brings BNPL under formal regulation, the EU Consumer Credit Directive II (CCD II) extends to BNPL, and US state lenders apply existing licensing law. The compliance bar is now: real ID, real underwriting, real monitoring, real audit pack.

Why does BNPL need identity verification, not just a card check?

Because BNPL extends credit, not just processes a card.

  • A card check proves the card is valid right now. It doesn't prove who's holding it.
  • BNPL approves a multi-week payment plan against a person, if the card later fails, the BNPL provider eats the loss.
  • Fraud rings exploit BNPL precisely because card auth is weaker than full underwriting, stolen identities + stolen cards + drop addresses are a textbook pattern.

Real identity verification (ID + face + AML) cuts first-payment default (FPD) at the source. The shopper presents a real document and a real face; Didit binds the application to a single human, not just a token.

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.

Who has to underwrite this way? Isn't BNPL still unregulated?

Not anymore. The regulatory map circa 2026:

  • United Kingdom, the FCA brings BNPL under formal Consumer Credit Act regulation starting 2026; full affordability checks, audit trails, and complaint handling required
  • European Union, Consumer Credit Directive II (CCD II, Directive (EU) 2023/2225) applies to BNPL from late 2026, lifting the small-credit exemption that previously sheltered it
  • United States, state-by-state lender licensing already applies in most states; the CFPB issued an interpretive rule treating Pay-in-4 as a credit-card product
  • Australia, ASIC (Australian Securities and Investments Commission) brings BNPL under the National Consumer Credit Protection Act from 2025

The shape of the compliance bar is the same in every region: verify the borrower, screen for sanctions and PEPs, monitor across the plan, keep a 5+ year audit trail. Didit ships that bar globally.

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.

What does the affordability + audit pack look like for the FCA?

Every borrower produces an exportable pack:

  • borrower_pid, your pseudonymous borrower id
  • kyc_status, Approved / Declined / In Review (Title Case With Spaces)
  • aml_status, Clear / Hit / Manual review
  • device_risk, score + top contributing signals
  • plan_parameters, instalment count, total amount, currency, merchant id
  • signature, X-Signature-V2 HMAC SHA-256

Pipe to your collections + compliance systems and to your regulator-facing reporting layer. Default retention is 5 years post-relationship per the EU AML package; the UK FCA's BNPL rules will sit on top. Aligned with SOC 2 Type 1, ISO/IEC 27001, and the General Data Protection Regulation, all of which Didit holds.

What about cross-border BNPL, can Didit handle the whole footprint?

Yes. The same /v3/ API covers every market:

  • United Kingdom · EU · EEA, FCA, Consumer Credit Directive II, plus the EU sanctions and PEP lists
  • United States, state-by-state lender licensing, CFPB credit-card treatment for Pay-in-4, OFAC SDN screening
  • Latin America, Brazil (LGPD + Pix), Mexico, Chile, Argentina, local IDs and watchlists
  • APAC, Australia ASIC, Singapore MAS, Indonesia OJK, Japan FSA, local IDs and watchlists
  • MEA, UAE, KSA, Egypt, local IDs and watchlists

One contract, one API key, one Workflow Builder. Per-region rules tuned per workflow, Didit handles 14,000+ document types across 220+ countries, sub-2-second verdict on entry-level Android, 48+ languages in the hosted UI.

How fast can a small team integrate this?

Four wires, one afternoon:

  • Open business.didit.me, sandbox key in 60 seconds, no credit card
  • Build a workflow in the Workflow Builder that bundles ID + Liveness + Face Match + Device & IP + AML Screening
  • Wire POST /v3/session/ to the apply step + the signed webhook to your decision engine
  • Wire POST /v3/transactions/ to every instalment charge + handle the four-value status enum

The Didit MCP (Model Context Protocol) server is included free, paste the integration prompt above into Claude Code, Cursor, Codex, Replit Agent, Devin, or Aider and the agent scaffolds the whole thing against the live /v3/ API.

Related

相关模块 + 工作流

身份与欺诈基础设施。

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

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