📌 Overview
A deposit not credited situation occurs when your transaction is confirmed on the blockchain — meaning the funds have successfully arrived at the destination address — but the receiving platform (exchange, wallet, or service) has not yet added the funds to your account balance.
This is different from a "missing deposit" where the transaction may still be pending or unconfirmed. Here, the blockchain shows success, but your account doesn't reflect it. This guide focuses specifically on this frustrating scenario and provides a clear path to resolution.
Missing Deposit: Transaction may be pending, unconfirmed, or network-related issues.
Deposit Not Credited: Transaction is confirmed on-chain but the platform's internal systems haven't completed the credit.
🔍 Common Reasons for Non-Credit
When a deposit is confirmed on-chain but not credited, the issue is almost always on the receiving platform's side. Here are the most frequent causes:
| Reason | Description | Typical Duration |
|---|---|---|
| Internal Processing Delay | The platform's automated system is backlogged due to high volume. | Minutes to hours |
| AML / Compliance Review | Deposits flagged for anti-money laundering checks may be held for manual review. | Hours to 48 hours |
| Wallet Maintenance | The platform is performing maintenance on their hot wallets or deposit systems. | Until maintenance ends |
| Hot Wallet Replenishment | The platform's hot wallet needs to be refilled before processing credits. | Minutes to hours |
| Technical Glitch | Rare software bug preventing automatic credit from completing. | Until support intervenes |
| Missing or Incorrect Memo | Exchange deposit required a memo/tag but was omitted or incorrect. | Manual credit needed |
| Deposit Address Mismatch | Funds sent to an address that doesn't match the platform's internal mapping. | Requires investigation |
🔎 Step 1: Verify On-Chain Status
Before contacting support, confirm the transaction is indeed successful on the blockchain. This prevents wasting time on a transaction that hasn't actually arrived.
-
1
Locate the TXID
Find the transaction hash from the sending wallet or exchange. This is your unique identifier.
-
2
Open the Correct Blockchain Explorer
Use Tronscan for TRON (TRC20), Etherscan for Ethereum (ERC20), BscScan for BNB Chain (BEP20), etc.
-
3
Check the Status
Look for Success status. Note the destination address, amount, and number of confirmations.
-
4
Verify the Destination Address
Ensure the receiving address matches exactly the deposit address provided by the platform.
Take a screenshot of the blockchain explorer page showing the successful transaction. This will be your most important piece of evidence when contacting support.
🛠️ Step 2: Actions to Take
Once you've confirmed the transaction is successful on-chain, follow these steps in order:
If the transaction was confirmed in the last 10–30 minutes, give the platform a bit more time. Some systems have batch processing delays.
Visit the platform's status page or social media channels for any announced maintenance or delays.
Reach out to the receiving platform's support team. Provide the TXID, deposit address, amount, and network.
Include a screenshot of the blockchain explorer showing the successful transaction. This speeds up verification.
Never share your private keys, seed phrase, or password with support. Legitimate support teams will never ask for these. Be cautious of unsolicited DMs offering to help — these are almost always scams.
💬 Step 3: How to Contact Support Effectively
When you contact support, providing the right information upfront can dramatically reduce resolution time. Use this template:
Subject: Deposit Not Credited – [TXID]
Hello,
I made a deposit that is confirmed on the blockchain but has not been credited to my account.
TXID: [paste transaction hash]
Amount: [amount] [asset] (e.g., 1,000 USDT)
Network: [TRC20 / ERC20 / BEP20]
Deposit Address: [address used]
Memo/Tag: [if applicable]
Screenshot: [attach explorer screenshot]
Please investigate and credit my account. Thank you.
If the first support response is generic or unhelpful, politely ask for escalation to a supervisor or the technical team. Provide your ticket number and reference the TXID again. Persistence and clear documentation are key.
📋 Manual Credit: How It Works
In many cases, support can manually credit your deposit once they verify the on-chain transaction. Here's what happens:
Manual credit is common when:
- The automated system failed due to a technical glitch.
- A memo was required but missing (support can manually attribute the funds).
- The deposit was flagged for compliance review and cleared.
Manual credit can take anywhere from 1 hour to 48 hours depending on the platform's workload and the complexity of the issue. Most simple cases are resolved within 24 hours.
🛡️ Preventing Deposit Credit Issues
While not all delays are avoidable, these best practices can minimize the risk:
If the platform provides a memo or destination tag, include it exactly. This is the most common cause of manual credit delays.
Ensure the network matches the deposit address. TRC20, ERC20, and BEP20 are not interchangeable.
For large amounts, send a small test first. Confirm it's credited before sending the full amount.
Before depositing, check the platform's status page or announcements for any maintenance or known issues.
⚖️ Deposit Not Credited vs. Missing Deposit
These two issues are often confused, but they require different approaches. Here's a clear breakdown:
🔴 Missing Deposit
- Transaction is pending or unconfirmed on-chain.
- Network congestion, low fee, or node issues.
- Transaction may not have been broadcast.
- Check mempool and wait for confirmations.
- May need to replace or accelerate the transaction.
🟡 Deposit Not Credited
- Transaction is confirmed (Success) on-chain.
- Platform's internal systems haven't credited.
- Usually a platform-side issue (delay, glitch, review).
- Contact support with TXID for manual credit.
- Resolution involves support intervention.
If the blockchain explorer shows Success, the issue is with the receiving platform. If it shows Pending or doesn't exist, the issue is with the transaction itself.