Deposit Didn't Arrive? Don't Panic — Check in This Order

You sent the transfer. The exchange balance is still zero. That spike of adrenaline is completely normal — but here's the honest conclusion upfront: the overwhelming majority of "missing" deposits aren't actually missing. The funds are stuck at a specific step you haven't identified yet. Truly unrecoverable situations are rare, and almost all of them result from a mistake made before the transfer, not something that went wrong during the wait.

Stop refreshing. And don't jump straight to support — the questions they'll ask you are exactly the five steps below. Work through them in order, and most people find their answer at step two. If this is among your first few deposits and you're not fully confident the setup was right in the first place — where to copy the address, which step to choose the network — go back to the deposit walkthrough and verify every step was done correctly before troubleshooting.

Step One: Get the TxID and Check On-Chain Status

Every investigation starts with the TxID (transaction hash) — the unique ID for this transaction on the blockchain. The sender's side always has it: if it went out from an exchange, check the withdrawal history; if it came out of a wallet, check the transaction list; if someone else sent it to you, ask them for it.

With the TxID, go to the block explorer for the network you used and look up the transaction — TRC20 uses TRONSCAN, ERC20/BEP20 uses Etherscan. Not sure how to do this? The TxID lookup guide walks through it in three minutes. The result will be one of three things:

• Transaction not found. It hasn't been broadcast to the blockchain: either it's still in the sending platform's processing queue, or the TxID was copied incorrectly. Go back to the sender's side and confirm the actual status.
• Transaction shows as failed. The transaction attempted to execute and was rejected. Your funds never moved from the sending address; if you initiated this withdrawal from an exchange, the platform will return the amount to your account balance. Resend once you've confirmed the status.
• Transaction shows as successful. The funds are on-chain and either in transit or already at the destination. Move to step two to find out why the platform hasn't credited the account yet.

If you can't find it: first double-check that you're using the right block explorer for this specific network — a TRC20 transaction looked up on Ethereum's explorer will return nothing, always. Also confirm the TxID is complete — one missing character and it won't match. One edge case: if the sender used Binance's internal transfer feature, the transaction never touched the blockchain, so there's no TxID to look up. Check the platform billing records instead.

Once you've confirmed the transaction is visible, cross-check one more detail: does the receiving address shown in the explorer match the deposit address you used? Match: go to step two. Mismatch: jump to step four.

Step Two: Confirmation Count — the Most Common "Missing" That Isn't

Transaction shows as successful on-chain, exchange still hasn't credited — about nine in ten cases stop here, and it's not a problem at all.

On-chain success and exchange credit are two separate events. The transaction being in a block is just the start: the exchange waits for additional blocks to build on top of that transaction — accumulating "confirmations" — before treating the credit as final. Think of it like a package arriving at a distribution centre: it's at the right location, but it hasn't been scanned into the system yet. Each platform has its own required confirmation count for each coin and network, and you'll find it listed on the deposit page.

Block speed determines how quickly confirmations accumulate: TRON produces a block roughly every 3 seconds, Ethereum about every 12 seconds, Bitcoin around every 10 minutes. The same confirmation count takes dramatically different amounts of wall-clock time on each chain — which is why a USDT deposit might clear in minutes while a Bitcoin transfer takes the better part of an hour. The network timing guide has the full breakdown by network.

Why does the platform need to wait at all? A brand-new block has a small theoretical chance of being reorganised away in a chain fork. More blocks stacked on top make that chance approach zero. The platform isn't stalling you — it's waiting for mathematical certainty before committing the credit. That's also why larger deposits sometimes require a higher confirmation count: the bigger the amount, the higher the required certainty threshold.

In your exchange's deposit history, you'll often see the count displayed in real time, like "12/20." If that number is climbing, you're fine — go get a coffee and come back. If the counter has been completely static for an extended period, open the block explorer and check the on-chain status again. Network congestion during busy periods can slow things down but shouldn't stop confirmations entirely. If the transaction is confirmed on-chain, your funds will credit once the count gets there.

Step Three: Maintenance Window and Minimum Deposit Amount

Confirmation count is cleared and you still haven't been credited? Two more things to check before escalating.

Check for a maintenance notice. Exchanges periodically suspend deposit or withdrawal processing for specific networks while they perform upgrades or wallet maintenance. During this window, your on-chain transaction may have arrived and is simply waiting in a queue. To check: open the deposit page, select your network, and look for a greyed-out status indicator or an explicit maintenance message. When in doubt, search the platform's announcement page for the network name — maintenance windows are typically announced in advance.

