Crypto casino deposit or withdrawal not arriving: checklist

When a crypto deposit is not credited or a withdrawal has not arrived, the fastest way to the cause is to ask one question first: does the blockchain show the transaction, and what does it say? The answer splits the problem cleanly – either the money is still with the sender, or it is in transit, or it has arrived somewhere and is waiting for a person or a system to act. This checklist shows how to find the transaction ID (TXID), how to read it in a block explorer, and which cause fits each result. It is a triage page: where a topic has its own guide we link to it instead of repeating it. Nothing here can promise that a payment will be recovered.

Step 1: get the transaction ID

The TXID (also “transaction hash” or “hash”) is the receipt of a blockchain transfer – a long string of letters and numbers that identifies exactly one transaction. Without it, neither you nor the casino’s support can look anything up.

• Deposit sent from a wallet: open the transaction in the wallet’s history and copy the hash, or use “view in explorer”.
• Deposit sent from an exchange: the withdrawal history of the exchange shows the TXID once it has broadcast the transfer. If it shows only “processing”, the exchange has not sent anything yet – the problem is on its side, not the casino’s.
• Withdrawal from the casino: the casino’s cashier or transaction history normally shows a TXID or a blockchain link after the casino has broadcast the payment. A request that is still “pending” with no TXID has not been sent; that is a casino-side status, see Step 4.

Step 2: look the TXID up in a block explorer

A block explorer is a public website that shows what a blockchain has recorded. Paste the TXID into the explorer for the right network – a Bitcoin hash will not be found on an Ethereum explorer. Common choices are mempool.space for Bitcoin, Etherscan for Ethereum, TRONSCAN for Tron and Solscan for Solana; these are examples, not recommendations, and any reputable explorer for the network works. Use the explorer’s own address bar and type or bookmark it yourself – do not follow search-ad or message links to “explorer” lookalikes.

What the result means:

On every explorer, check these fields: status, confirmations, from and to address, amount and, for tokens, the token name and contract. How confirmations work – and why each extra block makes a reversal less likely – is explained in the Bitcoin wiki; each casino sets its own required number per coin, shown in the cashier (see our payments guide on confirmations).

Step 3: deposit not credited – the causes, in order of frequency

1. Still waiting for confirmations. A deposit is credited only after the casino’s required confirmations. If the explorer shows fewer than the cashier requires, nothing is wrong yet.
2. Wrong network. The same coin can exist on several chains. USDT on Tron and USDT on Ethereum are separate tokens on separate ledgers; the explorer for the chain you used will show the transfer, but the casino’s address on that chain may not be watched. The mechanics and the casinos’ stated rules are in our USDT network guide.
3. Wrong address or an expired one. Some cashiers generate a fresh deposit address per session or per request. An old address may no longer be monitored. Copy the address from the cashier again each time and compare the first and last characters.
4. Different token or coin. Sending ETH when the cashier expects an ERC-20 token, or a look-alike token with the same ticker, will not be credited as the expected asset. On the explorer, compare the token contract with the one the cashier or the issuer publishes – Tether, for example, lists its tokens by network on its supported-protocols page.
5. Amount below the minimum. Many cashiers do not credit deposits below a minimum, and the real minimum can depend on the network. See the minimum-amounts guide for what happens below it.
6. Missing memo or destination tag. A few coins (XRP is the best-known example) share one casino address among many customers and identify you by a tag. The XRP Ledger documents this in its source and destination tags page. If the cashier shows a tag or memo, it must be entered exactly.
7. Sent from an exchange that batches or uses internal transfers. Some exchanges combine withdrawals or hold them for their own checks; an exchange-to-exchange transfer may be internal and have no TXID on the public chain.
8. The casino holds the deposit for review. A payment can be confirmed on-chain and still held by the casino’s own compliance checks. Only the casino can tell you; ask in writing.

If the explorer shows a confirmed transfer to the casino’s correct address on the correct network and the required confirmations have passed, contact support with the details in Step 6. Do not send the amount a second time while the first one is unresolved.

Step 4: withdrawal not arriving – which stage is it at?

A withdrawal passes through stages, and the status tells you which one you are in:

1. Requested / pending at the casino – no TXID. Nothing has been sent. Typical reasons are an ID check, a bonus wagering requirement, a limit, or a rule that withdrawals go back to the method used to deposit. These are covered in why withdrawals get rejected or stay pending, and expected times are discussed in casino withdrawal times explained. Identity checks are explained in the KYC guide; complete them through the casino’s own channels only.
2. Sent – a TXID exists. The casino has done its part. Use the explorer: is the transaction pending, confirmed or failed? Is the destination address yours, character for character?
3. Confirmed on-chain but not in your balance. Now the receiving side decides. Your wallet may need to be told about a token (many wallets hide unknown tokens until you add the contract) or may be showing the wrong network. An exchange credits only after its own confirmation count, may not support deposits of that token on that network, and may require a memo or tag.

