Casino withdrawal paid but not received? Check the TXID

If a casino marks a crypto withdrawal as paid but you have not received it, ask for the transaction ID (TXID), network and destination address. Check the transfer on that network's block explorer. A pending transaction, a failed transfer and a confirmed payment awaiting exchange credit need different responses. The casino's status label alone does not resolve which happened.

This guide covers ordinary on-chain withdrawals, with Bitcoin and Ethereum token examples. Lightning payments and internal transfers can use different records. The examples below are illustrative; we have not accessed your wallet, exchange account or casino account.

Start with the transaction, not the "paid" label

The broader crypto casino withdrawal process includes account checks, sending the payment and receiving it. Here, the question is narrower: what happened after the casino said it sent the money?

Status labels depend on the platform. For example, Kraken's withdrawal-status documentation distinguishes internal processing, broadcast and confirmation. Its Kraken Classic "Success" state means one network confirmation. That is a Kraken definition, not a rule for casino cashiers or receiving exchanges.

Use the explorer record to choose the next step:

A transaction that you cannot find is not, by itself, proof that the casino sent nothing. First rule out the wrong network, a mistyped hash and an explorer that has not indexed the transaction.

1. Get the TXID and the exact network

Request these details together:

• Withdrawal ID and the status printed in the casino account.

• Transaction hash and a link to its explorer record.

• Blockchain network, asset and amount sent.

• Destination address, including any required memo or tag.

• Broadcast time and the amount deducted as a withdrawal fee.

USDT alone is not a network name. If you requested USDT on TRON, an Ethereum transaction does not establish that the requested TRON transfer was delivered.

Keep the casino's withdrawal ID separate from the blockchain hash. The first identifies its account record; the second lets you inspect the transfer independently. On Ethereum, a hash is generated before the transaction is broadcast, so a hash string alone is not proof of inclusion or completion. Ethereum's transaction lifecycle describes those separate stages.

2. Open the correct explorer and compare the transfer

Use an explorer for the specified network, reached through a trusted wallet or the network's official documentation. Viewing a public transaction does not require a seed phrase, a wallet signature or a "verification" payment.

Compare the record with your withdrawal request, rather than checking only whether the page says success. Ethereum's explorer documentation identifies fields such as status, sender, recipient, value and token transfers.

For a token payout, inspect the actual token-transfer entry. The transaction's top-level recipient can be a contract; it need not be your wallet. Check the beneficiary address, the amount and the token contract against the receiving service's supported asset. A token's name alone is not enough.

For Bitcoin, compare the relevant output address and amount with the receiving details you supplied. The Bitcoin developer guide explains transaction outputs; do not assume that a total transaction value is the amount sent to you.

Two illustrative cases show why a quick glance can mislead:

• A Bitcoin transfer includes an output to your address, but has no confirmations. You have evidence of the transfer's current network state, not evidence that an exchange has credited it.

• An Ethereum transaction shows a value of 0 ETH but includes a USDT token transfer to your address. Zero ETH in that field does not mean no USDT was sent. Inspect the token transfer instead.

Save the explorer URL and the time you checked it. A screenshot without its network or timestamp makes a later dispute harder to follow.

3. Separate pending, failed and confirmed

Coinbase's pending-transaction guidance describes insufficient confirmations, network congestion and other delays. It recommends checking the transaction hash and contacting the sender about an unconfirmed transfer.

There is no universal confirmation count or payout deadline. Bitcoin.org's FAQ explains that confirmation times vary; the familiar roughly ten-minute block interval is an average, not a guaranteed waiting period for your transaction.

If the record shows a failed transfer, send that record to the casino and ask whether its cashier status will be corrected and how it will resolve the payout. Do not treat a failed attempt as a completed payment merely because the withdrawal balance was deducted.

If a successful transfer is confirmed, continue with the receiving account. An Ethereum transaction can be included in a block yet show failed execution. Check its success status as well as confirmations; account crediting is a separate service step.

4. Check the receiving exchange or wallet

Compare the full destination address and network with the receiving details for your account. For a custodial exchange, review its current deposit instructions for that asset, including supported networks and any memo or tag.

Coinbase's send-and-receive troubleshooting guide advises checking addresses, networks and account alerts. Missing account requirements can affect crediting even when a transfer exists. Use your receiving provider's own instructions; Coinbase's requirements are not automatically those of every exchange.

If the network or address is wrong, contact the sender and receiving service promptly. Recovery depends on the specific service and transfer; do not assume that it is either guaranteed or impossible. Never send an additional casino deposit to "release" the old payout.

A support message that keeps the case specific

For the casino, use:

Withdrawal [ID] is marked [status], but the funds have not arrived. It was requested for [asset and amount] on [network] to [address]. Please provide the transaction hash, broadcast time, asset and amount actually sent, including the withdrawal fee. If it has not been broadcast, identify the pending stage and next update time. If the attempt failed, explain how the payout will be resolved.

For the receiving service, use:

I am expecting [asset and amount] on [network] at [deposit address, plus memo/tag if applicable]. The transaction hash is [hash]; the explorer shows [status] when checked at [time and timezone]. Please confirm whether this transfer is recognised for my account and which deposit or account requirement prevents crediting.

Send those details privately through verified support channels. Public hashes and wallet addresses can reveal financial activity; a public complaint does not need your identity documents or complete account history.

Keep replies with the original request and explorer record. If the casino still refuses to clarify the payout stage, our casino refusing to pay guide explains how to organise a complaint. An unresolved transfer is a reason to preserve evidence, not enough on its own to label an operator fraudulent.

Technical sources reviewed on 30 September 2026. This is a transaction-checking workflow, not a promise of recovery or a finding about a particular casino.