Clause 2.1 confirms thresholds exist and stops short of naming one
Clauses 2.1 and 2.2, read side by side
Three kinds of document are named in clause 2.2 and the sum that summons them appears in none of the 902,657 characters read. Clause 2.1 goes further than silence: it tells the reader that specific financial thresholds exist, and leaves the figures out.
What clause 2.2 asks for
The document list in clause 2.2 is short and unremarkable. Verification may seek confirmation of identity, age, address and source of funds, and three items are named: a government issued ID, proof of address in the form of a utility bill or bank statement, and information relating to the payment method. The third of those is the one that reaches back into the cashier, where a separate rule requires every deposit and every payout to sit in the account holder’s own name — the coins accepted, the network rule attached to two of them, and the name-matching condition are at the deposit and payout methods. It opens the list with “may include, but it is not limited to”, so those three are examples of the category rather than its edge. The tone is friendly: cooperate promptly, and the operator will aim to make the process smooth and straightforward.
Every operator in our table asks for some version of that. Identity, address, payment instrument: the trio is the market’s common denominator, and there would be little to write about if the list were the whole story.
What clause 2.1 does that silence would not
The clause immediately above the document list is where this page comes from. By registering, the player consents to verification checks required by law or reasonably necessary for account integrity and compliance. Then the timing: these checks may be carried out at Account registration or at any time thereafter, “especially when specific financial thresholds are met and/or if specific risk factors arise”. The consent sentence and the document list are quoted together for each operator in Gamdom alternatives and their verification clauses.
Thresholds exist. Their location belongs to the house.
That sentence is an unusual thing to publish. It is a statement that the operator runs numeric triggers, made in a contract that prints none of the numbers. A player reading it learns that lines exist, that crossing one summons the request, and that the location of every line is internal. Silence would have left room to assume the checks are occasional and discretionary. This wording removes that assumption and replaces it with a system the reader cannot see.
The difference between an awkward published threshold and an unpublished one
Set two rules beside each other. Rocketpot writes, in clause 11.4 and the summary around it, that withdrawals above 0.05 BTC or 2,500 dollars may require verification, with further checks above 2,000 dollars and documents due within thirty calendar days. Wild Fortune goes further in the other direction: under clause 18.1, players funding in bitcoin must submit valid identification before playing at all, with deposits and bets blocked until that is done.
Wild Fortune’s rule is the more onerous of the two by a distance. It also has a quality Gamdom’s lacks: a player can act on it. The document request arrives at a moment the reader chose, with the balance still zero and nothing at stake in the outcome. Rocketpot’s threshold does the same job from the other side — it marks a line, and a line can be prepared for, stayed under, or crossed deliberately with the passport already scanned. That operator publishes a second figure a page later, and the two do not agree with each other; both, together with the payout arithmetic they sit beside, are read against this contract at three times the deposit against one.
What an unpublished trigger changes
An unpublished trigger removes that sequencing. The request arrives when the system decides, which in practice tends to be at the moment the account first tries to release a meaningful sum, with the balance sitting on the wrong side of the pause. Timing is the whole of the difference.
Nothing about that is unlawful or even unusual; what it changes is who chooses the timing, and the choice is worth more than it looks.
| Casino | Operator | Licence | Countries barred | Visit |
|---|---|---|---|---|
| Gamdom | not published | not published | 37 | Go to the casino site |
| Rocketpot | Danneskjold Ventures B.V. | Curacao | 34 | Go to the casino site |
| Bitcasino.io | Moon Technologies B.V. | Curaçao Gaming Authority | 1 | Go to the casino site |
| Wild.io | Nonce Gaming B.V. | Curaçao Gaming Authority | 45 | Go to the casino site |
| Wild Fortune | Metlait SRL | Anjouan Gaming Board | 47 | Go to the casino site |
| Instant Casino | Axenora Strategic Services N.V. | Curaçao Gaming Authority | 48 | Go to the casino site |
| CoinCasino | Igloo Ventures SRL | Anjouan Gaming Board | 36 | Go to the casino site |
| Bets.io | Bets Entertainment N.V. | Curaçao Gaming Authority revoked | 42 | Go to the casino site |
| Playbet.io | Bitx Operations N.V. | Curaçao Gaming Authority | 30 | Go to the casino site |
| CryptoLeo | Uno Digital Media B.V. | Curaçao Gaming Authority | 74 | Go to the casino site |
| BetPlays | not published | not published | 15 | Go to the casino site |
Rocketpot
Bitcasino.io
Wild.io
Wild Fortune
CoinCasino
CryptoLeo
BetPlaysHow much of this table works the same way
Being fair to the operator this domain is named after: discretionary verification is the market norm rather than an outlier. Of the eleven other rows in our table, nine record it as discretionary — triggered at the operator’s judgement, at first withdrawal, or before payout. Instant Casino’s clause 3.9 is the frankest of them, permitting checks at any time and suspension until they are satisfied, with our record noting that a monetary threshold is stated nowhere in it. That is the same shape as clause 2.1 minus the sentence about thresholds, and the two contracts are read line against line — including the payout column, where one of them does print a figure — at the smallest printed ceiling against none at all.
The remaining two rows publish a figure. Bitcasino.io names 2,500 euro in clause 6.6 and Rocketpot names 2,500 dollars in clause 11.4, and both add that smaller withdrawals may be checked anyway as the licence requires. So a published threshold is a floor for expectations rather than a promise of privacy below it.
Four rows attach a deadline to the player: fourteen days in Vave’s clause 8.7, thirty calendar days at Rocketpot and at Bets.io, and a two-week contact rule at Playbet.io under clauses 13.4 and 13.8. A deadline is a different kind of protection — it bounds how long the player has, and by implication how long the file can sit half-finished.
What stays unread here, and why the cell is blank
Three things would settle the threshold question and all three are beyond what we hold. The account screens describe numbered verification levels; the limits attached to each level live in account data rather than in published text. An anti-money-laundering page existed at the operator’s domain and was archived in June 2023, and it was never opened by us. And a Responsible Gambling Policy, which the terms declare forms part of them, could be located nowhere in either bundle.
So the verification cell for this row on our table stays empty, and empty on this site means the document went unread rather than meaning the sum is zero. The distinction is laboured deliberately, because the alternative is a figure invented to fill a column, and figures invented that way travel across the whole market once they are printed once.
The payout conditions this rule attaches to are gathered in the payout clauses. What a player can do while a check holds a balance belongs to the complaints procedure. The twelve-row comparison itself opens the front page.