무료
무료
월 $0. 신용카드 정보가 필요 없습니다.
- 무료 KYC 번들 (신분증 확인 + 패시브 라이브니스 + 얼굴 매칭 + 기기 및 IP 분석), 매월 500건 제공
- 차단된 사용자
- 중복 감지
- 모든 세션에서 200개 이상의 사기 신호 감지
- Didit 네트워크 전반에 걸쳐 재사용 가능한 KYC
- 사례 관리 플랫폼
- 워크플로 빌더
- 공개 문서, 샌드박스, SDK, MCP(Model Context Protocol) 서버
- 커뮤니티 지원
전 세계 2,000개 이상의 기관에서 신뢰합니다.
규제 기관의 요구 사항
플레이어를 확인하고, 자가 배제를 확인하세요. 모든 입금을 모니터링합니다.
모든 규제 대상 운영자는 18세 이상 연령 확인, 자가 배제 등록 교차 확인, 임계값 예금에 대한 AML, 출금 시 생체 인식 재인증을 의무적으로 수행해야 합니다. Didit은 이를 플레이어당 약 $0.40 + 예금당 $0.02의 비용으로 하나의 워크플로우로 제공합니다. 매월 500회 무료 인증.
작동 방식
가입부터 인증된 사용자까지 4단계.
- 단계 01
워크플로우 생성
ID, 본인 확인, 얼굴 매칭, 제재 목록, 주소, 연령, 전화번호, 이메일, 맞춤 질문 등 필요한 검사를 선택하세요. 대시보드에서 드래그 앤 드롭으로 워크플로우를 만들거나, 동일한 워크플로우를 API에 게시할 수 있습니다. 조건에 따라 분기하고 A/B 테스트를 실행하세요. 코딩은 필요 없습니다.
- 단계 02
통합
저희 Web, iOS, Android, React Native, Flutter SDK를 사용하여 네이티브로 임베드하세요. 호스팅된 페이지로 리디렉션하거나, 이메일, SMS, WhatsApp 등 어디든 사용자에게 링크를 보내기만 하면 됩니다. 귀하의 스택에 맞는 방식을 선택하세요.
- 단계 03
사용자가 플로우를 진행합니다.
Didit은 카메라, 조명 안내, 모바일 핸드오프, 접근성을 호스팅합니다. 사용자가 워크플로우를 진행하는 동안 200개 이상의 사기 신호를 실시간으로 분석하고 모든 필드를 신뢰할 수 있는 데이터 소스와 대조하여 확인합니다. 2초 이내에 결과를 받아보세요.
- 단계 04
결과를 받으세요
실시간 서명된 웹훅은 사용자가 승인, 거부되거나 검토를 위해 전송되는 즉시 데이터베이스를 동기화합니다. 필요에 따라 API를 폴링하거나, 콘솔을 열어 모든 세션과 신호를 검사하고 케이스를 직접 관리할 수 있습니다.
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 · 자가 배제 확인
모든 가입 시 등록부를 교차 확인합니다.
자가 배제 목록 및 규제 기관이 참여하는 경우 국가 등록부(영국 GAMSTOP, 스페인 RIGA, 이탈리아 RUA, 브라질 Programa Jogo Responsável)에 대해 Face Search 1:N(무료)을 실행합니다. 새로운 이름과 이메일로 재신청하는 자가 배제 플레이어는 200ms 이내에 플래그 처리됩니다.
Face Search 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(정치적 주요 인물), 부정적 미디어 목록이 매일 업데이트됩니다. 검사당 $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 · 입금 한도 + 손실 상한
플레이어 등급별 실시간 한도.
거래 모니터링 규칙 엔진은 일일/주간/월간 입금 한도 및 손실 상한을 실시간으로 적용하며, 호출당 $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 · 출금 재인증
모든 출금 시 얼굴 확인.
생체 인증은 플레이어의 등록 셀카와 얼굴 매칭을 실행하며, 인증당 $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 적중, 자가 배제 확인, 입금 기록, 출금 재인증 등 모든 것이 하나의 번들로 제공되며, 규제 기관의 요구 사항에 따라 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
통합
온보딩을 위한 한 번의 세션. 입금당 한 번의 트랜잭션 호출.
온보딩 세션을 시작하세요. 서명된 결과를 확인하세요. 모든 입출금 내역을 /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 통화당.문서 →에이전트 연동 준비 완료
단 한 번의 프롬프트로 책임감 있는 게임 환경을 구축하세요.
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 회원국 정부가 대면 인증보다 더 안전하다고 공식적으로 인정한 유일한 신원 확인 제공업체입니다.
보안 및 규정 준수 문서 읽기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플레이어 온보딩당, 연령 확인 + 신분증 + AML + 자가 배제 확인.
- $0.00거래 모니터링을 통한 입금/출금 모니터링당.
- <0ms자가 배제 인덱스에 대한 Face Search 1:N 조회당.
- 0매월, 모든 계정에서 무료 인증.
세 가지 티어, 하나의 가격표
무료로 시작하고, 사용량에 따라 지불하며, 엔터프라이즈로 확장하세요.
매월 500건의 무료 본인 확인을 영구적으로 제공합니다. 프로덕션 환경에서는 사용한 만큼만 지불하세요. 엔터프라이즈 고객에게는 맞춤형 계약, 데이터 상주 및 SLA(서비스 수준 협약)를 제공합니다.
가장 인기
사용한 만큼 지불
사용량 기반 요금제
사용한 만큼만 지불하세요. 25개 이상의 모듈. 모듈별 공개 가격, 월 최소 요금 없음.
- 전체 KYC $0.33 (신분증 + 생체 인식 + IP / 기기)
- 10,000개 이상의 AML 데이터셋, 제재, PEP, 부정적 미디어
- 데이터베이스 검증을 위한 1,000개 이상의 정부 데이터 소스
- 거래당 $0.02의 거래 모니터링
- 기업당 $2.00의 실시간 KYB
- 검사당 $0.15의 지갑 스크리닝
- 화이트 라벨 검증 플로우, 귀사의 브랜드, Didit의 인프라
엔터프라이즈
엔터프라이즈
맞춤형 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.