Learn
KYC at crypto casinos: what triggers it
“No KYC” marketing claims rarely survive the first large withdrawal. Here is when identity verification typically kicks in, and what we record in our tests.
What PayoutDB observed: KYC triggered at TrustDice
The clearest way to read KYC triggers at a crypto casino is a real measurement. In test TEST-TRU-4f0f1d5b (TrustDice USDT TRC20, 12 May 2026, withdrawal amount 75 USDT), KYC was triggered in full. TrustDice requested two documents:
- Government-issued photo ID
- Proof of address (utility bill / bank statement, dated within the last 3 months)
The submission was accepted in a single review cycle. The approval did not bounce, the team did not request additional documents, and the withdrawal then advanced to broadcast.
What this tells you about TrustDice's KYC policy:
- KYC is triggered at the withdrawal threshold, not at deposit time. Players who deposit and play below the threshold do not see a KYC prompt.
- The threshold sits at or below 75 USDT in our test conditions. Most regulated crypto casinos set it higher, often 1,000 USD or more — TrustDice is conservative here.
- Acceptance within one review cycle indicates the operator runs an active manual review team rather than a fully automated KYC pipeline. Document quality (clear photo, full edges visible) matters for first-pass acceptance.
The rest of this page covers the KYC triggers PayoutDB observes across operators we track. Where we have measured first-party tests, the operator-specific page links to its own KYC outcome.
What KYC actually is
KYC — Know Your Customer — is identity verification: photo ID, selfie, sometimes proof of address. Crypto casinos sit in a regulatory grey zone where KYC is often deferred until a withdrawal triggers it, rather than required at sign-up. That deferral is what “no-KYC” marketing usually refers to.
Common triggers
Across the operators we have tested, identity verification is most often requested when one of the following happens:
- + First withdrawal under the operator's stated threshold (often 1–2 BTC equivalent)
- + Same network and wallet you deposited from
- + Standard play patterns, no large bonus turnover edge cases
- − Large cumulative wins or single withdrawals above the threshold
- − Withdrawal to a network or wallet different from the deposit
- − VPN use detected, or sign-in from a restricted jurisdiction
- − Bonus abuse flags (multi-accounting, arbitrage patterns)
How we record KYC in tests
Every published payout test records one of three KYC outcomes: Not triggered in our test, Partially triggered (e.g. only email verification), or Triggered (full ID + selfie). We do not generalise from one test to a permanent absence of KYC — the result reflects one wallet, one amount, one moment in time. Your account may behave differently.
What our tests have observed
On the small-amount round-trip withdrawals we have measured to date — Stake USDT TRC20, TrustDice USDT TRC20, BetPanda USDT TRC20 — KYC was triggered under the conditions listed on each test page. That is consistent with the operators' published policies: identity verification at or before the first withdrawal, regardless of amount. Different operators, same outcome under our test conditions.
If you are weighing operators on KYC behaviour, treat per-operator marketing claims at evidence level D (operator-claim) until a measured test under documented conditions appears on the entity test page.
Frequently asked questions
TrustDice completed PayoutDB's own withdrawal test in 0:08:40.
Visit TrustDice