
Crypto casinos that require KYC before you withdraw
How many of the 24 casinos require KYC before withdrawal?
9 of the 24 crypto casinos on this register require identity verification before any withdrawal in their binding terms. 1 more makes it mandatory above a published threshold and 13 reserve it at their discretion, so 23 of 24 can demand ID before paying out. 1 operator's clause could not be read.
Documents last checked Reviewed by CryptoGuardz Register Desk, editorial desk
How this list is built
Operators whose own binding terms require identity verification before a withdrawal is released, regardless of what their marketing says.
| Operator | Status | Score | Licence | Measured payout | Why it qualifies |
|---|---|---|---|---|---|
| Flush | watchlist | 32 | unconfirmed | not tested | Documentation may be requested following any deposit or prior to any withdrawal, particula… |
| Jackbit | watchlist | 44 | verified | not tested | The operator's KYC policy is explicit: identification is to be carried out before any fina… |
| Lucky Block | watchlist | 18 | unconfirmed | not tested | The AML policy sets three verification steps. Step one, a self-declared form, "must be don… |
| Rakebit | watchlist | 50 | verified | not tested | Identity verification through KYC is required to withdraw funds. Verification may also be … |
| Roobet | watchlist | 69 | verified | not tested | The terms reserve the right to request KYC documentation at any time and to restrict depos… |
| Shuffle | watchlist | 57 | verified | not tested | Two of the operator's own documents give different triggers. The terms reserve the right t… |
| Sportsbet.io | watchlist | 64 | verified | not tested | The terms reserve additional verification for withdrawals exceeding 2,500 euros, and expre… |
| Thunderpick | watchlist | 47 | verified | not tested | Verification required prior to granting any withdrawal, and may be requested at any time. … |
| Winz.io | watchlist | 19 | unconfirmed | not tested | No threshold. The terms reserve the right to verify identity before processing any withdra… |
9 of 24 operators require ID before any withdrawal, 1 publishes a threshold and 13 decide case by case with no threshold; 1 not classified.
- required before withdrawal
- 9 Flush, Jackbit, Lucky Block, Rakebit, Roobet, Shuffle, Sportsbet.io, Thunderpick, Winz.io
- published threshold
- 1 Cloudbet
- discretionary, no threshold
- 13 BC.GAME, BetFury, Bets.io, Bitcasino, Duelbits, FortuneJack, Gamdom, mBit, Metaspins, Rollbit, Stake, Vave, Wild.io
| Trigger | Operators | Names |
|---|---|---|
| required before withdrawal | 9 | Flush, Jackbit, Lucky Block, Rakebit, Roobet, Shuffle, Sportsbet.io, Thunderpick, Winz.io |
| published threshold | 1 | Cloudbet |
| discretionary, no threshold | 13 | BC.GAME, BetFury, Bets.io, Bitcasino, Duelbits, FortuneJack, Gamdom, mBit, Metaspins, Rollbit, Stake, Vave, Wild.io |
This is the inverse list, and it exists because the useful question is not which casinos claim to be anonymous but which ones will ask for your passport at the moment you try to take money out.
Several operators on this list market themselves as no-KYC. Where that is the case it is recorded as a documented contradiction on the operator page, with the marketing claim and the binding clause cited side by side.
Why verification before payout is the honest default
An operator that verifies at withdrawal is doing what every licensed operator is required to do, at the point where it matters most. The alternative is not an operator that never verifies. It is an operator that verifies later, without warning, after a win. No-KYC as marketed means no verification to open an account, and usually none to deposit. Withdrawal is where the obligation lands. Terms that say so plainly are terms that have stopped selling and started describing.
The problem is never the check itself, it is the distance between the check and the claim. Jackbit reserves the right to hold a withdrawal for the time needed to check identity and investigate, and markets payouts as usually taking just minutes. Cloudbet allows 2,200 US dollars a day at the lower verification level and states that this cap persists while documents are under review, so the slowest moment is also the most restricted one. Both facts are disclosed. Only one of them is advertised.
Flush states payment within seventy-two hours after verification completes, which puts the two events in the right order and refuses to count the second against the first. That is the shape to look for. A clock that starts when documents are accepted is a clock the operator controls and can be held to. A clock that starts when a player clicks withdraw, while verification runs somewhere behind it, measures nothing at all and can be advertised anyway.
What a good verification process looks like
A good process is bounded, ordered and disclosed. It names the documents, names the time, and names what happens when something fails. Rakebit approves or denies within two days and extends to seven days or more where further procedures are required, which is a bound with a stated exception not an exception with no bound. Thunderpick's twenty-four hours works the same way. Neither is quick. Both can be measured against, which is the only property that survives a dispute.
A poor process is open ended in every direction. Roobet reserves the right to delay or decline during an investigation and states it may not be in a position to explain the nature of that investigation, leaving the player unable to satisfy a requirement they cannot see. Shuffle reserves additional verification procedures and other checks for any withdrawal, with no ceiling on either. Gamdom commits to no fixed time and cites internal review times. These clauses are lawful. None of them can be breached, because none of them promise anything.
The clearest signal is when the documents are asked for. An operator that requests them at registration or first deposit has verified an account holding nothing, and the process costs the player patience. An operator that waits until a withdrawal has verified an account holding a win, and the same process now costs money held in suspense. The register records what the documents say about verification. It does not measure how quickly any operator actually answers a submitted document, and it does not claim to.
Verification and what recourse it buys you
A verified account is what makes a complaint possible. Any regulator or dispute body starts by asking who the player is and which account is in question, and an anonymous account with a frozen balance gives them very little to act on. This is the unglamorous argument for verification: it is the identity a complaint attaches to. Eighteen of the twenty-four operators on the register had a licence confirmed in the issuing authority's own register, so for eighteen there is somewhere to send that complaint.
Four could not be confirmed. There, verification runs one way. The operator learns who the player is, and the player has no confirmed authority to appeal to if the payout does not arrive. That is not an argument for refusing to verify. It is an argument for knowing which of the two situations an account is in before funding it. Recourse and verification are a pair, and verification without recourse is disclosure with nothing on the other side of it.
Verification also does not settle the amount. A fully verified account at BetFury still meets a maximum win of 300,000 dollars and payouts over 50,000 paid in equal parts within thirty days. A verified account at Rakebit still meets EUR 500,000 paid over up to ninety days. The documents answer who is being paid. They do not answer how much, or when, and those clauses sit elsewhere in the same terms, usually a good deal further down the page.
Operators that do not qualify
Listed so the absence is visible. An operator missing from the table above has been reviewed and did not meet the criterion, which is different from not having been looked at.
- BC.GAME watchlist
- BetFury watchlist
- Bets.io watchlist
- Bitcasino watchlist
- Cloudbet watchlist
- Coins.game watchlist
- Duelbits watchlist
- FortuneJack watchlist
- Gamdom watchlist
- mBit watchlist
- Metaspins watchlist
- Rollbit watchlist
- Stake watchlist
- Vave watchlist
- Wild.io watchlist
The clauses that decide whether a verification request becomes an indefinite hold are the seven covered in the guide to reading casino terms.
The same question, asked in 4 other markets
The document an operator asks for is the one your own regulator has taught you to expect, so this question is written for each market against its own verification system. These pages cover BankID in Sweden, NemID in Denmark, and verification at operators outside the German and Spanish regimes.
How we decide
Every list on this site is a query against the same dataset, not a hand-written ranking. When an operator’s status changes, every page it appears on updates in the same build. The rules are at our methodology page and the underlying data is at the payout index.