Crypto casino withdrawals: the cap, the document threshold and the instalment clauses

Wagering the deposit: Vave cl. 8.11 and the like

Vave is the one operator on the list standing outside the ranking. Clause 8.11 of its terms sets an order: the money deposited is to be played first and requested afterwards. On casino and live casino the measure is three times the deposit, on sports bets once. Rocketpot cl. 11.2 likewise writes three rounds of wagering on the deposit.

Rainbet ties the subject to the fee: under cl. 8.2 no further cut is taken from a deposit wagered at least once. These requirements have nothing to do with a bonus; they apply to an account that takes no bonus too. Someone who deposits, plays a few hands and then asks for the whole amount back may find the request held if the wagering is not complete.

The effect at the cashier of the wagering difference between sports betting and casino is explained separately on the page describing the rate and limit clauses.

The period ceiling and the instalment clauses

Two rules are often confused. A period ceiling is the highest amount that can leave an account in a given period. An instalment clause governs a large win being paid out in parts.

The daily, weekly and monthly ceiling

The operators that write a ceiling as a figure are these:

• Wolfbet (cl. 15 §5): $8,000 a week, $30,000 in a calendar month.
• Wild Fortune (cl. 11.8): €1,000 a day, €5,000 a week, €15,000 a month; progressive jackpot wins are held outside those caps.
• Thunderpick (cl. 6.12): €100,000 a week.
• Bitsler (cl. 8.6): the operator sets the floor and the ceiling itself, with no figure in the clause.

Vave cl. 8.8, Metaspins and Rainbet set no ceiling per period. At four operators — Shuffle.com, Jack.com, Wild.io and TrustDice — the ceiling cell shows «—».

A ceiling does not mean the amount will not be paid; the part above the cap carries over to the next period. For planning, though, the difference is large: at Wild Fortune a balance of €12,000 is spread over at least three weeks by the weekly cap of €5,000. Wolfbet cl. 14 §7, meanwhile, governs something else: it limits the daily win to $100,000. That is not a ceiling on the way out but a ceiling on winnings, and the part above it may never be credited to the balance at all.

Instalments on a large win

Four texts write an instalment clause:

• Rocketpot (cl. 11.5): on wins reaching or exceeding $5,000, the monthly payment is limited to $5,000.
• Metaspins (cl. 12.5): no period ceiling, but the right to divide the payment into monthly parts is reserved; no threshold amount is written.
• Vave (cl. 8.8): no ceiling; where winnings reach 50,000 USDT the operator may, in exceptional cases, divide the payment into equal parts.
• Bitcasino.io (cl. 6.10): a large request can be processed at a maximum of 1 million USDT a week.

In the Rocketpot example a win of $20,000 is divided across four separate months under that clause. Faced with a large amount, making a plan around the slice in the terms is more realistic than expecting the whole thing in one go. To see the operators' caps side by side, look at the operator list with the files.

The demand for documents: the identity questions that come with a request

The identity clause usually comes into play together with a withdrawal request. Two texts set a threshold as a figure. Bitcasino.io's threshold in cl. 6.6 is €2,500 (or crypto of the same value); Rocketpot gives two separate figures in cl. 11.4 and 12.4, $2,000 and $2,500. Both texts also leave open the right to check requests below that figure.

Five sets of terms write plainly how many days you have once documents are asked for:

• Rainbet, cl. 20.1: 72 hours to send documents.
• Vave, cl. 8.7: fourteen days.
• Wild Fortune, cl. 8.4 and 9.3: two weeks.
• Rocketpot, cl. 12.2: thirty calendar days.
• Metaspins, cl. 9.10: thirty days.

Bitcasino.io, Shuffle.com, Bitsler, Thunderpick and Wolfbet write no deadline for sending documents. Even with no written deadline, a document asked for should not be left waiting; while the request hangs, the balance stays locked. Which documents are asked for and what to watch on the verification screen is set out in detail in the documents and thresholds guide.

The editorial desk's two real accounts

Alongside the clauses in the terms there are two observations. Both come from the editorial desk's own accounts, and both are the experience of a single account over a single period, not a rule.

Vave, 28 August 2026. The editorial desk put money into the account and took it back out. Withdrawals totalling roughly up to 5,000 USDT went through without any identity check being asked for. Even so, cl. 8.7 grants Vave the right to ask for identity before every payout; the observation does not change that clause.

TrustDice, May 2026. The account was funded with USDT over several weeks. No documents were asked for until the total out reached around $5,000; the first request after that point stayed in a “payment under review” state. An email from the compliance team followed, with a Veriff link inside it. A driving licence was refused and a passport was approved on the fifth attempt. Some time later TrustDice asked for the documents a second time, again by email.

The lesson the two observations share: silence below the threshold is not permanent. Keeping your passport and a proof of address ready before a large request makes an unexpected demand easier to meet.

