Written and checked by Ingrid HalvorsenTerms editor

Verification clauses, read 26 August 2026

Four verification clauses were read, and not one of them says no KYC

Eleven operators sit beside Stake.com in this table. Four of their verification clauses have been read, seven have not, and zero publish a sum at which documents become compulsory. That leaves three honest states for a cell, and none of them is the phrase in the query.

What each operator publishes about itself: the company named on the licence, the permit number and where it was read, how many countries the operator excludes in its own terms, and when identity documents are demanded. The country count is the length of a list the operator published, not our estimate of where it will accept you. An empty cell means the document was not read — it is not a zero, and it is not a permission.

Vavepaid placement: OperatorTechOptions Group B.V.
LicenceCuraçao no number
Countries barredlist not read
Before ID checkcase by case
Visit
Stake: OperatorMedium Rare N.V.
LicenceCuraçao Gaming Authority
Countries barred1
Before ID checkcase by case
Shuffle: OperatorNatural Nine B.V.
LicenceCuraçao Gaming Authority
Countries barred15
Before ID checkcase by case
BC.Game: Operatornot published
LicenceCuraçao Gaming Authority
Countries barred0
Before ID checknot published
Roobet: Operatornot published
Licencenot published
Countries barred0
Before ID checknot published
Rollbit: Operatornot published
Licencenot published
Countries barred0
Before ID checknot published
Duelbits: OperatorLiquid Entertainment N.V.
LicenceCuraçao Gaming Authority
Countries barred0
Before ID checknot published
Bets.io: OperatorTechno Wave Systems S.R.L.
LicenceCuraçao Gaming Authority
Countries barred42
Before ID checkcase by case
Cloudbet: OperatorHalcyon Super Holdings B.V.
LicenceCuraçao Gaming Authority
Countries barred2
Before ID checkcase by case
MyStake: Operatornot published
LicenceCuraçao Gaming Authority
Countries barred0
Before ID checknot published
TrustDice: Operatornot published
LicenceCuraçao Gaming Authority
Countries barred0
Before ID checknot published
BetFury: OperatorUniverse B Games B.V.
LicenceCuraçao Gaming Authority
Countries barred0
Before ID checknot published

What the four read documents actually say

Eleven operators sit in the comparison table beside Stake.com. Four of their verification clauses have been opened for this site, and each one reserves a right to ask for identity documents. Three are set out here; the fourth belongs to the paid row and is quoted further down.

Shuffle puts it in clause 4.1: the operator may request KYC documentation at any time it deems necessary, and may restrict access or withdrawals until identity is established to its satisfaction. Its anti-money-laundering policy goes further and describes a risk-based threshold at which withdrawal functions may be suspended — then does not print the amount.

Bets.io puts it in clause 5, and its wording is the most concrete of the four. Proof of identity, source of funds and bank statements may be demanded before a deposit or a withdrawal is processed. A player has 30 calendar days to supply them, the account may be suspended until they arrive, and false documents are named as grounds for confiscation.

Cloudbet puts it in clause 18.1.1, inside an anti-money-laundering and KYC policy that requires reliable independent identity documents and gives four examples: identity card, passport, bank statement, utility bill. It reserves verification of any customer it deems risky or suspicious, and re-verification of a customer already cleared once.

Stake.com's own clause 4.8 sits beside those three: documents may be requested at any time to establish identity and location, service, payment and withdrawal may be restricted until identity is sufficiently determined, and withdrawals require identity verification.

Four documents, four different arrangements of the same right. Zero of them describe an operator that does not verify.

Three states of a cell, and the query matches none of them

The phrase in the search box asks for a fourth state that this reading has never produced.

The first real state is a published threshold: the operator writes a sum into its own document, prints the clause number, and a reader can open the same page and find the same figure. Across all twelve rows, that state is empty. Not one operator here publishes an amount below which documents are not asked for.

The second is a clause read with no threshold in it. Five rows are here — the four above plus Stake.com — and this is the majority of what has been read anywhere in the library. The clause describes the right, the triggers and the consequences, and leaves the amount to the operator's judgement.

The third is a document nobody here has opened. Seven rows are in that state, and it is the one most easily converted into a false headline. An unread clause is unknown. It is not zero, it is not a permission, and it is not evidence of anything about the operator behind it.

Those are the three cells this site is willing to print, and how we read sets out the order in which the closed ones get opened.

The seven documents that stay closed

BC.Game, Roobet, Rollbit, Duelbits, MyStake, TrustDice and BetFury make up the seven. Each has a verification policy of its own; none of it has been read here.

The temptation on a page targeting this phrase is obvious. Seven brands with an empty verification cell could be listed as sites that ask for nothing, and the list would rank. It would also be a fabrication, because the evidence for it is the absence of a reading rather than the presence of a document.

