Binance Deposit Not Showing Up? How to Trace a Missing Deposit
You sent crypto to Binance from another wallet or platform, or bought some USDT with fiat, and you wait and wait but the balance won't budge. Doubt starts to creep in. Just like with withdrawals, a deposit that hasn't shown up almost never means the money vanished into thin air; it's stuck at one step along the way. The first thing to do is figure out which kind of deposit you actually made, an on-chain crypto deposit, a C2C buy, or a fiat deposit, because the causes and the people to contact are completely different for each. Get the category right and the rest is easy. This is a companion piece to what to do when a withdrawal doesn't arrive, and the logic runs in the same vein.
01First sort out which kind of deposit it is
"Deposit" is one word to a beginner, but it's actually three different things. Match yours first:
On-chain crypto deposit. You moved coins over a blockchain from an external wallet or another exchange to the deposit address Binance gave you. This is the one that goes wrong most often and is most worth examining closely, so it gets the spotlight below.
C2C buy. You traded peer-to-peer with a merchant on the C2C market, using fiat (say your local currency) to buy USDT. There's no "on-chain transfer" to you here; the merchant moves the coins from their Binance account to yours, and problems usually crop up around the order and release step.
Fiat deposit. You loaded fiat currency onto the platform via a bank card or a third-party payment channel. When this path stalls, it's mostly stuck at the payment processor or bank end.
Sorting out the type is the same as deciding "who to contact": an on-chain deposit, the problem may be on-chain or in Binance's crediting; C2C, go through the order and platform support; a fiat deposit, check the payment channel and the deposit order. Get the direction wrong from the start and you'll only wait longer and worry more for nothing.
02Common causes for an on-chain deposit not arriving
If an on-chain deposit hasn't arrived, run down the causes one by one; it's basically one of these:
You chose the wrong network. As with withdrawals, this is the number one trap. The chain you pick when sending must match the chain that Binance deposit address supports. If Binance gives you a TRC20 USDT deposit address but you send over the ERC20 network, you're asking for trouble.
You missed or mistyped the memo / tag. Some coins need a memo or tag in addition to the address when deposited to an exchange, to match the funds to your account. Miss it or get it wrong and the coins may reach the platform's address without being credited to you, requiring manual handling.
Not enough confirmations yet. The coins are already on-chain but haven't gathered the number of confirmations Binance requires, so the balance hasn't updated. This is just slow, not lost; it'll arrive once it's confirmed enough. Beginners panic most at this step, the block explorer already shows it, so why hasn't the account moved? It's simply waiting for confirmations. Different chains require different counts, so just wait it out.
You deposited to the wrong address. A copy-paste slip, or using an expired address or one that isn't yours, and the coins go elsewhere. This is the thorniest. A reminder: it's best to grab and copy the deposit address fresh from the Binance page every time, rather than saving one old address and reusing it for convenience, the address for some coins may get updated by the platform, and using a stale one can cause problems.
The coin or chain is unsupported or paused. Occasionally a niche coin, or a chain's deposits, get temporarily paused for maintenance. The page usually shows a notice for this, so if you see one, don't deposit at that moment, wait until it's back.
The golden rule for deposits is the same as for withdrawals: the network must be right, paste the address rather than typing it by hand, and don't miss a required memo. Get any of these three wrong and at best you'll need a manual recovery, at worst you may never get it back. Ten extra seconds checking beats begging support later. For how chains correspond, see how to pick TRC20/ERC20/BEP20.
03How to check: transaction history + block explorer
To check a deposit, two tools are enough: the platform's transaction/deposit history, and a block explorer.
Check the Binance side first. Go to "Wallet → Transaction History → Deposit" and find this entry, then look at the status. If it shows "Processing / Pending confirmation," the platform has detected it and is waiting on confirmations or crediting, so keep waiting. If there's no record at all, the problem may be on the sending side (not yet broadcast on-chain, or an address/network error).
Then check the TxID on a block explorer. This step settles it for good. On the sending side (your wallet or another platform), find the transfer's TxID (transaction hash), copy it, and look it up on the right chain's block explorer: for TRON (TRC20) use Tronscan, for Ethereum (ERC20) use Etherscan. Focus on two things: whether the transaction is successful, and whether the receiving address (To) is exactly the deposit address Binance gave you. If those two check out, the coins really did go to the right place, and what's left is to wait for crediting or ask support to top it up.
Each coin and chain needs a different number of confirmations, and arrival time also depends on on-chain congestion. The exact requirement follows what the Binance deposit page shows right now, so don't apply a fixed number. Once you've learned to check a TxID, you can judge for yourself where your coins are whenever a deposit or withdrawal goes sideways, instead of just waiting anxiously.
04Match your situation to the fix
Map what you found to how to handle it:
Block explorer shows still confirming → it'll arrive once it has enough confirmations, especially on chains that are naturally slow.
Shows successful, the receiving address is exactly the Binance deposit address, but the account hasn't updated → usually it's mid-crediting or missing a memo, so wait a bit; if it's still not in after a good while, bring the TxID to official Binance support to credit it or verify.
Wrong network or missing memo → contact Binance support, provide the TxID, and apply for a manual recovery; whether it can be recovered depends on platform policy.
Deposited to the wrong address, coins went elsewhere → the hardest case; it largely depends on who owns the address and whether the other platform will cooperate, and in many cases it can't be recovered.
C2C or fiat deposit problem → go through that order's status and platform support, and don't get entangled in private transfers with the other party. For how to buy safely on C2C, see is C2C safe, and how to avoid tainted USDT and frozen cards.
A bit more on C2C, since this is where beginners trip up most. C2C is a peer-to-peer trade where you pay the merchant and the merchant releases USDT to you. If you've already paid but the merchant keeps stalling on the release, do not cancel the order, cancelling strips your payment proof of its basis. The right move is to keep your payment records and open a dispute within the order to bring the platform in. Likewise, if someone messages you outside the order asking you to cancel, switch to another channel, or pay some extra "fee," it's almost always a scam, so ignore it entirely. For the safe C2C workflow, definitely read how to avoid tainted USDT and frozen cards on C2C first and memorize the hazards.
A fiat deposit (bank card or a payment channel) that hasn't arrived is a different situation: the money may still be sitting in the payment processor's or bank's pipeline, which isn't fully within Binance's control. First check the status in the deposit order; if it shows processing, give it some time. If the money has already been debited from your card but the order failed or has gone silent for a long time, bring your payment proof (the debit record, order number) to Binance support to verify, and watch out for whether the payment provider's risk controls blocked it.
Explanations of deposit statuses and recovery flows follow the current pages of the official Binance Help Center. For the whole journey from depositing to buying, work through the complete first-buy guide; for the first step of turning local currency into USDT, see how to buy USDT with your local currency.
FAQFAQ
My on-chain deposit still hasn't arrived. Is it lost?
In most cases it isn't lost; it's either still confirming, or something went wrong with the network or memo at deposit time. First copy that transfer's TxID and check it on the right chain's block explorer: if it shows still confirming, it'll arrive once it has enough confirmations; if it shows successful and the receiving address is exactly the Binance deposit address you were given, the platform is usually mid-crediting, so wait a bit or contact support to credit it manually. The genuinely tricky cases are choosing the wrong network or missing a memo.
I forgot to enter a memo or tag on a deposit. What now?
Some coins (when sent to certain platforms) require a memo or tag in addition to the address, to match the funds to your account. Miss it or get it wrong, and the coins may reach the platform's main address without being credited to you. This usually means contacting Binance support and applying for a manual recovery with details like the TxID; whether it can be recovered depends on platform policy, so always confirm whether a memo is required before you deposit.
Who do I contact if a C2C buy or fiat deposit doesn't arrive?
First work out which it is. C2C is a peer-to-peer trade with a merchant; if there's a problem at the release step, check the order status and use the platform's dispute/support channels, and don't get into private transfers with the other party. For a fiat deposit (bank card or a payment channel) that hasn't arrived, it may be stuck at the payment processor or your bank, so check the deposit order status and, if needed, contact Binance support and verify your payment receipt.