Skip to main content
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
iGaming · Michezo ya kubahatisha inayowajibika

Umri, utambulisho, na kujiondoa katika kikao kimoja salama zaidi.

Lango la umri wa miaka 18+, Uthibitishaji wa Kitambulisho, ukaguzi wa orodha ya kujiondoa, AML kwenye amana, UKGC, MGA, Curaçao rafiki kwa ukaguzi. ~$0.40 kwa usajili wa mchezaji.

Anza bureSoma nyaraka
Inaungwa mkono na
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

Inaaminika na mashirika 2,000+ duniani kote.

Mchoro wa sinema, giza, usioeleweka wa iGaming-responsible-gaming stack, paneli nne za glasi zinazoelea, zinazopitisha mwanga katika mtazamo wa 3D kwenye nyeusi safi, zikipitishwa na mstari mweupe wa Didit Blue na zikizungukwa na mabano manne ya skana yanayong'aa. Kila paneli hubeba motifu ndogo nyeupe-nyepesi isiyo dhahiri (mviringo wa uso na arc ya umri, mchemraba wa kete, duara la gurudumu la roulette, ngao yenye pau ya kusimamisha).

Kinachodaiwa na wadhibiti

Thibitisha mchezaji. Angalia kujiondoa. Fuatilia kila amana.

Kila opereta anayedhibitiwa anadaiwa lango gumu la umri wa miaka 18+, ukaguzi wa orodha ya kujiondoa, AML kwenye amana za kizingiti, na uthibitishaji upya wa biometriska kwenye uondoaji. Didit huwasilisha kama mtiririko mmoja wa kazi kwa ~$0.40 kwa mchezaji + $0.02 kwa amana. Uthibitishaji 500 bila malipo kila mwezi.

Jinsi inavyofanya kazi

Kuanzia kujisajili hadi mtumiaji aliyethibitishwa kwa hatua nne.

  1. Hatua 01

    Unda mtiririko wa kazi

    Chagua ukaguzi unaotaka, ID, liveness, face match, vikwazo, anwani, umri, simu, barua pepe, maswali maalum. Ziburute kwenye mtiririko kwenye dashibodi, au tuma mtiririko huo huo kwenye API yetu. Panga masharti, fanya majaribio ya A/B, hakuna code inayohitajika.

  2. Hatua 02

    Unganisha

    Pachika moja kwa moja na SDK yetu ya Web, iOS, Android, React Native, au Flutter. Elekeza kwenye ukurasa uliopangishwa. Au tuma tu mtumiaji wako kiungo, kwa barua pepe, SMS, WhatsApp, popote. Chagua kinachofaa stack yako.

  3. Hatua 03

    Mtumiaji anapitia mtiririko

    Didit huandaa kamera, ishara za mwanga, uhamishaji wa simu, na ufikiaji. Mtumiaji akiwa kwenye mtiririko, tunapima ishara 200+ za udanganyifu kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vya kuaminika. Matokeo yanapatikana chini ya sekunde mbili.

  4. Hatua 04

    Unapokea matokeo

    Webhooks zilizotiwa saini kwa wakati halisi huweka database yako sawa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Piga API inapohitajika. Au fungua console kukagua kila session, kila ishara, na kudhibiti kesi kwa njia yako.

Imejengwa kwa waendeshaji waliodhibitiwa · Bei kama miundombinu

Ukaguzi sita. Simu mbili za API. $0.40 kwa kila mchezaji.

Uzingatiaji wa michezo ya kubahatisha inayowajibika si ukaguzi mmoja, ni mapishi. Washa kila moduli kwa kila mdhibiti, badilisha kifurushi cha sheria kwa kila soko, endesha mtiririko huo huo kote UKGC, MGA, Curaçao, SIGAP, na ANJ.
Soma nyarakaPata API key
01 · Lango la umri wa miaka 18+

Njia rahisi zaidi: Ukadiriaji wa Umri kwanza.

Ukadiriaji wa Umri kwa $0.10 huendeshwa kwa kila usajili. Watumiaji wenye umri wa miaka 18+ wanapita; wale walio karibu na mpaka (16-21) huongezwa hadi Uthibitishaji wa Kitambulisho kwa $0.15. Ni kundi la wale walio karibu na mpaka pekee ndio hulipa zaidi, huweka gharama ya wastani kwa kila mchezaji kuwa chini.
Moduli ya Ukadiriaji wa Umri
02 · Ukaguzi wa kujiondoa

