From cashier status to wallet
Approved but Not Received: Status, Hash, Chain and the Receiving Side
An approved request means the operator has said yes; it does not yet mean the coins sit in your wallet. Here is how to read the status, find the transaction hash and see which party holds the payout now.
Approved but not received is one of the most common places for a crypto payout to look stuck. The cashier has said yes and your wallet still shows nothing. Between those two screens sit three more stages: the operator broadcasts the transaction, the chain confirms it, and the receiving wallet or exchange credits it.
This page follows those stages in the order you can check them yourself. It starts with the one piece of evidence that settles most questions, the transaction hash, and ends with a routine for the moment a status stops moving. The five stages of a payout are drawn in full on a page of their own.
What the cashier's words mean
Status labels differ from one cashier to the next, and the terms of the ranked operators do not define them. Read each label against the five stages instead:
- Requested or pending. You have asked and nobody has approved yet. The rules of stage two apply here: the identity check, play-through, caps and instalments. The page on ceilings and payouts in slices covers the last two.
- Approved. The operator has accepted the request. Depending on the cashier, the transfer may still sit in a queue before anyone signs it.
- Sent, completed or processed. The operator reports a broadcast. From here on, the chain and the receiver hold the payout.
- Cancelled or returned. The request has been stopped. If the balance does not show the amount again, ask support where it went; the page on cancel options in a cashier covers this case.
A label that says approved without a hash means the payout is still inside the casino. A label that says sent should come with a hash, and if it does not, ask for one. When the label goes back from approved to pending, a new check has usually opened at stage two, and the page on identity checks and document deadlines explains what the operator may want.
| Casino | Score | Identity check | Instalments | Link |
|---|---|---|---|---|
Ad VaveEditorial real-money account | 3/5 | At withdrawalcl. 8.7 | Exceptional case: wins from 50,000 USDT upward can be split into equal partscl. 8.8 | Visit Vave |
1 Bitcasino.io | 4/5 | After a trigger eventcl. 3.13, 6.6 | Large requests: at most 1 million USDT a week until settled; no threshold namedcl. 6.10 | Fact box |
2 Rocketpot | 4/5 | At withdrawalcl. 11.4, 12.4 | Wins of $5,000 or more: at most $5,000 a month until settledcl. 11.5 | Fact box |
3 Wild Fortune | 4/5 | After a trigger eventcl. 2.7, 11.2 | Over €15,000 on the balance: paid in monthly slices, each capped at €15,000cl. 11.8 | Fact box |
4 Metaspins | 3/5 | After a trigger eventcl. 9.7 | Monthly instalments possible where a payment method limits the amount; no threshold namedcl. 12.5 | Fact box |
7 Bitsler | 2/5 | After a trigger eventcl. 8.22, 4.3 | Large requests: instalments and/or payment in BTC, ETH or USDT; no threshold namedcl. 8.13 | Fact box |
8 Thunderpick | 2/5 | No moment namedcl. 21.1 | Over €400,000 won: paid in monthly slices, each capped at €400,000cl. 6.12 | Fact box |
Approved but not received: find the transaction hash first
Every transfer on a public chain carries an identifier. It is called a transaction hash or TXID, a long string of letters and digits, and many cashiers show it in the transaction history once the coins have gone out. If yours does not, ask support for it and quote your request ID.
Paste the hash into a block explorer for the chain the payout used. The explorer shows what the chain itself records: the sending address, the receiving address, the amount, and how far the transfer has progressed toward being final. Nothing in that record depends on what the cashier says.
Three checks settle most cases:
- Is there a hash at all? No hash, no broadcast: the coins are still with the operator, and the question belongs to its support.
- Does the receiving address match yours? Compare it character by character with the address you entered, above all the first and last few characters.
- Is it the right chain? An explorer for one chain will not find a transaction from another. If the hash turns up nowhere, try the explorer for the other chain your coin runs on.
Confirmations and finality: the chain's share
Once a transfer is broadcast, the chain decides when it counts as settled, and each protocol describes that point in its own documentation. Bitcoin adds a confirmation with every new block, and bitcoin.org advises waiting for several of them before treating a high-value transfer as settled. Ethereum's documentation on ethereum.org divides time into slots and epochs and describes the point at which a block is finalised.
TRON's developer documentation speaks of a block being solidified once enough Super Representatives have built on top of it. Solana's RPC documentation distinguishes three commitment levels. The lowest, processed, can still be rolled back; confirmed and finalized come after it.
None of these is set by a casino. The operator decides when to broadcast, the protocol decides when the transfer is final, and the receiver decides when to credit it. The page on how operators count confirmations on deposits sets the protocols against the casinos' own deposit rules.
If the explorer shows the transfer as still unconfirmed, the operator has done its part and the chain has not finished yet. On chains with a fee market, a transfer sent with a low fee can wait longer for its first confirmation than one sent with a higher fee.
A wrong network: the right coin on the wrong chain
One token can live on several chains. Rocketpot names USDTE and USDTT as separate coins in clauses 7.1 and 10.1 (read 2 September 2026): the same dollar token, carried on two different chains.
If the payout went out on one chain and the address you gave belongs to another, the explorer shows a completed transfer while your wallet shows nothing. Whether coins sent across that mismatch can be recovered depends on the wallet or exchange that controls the address, not on the casino.
Two rules on file keep coin and chain matched from the start. Rocketpot's clause 11.1 sends a payout only in the deposit coin and only to the deposit wallet. Shuffle.com's clause 10.2 lifts the play-through when a crypto payout goes back to the address that funded the account, over the same chain (read 8 September 2026). Both reward one habit: deposit from the wallet you want to be paid in, and leave coin and chain unchanged. The page on one token carried on two chains goes through the choice in detail.
When an exchange is on the receiving end
If the payout goes to an exchange account rather than a wallet you control, one more party joins the line of hand-offs. The exchange watches the chain and credits your account by its own rules: how many confirmations it waits for, which chains it accepts for a given coin, whether it needs a memo or tag with the deposit, and what checks its own compliance desk runs.
Here the hash is again the key. If the explorer shows the transfer as final and the receiving address matches your deposit address at the exchange, the operator's part is finished. The question now belongs to the exchange's support, and the hash, the amount and the time of the transfer are what they will ask for.
Three exchange habits are worth checking before you give a casino any address: a deposit address that has changed since you last copied it, a coin that the exchange accepts on one chain only, and a memo field for coins that need one. All three sit on the exchange's deposit screen.
Approved but not received: a routine for a status that stops moving
- Save the status. Take a dated screenshot of the approved request and note its ID.
- Get the hash. Copy it from the history, or ask support for it.
- Check the explorer. Confirm the receiving address, the amount, the chain and how far the transfer has progressed.
- No hash yet. Write to the casino's support, quote the request ID and ask which step the request is at.
- Hash final, address yours. Contact the support of the wallet or exchange and send them the hash.
- Address not yours. Write to the casino's support without delay, with a screenshot of the address you entered.
- Keep everything. Add each message to an evidence file; what belongs in one is set out on the page about stuck requests.
A stuck status is easier to resolve when you can say exactly which of the three parties holds the coins. The hash tells you that in one look.