Forum questions against the terms
Forum questions and the clause that answers them
In forums readers ask about closed accounts, documents and withdrawals standing still. Here we take the questions one at a time and show where the answer actually stands: in the operator's own terms and in the licence register.
Forum threads are where players go when something has gone wrong, and the questions they ask there are good ones. What a thread cannot give you is a check: the person writing may be angry, may have missed a clause, may remember wrongly or may have an interest of their own in the matter.
That is why forum threads are never a source here. We take the questions that recur instead and answer them with the clause that governs the matter, and with the register where the licence is supposed to stand. No quotations, no user names and no links to threads.
What a post can and cannot show
Whoever writes may be angry, may have missed a condition, may remember wrongly or may have an interest of their own. You as a reader cannot tell those cases apart, and the decisive detail is usually missing: which clause the operator cited and what date the terms carried.
Terms change as well. Rocketpot's bonus terms, for instance, were edited on 10 August 2022, and a thread from another year may concern an entirely different text. An answer that can be tested therefore has three parts: a clause, a document and a date.
How to find the right clause yourself
The method works for any thread you come across.
- Open the operator's general terms. The link is nearly always in the footer, often as Terms or Terms and Conditions.
- Search the text for verification, KYC, withdrawal, bonus, inactive and restricted.
- Note the clause number and the date of the document.
- Keep a copy or a screenshot with the date, so that you can show which wording applied.
- Put the forum's claim against the clause. Where they do not agree, the clause governs.
We use the same method for the whole list, and it is described in detail under how the desk reads the terms.
“The account was closed after I sent documents”
The commonest explanation is that a deadline ran out or that the documents were not accepted. Several operators write out both the deadline and the consequence:
- Vave, cl. 8.7: documents have to arrive within 14 days of the first request. Otherwise the account can be closed and the winnings withdrawn. Incorrect details lead to a refused withdrawal and a closed account.
- Wild Fortune, clause 9.3: if verification is not completed within two weeks the account can be closed and the funds forfeited.
- Metaspins, clause 9.10: 30 days, after which suspension or closure and the balance taken. Clause 9.9 covers details that do not match.
- Rocketpot, clause 12.2: 30 calendar days, after which the funds are frozen. Clause 12.3 covers forged details.
- Rainbet, clause 20.1: funds can be confiscated if the identity check does not go through.
Another ground for closure is that the account was opened from a country standing on the operator's restricted list, which is explained neutrally on the page about licence registers and country lists.
“They wanted more documents than I expected”
The lists are longer than many expect. Vave counts four ways in cl. 8.7: a selfie with the identity document, a selfie with the document plus a handwritten note carrying the site's name and the date, a telephone call and sometimes a video call. The document has to show name, photograph, date of birth and citizenship.
Wild Fortune may ask for a passport or a driving licence, a proof of address, proof that the payment method is yours, and a telephone call. If your documents use an alphabet other than the Latin or Cyrillic one, verification may go by video (clause 9.5). Bitcasino.io names in clause 6.5 photo identification, a proof of address, a copy of the card and proof of ownership of the payment method, and clause 3.13 leaves room for random account reviews. Rocketpot may under clause 11.8 ask you to sign a message from the wallet an early deposit came from.
The desk's own trial shows what that can look like in practice. At TrustDice in May 2026 the driving licence was rejected, the passport was accepted only on the fifth upload, and some time afterwards a fresh request for documents arrived by e-mail. That is an observation from one account, not a clause. The difference between a bank login and the operator's own identity review is explained on a page of its own.
“The withdrawal is standing still and nobody says why”
There is usually a clause that explains the pause. Under cl. 8.7 Vave may hold pending withdrawals while identity is checked, and cl. 8.11 requires the deposit to have been wagered three times in the casino before a withdrawal. How the wagering of the deposit works is explained in the walkthrough of bonuses.
A few operators print an amount for when the check may begin. Rocketpot gives 0.05 BTC or 2,500 $ in clause 11.4 and 2,000 $ in clause 12.4, two figures in the same document. Bitcasino.io gives 2,500 € in clause 6.6 and reserves checks below the amount as well. Wolf.bet may under clause 5 §2 hold funds on suspicion and may then not say that an investigation is under way.
Caps per period stop withdrawals too. Wolf.bet sets the limit under 15 §5 at 8,000 USD a week and 30,000 USD in a calendar month. Wild Fortune sets 1,000 per day, 5,000 per week and 15,000 per month in euro or dollars (11.8). Rocketpot pays a win from 5,000 $ at no more than 5,000 $ a month (11.5).
Our two trials show the same pattern. At Vave on 28 August 2026 the withdrawals were paid out without any identification being asked for, up to around 5,000 USDT in total. At TrustDice no verification was required until the sum of the withdrawals had passed roughly 5,000 US$; the next withdrawal received the status “payment under review”, and an e-mail with a Veriff link arrived. What the pace otherwise depends on is in the guide to the wait behind a withdrawal.
“The deposit does not show on the account”
With crypto, the wrong coin or the wrong network is the commonest cause. Rainbet warns in clause 7.9 that money sent in a coin or on a network the cashier does not handle is likely gone for good. Wolf.bet states in 14 §2 and 14 §3 that deposits between different chains and through contracts are lost. Rocketpot does not book deposits below 0.001 BTC under clause 10.2.
So check the address, the coin and the network in the cashier before you send. Rocketpot requires one confirmation on the network under clause 10.5, and Bitcasino.io three confirmations before a withdrawal under clause 6.1.
“I could not withdraw the same way I deposited”
Several sets of terms tie the withdrawal to the deposit. Rainbet's clause 8.4 requires the same method, Metaspins' clause 11.3 the same cryptocurrency and Rocketpot's clause 11.1 the same coin and wallet. If you deposit with one coin and want to withdraw with another, read those clauses first.
“The balance shrank while I was away”
Inactivity can cost money. Metaspins takes ten dollars a month under clause 13.1 once the account has been inactive for twelve months. Search for inactive or dormant in your operator's terms before you leave money on an account you are not using.
“The licence number in the footer does not match”
This is a question you can test entirely on your own. The Curaçao certificate portal cert.cga.cw is searched on domain or company name, and the public Anjouan register sits at anjouangaming.com. How the authorities differ is described in the overview of licensing countries for foreign operators. Four examples from the ranking:
- Rocketpot prints 1668/JAZ, and the Curaçao portal showed “not valid” for it on 12 and 13 September 2026.
- Wild.io: the certificate stands in the name of Nonce Gaming B.V., but in the terms you meet Stack Gaming Ltd.
- Metaspins prints a number from Anjouan, and the Curaçao register lists Metaspins N.V. — two authorities that are not reconciled with each other.
- Vave: on 12 September 2026 the certificate carried a single domain, vavegame.com.
Addresses and dates for every register are in the list with dates of reading.
A complaint that can be tested
A complaint carrying a clause number gets a different answer from an angry e-mail. Gather this before you write:
- The clause the operator is citing, and the date on the terms.
- Screenshots from the cashier and the account history.
- The transaction hash, where crypto is concerned.
- Every e-mail, with its date.
Ask support to state which clause the decision rests on. If you get no answer you can turn to the licensing authority that stands in the register, not the one that merely stands in the footer. How each operator in the list handles identity checks and licences appears from the operators' boxes in the comparison.