Linganisha rejista kwa kila usajili.

Utafutaji wa Uso 1:N (bure) dhidi ya faharisi yako ya kujiondoa na, ambapo mdhibiti anashiriki, rejista ya kitaifa (UK GAMSTOP, Spain RIGA, Italy RUA, Brazil Programa Jogo Responsável). Mchezaji aliyejiondoa anayeomba tena kwa jina jipya + barua pepe mpya hugunduliwa chini ya 200ms.
Moduli ya Utafutaji wa Uso 1:N
03 · AML kwenye amana

Chunguza waweka amana walio juu ya kizingiti.

Uchunguzi wa AML kwenye amana zilizo juu ya kizingiti kilichosanidiwa na mwendeshaji (kiasi cha £/€/$). Orodha 1,300+ za vikwazo, Watu Walio Wazi Kisiasa (PEP), na orodha za habari mbaya katika lugha 14, zikiboreshwa kila siku. $0.20 kwa kila ukaguzi.
Moduli ya Uchunguzi wa AML
04 · Vikomo vya amana + vikomo vya hasara

Vikomo vya wakati halisi kwa kila ngazi ya mchezaji.

Injini ya sheria ya Ufuatiliaji wa Miamala inatekeleza vikomo vya amana vya kila siku / wiki / mwezi na vikomo vya hasara kwa wakati halisi kwa $0.02 kwa kila simu. Vikomo vilivyowekwa na mchezaji mwenyewe huheshimiwa kwanza; vikomo vilivyowekwa na mdhibiti vinatangulia. Hariri sheria katika Workflow Builder isiyo na code bila kupeleka tena.
Moduli ya Ufuatiliaji wa Miamala
05 · Uthibitishaji upya wa uondoaji

Ukaguzi wa uso kwa kila uondoaji.

Uthibitishaji wa Biometric huendesha Face Match dhidi ya selfie ya usajili wa mchezaji kwa $0.10 kwa kila uthibitishaji. Huzuia uchukuaji wa akaunti kutoa pesa, nguvu sawa ya msingi huwezesha mabadiliko ya mipangilio ya akaunti na uthibitishaji upya wa kutotumika.
Moduli ya Uthibitishaji wa Biometric
06 · Kifurushi cha ukaguzi kwa kila mdhibiti

UKGC, MGA, Curaçao, SIGAP, ANJ.

Templates za usafirishaji kwa kila mdhibiti zinapatikana kwenye Business Console, ushahidi wa kitambulisho, matukio ya AML, ukaguzi wa kujiondoa, logi ya amana, uthibitishaji upya wa uondoaji, zote katika kifurushi kimoja, zikihifadhiwa kwa miaka 5 kulingana na mahitaji ya mdhibiti.
Sekta, Kamari & iGaming
Unganisha

Session moja kwa onboarding. Simu moja ya transaction kwa kila amana.

Fungua session ya onboarding. Soma uamuzi uliotiwa saini. Tuma kila amana + uondoaji kwa /v3/transactions/.
POST /v3/session/Onboard
$ 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" }
  }'
201Imeundwa{ "session_url": "verify.didit.me/..." }
Zuia uundaji wa akaunti hadi webhook iseme status: Approved.nyaraka →
POST /v3/transactions/Amana
$ 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": "Amana ya mchezaji" }
  }'
201Imeundwa{ hali IMEIDHINISHWA · INAANGALIWA · IMETUPILIWA MBALI · INAMSUBIRI MTUMIAJI }
Injini ya sheria inatekeleza mipaka + AML kwa wakati halisi. $0.02 kwa kila simu.nyaraka →
Ujumuishaji tayari kwa agent

Tekeleza michezo ya kubahatisha inayowajibika kwa amri moja.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Agent inajenga mtiririko wa onboarding, inaunganisha simu ya ufuatiliaji wa amana, inaandikisha AML inayoendelea, na kuongeza uthibitisho upya wa uondoaji.
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.
Inatii kwa muundo

Fungua nchi mpya kwa kubofya mara moja. Tunafanya kazi ngumu.

