Skip to main content
Didit 融资 750 万美元，打造身份与欺诈基础设施
Didit
买家欺诈筛选

分两阶段筛选高风险结账。先用廉价信号，仅在必要时才进行生物识别。

以 $0.03 的价格对每个高风险购物车进行网络和设备评分。仅当信号不足时，才对小部分案例进行生物识别检查。每月免费 500 次验证。

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

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

深色抽象买家欺诈筛查堆栈, 在纯黑色背景上，四个半透明的深色玻璃面板以3D透视浮动，由一条发光的Didit蓝色垂直线贯穿，并由发光的扫描支架框住。每个面板上都有一个微小的浅白色抽象图案（带盾牌的购物车、带两个定位点世界地图、带信号弧的智能手机、风险滑块）。

为什么大多数结账无需摩擦

对可信买家无摩擦。对突发欺诈果断处理。

90% 的订单来自常用设备的日常买家, 他们应该一路畅通。 10% 存在风险高峰的订单则需要筛查：低价值订单只需 $0.03 的 IP + 设备检测， 高价值订单则需 $0.10 的生物识别升级。每月免费提供 500 次验证。

工作原理

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

  1. 步骤 01

    创建工作流

    选择您需要的检查项, 身份、活体检测、人脸比对、制裁名单、地址、年龄、电话、邮箱、自定义问题。在控制面板中将它们拖入工作流，或通过我们的 API 发布相同的工作流。根据条件进行分支，运行 A/B 测试，无需代码。

  2. 步骤 02

    集成

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

  3. 步骤 03

    用户完成流程

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

  4. 步骤 04

    您接收结果

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

专为结账设计 · 基础设施定价

两个阶段。低价值订单 $0.03。高价值订单 $0.13。

买家欺诈筛查是一个组合, 购物车触发器、网络信号、生物识别升级、审计包、回头客信任。在工作流构建器中为每个工作流切换这些功能。
阅读文档获取 API 密钥
01 · 结账触发器

您决定时机，Didit 负责风控。

购物车总额超出您的层级。礼品卡堆叠三张或更多。收货国家与账单卡不符。首次在新设备上购买。速度异常, 在窗口 W 内有 N 个订单。支付/退款目的地在流程中途更改。所有这些都可在无代码工作流构建器中编辑。
工作流编排器模块
02 · 廉价 IP + 设备筛查

信号优先。成本低。决策快。

设备和 IP 分析返回 0-100 的风险评分，以及 VPN、Tor、数据中心、国家、ASN 和设备指纹标志。每次调用 $0.03，耗时不到 100 毫秒。对明显案例做出决定性判断, 当场拒绝或批准，无需摄像头。
设备与 IP 分析模块
03 · 生物识别升级

信号不足时，进行人脸核验。

对于高价值购物车，升级到被动活体检测 ($0.10)，并可选择与存储的买家肖像进行 1:1 人脸比对 ($0.05)。通过 iBeta Level 1 PAD 认证。两秒内出结果。结账时的人脸检查无法通过被盗卡解决。
生物识别认证模块
04 · 拒付证据包

每次争议都有审计包。

决策负载是拒付案例文件, 生物识别结果、IP 评分、设备指纹、国家、ASN、历史订单记录。与欧盟卡的 3-D Secure 2.x 责任转移和 Visa Compelling Evidence 3.0 (CE3.0) 信任客户标准自然匹配。
Webhook 参考
05 · 回头客可复用信任

回头客和信任买家可免去繁琐步骤。

一旦买家在平台上通过一次身份验证，该凭证可在未来的结账中免费复用，通过 Reusable KYC 实现。查找买家之前的 `session_id`；如果凭证有效且最近，则跳过实时筛查。永久免费。
可复用 KYC 模块
06 · Webhook 管道 + 购物车操作

签名判决。购物车操作已连接。

签名的 Webhook 会返回“已批准”、“审核中”或“已拒绝”。使用 HMAC SHA-256 验证 X-Signature-V2。已批准则发货。审核中则暂停，等待人工审核，并将每个模块的信号作为初始案例文件。已拒绝则取消并退款。
Webhook 参考
集成

一个会话。两个阶段。一个签名结果。

针对买家筛查工作流开启筛查。读取签名结果。发货、暂缓或取消。
POST /v3/session/买家风控
$ 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_buyer_screen",
    "vendor_data": "order-A4421",
    "metadata": { "cart_total_cents": 78500 }
  }'
201已创建{ "session_url": "verify.didit.me/..." }
在 webhook 返回 status: Approved 之前，暂停订单。文档 →
POST /webhooks/didit判决
// X-Signature-V2 verified upstream
if (payload.status === "Approved") {
  shipOrder(payload.vendor_data);
} else if (payload.status === "Declined") {
  cancelAndRefund(payload.vendor_data);
}
200确定status Approved · Declined · In Review · Not Finished
在读取负载前，验证 X-Signature-V2。文档 →
代理就绪集成