So the seven appear on this page only as blanks. They take no score, no ranking position and no recommendation. Should one of those policies be opened later, the entry fills with whatever the wording says, and this page moves with it.

Most of the confusion in this query comes from collapsing two moments into one.

What an account needs at opening is one question: an email address, sometimes a username, sometimes nothing more. What a payout needs is a second question, answered by a different clause, at a moment when a balance already exists. Nearly every article that promises verification-free play is describing the first door and letting a reader assume the second.

The documents read here separate them plainly. Bets.io names both deposits and withdrawals in clause 5. Cloudbet's policy is triggered by risk assessment rather than by the signup form at all. Stake.com's clause 4.8 makes verification a condition of withdrawal outright. The paid row on this site — Vave, which holds the paid placement, takes no score and no rank — records an email signup in one field and, in clause 8.7, the right to demand documents before any withdrawal at the operator's discretion, with fourteen days to supply them.

An easy signup is a real convenience and a genuine difference between products. It is not a statement about what happens when money leaves, and no clause read for this site turns it into one.

What happens when the request arrives

Two of the read documents describe the machinery, and it is worth knowing before it starts rather than during.

Bets.io's 30 calendar days is the longest published window in this reading, with account suspension named as the interim state. The paid row's fourteen days under clause 8.7 is the shortest. Stake.com, Shuffle and Cloudbet name no deadline at all, which means a wait of that kind is bounded by the operator's own pace and by nothing a reader can point at.

The document requests themselves escalate in weight. An identity card proves a name. A utility bill proves an address. Source of funds, which Bets.io names, asks a customer to account for where money came from, and it is the request that takes longest to satisfy. A reader choosing on this axis is really choosing between clauses that name their documents and clauses that do not.

Why the country lists are a separate question

Verification asks who and where. The territorial clause answers only where, and it answers it in advance and in public.

Those two are constantly merged in writing about this subject, and they behave differently. Stake.com's territorial clause runs to a single country. Shuffle's runs to fifteen, Cloudbet's to two, and Bets.io's to forty-two. A long list is not a strict verification policy and a short one is not a lenient one — Bets.io publishes both the longest territorial list in the table and the most detailed document demand.

Where a reader lives changes which of those lists matters and changes nothing about the verification clause. The counts are set out country by country: the United Kingdom, India, Canada and Australia each carry their own from the same day.

Which Stake this page compares against

The clause numbers above belong to Stake.com, the operator whose licence entry names Medium Rare N.V. and whose territorial clause runs to one country. That is the brand these eleven rows were set beside.

Stake.us is a separate product with its own documents, and none of them was opened for this page. Nothing here describes it, and no verification wording above transfers to it. The two are kept apart on Stake.com vs Stake.us, which is where a reader who meant the second one should go.

What this page is willing to conclude

It concludes four things, and stops.

Four verification clauses among these eleven operators have been read, and every one of them reserves the right to demand identity documents. Zero operators in the table publish a threshold. Seven documents are unread, and unread means unknown. And the right to ask for papers at payout survives in every document opened here, which is why no row on this site is described by the phrase that brought you to it.

The ladder that the query imagines — levels, sums, a ceiling that lifts — is examined clause by clause on Stake KYC levels, and the payout side of the same right is traced on Stake withdrawal time. The full table, with the licence entries and territorial counts behind every row, is on the front page.

Questions people actually type

Which sites like Stake have no KYC?

On the reading behind this page, none can be described that way. Four verification clauses among the eleven rows beside Stake.com have been opened — Shuffle at 4.1, Bets.io at 5, Cloudbet at 18.1.1, and the paid row at 8.7 — and every one of them reserves the right to demand identity documents. The other seven documents have not been read, which makes them unknown rather than open. An unknown is not an answer to this question in either direction.

If an operator does not ask at signup, will it ask later?

It keeps the right to. Every clause read for this site places the request at the operator's discretion, and three of the four tie it directly to money leaving: Bets.io names deposits and withdrawals, the paid row names any withdrawal, and Stake.com's clause 4.8 says withdrawals require identity verification. A quiet signup describes the front door. It says nothing about the cashier, and none of these documents promises silence there.

What triggers verification?

Four triggers appear in the wording read here. A withdrawal request is the commonest. Risk or suspicion is named by Cloudbet at 18.1.1, which also reserves re-verification of a customer already cleared once. A risk-based internal threshold is described by Shuffle, whose policy says withdrawal functions may be suspended once it is reached and does not publish the amount. And plain discretion at any time appears in all four. No trigger in any of these documents is a published sum.

Does an empty cell on this site mean an operator has no verification requirement?

No. Seven of the twelve rows have a verification clause nobody here has opened, and the site prints that as a blank rather than as a zero. A blank records our reading, not the operator's policy: it enters no total, lifts no row up the table, and supports no claim. Reading one of those documents is the only thing that would change the entry.