無料
無料
月額$0。クレジットカード不要。
- 無料KYCバンドル（本人確認 + パッシブ・ライブネス + 顔照合 + デバイス＆IP分析）, 毎月500回まで
- ブロックリストユーザー
- 重複検出
- すべてのセッションで200以上の不正シグナル
- Diditネットワーク全体でのKYC再利用
- ケース管理プラットフォーム
- ワークフロービルダー
- 公開ドキュメント、サンドボックス、SDK、MCP (Model Context Protocol) サーバー
- コミュニティサポート
世界中の2,000以上の組織から信頼されています。
ほとんどのチェックアウトで摩擦が不要な理由
信頼できる買い手にはスムーズな体験を。不正の急増には断固たる対応を。
注文の90%は、信頼できるデバイスを使用する日常的な購入者によるもので、スムーズに 処理されるべきです。リスクが急増する10%のケースでは、スクリーンが適用されます。安価なケースでは$0.03のIP+デバイスチェック、高額なケースでは$0.10の生体認証ステップアップ。毎月500件の認証が無料です。
仕組み
サインアップから認証済みユーザーまで、4つのステップで完了。
- ステップ 01
ワークフローを作成
ID、生体認証、顔照合、制裁リスト、住所、年齢、電話番号、メールアドレス、カスタム質問など、必要なチェックを選択します。ダッシュボードでフローにドラッグ＆ドロップするか、同じフローをAPIにポストします。条件分岐やA/Bテストもコード不要で実行できます。
- ステップ 02
連携
Web、iOS、Android、React Native、Flutter SDKでネイティブに組み込むか、ホストされたページにリダイレクトします。または、メール、SMS、WhatsAppなど、どこからでもユーザーにリンクを送信するだけです。お使いのスタックに合った方法をお選びください。
- ステップ 03
ユーザーがフローを完了
Diditは、カメラ、照明の指示、モバイル連携、アクセシビリティをホストします。ユーザーがフローを実行中に、200以上の不正信号をリアルタイムでスコアリングし、すべてのフィールドを信頼できるデータソースと照合して検証します。2秒以内に結果が出ます。
- ステップ 04
結果を受け取る
リアルタイムの署名付きWebhookにより、ユーザーが承認、拒否、またはレビューに送られた瞬間にデータベースが同期されます。必要に応じてAPIをポーリングすることも可能です。または、コンソールを開いてすべてのセッション、すべての信号を検査し、ケースを独自の方法で管理できます。
01 · チェックアウトトリガー
実行タイミングは自由に設定。スクリーニングはDiditにお任せください。
設定した上限を超えるカート合計額。3つ以上のギフトカードの積み重ね。請求カードと異なる配送国。新しいデバイスからの初回購入。速度異常, 期間W内のN件の注文。フロー途中で変更された支払い/返金先。これらすべてをノーコードのワークフロービルダーで編集可能です。
ワークフローオーケストレーターモジュールDidit · Risk-trigger policy
When the screen fires.
SignalThresholdScreen
- Cart total above tier> $500IP + step-up
- Gift-card stack≥ 3 cardsStep-up
- Geo mismatch · shippingCountry flipIP only
- New device · first buyFirst seenIP only
- Returning buyer · cleanTrustedPass
Edit rules in the Workflow Builder. No redeploy.
02 · 安価なIP + デバイススクリーン
まずシグナルで判断。低コストで迅速に。
デバイス＆IP分析は、0〜100のリスクスコアに加え、Virtual Private Network (VPN)、Tor、データセンター、国、Autonomous System Number (ASN)、デバイスフィンガープリントのフラグを返します。1コールあたり$0.03、100ms未満で完了します。明らかなケースでは即座に判断を下し、その場で拒否または承認され、カメラは不要です。
デバイス＆IP分析モジュールDidit · Device & IP Analysis
Signals first. Cheap. Decisive.
SignalDetectedScore / verdict
- Residential VPN exitBright Data · NLBlock
- Country mismatch · ship-toCard US → Ship NGStep up
- Headless browser flagnavigator.webdriverBlock
- Device velocity8 orders · 30 minStep up
- Residential ISP · trusted deviceVodafone · iOSPass
Score, flags, country, ASN, under 100ms.
03 · 生体認証ステップアップ
シグナルだけでは不十分な場合に顔認証を実施。
高額なカートでは、パッシブ生体認証（$0.10）にエスカレートし、オプションで保存された購入者の顔写真との1:1顔照合（$0.05）を行います。iBeta Level 1 Presentation Attack Detection (PAD) 認定済み。2秒未満で判定。チェックアウト時の顔認証は、盗まれたカードでは突破できません。
生体認証モジュールDidit · Biometric Authentication
A face check when signals aren't enough.
Confirm · 1 of 1
Hold still for the check
- IP + device pre-screen$0.03
- Passive Liveness$0.10
- Face Match 1:1 (optional)$0.05
- Verdict in webhook—
iBeta Level 1 PAD · sub-2-second~$0.13 per event
04 · チャージバック証拠パック
あらゆる紛争に監査パックを提供。
決定ペイロードはチャージバックケースファイルです, 生体認証判定、IPスコア、デバイスフィンガープリント、国、Autonomous System Number (ASN)、過去の注文履歴。EUカードの3-D Secure 2.x責任移行や、Visa Compelling Evidence 3.0 (CE3.0) の信頼できる顧客基準と自然に連携します。
WebhookリファレンスDidit · Chargeback evidence
Audit pack for every dispute.
order-A4421 · evidence pack
- Biometric step-upApproved · 0.94 sim
- IP + device score11 / 100 · clean
- Country + ASNES · Movistar
- Signed webhook payloadSHA-256 verified
- Buyer prior orders120 days · 14 orders
Pairs with 3-D Secure 2.x and Visa Compelling Evidence 3.0.
05 · リピーター向けの再利用可能な信頼
信頼できるリピーターはスムーズに利用できます。
一度プラットフォームで本人確認を完了した購入者は、Reusable KYCを通じて、将来のチェックアウト時に無料でその認証情報を再利用できます。購入者の以前の`session_id`を検索し、認証情報が有効で最近のものであれば、ライブスクリーンをスキップします。永続的に無料です。
Reusable KYCモジュールDidit · Reusable KYC
Returning buyers skip the friction.
First pass
verified credential
Issued2026-03-14
valid · 12 months$0.00 reuse
Checkout
One verified buyer. Many low-friction checkouts.Free forever
06 · Webhookパイプライン + カートアクション
署名付きの判定。カートアクションと連携。
署名付きWebhookがApproved、In Review、またはDeclinedのステータスで届きます。X-Signature-V2をHash-based Message Authentication Code (HMAC) SHA-256で検証します。Approvedは注文を発送します。In Reviewは、各モジュールの信号を初期ケースファイルとして手動レビューのために保留します。Declinedはキャンセルと返金を行います。
WebhookリファレンスDidit · Webhook · X-Signature-V2
Signed verdict. Cart action wired.
POST /webhooks/didit
{
"session_id": "order-A4421",
"vendor_data": "order-A4421",
"status": "Approved",
"ip_analysis": { "score": 11 },
"liveness": { "status": "Approved" }
}- Approvedship the order
- In Reviewhold for manual review
- Declinedcancel + refund + log
Verify the signature BEFORE reading the body.
連携
1つのセッション。2つのステージ。1つの署名済み判定。
購入者スクリーンワークフローに対してスクリーンを開きます。署名された判定を読み取ります。発送、保留、またはキャンセルを行います。
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);
}200OKステータス: 承認済み・拒否・審査中・未完了
ペイロードを読み込む前に
X-Signature-V2を検証してください。ドキュメント →エージェント対応統合
購入者不正対策を1つのプロンプトで実装。
Claude Code、Cursor、Codex、Devin、Aider、またはReplit Agentに貼り付けてください。スタック情報を入力すると、エージェントがカートトリガーを連携し、2段階のスクリーニングを実行し、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以上の国で稼働しており、四半期ごとに監査とペネトレーションテストを実施しています。EU加盟国の政府が対面認証よりも安全だと正式に認めた唯一のIDプロバイダーです。
セキュリティ＆コンプライアンス資料を読むEU金融サンドボックス
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準拠
実績データ
実績データ
- $0.00デバイスとIPアドレスの分析。安価なケースでは費用対効果が高く、明らかな不正には決定的な効果を発揮します。
- $0.00高額カートイベントごとの生体認証ステップアップ。ステップアップは$0.10、IPアドレス分析は$0.03です。
- <0sエントリーレベルのAndroid端末でのステップアップ認証の判定にかかる時間（エンドツーエンド）。
- 0毎月、すべてのアカウントで無料の認証をご利用いただけます。
3つのティア、1つの料金表
無料で開始。従量課金。エンタープライズまで対応。
毎月500回まで無料認証を永続的に提供。本番環境では従量課金。エンタープライズプランではカスタム契約、データレジデンシー、SLA（サービスレベルアグリーメント）に対応します。
最も人気
従量課金
従量課金
使った分だけお支払い。25以上のモジュール。モジュールごとの公開価格、月額最低料金なし。
- フルKYC（本人確認 + 生体認証 + IP / デバイス）が$0.33
- 10,000以上のAMLデータセット, 制裁、PEP、ネガティブ情報
- データベース検証のための1,000以上の政府データソース
- トランザクションモニタリングが1トランザクションあたり$0.02
- ライブKYBが1企業あたり$2.00
- ウォレットスクリーニングが1チェックあたり$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.