Tunafungua kampuni tanzu za ndani, tunapata leseni, tunafanya majaribio ya kupenya, tunapata vyeti, na tunalingana na kila kanuni mpya. Ili kusafirisha uthibitishaji katika nchi mpya, geuza swichi. Nchi 220+ ziko hewani, zinakaguliwa na kupimwa kila robo mwaka, mtoa huduma pekee wa utambulisho ambaye serikali ya nchi mwanachama wa EU imemwita rasmi kuwa salama zaidi kuliko uthibitishaji wa ana kwa ana.
Soma faili ya usalama na utiifu
EU financial sandbox
Tesoro · SEPBLAC · BdE
ISO/IEC 27001
Usalama wa habari · 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-aligned kwa muundo

Namba za uthibitisho

Namba za uthibitisho
  • ~$0.40
    Kwa kila mchezaji aliyeingizwa, umri + kitambulisho + AML + ukaguzi wa kujiondoa.
  • $0.00
    Kwa kila amana / uondoaji unaofuatiliwa kupitia Ufuatiliaji wa Miamala.
  • <0ms
    Kwa kila Utafutaji wa Uso 1:N dhidi ya orodha yako ya kujiondoa.
  • 0
    Uthibitishaji wa bure kila mwezi, kwenye kila akaunti.
Ngazi tatu, orodha moja ya bei

Anza bure. Lipa kulingana na matumizi. Panua hadi Enterprise.

Uthibitishaji 500 bila malipo kila mwezi, milele. Lipa kadri unavyotumia kwa uzalishaji. Mikataba maalum, uhifadhi wa data, na SLA (Service Level Agreements) kwenye Enterprise.
Bure

Bure

$0 / mwezi. Hakuna kadi ya mkopo inayohitajika.

  • Kifurushi cha bure cha KYC (Uthibitishaji wa Kitambulisho + Passive Liveness + Face Match + Uchambuzi wa Kifaa & IP), 500 / mwezi, kila mwezi
  • Watumiaji Waliozuiwa
  • Utambuzi wa Marudio
  • Ishara 200+ za udanganyifu kwenye kila session
  • KYC inayoweza kutumika tena kwenye mtandao wa Didit
  • Jukwaa la Usimamizi wa Kesi
  • Workflow Builder
  • Nyaraka za umma, sandbox, SDKs, server ya MCP (Model Context Protocol)
  • Usaidizi wa jamii
Anza bure
Maarufu zaidi
Lipa kulingana na matumizi

Kulingana na Matumizi

Lipa tu kwa unachotumia. Moduli 25+. Bei za umma kwa kila moduli, hakuna ada ya chini ya kila mwezi.

  • KYC kamili kwa $0.33 (Kitambulisho + Biometric + IP / Kifaa)
  • Data za AML 10,000+, vikwazo, PEPs, habari hasi
  • Vyanzo vya data vya serikali 1,000+ kwa Uthibitishaji wa Database
  • Ufuatiliaji wa Miamala kwa $0.02 kwa kila muamala
  • KYB ya moja kwa moja kwa $2.00 kwa kila biashara
  • Uchunguzi wa Wallet kwa $0.15 kwa kila ukaguzi
  • Mtiririko wa uthibitishaji wa Whitelabel, brand yako, miundombinu yetu
Tazama orodha kamili ya beiAnza bure
Biashara Kubwa

Biashara Kubwa

MSA & SLA maalum. Kwa idadi kubwa na programu zilizodhibitiwa.

  • Mikataba ya kila mwaka
  • MSA, DPA, na SLA maalum
  • Kituo maalum cha Slack na WhatsApp
  • Wakaguzi wa mikono wanapohitajika
  • Masharti ya muuzaji na white-label
  • Vipengele vya kipekee na ushirikiano wa washirika
  • CSM aliyetajwa, ukaguzi wa usalama, usaidizi wa kufuata
Wasiliana nasi

Anza bure → lipa tu wakati ukaguzi unafanyika → fungua Enterprise kwa mkataba maalum, SLA, au uhifadhi wa data.

FAQ

Maswali ya kawaida

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.

Related

Moduli zinazohusiana + mtiririko wa kazi

Miundombinu ya utambulisho na udanganyifu.

API moja kwa KYC, KYB, Ufuatiliaji wa Miamala, na Uchunguzi wa Wallet. Unganisha ndani ya dakika 5.

Anza bila malipoZungumza nasi
Uliza AI ifupishe ukurasa huu