Documents, deadlines and two tests
The moment identity verification enters the terms
Identity verification does not arrive at the same moment in any two houses. This page sets out the point at which each clause sets it off, the amount attached where one exists, and what two tests with the desk's own money showed in practice.
At sign-up, the fields asked for tend to be the same at any house: name, date of birth, email, sometimes country. Identity verification proper — sending a document, checking it against the account holder's name — is another step, and each house's terms mark a different moment for it to begin.
This page sets out those moments, the two amounts in euros and dollars that appear in the texts, and the deadline each house gives for sending the document. The same survey appears arranged side by side on the crypto casino ranking page.
The moment the text marks for identity verification
In three houses, the clause ties identity verification to the withdrawal: Vave asks for identity before any payment (cl. 8.7), Rocketpot does the same in the clause that deals with withdrawals, and Rainbet also makes payment conditional on the check. None of the three describes an earlier trigger — the moment stated is the withdrawal request itself.
Bitcasino.io uses a different design: clause 3.13 describes a condition, and it is from there that clause 6.6 applies its amount — 2,500 EUR, or the equivalent converted into cryptocurrency. It is not the withdrawal itself that sets off the check, but the condition clause 3.13 describes first.
Two houses leave the moment open: Thunderpick and Wolfbet do not name, in the available text, the exact point at which identity verification begins to apply. That does not mean there is no check — it means the clause does not print the trigger.
| House | Points | When the document is asked for | Amount that triggers the document | Link |
|---|---|---|---|---|
 VaveTest with the desk's own money | 3/5 | At the moment of withdrawal cl. 8.7 | no amount | Visit the casino |
1 Bitcasino.io | 4/5 | After a described event cl. 3.13, 6.6 | 2,500 EUR, or the same value in crypto cl. 6.6 | |
2 Rocketpot | 4/5 | At the moment of withdrawal cl. 11.4, 12.4 | 2,500 USD in one clause, 2,000 USD in the other cl. 11.4, 12.4 | |
3 Wild Fortune | 4/5 | After a described event cl. 2.7, 11.2 | no amount | |
4 Metaspins | 3/5 | After a described event cl. 9.7 | no amount | |
5 Rainbet | 3/5 | At the moment of withdrawal cl. 20.1 | no amount | |
6 Shuffle.com | 3/5 | After a described event cl. 5.2 | no amount |
The two amounts, in euros and dollars
Only two houses among those named across these pages print a numerical amount tied to identity verification. Bitcasino.io fixes 2,500 EUR or the equivalent in cryptocurrency (cl. 6.6), with the condition coming from clause 3.13. Rocketpot prints a band, not a single number: between 2,000 and 2,500 USD depending on the clause — 2,500 dollars (or 0.05 BTC) in clause 11.4 and 2,000 dollars in clause 12.4, two close numbers in two different parts of the same document.
The other houses named on this page do not publish, in the passages read, an amount equivalent to those two — and the absence of a number in this survey is not the same as an absence of checking on the house's part.
Document deadlines, with the clause
Once identity verification is asked for, each house gives a deadline for sending the document. Vave sets 14 days (cl. 8.7). Rocketpot sets 30 calendar days (cl. 12.2). Metaspins adds up to the same, 30 days (cl. 9.10). Wild Fortune writes the deadline in words rather than a figure: two weeks (cl. 8.4 and 9.3). Rainbet leaves the pattern of days and sets hours: 72 hours to answer a request (cl. 20.1), a response deadline rather than one for sending a complete document.
None of these deadlines is a payment deadline — they are deadlines for the player to send something, each with the clause that prints it.
Two tests with the desk's own money
The desk ran two real tests to see how identity verification works in practice, not only in the text.
The first test is dated 28 August 2026, with a deposit and withdrawals of the desk's own money at Vave. No request for a document appeared while the running total withdrawn stayed below roughly 5,000 USDT — an observation about what happened in that test, not a rule: clause 8.7 still allows Vave to ask for identity before any payment, at any moment.
The second test ran in May 2026, at TrustDice, with USDT deposits spread over several weeks. There too the withdrawals went through without trouble while the total stayed below about US$5,000; past that point the status turned to “payment under review” and a link to the Veriff platform arrived for the document. A driving licence was refused; a passport was accepted on the fifth attempt. After that, a second request, distinct from the first, arrived by email.
The two tests show the same underlying pattern: a running total, rather than the size of one withdrawal, appears to weigh on the decision to ask for identity — but neither house prints that trigger as a fixed number in its own terms.
What this page does not suggest
Nothing here points to a way of avoiding the document request. The two tests describe what happened in a specific window, with a specific amount of the desk's money; the clauses still hold exactly as written, and any house may ask for identity before that point if it decides to. For the rest of each house's score, see the methodology and the full ranking. The document deadlines gathered here also appear, alongside the amount ceilings, on the page about the withdrawal ceiling.
Frequently asked questions
At what moment does Vave ask for identity verification?
Why does Rocketpot print two different amounts for the same kind of check?
What changed in the TrustDice test once the total withdrawn passed US$5,000?
Is a 72-hour deadline the same kind of deadline as 30 calendar days?
