Usia, identitas, dan pengecualian diri dalam satu sesi yang lebih aman.
Batasan usia 18+, Verifikasi ID, pemeriksaan silang daftar pengecualian diri, AML pada deposit, siap audit UKGC, MGA, Curaçao. ~$0.40 per onboarding pemain.
Dipercaya oleh 2.000+ organisasi di seluruh dunia.
Apa yang regulator tuntut
Verifikasi pemain. Periksa pengecualian diri. Pantau setiap deposit.
Setiap operator teregulasi wajib memiliki batasan usia 18+ yang ketat, pemeriksaan silang daftar pengecualian diri, AML pada deposit ambang batas, dan otentikasi ulang biometrik saat penarikan. Didit menyediakannya sebagai satu alur kerja dengan biaya sekitar $0.40 per pemain + $0.02 per deposit. 500 verifikasi gratis setiap bulan.
Cara kerjanya
Dari pendaftaran hingga pengguna terverifikasi dalam empat langkah.
Langkah 01
Buat alur kerja
Pilih pemeriksaan yang kamu inginkan, ID, liveness, face match, sanksi, alamat, usia, telepon, email, pertanyaan kustom. Cukup drag-and-drop ke alur di dashboard, atau post alur yang sama ke API kami. Buat percabangan berdasarkan kondisi, jalankan A/B test, tanpa perlu coding.
Langkah 02
Integrasikan
Integrasikan secara native dengan SDK Web, iOS, Android, React Native, atau Flutter kami. Redirect ke halaman yang di-host. Atau cukup kirim link ke user kamu, via email, SMS, WhatsApp, atau platform lainnya. Pilih yang paling sesuai dengan stack kamu.
Langkah 03
Pengguna melewati alur
Didit mengelola kamera, isyarat pencahayaan, mobile hand-off, dan aksesibilitas. Saat user dalam alur, kami menilai 200+ sinyal fraud secara real-time dan memverifikasi setiap field terhadap sumber data yang terpercaya. Hasilnya kurang dari dua detik.
Langkah 04
Kamu akan menerima hasilnya
Webhook terautentikasi secara real-time menjaga database kamu tetap sinkron saat user disetujui, ditolak, atau dikirim untuk ditinjau. Lakukan polling API sesuai permintaan. Atau buka konsol untuk memeriksa setiap sesi, setiap sinyal, dan mengelola kasus sesuai keinginanmu.
Dibuat untuk operator teregulasi · Harga sekelas infrastruktur
Enam pemeriksaan. Dua panggilan API. $0.40 per pemain.
Kepatuhan responsible-gaming bukan hanya satu pemeriksaan, ini adalah resep. Aktifkan setiap modul per regulator, tukar bundle aturan per pasar, jalankan workflow yang sama di UKGC, MGA, Curaçao, SIGAP, dan ANJ.
Estimasi Usia seharga $0.10 berjalan di setiap pendaftaran. User yang terbukti berusia 18+ akan lolos; yang mendekati batas (16-21) akan ditingkatkan ke Verifikasi ID seharga $0.15. Hanya kelompok yang mendekati batas yang membayar lebih, ini menjaga biaya rata-rata per pemain tetap rendah.
Face Search 1:N (gratis) terhadap indeks self-exclusion kamu dan, jika regulator berpartisipasi, daftar nasional (UK GAMSTOP, Spanyol RIGA, Italia RUA, Brazil Programa Jogo Responsável). Pemain yang self-excluded yang mendaftar ulang dengan nama + email baru akan terdeteksi dalam waktu kurang dari 200ms.
AML Screening pada deposit di atas ambang batas yang dikonfigurasi operator (jumlah £/€/$). 1.300+ daftar sanksi, Politically Exposed Persons (PEP), dan media yang merugikan dalam 14 bahasa, diperbarui setiap hari. $0.20 per pemeriksaan.
1,300+ lists · 14 languages · daily refreshThreshold configurable
04 · Batas deposit + batas kerugian
Batas real-time per tier pemain.
Mesin aturan Transaction Monitoring memberlakukan batas deposit harian / mingguan / bulanan dan batas kerugian secara real-time dengan biaya $0.02 per panggilan. Batas yang ditetapkan sendiri oleh pemain akan diutamakan; batas yang diamanatkan regulator akan mengesampingkan. Edit aturan di Workflow Builder tanpa kode tanpa perlu redeploy.
Autentikasi Biometrik menjalankan Face Match terhadap selfie pendaftaran pemain dengan biaya $0.10 per autentikasi. Ini mencegah pengambilalihan akun untuk melakukan penarikan, primitif yang sama juga mendukung perubahan pengaturan akun dan re-autentikasi dormansi.
Template ekspor per regulator tersedia di Business Console, bukti identitas, temuan AML, pemeriksaan self-exclusion, log deposit, re-autentikasi penarikan, semuanya dalam satu bundle, disimpan selama 5 tahun sesuai persyaratan regulator.
Rule engine menerapkan batasan + AML secara real time. $0.02 per panggilan.dokumen →
Integrasi siap agen
Selesaikan responsible gaming hanya dengan satu prompt.
Tempel ke Claude Code, Cursor, Codex, Devin, Aider, atau Replit Agent. Isi stack kamu. Agent akan membuat alur onboarding, menghubungkan panggilan pemantauan deposit, mendaftarkan AML berkelanjutan, dan menambahkan otorisasi ulang penarikan.
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.
Butuh konteks lebih? Lihat dokumentasi modul lengkapnya.docs.didit.me →
Dirancang untuk kepatuhan
Buka negara baru dengan satu klik. Kami yang mengerjakan bagian sulitnya.
Kami membuka anak perusahaan lokal, mengamankan lisensi, menjalankan pengujian penetrasi, mendapatkan sertifikasi, dan menyelaraskan dengan setiap regulasi baru. Untuk meluncurkan verifikasi di negara baru, cukup aktifkan tombol. 220+ negara sudah aktif, diaudit dan diuji penetrasi setiap kuartal, satu-satunya penyedia identitas yang secara formal disebut oleh pemerintah negara anggota Uni Eropa lebih aman daripada verifikasi langsung.
Per pemain yang di-onboard, verifikasi usia + ID + AML + pemeriksaan pengecualian diri.
$0.00
Per deposit / penarikan yang dipantau via Transaction Monitoring.
<0ms
Per Face Search 1:N terhadap indeks pengecualian diri kamu.
0
Verifikasi gratis setiap bulan, di setiap akun.
Tiga tingkatan, satu daftar harga
Mulai gratis. Bayar sesuai penggunaan. Skala ke Enterprise.
500 verifikasi gratis setiap bulan, selamanya. Pay-as-you-go untuk produksi. Kontrak kustom, data residency, dan SLA (Service Level Agreements) untuk Enterprise.
Gratis
Gratis
$0 / bulan. Tidak perlu kartu kredit.
Paket KYC gratis (Verifikasi ID + Passive Liveness + Face Match + Analisis Perangkat & IP), 500 / bulan, setiap bulan
User yang masuk daftar hitam
Deteksi Duplikat
200+ sinyal fraud di setiap sesi
KYC yang dapat digunakan kembali di seluruh jaringan Didit
Platform Manajemen Kasus
Workflow Builder
Dokumentasi publik, sandbox, SDK, server MCP (Model Context Protocol)
Mulai gratis → bayar hanya saat pemeriksaan berjalan → buka Enterprise untuk kontrak kustom, SLA, atau data residency.
FAQ
Pertanyaan umum
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:
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.
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:
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.