KYC clauses in fifteen crypto casinos: what a figure is not

Where the published triggers sit

Only two clauses in this set of fifteen carry a figure, and they are not the same shape. Cloudbet places additional checks at the point where cumulative deposits reach USD 2,200. Bitcasino.io and Sportsbet.io share clause 6.6, which applies additional verification procedures to withdrawals exceeding EUR 2,500. No other operator among the fifteen names an amount. The units differ and the measurement points differ: one tracks money paid in over time, the other tracks a single withdrawal.

The same scarcity appears across the wider reference library. Exactly five of the 100 brands publish an amount in an identity clause itself. Bitcasino.io, Sportsbet.io and Livecasino.io all publish EUR 2,500 in clause 6.6. Rocketpot publishes USD 2,500 in clause 11.4, and Empire.io publishes 2,000 USDT in clause 5.4. There is no sixth clause of this kind in the library, and no more general industry threshold appears anywhere in these documents.

A published figure looks like certainty, but it is only a trigger. It identifies the point at which the operator may ask for additional documents, and it says nothing about what happens after the request. Nothing in any of the fifteen clauses sets a time limit for the operator to review what has been supplied, and nothing states whether the balance is treated as available while the review is open.

What a clause number gives a reader

Five operators number their identity clauses without putting an amount inside them. Vave clause 8.7 allows documents to be requested before any payout, at the operator’s discretion, and gives the player fourteen days to produce them. Stake clause 4.8 allows the operator to request identity documentation at any time to determine identity and location, and to restrict service, payment or withdrawal until satisfied. Cloudbet clause 18.1.1 requires reliable independent identity documents. Shuffle clause 4.1 may request documentation at any time if it deems it necessary. Metaspins clause 9.7 requires identity verification once gambling reaches a threshold its own terms do not state.

A clause number is not a friendly gesture. It is a reference point a reader can quote, and a marker that allows a later version of the terms to be compared. This page records clause numbers wherever they appear, and records their absence when it cannot find one. Readers who want the checkable detail behind this page will find it in the method notes.

The wider library confirms why the numbers matter. An identity provision was found at 49 of 100 brands, and all 49 reserve the right to request documents at the operator’s own discretion. Not one of those 49 promises never to ask. Twenty-seven carry a clause number that can be quoted back, while the remaining 22 sit on unnumbered policy pages.

What an archived page can and cannot show

Five of the fifteen have identity provisions that could not be tied to a numbered clause. BitStarz makes identity verification an obligatory procedure and may require proof of identity and proof of address, but no clause number was recorded for it. BC.Game has an identity provision and no recorded clause number. TrustDice, 7BitCasino and Duelbits were read from an archived copy of the operator’s own pages, and there too no identity clause number was recorded.

An unnumbered identity provision is still a provision. BitStarz and BC.Game state that documents may be required, so the absence of a clause number does not mean the absence of a policy. An archived page is a true page from the operator, but it cannot show edits made after the archive was taken. The three archived names in this section were captured this way in the reading process.

Across the wider set the same three-way split appears: 38 of 100 brands were read live, 41 from an archived copy, and 21 could not be opened at all. When a field on this page says not found, it means this library did not find the clause. It is never treated as evidence that the operator does not have one.

When nothing could be read

Three operators produced nothing readable. Rollbit and Bitz are two of them. The third was unreadable in the same way and is not described further here. The distinction is between no readable terms and no document policy. An empty field means this library could not read the provision, never that the provision cannot exist.

This empty field is the one most often sold as a convenience. A casino without a visible request procedure can be presented as one that lets players move without checks. That presentation rests on a statement about the future that no document in this set supports. A silent terms page says nothing either way, and this page does not guess.

The consequences of the clauses that were read are recorded elsewhere on this site. Cloudbet, Bitcasino.io, Sportsbet.io and Metaspins all have consequence clauses that allow balances or winnings to be confiscated in specific circumstances. None of those powers is balanced by a clause that tells the player how long the operator may take to decide.

Why the fourteen-day deadline points one way

Only one deadline exists anywhere in the fifteen, and it runs against the player. Vave clause 8.7 allows fourteen days for documents to arrive after a request made before payout. No clause in the set limits the time an operator may take to review documents once supplied. No clause states what happens to a balance during the review, and no clause lists the exact documents the operator will accept.

Those absences are documented, and they are not treated here as oversights. A missing operator-side deadline is part of the shape of these terms: the player is asked to act on time, while the operator’s processing time is left to judgement. A fourteen-day supply period is therefore a fourteen-day hold on the balance in the ordinary case.

The consequence clauses give that hold its edge. Metaspins clause 9.10 allows the balance to be confiscated if documents are not supplied in time. Cloudbet clause 11.4 reserves the right to close an account and confiscate a remaining balance where terms were circumvented by betting from a prohibited jurisdiction. Bitcasino.io and Sportsbet.io clause 3.3 allows the account to be closed immediately, winnings and rewards confiscated, and the remaining balance returned subject to charges.

What a document request makes visible

A request for identity documents is the moment at which a player’s residence becomes visible to the operator. Thirteen of the fifteen operators on this shortlist prohibit players from the United Kingdom in their own terms. Bitz and Jackbit do not. For the thirteen, the identity clause and the country clause have to be read together: one gathers proof, and the other says what proof of a British residence means.

The clause by clause country entry for each operator is on the UK player restrictions page. The question of whether that exclusion applies at deposit, at withdrawal or never is handled on the UK ban timing page. The shortlist itself arranges the fifteen by whether they accept a British player.

For a British reader, the document clause is the term that gives the country clause its force. A prohibition on UK players stays abstract until a request for proof of address arrives. At that point the two clauses become one procedure, and the consequences listed on this page are what the operator can use. The reasons these operators give for excluding British players are covered on the page about why crypto casinos exclude Britain.