The minimum withdrawal and a contradiction between two texts

The floor is read off the terms too. Rainbet cl. 8.1 asks for at least $15 per request. At Wolfbet, meanwhile, two texts do not agree: the frequently asked questions page writes 15 USDT for USDT, while cl. 14 §5 of the terms gives the floor as $0.01. Both texts belong to the operator; the cleanest course is to ask the support team in writing, before the request, which one is applied.

For a reader searching for a “bitcoin withdrawal casino”, the same logic holds on the BTC side: the per-coin floor is written on the cashier screen, and the network fee can often be deducted from the amount withdrawn. Rocketpot cl. 11.1 sets one further restriction: a withdrawal can be made only in the coin deposited and to the wallet the deposit came from. Depositing USDT and taking BTC out is not possible under that text.

If you are going to be paid in USDT, the choice of network matters as much as the floor; the difference between TRC20 and ERC20 is set out on the stablecoin and network page.

Metaspins cl. 11.3 requires the same crypto asset and Rainbet cl. 8.4 the method used for the deposit. So the coin and wallet you choose on a deposit largely settle the way back as well; the details are on the page about choosing a wallet.

When a request can be stopped

The terms also write on what grounds they may hold or refuse a payment request. Knowing these in advance shows you which clause to look at in the correspondence:

• Vave (cl. 8.12): deposits made with e-payment systems, requests inconsistent with the bets placed (minimum odds 1.1) and abuse of the account.
• Rocketpot (cl. 11.6, 12.3 and 12.5): the ratio of deposit to bets falling below 1.1, incorrect personal information and a deposit never played.
• Wolfbet (cl. 15 §6): suspicion of fraud or money laundering.
• Bitsler (cl. 8.18 and 8.22): an attempt at double spending and unusual transactions.
• Metaspins (cl. 12.3): the right to hold a request until the identity check is complete.

Most of these clauses are not a promise but a right left to the operator's discretion. If your request is held, ask support in writing which clause it rests on; the answer is the shortest way to decide the next step.

Fees: the deductions on the request side

The amount missing from a payment request can come from three separate sources: the network fee, the cashier's own fee and, where there is one, an intermediary institution's share. The network fee goes to the chain and is set by how busy the network is at that moment rather than by the size of the amount.

The terms write the cashier fee with varying degrees of plainness. We saw above that Rainbet cl. 8.2 takes no cut from a wagered deposit. Shuffle.com cl. 10.7 writes that a fee may be applied and that it will be shown before the confirmation; the same operator's cl. 10.2 does not apply the requirement that the deposit be wagered once on a crypto request to the same wallet over the same network (read 8 September 2026). Metaspins cl. 12.2 says a request may be charged for depending on the method selected.

Note the net amount shown on the confirmation screen before the request. Comparing it with the amount that reaches your wallet shows which item the deduction came from.

A crypto casino withdrawal step by step

The order to follow on the request screen is this:

1. Check from your account history that the wagering requirement is complete.
2. Choose the coin and the network; where possible, the same coin and network you used for the deposit.
3. Copy the destination address from your own wallet or exchange account and compare the first and last characters.
4. If the destination is an exchange and a memo field appears on screen, enter the memo the exchange gives you in full.
5. Keep the amount between the floor and the period ceiling.
6. Confirm the request; at this stage the cashier may ask for email confirmation or two-step verification.
7. Keep the transaction ID and a screenshot, with the date.

Once the request is made, the status screen usually shows stages such as “pending”, “processing” and “sent”. When “sent” appears a transaction ID is created too; paste that ID into the network's block explorer and you can see for yourself that the transfer was written to the chain. If the status does not change for a long time, write the support team a single message containing the request number, the amount and the date.

When choosing a network it helps to know in advance what the fee comes to on each chain; those differences are set out in the network and fee comparison.

There is no way back on a bitcoin withdrawal from a casino

A crypto transfer once written to the chain cannot be recalled. If the address is wrong, if the network is one the destination does not support, or if the memo is missing, the money can come back only through the goodwill of the receiving side. The chargeback mechanism of card payments has no equivalent on a blockchain.

So making a small test request to an address you are using for the first time, before sending a large amount — while respecting the cashier's and the recipient's floors — is a practical safeguard. For every request, keep the date, the amount, the coin, the network, the destination address and the transaction ID somewhere; those records serve both in correspondence with support and at the stage where the coin turns into lira. The steps of that stage are on the page describing the route from coin to lira.

A withdrawal is also a good moment to take a break from play. Taking part of the balance into your own wallet limits the urge to go on playing with what is left. You can set yourself a loss limit and a time limit, and where you need it, get support from YEDAM (the Yeşilay Counselling Centre) on its helpline, 115.

Frequently asked questions