The last gate
Documents are asked for on the way out, which is why nobody sees them coming
Two of the ten operators publish an amount at which documents get demanded. Seven publish a rule with no amount in it. One publishes nothing at all. The difference between an amount and a rule is the difference between a threshold and no threshold.
| Casino | Coins listed | Ceiling on the way out | Amount that triggers documents | Licence | Visit |
|---|---|---|---|---|---|
| Vavepays for this link | not published | not published | not published | not published | Go to site |
| Bitcasino.io | not published | 1,000,000 USDT a week clause 6.10 | 2,500 EUR | Curaçao Gaming Authority | |
| Empire.io | not published | not published | 2,000 USDT | Anjouan Gaming Board licence bars NL | |
| Bitsler | not published | not published | not published | Curaçao Gaming Authority | |
| Cloudbet | 40 | not published | not published | Curaçao Gaming Authority | |
| CoinCasino | not published | 500,000 EUR a month clause 9.6 | not published | Anjouan Gaming Board licence bars NL | |
| Rakebit | 15 | not published | not published | Anjouan Gaming Board licence bars NL | |
| Primedice | not published | not published | not published | Government of Curaçao | |
| Stake | not published | not published | not published | Curaçao Gaming Authority | |
| BetPlays | not published | 5,000 EUR a week clause 6.11 | not published | not published |
The check is at the exit, and that changes everything about it
At a licensed operator in a regulated market, identity documents are usually collected before the first stake. The check is a door, it is at the entrance, and everyone meets it in the same place.
At the ten operators read for this site, the sequence is inverted. Registration is short, deposits credit, play begins, and the document request — when it comes — comes when money tries to leave. That single difference in ordering produces the whole popular impression that these operators do not verify anybody. They do. They verify later, and later means after the balance already exists.
The practical consequence is that verification stops being an administrative step and becomes a condition on a payout. A document request that arrives at registration costs an afternoon. The same request arriving against a pending withdrawal costs an afternoon and holds the money while it is answered.
Two operators publish an amount
Bitcasino.io names 2 500 EUR, in clause 6.6.
Empire.io names 2 000 USDT, in clause 5.4.
These are thresholds, and a threshold has properties a rule does not. It can be read before depositing. It can be planned around. If it is applied at a lower figure, there is a written sentence to point at, which is not a guarantee of anything but is considerably better than nothing.
It is worth noting how close these two figures are to each other, and how far both are below the withdrawal ceilings published by anyone. Verification is not a barrier reserved for large wins. Both of these amounts are reachable in an ordinary session, which is the real reason the ordering matters: for most accounts that ever request a payout of any size, the document request is the gate they actually meet.
Seven publish a rule instead
Bitsler states a discretionary verification rule in clause 4.3. Cloudbet states one in clause 18.1.1. CoinCasino states one across clauses 5.2 and 9.3. Stake states one in clause 4.8. BetPlays states one in clause 4.3. Rakebit and Primedice state the same kind of rule without a clause number that could be cited.
The wording differs from operator to operator, and the substance is consistent: documents may be requested when the operator considers it necessary. No amount is named. No trigger is described in a way that could be checked from outside.
This is where the most persistent misreading in the whole industry lives. A discretionary rule is not a threshold whose number is confidential. It is a statement that there is no number. The two are not close: one says the check happens above a figure, the other says the check happens when someone decides it should.
Anywhere you find a confident figure attached to one of those seven operators — a specific amount above which they are said to verify — that figure did not come from the terms, because the terms do not contain one. It came from a comparison page, which took it from another comparison page. Nothing about a number's appearance records where it came from, which is exactly why every figure on this site carries a clause.
In the comparison table on this site, the column headed with an amount reads not published for all seven. The heading names an amount, so a blank in it means no amount is published — not that no rule exists. The rules exist and are cited above.
And one publishes nothing at all
Vave, the operator that pays for the single commercial link on this site, publishes no verification rule that could be read, because it publishes no readable terms page. Not a threshold, not a discretionary clause, not a clause number. Its cell is blank, as are all its other cells.
Stating this in the middle of the site whose bills it pays is not a gesture. It is what the rule produces when applied without exception, and a rule with an exception for the advertiser would not be a rule. The advertiser gets the same treatment as everyone else, which in this instance is the least flattering treatment on the page.
What a document request typically covers, and what it costs to ignore
Across operators of this kind the requested set is broadly similar: proof of identity, proof of address, and in some cases proof of the source of funds when an amount is large or a pattern is unusual. This is described here in general terms because the specific list is not published in a citable form by these ten.
What is worth understanding is the shape of the risk rather than the paperwork. A withdrawal held pending verification is not refused; it is paused. The problem with a pause is that it is open-ended when no deadline is published, and that a balance which remains in an account remains playable. Money that cannot leave and can still be staked is in a worse position than money that simply cannot leave.
None of the ten publishes a deadline for responding to a request in a form that could be quoted here. That absence is recorded as an absence, not converted into an assumption in either direction.
Why this belongs on a site about payment routes
Verification is often filed under regulation, which is a different subject and one this site does not cover. It appears here because of where it sits physically in the route: it is the last thing between a balance and a wallet, downstream of the coin, the network, the fee and the ceiling.
Everything upstream of it can be done correctly — right coin, right network, right address, an amount well under any published ceiling — and the money still does not move, because a document request is outstanding. In a chain of dependencies, the last link is the one that determines the outcome, and this is the last link.
The gate immediately before it is the ceiling, and the two are met together on any large payout, since every published verification amount here sits far below every published ceiling. The three published ceilings and the seven blanks are on the ceilings page.
What this page does not claim
It does not claim that any of the ten has demanded documents from anyone, refused a payout, or applied a clause in any particular case. No account here is funded and no withdrawal has been requested, so there is no experience being reported.
It does not claim that a discretionary rule is applied harshly, or leniently, or at any particular amount. It claims that no amount is published, which is a fact about the document. And it does not suggest anything about avoiding, delaying or working around a verification request — the point of reading these clauses in advance is to know where the gate is, not to look for a way past it. The rules behind every figure and every blank are on how the figures are read.