You sent the coins, the exchange says "completed", and the casino balance says zero. Every crypto gambler meets this moment eventually, and the panic is universal. The good news: in the deposit-failure cases we've handled across the audit and reader correspondence, genuine loss is rare. The money is almost always somewhere findable. Here's the diagnostic, in the order that resolves fastest.
Step zero: get your transaction hash
Everything starts with the txid: the hash your wallet or exchange generated when it broadcast the transfer. Find it in your withdrawal history and paste it into the right block explorer (mempool.space for Bitcoin, tronscan.org for TRC-20, etherscan.io for Ethereum, solscan.io for Solana). Three facts on that page decide everything below: confirmation count, destination address, and network.
Cause 1: not enough confirmations yet
The most common and most benign. Casinos credit deposits after a confirmation threshold: typically 1 confirmation for BTC (~10 minutes), 10–20 for ETH, and near-instant thresholds on Tron and Solana. A BTC deposit sent with a low fee during mempool congestion can sit unconfirmed for an hour-plus; the explorer will show it as pending.
Fix: wait. If the fee was badly underpriced, some wallets offer replace-by-fee (RBF) to bump it. The casino cannot credit what the chain hasn't confirmed, and as we covered in the withdrawal-speed piece, checking mempool congestion before sending is a thirty-second habit that prevents this entirely.
Cause 2: wrong network
The dangerous one, and we wrote a full section on it in the USDT guide. You selected TRC-20 at the exchange while the casino's deposit address was ERC-20 (or BEP-20, or any other mismatch). The explorer check makes it obvious: your transaction confirmed on a network the deposit address wasn't configured for.
Fix: contact support immediately with the txid, the networks involved, and the amounts. Recovery depends on whether the operator controls the destination key on the network you actually used. Some do and recover with a fee and a wait measured in weeks; some can't or won't. This is the one cause where money genuinely dies, and it's entirely preventable: the address-prefix check (Tron addresses start with T, Ethereum with 0x) plus matching the network label on both screens.
Cause 3: missing memo or destination tag
XRP, and some exchange-hosted deposit systems, use a shared address plus a memo/tag to route funds to your account. Send without the tag and the coins land at the operator's wallet with no routing information. Our XRP audit found exactly this pattern generating support tickets: the funds arrive, the ledger can't place them.
Fix: support ticket with txid and your account details. Operators can almost always manually credit tagged-currency deposits once you prove the send: it's a known failure mode with an established process. Expect a delay, not a loss.
Cause 4: under the minimum
Deposit minimums ($20 equivalent at Cinoslots, $1 at Duelbits and 22bet, varying per operator and per asset) are evaluated on the received amount. An exchange withdrawal that leaves at exactly the minimum arrives under it after network fees, and sub-minimum deposits credit nothing at most cashiers automatically.
Fix: support ticket. Most operators credit sub-minimum deposits manually on request; a few absorb them permanently per their terms (a clause worth checking before you use any new cashier). Prevention: send 5–10% above the stated minimum.
Cause 5: stale or regenerated deposit address
Some cashiers rotate deposit addresses per session or per deposit. Sending to an address you saved weeks ago can land funds at an address the cashier no longer watches, even though the operator still controls it.
Fix: support ticket with txid; crediting is routine since the key is theirs. Prevention: generate a fresh deposit address for every send, every time. It also improves your privacy hygiene as a side effect.
Cause 6: the chain is fine, the casino is slow
Explorer shows confirmed, address matches, network matches, memo included, amount over minimum, and the balance is still zero: the crediting delay is operator-side. Cashier queues, wallet-node sync lag, or a stuck internal job. In our 55-operator audit, operator-side crediting delays beyond 30 minutes post-confirmation were rare at ranked operators and routine at several we blacklisted; deposit-crediting reliability is part of the withdrawal-integrity criterion for exactly that reason.
Fix: support, with the txid and a screenshot of the explorer confirmation. A competent desk resolves this in minutes (Bitstarz's 92-second median first response is the pace-setter on our list). A desk that stalls past 24 hours on a confirmed deposit is telling you something about how withdrawals will go too; weigh it accordingly.
The escalation path when support stalls
Document everything: txid, explorer screenshots, timestamps, every support exchange. Then escalate in order: named supervisor within the operator, then the licensing regulator (post-LOK Curaçao OGL complaints go directly to the Curaçao Gaming Authority; Anjouan runs an ADR step), and if the operator turns out to be unlicensed, the lesson is the one we keep repeating. Deposits that stay missing at licensed operators are genuinely rare; the regulator route exists and works on a weeks-scale clock.
How long does a crypto casino deposit take to show up?
Fast rails (Tron, Solana) credit in under a minute; BTC needs its confirmation threshold (usually 1 block, ~10 minutes); ETH typically 10–20 confirmations. Add operator-side crediting, which is near-instant at good cashiers. Anything past an hour with a confirmed transaction is worth a support ticket.
I sent crypto to the casino but it never arrived. Is my money gone?
Probably not. Check the transaction hash on a block explorer: if it confirmed at the correct address and network, the funds arrived and support can credit them. Genuine loss basically requires a network mismatch at an operator unable to recover cross-chain sends, which is why the network check before sending matters most.
What happens if I deposit less than the casino minimum?
Most cashiers won't auto-credit sub-minimum amounts; support can usually credit manually on request, though some operators' terms let them absorb small residues. Send comfortably above the minimum so network fees can't drag you under it.
Why does my USDT deposit say completed on the exchange but not the casino?
"Completed" at the exchange means broadcast, not credited. The usual culprits are network mismatch (TRC-20 vs ERC-20) or the casino's confirmation threshold. The transaction hash on the correct network's explorer tells you which situation you're in.
Can a casino steal my deposit?
A licensed operator gains nothing and risks its licence by eating deposits; disputes there resolve through support or the regulator. Unlicensed operators are a different world, and deposit theft is one of the documented patterns on our blacklist. The licence check before the first deposit is the entire defence.
The verdict
A missing deposit is a diagnostic exercise, not a catastrophe: hash, explorer, six causes, in that order. Adopt the three prevention habits (network match, copy-paste addresses, test deposit first) and you'll never run the diagnostic at all. And if an operator's desk goes quiet on a confirmed deposit, believe what that tells you, before your next withdrawal finds it out the hard way.
Researched and written by the CryptoCasinoi Editorial Team under methodology v3.3. Crediting-behaviour observations from the February–May 2026 audit cycle. Affiliate relationships disclosed here.