If you've hit a maintenance window: do nothing. Your funds are safe on-chain. The platform will process and credit them automatically once maintenance ends. You don't need to submit a ticket or take any action. The one thing not to do is panic-send a second transaction — once maintenance ends you'll receive both, which is unnecessary complexity.

Check the minimum deposit amount. Many coins have a floor — deposits below the threshold won't appear in your account and often aren't returned. If you sent a very small test amount (which is usually the right idea — we have a guide on that) and it hasn't appeared, check the small print on the deposit page for the minimum accepted amount. This is a trap specifically for cautious senders: the instinct to test with a tiny amount is correct, but the test amount has to clear the minimum threshold or it simply disappears. The threshold is shown on the deposit page; the details on small deposits and dust amounts are in the minimum deposit guide.

Step Four: Wrong Network or Missing Memo

If the block explorer address from step one didn't match your deposit address, or the transaction cleared but the account shows nothing, look at the two most common setup errors.

Wrong network. Classic scenario: the deposit page was showing a BEP20 address, but you sent ERC20 instead. Both address formats start with 0x and look identical — the exchange shows no error at the time, the blockchain confirms the transaction as successful, but the funds landed on a chain the platform wasn't watching. To confirm: compare the network shown in your withdrawal record against the network you had selected on the receiving platform's deposit page. If they don't match, that's the cause. Most cases like this are recoverable — whether and how depends on who controls the private key for that address. The wrong network recovery guide breaks down the specific scenarios.

Missing or wrong Memo / Tag. For XRP, TON, and several other coins, the deposit address is shared across all users — the platform uses the Memo or Tag field to route the incoming funds to the correct individual account. The address was correct; the Memo was blank or wrong. The funds arrived at the platform but couldn't be attributed to your account. This is usually recoverable via a support ticket with the right documentation. The steps and what to prepare are in the Memo recovery guide.

Step Five: Contacting Support, and When Funds Are Actually Gone

You've ruled out all of the above. Time to contact support. What separates a ticket that resolves quickly from one that drags is preparation. Don't start with "my deposit is missing" — open with all the materials in one message:

• TxID — the complete hash; this is the key to everything;
• Coin, network, amount, approximate time of transaction;
• A screenshot from the block explorer showing the transaction status and receiving address;
• If there's a Memo issue, include a screenshot from the time of the transfer showing what was (or wasn't) entered.

A complete ticket typically gets resolved in a fraction of the time of an incomplete one. After submitting, wait. Human account review operates on a timeline of days, not hours. No reply doesn't mean no one is working on it. Two things that slow everything down: submitting the same question in multiple tickets (they compete with each other in the queue) and using any "customer support" that contacted you via DM, social media, or group chat — none of those are real support channels, all of them are scams.

Now, the honest part about what "actually gone" looks like, because false hope and misplaced resignation are both harmful: sending to an address no one controls, or to a format-incompatible address that acts as a black hole — these are genuinely unrecoverable. On-chain transfers are irreversible; no platform or institution can force those funds back. Wrong network and missing Memo are usually different — there's often a path, but it depends on whether the receiving side can cooperate. Outside these specific cases, the funds are somewhere and there's a process to find them.

One more thing to say clearly: after you post publicly about a missing deposit, "official recovery specialists," "blockchain investigators," and "dedicated crypto lawyers" will start messaging you within the hour. Every single one who leads with an upfront fee is a scammer. Legitimate support does not require a pre-payment to start looking. Getting stuck once is painful enough; getting scammed a second time while already stressed is what these people are counting on.

Once the episode resolves, do a quick post-mortem: which step was the actual problem? Add that step to your standard checklist for future transfers. Troubleshooting is patching after the fact; building the check in before sending is how you stop needing to troubleshoot.

Frequently Asked Questions

The blockchain shows success — why hasn't the exchange credited it?

On-chain "success" means the transaction is in a block. The exchange still waits for a required number of additional blocks (confirmation count) before crediting your account. You can usually see this count in your deposit history as it accumulates. Once it reaches the platform's threshold, the credit happens automatically. This is the most common cause of "missing" deposits that aren't actually missing.

How long is too long before I should worry?

TRC20 and BEP20 typically credit within a few minutes. ERC20 can take longer during congestion. If the blockchain confirmed the transaction, the platform hasn't posted any maintenance notice, and it's been several hours, work through this guide in order and bring your TxID to support if nothing resolves it.

When are funds actually gone for good?

The most common unrecoverable situation: sending to an incorrect address that no one controls, or to an address format that's incompatible with the receiving chain. Wrong network and missing Memo are usually recoverable if the receiving platform cooperates. Ignore any private message claiming they can recover funds for a fee — that is always a scam.