Crypto Deposit Not Credited: What to Do

First: check whether it actually left

Before contacting anyone, establish where the transaction is. Every transfer has a transaction hash — a long identifier the sending platform shows you. That hash is the evidence for everything that follows.

1. Find the transaction hash in your withdrawal history on the sending platform.
2. Paste it into the block explorer for that network.
3. Read the status: pending, confirmed, or failed.

Diagnosing from what the explorer says

What you see	What it means	What to do
Not found	The transaction may not have broadcast, or you are on the wrong explorer	Check the network, then the sending platform
Pending / unconfirmed	Broadcast but not yet included	Wait; on congested networks this can take longer
Failed	It reverted — funds did not leave	Check your balance; usually only the fee was spent
Confirmed, correct address	It arrived on-chain; the exchange has not credited it yet	Contact the exchange with the hash
Confirmed, different address	Sent to the wrong destination	See the recovery section below

The most common causes, in order

1. Wrong network. By a wide margin the most frequent cause. The transaction succeeded on a chain the receiving exchange does not monitor for that address. See which network to use.
2. Missing memo or tag. Some assets — XRP and several others — require a destination tag or memo alongside the address. Without it the exchange cannot attribute the deposit to your account. This is usually recoverable through support.
3. Below the minimum deposit. Many exchanges discard deposits under a threshold. Check the deposit page before sending small amounts.
4. Deposit address reused or expired. Some platforms rotate addresses; an old one may no longer credit.
5. Exchange delay. Sometimes it simply takes longer than expected, particularly during congestion or maintenance.
6. Account restriction. Incomplete KYC can hold a deposit until verification completes.

What to send support

A support ticket without these details will take far longer:

• The transaction hash
• The network used
• The sending address and the receiving address
• The exact amount and the asset
• The date and time, with timezone
• A screenshot of the deposit address page you copied from

Raise it with the receiving platform. The sending platform's job ended when the transaction confirmed on-chain, and it cannot credit funds on someone else's system.

What is recoverable and what is not

Being honest about this matters, because it determines how much effort is worth spending.

Situation	Realistic outcome
Confirmed on-chain, correct address, not credited	Usually resolved by support within days
Missing memo or tag	Usually recoverable, sometimes for a fee
Wrong network, exchange supports that chain	Sometimes recoverable, often for a fee, can take weeks
Wrong network, exchange does not support that chain	Usually not recoverable
Sent to an address nobody controls	Not recoverable

Preventing it next time

1. Open the deposit page first and copy the address from there.
2. Match the network on both sides before sending anything.
3. Send a small test amount and confirm arrival.
4. Check whether the asset requires a memo or tag.
5. Check the minimum deposit amount.

The test transaction costs a few rupees in fees and removes almost all of this risk. It is the single most useful habit when moving funds between platforms.

Confirmations, and why the wait varies

Exchanges do not credit a deposit the moment it appears. They wait for a number of confirmations — additional blocks built on top of the one containing your transaction — because a very recent block can still be reorganised.

Network	Typical confirmations required	Rough wait
TRON (TRC20)	~20	Under a minute
BNB Chain (BEP20)	~15	Under a minute
Ethereum (ERC20)	~12-64 depending on platform	Minutes
Bitcoin	~2-6	20 minutes to an hour

Requirements differ by exchange and are usually shown on the deposit page. Larger deposits sometimes need more confirmations than small ones on the same platform.

When the sending platform is the problem

Not every delay is at the receiving end. A withdrawal can sit in the sending exchange's own queue before it ever reaches the blockchain — pending manual review, held by a risk check, or waiting on batch processing.

The tell is simple: if there is no transaction hash yet, the funds have not left. Nothing the receiving exchange can do will help, and the ticket belongs with the sender. If there is a hash, the sender's part is finished.

Keep the evidence regardless of outcome

Whether or not the deposit is recovered, keep the hash, the screenshots and the ticket reference. In India each transfer needs its own record for Schedule VDA, and an unexplained gap between what left one platform and what arrived at another is exactly the kind of discrepancy that is painful to reconstruct at filing time.

Related guides

• TRC20 vs ERC20 vs BEP20
• Sent crypto to the wrong network
• Transferring crypto between exchanges
• Crypto security checklist

Educational content, not financial or tax advice. Fees, limits and processing times change — confirm current terms on the platform before acting. Exchange links are referral links; we may earn a commission at no cost to you, which does not affect what is written here.