If you entered an address that is not yours or on a network your wallet does not support, the transfer is final. The casino cannot cancel a broadcast transaction, and neither can the network; ask support in writing what, if anything, it can do and whether it charges for that.

Step 5: stuck or very slow transactions

• Bitcoin: a transaction with too low a fee waits in the unconfirmed pool until blocks have room for it. Only the sender can speed it up (by paying a higher fee through a fee-bump feature in their wallet, where the wallet supports it). Nodes eventually drop unconfirmed transactions that stay unconfirmed for a long time, after which the explorer may no longer show it and the coins become spendable again by the sender. mempool.space shows the current fee level needed for the next blocks.
• Ethereum and EVM chains: a transaction can sit as “pending” if its gas price is below what the network currently accepts. Transactions from one wallet are processed in nonce order, so one stuck transaction blocks the ones after it. ethereum.org explains transactions, including nonces and the stages from pool to block. Fees are explained in our USDT guide.
• Tron: transactions carry an expiration (the developer documentation gives +60 seconds as the default) after which an unconfirmed one is dropped, and a contract transfer can fail when the fee or energy limit is too low; see Tron’s transaction reference. Holding some TRX for fees is part of sending USDT on Tron.

Waiting is usually the right response to “pending” – but never send the same payment again before you have seen the first one fail or be dropped.

Step 6: what to send to support

Write rather than chat where you can, so you have a record. Include:

• your account name or ID and the casino’s name for the cashier action (deposit or withdrawal);
• the TXID, the network and the coin or token;
• the amount, the time you sent or requested it (with time zone) and the address you sent to or received at;
• a screenshot of the explorer page showing status, confirmations, from, to and amount;
• for exchange-sourced deposits, the exchange’s withdrawal record.

Ask a precise question: “Has this transaction been received, and if it is held, why and for how long?” If the answer is unsatisfactory, the escalation routes by licence are in our guides on rejected withdrawals and licences and complaints. Be wary of anyone who messages you offering to “recover” funds for an advance payment – that is a recognised fraud pattern – and never share seed phrases, private keys or wallet passwords with anyone, including support.

What the 15 casinos we profile document

10 of the 15 casinos list at least one crypto method in their payment documentation. The table shows the coins we recorded, the withdrawal time the casino itself states and whether it states a casino-side withdrawal fee. This is what each casino says on the date shown, and we have not tested it; network fees are separate and are never a casino fee. Per-coin minimums are in the minimum-amounts guide, and the cashier after login remains the only reliable source for networks and confirmation counts.

Frequently asked questions

How long should I wait before worrying about a crypto deposit?

Wait until the explorer shows at least as many confirmations as the casino’s cashier requires. Block times differ widely between networks, so a few minutes can be normal on one chain and too short on another. If the transfer is confirmed and complete and the balance is still missing after the casino’s stated crediting time, contact support with the TXID.

Can the casino or the network reverse a confirmed transaction?

No. A confirmed blockchain transfer cannot be cancelled by the network, the sender or the receiver. A casino may be able to return funds voluntarily, but it is not obliged to do so unless its terms say so; the rules we recorded for wrong-network transfers are in the USDT guide.

My explorer shows the transaction as successful but the casino says it has not arrived. Who is right?

Both can be true. “Successful” means the network recorded it; the casino may be waiting for more confirmations, or the funds may be on a different network, address or token than the casino expected. Compare the exact address, network and token, then ask the casino to confirm in writing whether it can see the transaction.

Is a long “pending” status on a withdrawal a bad sign?

Not necessarily. A request with no TXID is waiting for a decision inside the casino, often an identity or bonus check. It becomes a concern when it exceeds the time the casino states and support gives no reason; our withdrawal-times guide explains how binding such statements are.

Conclusion

Triage in this order: get the TXID, look it up on the right network’s explorer, and read status, confirmations, destination and token. “Not found” points to the sender, “pending” means wait and compare with the casino’s requirement, “confirmed to the right address” points to the casino’s crediting or review, and “confirmed elsewhere” is final. For withdrawals, no TXID means the casino has not sent anything yet. Keep every record, write to support with the details above and never resend a payment that might still arrive. Gambling is for adults (18+) and carries a risk of loss; set a deposit limit before you play, and if play is becoming a problem, free, confidential help is listed on our responsible gambling page. How we record casino statements is described in our methodology.

Sources

• Bitcoin Wiki, Confirmation, accessed 10 Oct 2026.
• ethereum.org, Transactions, accessed 10 Oct 2026.
• Tron Developer Hub, Transaction reference, accessed 10 Oct 2026.
• Tether, Supported protocols, accessed 10 Oct 2026.
• XRP Ledger, Source and destination tags, accessed 10 Oct 2026.
• mempool.space, FAQ, accessed 10 Oct 2026.
• Each casino’s help centre and cashier, as recorded in the profile linked in the table (casino says, with the date checked).