一键部署买家欺诈风控。

粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent。填写您的技术栈。Agent 将连接购物车触发器，运行两阶段风控，验证 webhook，并处理或暂存订单。
didit-integration-prompt.md
You are integrating a Didit buyer-side fraud screen on a marketplace / e-commerce checkout. Goal: catch stolen-card use, account takeover, gift-card stack abuse, geo-mismatch friendly fraud, and bot scalping on high-value carts. Two stages — cheap signals first, biometric step-up only when signals aren't enough.

WHY THIS SHAPE
  - Most checkouts don't need any friction. Day-to-day buyers on trusted devices from residential networks should sail through.
  - A small percentage are high-value or high-risk — cart over a threshold, gift-card stack, payout to a new card, geo mismatch, new device, velocity anomaly. On those, run a screen.
  - Two stages keep the cost and the friction proportional to the risk. Cheap IP + device check ($0.03) is decisive on the obvious cases. Biometric step-up ($0.10) only fires when the cheap signals are inconclusive AND the order is high-value.
  - 500 verifications free every month. The screen runs inside the free tier for most teams while they tune the thresholds.

PRE-REQUISITES
  - Production API key from https://business.didit.me (sandbox key in 60 seconds, no credit card).
  - A webhook endpoint with HMAC SHA-256 verification of the X-Signature-V2 header using your webhook secret.
  - A Workflow Builder workflow with Device & IP Analysis and optionally Passive Liveness + Face Match 1:1 against the stored buyer portrait.
  - A server-side cart-gate that defaults to BLOCK on the high-risk path and only unblocks on a verified webhook with status: Approved.

STEP 1 — Decide WHEN to screen (your code, not Didit's)
  Run your usual checkout signals. Default triggers worth a screen:
    - Cart total above your account-level tier (e.g. > $500)
    - Gift-card stack of three or more cards in one order
    - Shipping country that doesn't match the billing-card country
    - First buy from a new device
    - Velocity anomaly — N orders within window W from the same buyer
    - Payout / refund destination changed mid-flow

  Day-to-day reads from trusted-device + residential-network buyers do NOT need a screen.

STEP 2 — Open the screen session
  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<wf id with Device & IP Analysis + optional Passive Liveness + Face Match 1:1>",
      "vendor_data": "<your order id, max 256 chars>",
      "callback": "https://<your-app>/checkout/screen/callback",
      "metadata": {
        "cart_total_cents": 78500,
        "currency": "EUR",
        "trigger": "high_value_cart"
      }
    }

  Response: 201 Created with a hosted session URL. Show inline at checkout (web), or open in a Software Development Kit (SDK) webview (mobile). The order stays in HOLD on your side until the signed webhook lands.

STEP 3 — Read the signed webhook
  Didit POSTs the verdict. Verify X-Signature-V2 (HMAC SHA-256 of the raw body) BEFORE reading the JSON.

  Payload (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your order id>",
      "status": "Approved",
      "ip_analysis": { "status": "Approved", "score": 11 },
      "liveness":    { "status": "Approved" },
      "face":        { "status": "Approved", "similarity_score": 0.93 }
    }

  Session status enum (exact case, Title Case With Spaces): Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned.

STEP 4 — Branch the cart action
  Approved      → ship the order, capture the auth, send the confirmation.
  In Review     → hold the order. Route to manual review with the per-module signals as the case file.
  Declined      → cancel the order, refund the auth, log warnings (liveness / face-match / ip flags), throttle the source IP.
  Not Finished  → invite the buyer to retry the screen with a fresh session URL. Don't ship.

STEP 5 — (Optional) Reusable Know Your Customer (KYC) for returning trusted buyers
  Once a buyer has passed identity once on the platform, the credential can replay on future checkouts at no cost via Reusable KYC. Look up the buyer's prior session_id; if the credential is valid and recent, skip the live screen.

  That keeps the friction on the unknown traffic only. Free forever.

STEP 6 — Use the decision payload as the chargeback evidence pack
  When a dispute lands, pull the full decision payload via:
    GET https://verification.didit.me/v3/session/{session_id}/decision/
    Headers:
      x-api-key: <your api key>

  Pairs naturally with:
    - 3-D Secure 2.x (3DS2) liability shift on EU cards
    - Visa Compelling Evidence 3.0 (CE3.0) — biometric + IP + device fingerprint + prior-order history meets the "trusted customer" bar
    - Mastercard Identity Check chargeback dispute kit

WEBHOOK EVENT NAMES
  - Sessions: standard session webhook. One endpoint, status field tells you the lifecycle.
  - Verify X-Signature-V2 (HMAC SHA-256) on every payload.

