無料
無料
月額$0。クレジットカード不要。
- 無料KYCバンドル（本人確認 + パッシブ・ライブネス + 顔照合 + デバイス＆IP分析）, 毎月500回まで
- ブロックリストユーザー
- 重複検出
- すべてのセッションで200以上の不正シグナル
- Diditネットワーク全体でのKYC再利用
- ケース管理プラットフォーム
- ワークフロービルダー
- 公開ドキュメント、サンドボックス、SDK、MCP (Model Context Protocol) サーバー
- コミュニティサポート
世界中の2,000以上の組織から信頼されています。
規制当局が求めるもの
プレイヤーを認証。自己規制を確認。すべての入金を監視。
すべての規制対象事業者は、厳格な18歳以上年齢確認、自己排除登録との照合、 しきい値を超える入金に対するAML、出金時の生体認証再認証を義務付けられています。 Diditはこれらを1つのワークフローとして、プレイヤー1人あたり約$0.40 + 入金1件あたり$0.02で提供します。 毎月500件の認証が無料です。
仕組み
サインアップから認証済みユーザーまで、4つのステップ。
- ステップ 01
ワークフローを作成
本人確認、生体認証、顔照合、制裁リスト、住所、年齢、電話番号、メールアドレス、カスタム質問など、必要なチェックを選択します。ダッシュボードでフローにドラッグ＆ドロップするか、同じフローをAPIにポストします。条件分岐やA/Bテストも、コード不要で実行できます。
- ステップ 02
統合
Web、iOS、Android、React Native、FlutterのSDKでネイティブに組み込むか、ホストされたページにリダイレクトします。または、メール、SMS、WhatsAppなど、どこからでもユーザーにリンクを送信するだけです。お使いのスタックに合った方法をお選びください。
- ステップ 03
ユーザーがフローを完了
Diditがカメラ、照明の指示、モバイル連携、アクセシビリティをホストします。ユーザーがフローを実行している間、200以上の不正シグナルをリアルタイムでスコアリングし、すべてのフィールドを信頼できるデータソースと照合して検証します。2秒以内に結果が出ます。
- ステップ 04
結果を受け取る
リアルタイムの署名付きWebhookにより、ユーザーが承認、拒否、またはレビューに送られた瞬間にデータベースが同期されます。必要に応じてAPIをポーリングすることも可能です。または、コンソールを開いてすべてのセッション、すべてのシグナルを検査し、ケースを管理することもできます。
規制対象事業者向けに構築 · インフラ並みの価格
6つのチェック。2回のAPIコール。プレイヤー1人あたり$0.40。
責任あるゲーミングのコンプライアンスは単一のチェックではなく、レシピのようなものです。規制機関ごとにモジュールを切り替え、市場ごとにルールバンドルを交換し、UKGC、MGA、Curaçao、SIGAP、ANJ全体で同じワークフローを実行できます。
01 · 18歳以上年齢確認
最も安価なパス：まず年齢推定。
年齢推定は$0.10で、すべてのサインアップ時に実行されます。18歳以上の確実なユーザーは通過し、ボーダーライン（16〜21歳）のユーザーは$0.15の本人確認にエスカレートします。ボーダーラインのコホートのみ追加料金が発生するため、プレイヤーあたりの平均コストを低く抑えられます。
年齢推定モジュールDidit · Age Estimation
18+ enforced. Cheapest path.
Estimated bandNext stepVerdict
- 25+ confidentAllowPass
- 18-24 confidentAllowPass
- 16-21 borderlineID VerificationEscalate
- Under 18 confidentBlock + logBlock
ID Verification adds $0.15 on borderline only
02 · 自己排除チェック
すべてのサインアップで登録をクロスチェック。
自己排除インデックスと、規制機関が参加している場合は国家登録（UK GAMSTOP、スペイン RIGA、イタリア RUA、ブラジル Programa Jogo Responsável）に対して、顔検索1:N（無料）を実行します。新しい名前と新しいメールアドレスで再申請した自己排除プレイヤーは、200ミリ秒以内にフラグが立てられます。
顔検索1:NモジュールDidit · Face Search 1:N
Self-exclusion, on every signup.
New player
Self-excluded · GAMSTOP0.93Block
Self-excluded · operator0.91Block
Cooling-off · 30 days0.88Hold
Clear0.04Pass
<200ms per index lookup
03 · 入金時のAML
しきい値を超える入金者をスクリーニング。
オペレーターが設定したしきい値（£/€/$金額）を超える入金に対するAMLスクリーニング。14言語で1,300以上の制裁リスト、政治的要人（PEP）、ネガティブメディアリストを毎日更新。1チェックあたり$0.20。
AMLスクリーニングモジュールDidit · AML
Screen the depositor above threshold.
HitSource listAction
- Sanctions matchOFAC SDNBlock
- PEP · foreign officialDow Jones PEPReview
- Adverse media · financeEU adverseReview
- ClearAll listsPass
1,300+ lists · 14 languages · daily refreshThreshold configurable
04 · 入金制限 + 損失上限
プレイヤーティアごとのリアルタイム制限。
トランザクション監視ルールエンジンは、日次/週次/月次の入金制限と損失上限をリアルタイムで強制し、1コールあたり$0.02です。プレイヤーが設定した自己制限が優先され、規制機関が義務付けた上限がそれを上書きします。コード不要のワークフロービルダーでルールを編集でき、再デプロイは不要です。
トランザクション監視モジュールDidit · Transaction Monitoring
Limits per tier. Real-time.
RuleThresholdAction
- Daily deposit · Tier 1≤ £100Pass
- Weekly deposit · Tier 1≤ £500Pass
- Monthly loss cap≤ £1,000Review
- Velocity · 5 deposits / 1hBurstReview
- Self-imposed limit hitUser-setBlock
Rules editable in no-code Workflow Builder
05 · 出金再認証
すべての出金時に顔チェック。
生体認証は、プレイヤーの登録時の自撮り写真と顔照合を1認証あたり$0.10で実行します。アカウント乗っ取りによる出金をブロックし、アカウント設定変更や休眠状態からの再認証にも同様の機能を提供します。
生体認証モジュールDidit · Biometric Authentication
Face check on withdrawal.
Enrolment
Withdrawal
Similarity0.95Approve
Re-auth cadence configurable per app
06 · 規制機関ごとの監査パック
UKGC、MGA、Curaçao、SIGAP、ANJ。
規制機関ごとのエクスポートテンプレートはビジネスコンソールに搭載されています。本人確認証拠、AMLヒット、自己排除チェック、入金ログ、出金再認証など、すべてが1つのバンドルにまとめられ、規制機関の要件に従って5年間保持されます。
業界, ギャンブル＆iGamingDidit · Audit log
Regulator-ready audit pack.
- UK Gambling Commission (UKGC)Sandboxes + RAG export
- Malta Gaming Authority (MGA)License-class compliance
- Curaçao Gaming Control Board (CGCB)Operator-disclosure ready
- SIGAP (Brazil) + ANJ (France)Per-jurisdiction templates
5-year retention configurableSOC 2 · ISO 27001
連携
オンボーディングは1セッション。入金ごとに1回のトランザクションコール。
オンボーディングセッションを開きます。署名された判定を読み取ります。すべての入金と出金を /v3/transactions/ にポストします。
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_igaming_onboard",
"vendor_data": "player-91",
"metadata": { "regulator": "UKGC" }
}'201作成済み{ "session_url": "verify.didit.me/..." }
ウェブフックが
status: Approvedを返すまでアカウント作成をブロック。ドキュメント →POST /v3/transactions/入金
$ curl -X POST https://verification.didit.me/v3/transactions/ \
-H "x-api-key: $DIDIT_API_KEY" \
-d '{
"transaction_id": "deposit-991",
"transaction_details": { "direction": "INBOUND", "amount": "150.00", "currency": "GBP", "currency_kind": "fiat" },
"subject": { "vendor_data": "player-91", "full_name": "Jamie Example" },
"counterparty": { "full_name": "プレイヤー入金" }
}'201作成済みステータス: 承認済み · レビュー中 · 却下済み · ユーザー待ち
ルールエンジンがリアルタイムで制限とAMLを適用。
$0.02 /コール。ドキュメント →エージェント対応統合
責任あるゲーミングを1つのプロンプトで実装。
Claude Code、Cursor、Codex、Devin、Aider、またはReplit Agentに貼り付けてください。お使いのスタックに合わせて設定すると、オンボーディングワークフローの構築、入金監視コールの接続、継続的なAML登録、出金再認証の追加が自動で行われます。
didit-integration-prompt.md
You are integrating Didit into a regulated iGaming / sports-betting operator (UK Gambling Commission, Malta Gaming Authority, Curaçao, SIGAP, ANJ). Three obligations on every player and every deposit:
- Onboarding: 18+ age gate, ID Verification, self-exclusion register cross-check.
- Deposits: AML on above-threshold deposits, real-time deposit limits + loss caps.
- Withdrawals + sensitive actions: biometric re-auth against the enrolment selfie.
Recommended recipe + pricing (verified live):
- Onboarding session: $0.10 Age Estimation + $0.15 ID Verification + $0.10 Passive Liveness + $0.05 Face Match 1:1 + $0.20 AML (above threshold). Face Search 1:N against self-exclusion register: free. Average ~$0.40 per player.
- Per-deposit / per-withdrawal transaction: $0.02 per call to Transaction Monitoring (rule engine + limits).
- AML re-screening on flagged transactions: $0.20 per check.
- Biometric re-auth on withdrawal: $0.10 per auth.
- 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.
HMAC-SHA256 verification MUST run against the raw body bytes (the raw payload as Didit sent it) BEFORE any JSON parsing — re-serialising the parsed body changes whitespace and key order, which invalidates the signature. - A workflow_id from the Workflow Builder that bundles Age Estimation + ID Verification + Passive Liveness + Face Match 1:1 + Face Search 1:N (against your self-exclusion index) + AML Screening.
- A self-exclusion index loaded into the Didit Face Search 1:N — your own banned-players list at minimum; GAMSTOP / RIGA / equivalent national register where the regulator participates.
- Transaction Monitoring enabled in the Business Console with the rule bundle for sports-betting or online-casino seeded.
STEP 1 — Open the onboarding session at signup
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<wf id with age gate + ID + AML + Face Search self-exclusion>",
"vendor_data": "<your player id, max 256 chars>",
"callback": "https://<your-app>/igaming/onboarding/callback",
"metadata": {
"regulator": "UKGC",
"license_class": "remote_casino_betting",
"min_age": 18
}
}
Response: 201 Created with the hosted session URL. Redirect the player. Sub-2-second median verdict on completion.
STEP 2 — Read the signed webhook on the onboarding verdict
Didit POSTs to your callback. Session statuses are Title Case With Spaces:
Body (excerpted):
{
"session_id": "<uuid>",
"vendor_data": "<your player id>",
"status": "Approved",
"age_estimation": { "estimated_age": 27, "confidence": 0.92 },
"id_verification": { "status": "Approved", "dob": "1997-03-12" },
"face": { "status": "Approved", "similarity_score": 0.94 },
"face_search": { "status": "Approved", "matches": [] },
"aml": { "status": "Approved", "hits": [] }
}
Session 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.
STEP 3 — Branch on the onboarding verdict
Approved + 18+ → unlock the player account.
Approved + Face Search hit on self-exclusion → block, log to compliance, surface support resources.
Declined → block, log AML hit detail.
In Review → hold the account, route to ops queue.
STEP 4 — Monitor every deposit + withdrawal
POST https://verification.didit.me/v3/transactions/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"transaction_id": "<your deposit reference>",
"transaction_category": "finance",
"transaction_details": {
"direction": "INBOUND",
"amount": "150.00",
"currency": "GBP",
"currency_kind": "fiat",
"action_type": "deposit"
},
"subject": {
"entity_type": "individual",
"vendor_data": "<your player id>",
"full_name": "<player full name>"
},
"counterparty": {
"entity_type": "individual",
"full_name": "Player deposit"
}
}
Response: status APPROVED | IN_REVIEW | DECLINED | AWAITING_USER. Rule engine evaluates against deposit limits, loss caps, velocity thresholds, and Reasonable-Affordability triggers in real time.
STEP 5 — Biometric re-auth on withdrawal
Open a re-auth session before processing a withdrawal:
POST https://verification.didit.me/v3/session/
Body:
{
"workflow_id": "<wf id with Liveness + Face Match against enrolment selfie>",
"vendor_data": "<your player id>",
"metadata": { "trigger": "withdrawal", "withdrawal_amount": "500.00" }
}
Block the withdrawal until status: Approved with similarity above your threshold (default 0.85).
STEP 6 — Ongoing AML monitoring on the active player base
Every Approved player is automatically re-screened DAILY by Didit's continuous AML monitoring at $0.07 per player per year. The same session webhook fires when the verdict flips.
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, DECLINED, AWAITING_USER). They live in different APIs — don't mix them in the same code path.
- Self-exclusion cross-check must happen BEFORE the player can deposit — a post-deposit check is useful for audit but creates a refund obligation.
- Default audit retention is 5 years post-relationship per the UK Gambling Commission / Malta Gaming Authority requirements; configure per workflow in the Business Console.
- 200+ fraud signals are evaluated on every onboarding session at no extra cost.
Read the docs:
- https://docs.didit.me/sessions-api/create-session
- https://docs.didit.me/transaction-monitoring/overview
- https://docs.didit.me/core-technology/aml-screening/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.40プレイヤー1人あたりのオンボーディング費用, 年齢確認 + 本人確認 + AML + 自己規制チェック。
- $0.00トランザクションモニタリングによる入出金監視1件あたり。
- <0ms自己規制インデックスに対するFace Search 1:Nルックアップ1件あたり。
- 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 does 'responsible gaming' actually mean for an iGaming operator?
Three obligations a regulated operator owes on every player, every deposit, and every withdrawal:
- Age & identity, confirm the player is 18+ (or the local statutory age) and that the documented identity matches the live face.
- Self-exclusion respect, refuse to onboard or accept funds from anyone on a self-exclusion register, including national schemes (UK GAMSTOP, Spain RIGA, Italy RUA, Brazil Programa Jogo Responsável).
- Affordability + harm prevention, enforce deposit limits, loss caps, and reasonable-affordability triggers; provide self-imposed-limit tools; surface support resources when risk signals fire.
Didit ships the verification + cross-check + monitoring half; you wire the support-resources surfacing on top.
Which regulators does this recipe satisfy?
The major ones an EU + UK + LATAM operator typically holds licences from:
- UK Gambling Commission (UKGC), Licence Condition 17 (age + identity) + Licence Condition 16 (anti-money laundering).
- Malta Gaming Authority (MGA), Player Protection Directive + Implementing Procedure on AML.
- Curaçao Gaming Control Board (CGCB), post-2023 LOK reforms.
- SIGAP (Brazil), federal sports-betting and online-casino regulation under Lei nº 14.790/2023.
- ANJ (France), Autorité Nationale des Jeux.
- Spelinspektionen (Sweden), DGOJ (Spain), ADM (Italy), KSA (Netherlands), all aligned around the same age + ID + AML + self-exclusion + limits pattern.
Didit's audit-pack templates ship per regulator in the Business Console.
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.
How does the self-exclusion register cross-check work?
Two layers stack:
- Operator-private exclusion index, every player who has self-excluded on your platform is indexed by face embedding. Mandatory; the regulator expects this.
- National register, where the regulator participates (GAMSTOP in the UK, RIGA in Spain, RUA in Italy, Programa Jogo Responsável in Brazil), the player's face is also cross-checked against the national register via Face Search 1:N.
Sub-200ms verdict. A self-excluded player re-applying with a new email + new IP + a different document is caught because the face is the constant. Free, included in every workflow.
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 does biometric re-auth on withdrawal stop fraud?
Account-takeover attackers don't want to lose chips, they want to cash out. A withdrawal flow without re-auth is the most-attacked surface in iGaming.
Biometric Authentication runs a Face Match against the player's enrolment selfie at $0.10 per auth. The withdrawal is held until the verdict is Approved with similarity above your threshold (default 0.85, higher for big withdrawals). Same primitive optionally runs on:
- Account-settings change (password reset, withdrawal-address change).
- Login from a new device + new IP country.
- Dormancy return (player back after 60+ days).
A hijacked account can't cash out, change the destination bank, or re-route the funds without facing the camera.
How does this all integrate with my existing player wallet / RGS?
Three integration points:
- Onboarding, your signup form opens a /v3/session/ and gates account creation on the signed webhook.
- Deposits + withdrawals, your wallet posts each transaction to /v3/transactions/ before settling; rule engine returns APPROVED / IN_REVIEW / DECLINED / AWAITING_USER inline.
- Withdrawal re-auth, your wallet opens a new /v3/session/ (Liveness + Face Match) and holds the payout until the webhook returns
Approved.
Four pluggable integrations, no replatform. Same /v3/ contract across the lifecycle. Same audit pack across every player.
What about crypto-first iGaming operators?
Same flow, with one extra: wallet screening on every deposit and withdrawal.
The /solutions/crypto-onramp-kyc-kyt recipe applies, wallet screening runs INSIDE POST /v3/transactions/ via currency_kind: "crypto" and a wallet address on the counterparty. Sanctioned-wallet, mixer, and exchange-high-risk categories are scored at $0.15 per check (Didit managed) or $0.02 per check (bring-your-own provider key).
Combined with the standard iGaming recipe, a crypto-first sports-betting platform runs ~$0.40 player onboarding + $0.17 per crypto deposit (when wallet screening is on) + $0.02 per fiat transaction.