One clause, quoted whole
Clause 21.1 leaves the trigger to the operator, and one row prints a figure
The whole of the identity policy in 75,770 characters of terms is a single clause. It names two document types, reserves security questions at the operator's sole discretion, and attaches no amount to any of it. Across the wider library the shape repeats: 49 verification clauses have been read, all 49 keep the decision with the operator, and five name a sum.
Five documents published by this operator run to 144,241 characters, of which the terms account for 75,770. The identity policy inside all of that is one clause.
| Casino | Operator | Licence | Before ID check | Studios | Visit |
|---|---|---|---|---|---|
| Vavepaid placement | Latcas B.V. | Curaçao Gaming Authority | case by case | 40 | Visit |
| Thunderpick | Paloma Media B.V. | Curaçao Gaming Authority | case by case | not published | |
| Sportsbet.io | not published | Curaçao Gaming Authority | 2,500 EUR | not published | |
| Cloudbet | Halcyon Super Holdings B.V. | Curaçao Gaming Authority | case by case | not published | |
| Rollbit | Bull Gaming N.V. | Curaçao Gaming Authority | not published | not published | |
| Roobet | Raw Entertainment B.V. | Curaçao Gaming Authority | not published | not published | |
| Duelbits | Liquid Entertainment N.V. | Curaçao Gaming Authority | not published | not published | |
| Shuffle | Natural Nine B.V. | Curaçao Gaming Authority | case by case | not published | |
| BetFury | Universe B Games B.V. | Curaçao Gaming Authority | not published | not published | |
| TrustDice | not published | Curaçao Gaming Authority | not published | not published | |
| Rolletto | not published | Curaçao Gaming Authority | not published | not published |
Clause 21.1, in the operator's own words
If for any reason we require that you validate your identity, you may be required to submit additional information or documentation – such as government issued ID or proof of residency. In certain cases and at our sole discretion, you may be required to answer one or more security questions.
Three things are named there. Two document types, government-issued ID and proof of residency. One additional mechanism, security questions, expressly at the operator's discretion. And an opening condition, if for any reason we require, which is the clause telling the reader that the trigger is a judgement rather than a rule.
An amount appears nowhere in it.
That is not a drafting oversight. A contract that intended to bind itself to a figure would print the figure, as four operators elsewhere in this library do. A contract that intends to keep the decision writes the sentence above.
Where the policy is kept, and why that matters
This operator holds its identity language as an anchored section inside the general terms rather than as a file of its own, and does the same with its anti-money-laundering wording. A reader hunting for a standalone KYC policy document will hunt for a while.
There is a linked KYC Policy page, and its text was not among the documents captured, so nothing from it is quoted or counted here.
The operator's marketing carries a sentence of its own: that each account and transfer is verified. Reading that as a description of identity checks would be a stretch the wording does not support, because the same verb covers ordinary security and fraud screening, and the marketing page is not the document that binds anybody. It is recorded and not used.
A drawing, made for this page. It stands for the way every number on this site is arrived at: a document opened from top to bottom and read against the clause number it sits under. For this operator that came to 144,241 characters across five documents on 2 September 2026, and the half that governs bonuses was not among them.
The three strengths of an identity cell
Every cell in this column on this site is one of three things, and the difference is what a reader can hold an operator to.
A published amount is the strongest. Sportsbet.io is the only row here that carries one: €2,500, clause 6.6. Its own wording qualifies it in a way worth quoting the sense of — the same clause reserves the right to verify smaller withdrawals too. So the figure marks the level above which checks are expected, not a level below which they are excluded. Even the strongest cell in the column is a floor rather than a promise.
A described check with the amount left out is the middle strength, and four rows sit there. This brand at clause 21.1. Cloudbet at clause 18.1.1, whose terms require customers to produce reliable, independent documents and which reserves the right to re-verify a customer it has already verified once. Shuffle at clause 4.1, which reserves the right to ask for KYC documentation at any time it deems necessary, with an anti-money-laundering policy that describes a withdrawal threshold and gives no amount for it. Vave at clause 8.7, which allows the demand before any payout and gives the customer fourteen days to answer it.
A blank is the third, and it records ignorance on this side rather than leniency on the operator's. Six rows in the table are blank here.
Vave's fourteen days is the only deadline of any kind in the column, and it runs against the customer. No row in this table sets a period inside which the operator must decide once documents arrive.
Five figures in a hundred operators
The pattern is not local to this table. Across the wider library of 100 operators, a verification clause has been read for 49. All 49 reserve the right to require documents at the operator's own judgement. Five of the 49 attach an amount to it.
| Operator | Amount | Clause |
|---|---|---|
| Bitcasino.io | €2,500 | 6.6 |
| Sportsbet.io | €2,500 | 6.6 |
| Livecasino.io | €2,500 | 6.6 |
| Rocketpot | $2,500 | 11.4 |
| Empire.io | 2,000 USDT | 5.4 |
Three of those five share a clause number as well as a figure, which is what happens when brands share a back office rather than what happens when a market converges on a standard.
A drawing, made for this page. The sheet is the point of it: every figure on this page comes from a numbered clause in a published contract, and the one thing that contract never prints is the clock on the wall behind the counter. The amounts are there — €10, €100,000 a week, €400,000 in instalments — and a processing time stated in hours or days is not.
Five in a hundred is the honest scale of the thing. A reader who leaves one operator because it will not name a sum is looking for a property that 95 of a hundred also decline to publish, and the search is better framed as finding one of the five than as escaping the norm.
What an unpublished trigger changes
It moves the moment of surprise. With a printed figure, a customer knows before depositing which side of the line a planned withdrawal falls on. Without one, the request can arrive at any size, on any day, and the first notice of it is usually a payout that has stopped moving.
It also removes the sentence a person would otherwise quote. A dispute about a check against a published threshold is an argument about a number; a dispute about a check under clause 21.1 is an argument about whether the operator's judgement was exercised reasonably, and the clause has already answered that by calling the discretion sole.
Nothing on this page is advice about documents, and no page on this site carries any. What is here is the wording, its clause number, and what the wording leaves open.
One adjacent clause belongs in the same reading, because it is triggered by suspicion rather than by identity and lands on the same balance. Clause 6.19 reserves the right to apply a wagering requirement of at least five times the deposit where the operator suspects the service is being used as a mixer — a floor with no ceiling, attached to money the customer put in unaided. How that reads from the customer's side is at suspended accounts and held balances.
What the same eleven operators commit to on the way out is at how long a withdrawal takes. Which of them a stranger can look up in a register is at ten permits and one blank.