WHAT IT BLOCKS
  - Stolen-card use on first-time-buy + geo mismatch
  - Account takeover on a previously-verified buyer (the step-up is the second-factor)
  - Friendly fraud where the cardholder disputes a charge they actually authorised
  - Bot scalpers running multi-item carts from datacenter Internet Protocol (IP) addresses
  - Gift-card stack drains funded by a stolen card
  - Reshipper / mule patterns (ship-to address inconsistent with prior orders)

CONSTRAINTS
  - Session statuses use Title Case With Spaces. Never UPPER_SNAKE_CASE — that's the Transactions API.
  - Start with IP-only on the cheap cases. Add the biometric step-up only on high-value carts or when IP alone is inconclusive — keeps cost down and friction proportional.
  - 200+ fraud signals are evaluated on every session at no extra cost — read them off the decision payload, don't re-query.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/core-technology/ip-analysis/overview
  - https://docs.didit.me/core-technology/biometric-auth/overview
  - https://docs.didit.me/core-technology/reusable-kyc/overview
  - 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
    针对低风险案例的设备与IP分析调用, 对明显欺诈行为果断处理。
  • $0.00
    每笔高价值购物车事件，包含生物识别验证步骤, 验证 $0.10 + IP $0.03。
  • <0s
    入门级安卓设备上的端到端升级验证。
  • 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 is buyer fraud on a marketplace?

Any pattern where the person paying does not have the right to pay with that instrument, or where the transaction is structured to trigger a later chargeback.

Common shapes:

  • Stolen-card use, a fresh card-not-present buy from a new device on a country-mismatch ship-to
  • Account takeover, an attacker uses a hijacked logged-in account to buy and ship to themselves
  • Friendly fraud, the cardholder authorised the purchase, received the goods, then disputes the charge
  • Gift-card stack abuse, stolen card funds a stack of digital gift cards that are immediately drained
  • Bot scalpers, automated checkout farms buying limited-supply items at scale
Why two stages instead of one universal screen?

Friction has a cost. Conversion drops measurably on every extra checkout step. Most buyers, known device, residential network, normal cart total, should sail through with no screen at all.

Two stages keep the friction proportional to the risk:

  • Stage 1 ($0.03), Device & IP Analysis is cheap and silent. Decisive on the obvious cases (VPN + datacenter Internet Protocol (IP) + headless browser = block on the spot; trusted device + residential ISP = pass on the spot).
  • Stage 2 ($0.10), Passive Liveness step-up fires only on the small slice where stage 1 is inconclusive AND the cart total is above the worth-it threshold.

The result: the median checkout adds zero friction, and the high-risk slice gets a decisive check.

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.

When does the biometric step-up fire?

Only when stage 1 is inconclusive AND the order is high-value enough to justify the friction. Examples:

  • IP score is in the grey zone (say 40–70) but cart is above \$500
  • Cart includes a high-resale digital good (gift card stack, electronics, luxury) on a new device
  • Buyer is paying out to a card seen for the first time on a returning account
  • Velocity-rule trip on an established buyer

The step-up is Passive Liveness at \$0.10, optionally with a Face Match 1:1 against the stored buyer portrait at an extra \$0.05. Sub-two-second verdict on entry-level Android.

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 this work on mobile and web?

Yes. The same POST /v3/session/ powers both. On web, render the returned session_url inline at checkout. On mobile, open it in the Didit Software Development Kit (SDK) webview, five SDKs ship: Web, iOS, Android, React Native, Flutter, all free.

The verdict comes through the same signed webhook regardless of surface. One integration, every platform.

What does the recipe cost?

Two line items in the worst case:

  • Device & IP Analysis check: \$0.03 per call (cheap stage)
  • Passive Liveness step-up: \$0.10 per session (only on the high-value cases)
  • Face Match 1:1 against stored portrait (optional): \$0.05 per match

Median protected checkout that needs both stages: ~\$0.13. Most checkouts run only stage 1 at \$0.03. Returning trusted buyers via Reusable KYC are free forever.

The first 500 verifications every month are free on every account.

Which industries run this recipe?

Anywhere the basket is big enough that a stolen-card buy hurts:

  • High-AOV marketplaces, electronics, luxury, art, second-hand goods over \$500
  • Digital-good resellers, gift cards, in-game items, software licences
  • Ticketing, sports, concerts, travel, where scalping bots cluster
  • Subscription commerce, high-tier subscription boxes, premium SaaS plans
  • Cross-border e-commerce, geo-mismatch shipping is the universal red flag
  • Pharmacy / regulated products, age + identity + chargeback all matter together

One workflow, every cart shape.

Related

相关模块与工作流

身份与欺诈基础设施。

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

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