Same-method rules and bank charges
Card vs Crypto Payouts: Where Each Rail Can Hold Your Money
A card payout and a crypto payout leave the casino by different routes, with different parties in the middle. Which route you may use is decided by the same-method clauses in the terms and by what the cashier actually offers.
Card vs crypto payouts is, underneath, a question about rails. On the crypto rail the casino approves a request and broadcasts a transaction, after which the chain and your wallet take over. On the card or bank rail the casino approves and then hands the money to a payment provider, which may route it through an intermediary bank before your own bank credits it. Which rail a withdrawal may use is often not your choice at all, because several operators tie the payout to the way you deposited.
The two rails, stage by stage
Both rails start the same way. You make a request, and the casino approves it or holds it; that is where the identity check, the play-through and any security hold apply. Only after approval do the rails part.
On the crypto rail the next steps are broadcast, confirmation and credit. Broadcast gives the transaction a hash that anyone can look up in a block explorer for that chain; confirmation follows the chain's protocol; credit is decided by the wallet or exchange you send to. The five stages in detail show who acts at each point.
On the card or bank rail the steps after approval belong to a payment service provider and to the banks behind it. There is no public hash to follow. If something stalls, the reference number from the casino or its provider is what you quote to your bank, and from there the bank's own rules apply.
| Casino | Score | Fees | Same method | Link |
|---|---|---|---|---|
| Ad | 3/5 | Intermediary bank charge on a bank payout capped at 16 USDTcl. 8.6 | — | Visit Vave |
| 2 | 4/5 | — | Payout in the deposit coin, to the deposit walletcl. 11.1 | Fact box |
| 3 | 4/5 | Intermediary bank charge on a bank payout capped at €16cl. 11.11 | — | Fact box |
| 4 | 3/5 | Charges may apply by method (cl. 12.2), while the homepage advertises 0% feescl. 12.2 | Payout by the deposit method and in the deposit coincl. 12.2 and 11.3 | Fact box |
| 5 | 3/5 | Withdrawals carry no commission after a 1× roll-over of the depositcl. 8.2 | Payout to the method used for the depositcl. 8.4 | Fact box |
| 6 | 3/5 | A fee may apply and is shown before you confirmcl. 10.7 | — | Fact box |
| 7 | 2/5 | — | The deposit method where possible; may be split across methodscl. 8.14 | Fact box |
Card vs crypto payouts under same-method clauses
Four operators on file decide the rail for you, all read on 2 September 2026:
- Rainbet, clause 8.4: payout to the method used for the deposit.
- Metaspins, clauses 12.2 and 11.3: payout by the deposit method and in the deposit coin.
- Bitsler, clause 8.14: payout by the deposit method where possible, and a payout may be split across methods.
- Rocketpot, clause 11.1: payout in the deposit coin, to the wallet the deposit came from.
A clause like this fixes the rail at the moment of deposit. If you pay in one way and later want your money back another way, the clause settles the question, not your preference. That is why the deposit page, not the withdrawal page, is where card vs crypto payouts are really decided.
Bitsler's wording leaves more room than the others: «where possible», and a payout may be split. One withdrawal can then come back in parts, through different routes, and each part follows its own rail. Metaspins goes the other way and adds the coin to the method, so a deposit made in one coin comes back in that coin.
A mixed deposit history
Same-method clauses are simple while every deposit takes one route. They get harder once you have paid in two ways. Suppose you deposit once by card and once in crypto at an operator with such a clause. Rainbet's clause 8.4 sends a payout to the method used for the deposit, but it does not say how a mixed history is divided, and Bitsler's clause 8.14 allows a split across methods without saying in what proportion. The fair reading is that the operator decides the split within its clause.
Before you add a deposit by another route, ask support how a later withdrawal would be divided, and keep the written answer. The same logic applies to coins: at Metaspins a deposit in one coin comes back in that coin (clause 11.3), so two deposits in two coins can mean two separate withdrawals, each with its own minimum and its own network fee.
Card vs crypto payouts: what the terms on file leave open
None of the clauses on file states that a particular operator pays out to cards. Same-method rules speak of «the deposit method» in general, and two fee clauses mention bank payouts by capping an intermediary charge. Whether a card, a bank transfer or only crypto appears as a withdrawal option is shown in each operator's cashier, and the options on the withdrawal tab can differ from those on the deposit tab.
So read the cashier rather than a marketing page:
- Open the withdrawal tab before you deposit. List every method it shows, not only the ones on the deposit tab.
- Match both lists against the same-method clause. A card on the deposit tab with no card on the withdrawal tab is a mismatch to resolve first.
- Check the minimum per method. Shuffle.com, for example, sets its minimum per method and shows it in the cashier (clause 10.6).
- Check the fee per method. Shuffle.com shows a fee, where one applies, before you confirm (clause 10.7); Metaspins allows charges by method (clause 12.2).
- Ask support in writing if the tabs disagree, and keep the answer with its date.
Intermediary bank charges
Two operators put a number on the cost of the bank rail. Wild Fortune caps the intermediary bank charge at €16 (clause 11.11, read 2 September 2026), and Vave at 16 USDT (clause 8.6, read 25 August 2026). The charge is taken by a bank standing between the casino's bank and yours; the clauses set how much of it can land on you. The crypto rail has no such bank, and its cost is the network fee of the chain you pick, which the page on the two kinds of fee separates from the operator's own charge.
Coin lists on the crypto rail
If crypto is the rail, the next question is which coins. The published lists run from 9 named coins at Rainbet, whose list stays open, through 10 at Wild Fortune, 12–13 at Bitcasino.io and 13 at Rocketpot, up to 32 at Wolfbet (documents read 2–8 September 2026). The coin-list figure shows the gaps as well: most other ranked casinos print no list in the documents on file.
Most lists name coins, not chains. Rocketpot is the operator on file that splits one token by chain, with USDTE and USDTT as entries of their own (clauses 7.1 and 10.1). Where a cashier shows one USDT row, find out which chain the casino sends on before you give it a receiving address; the guide to coins and chains explains why it matters.
The identity check sits before both rails
Whichever rail you use, the approval step comes first, and the identity check is where most holds happen. Bitcasino.io names €2,500 or its crypto equivalent as the document threshold (clause 6.6); Rocketpot names $2,000–$2,500 across two clauses (11.4 and 12.4). The document windows stretch from Rainbet's 72 hours (clause 20.1) to Rocketpot's 30 calendar days (clause 12.2). A change of rail does nothing to these rules, and the page on identity checks covers them operator by operator.
Security rules sit at the same step. Bitcasino.io (clause 4) and Rocketpot (clause 11.9) keep the cashier closed for 48 hours after a password change, whatever rail you choose. Settle passwords and two-factor authentication before a request, not during one.
Records to keep on each rail
On the crypto rail, keep the transaction hash, the sending and receiving addresses and the chain name for every withdrawal. On the bank rail, keep the casino's reference, the provider's name if the cashier shows it, and the matching line on your bank statement. With those in hand a stalled payout can be traced from either end, and the page on pending payouts shows what to ask at each stage. A dated copy of the terms you relied on belongs in the same file.