Why was my crypto deposit rejected or returned?
If your crypto deposit was rejected or returned, don’t worry, this usually happens when a deposit does not meet the technical requirements of the receiving wallet. Common causes include unsupported networks, incorrect token types, or missing deposit details.
Crypto deposits must follow strict blockchain rules to be credited correctly. Before troubleshooting, it’s helpful to review:
Common reasons your crypto deposit was rejected or returned
Unsupported or incorrect blockchain network
Crypto deposits must be sent using a supported blockchain network. If you send a deposit on an unsupported or incorrect network, the system may reject it or fail to credit it.
For example
- •You sent USDT on BEP20
- •Your Raseed deposit address supports USDT on ERC20 only
In this case, the deposit may be rejected, returned, or not credited automatically. Always confirm that both the crypto asset and the network match exactly before sending.
Deposit sent to an incorrect wallet address
Blockchain transactions are irreversible. If a deposit is sent to:
- •The wrong wallet address
- •An old or expired address
- •An address not associated with your Raseed account
The blockchain may still confirm the transaction, but the funds will not reach your Raseed wallet.
To avoid this, always copy the deposit address directly from your Raseed app
immediately before sending.
Missing or incorrect Memo / Tag (when required)
Some cryptocurrencies require an additional identifier to route deposits correctly, such as a:
- •Memo
- •Tag
- •Destination Tag
- •Payment ID
If this information is missing or incorrect, the deposit may be rejected, held, or returned, even if the transaction is successful on-chain. If your deposit screen shows a Memo or Tag field, it must be included exactly as shown.
Non-standard or smart contract deposits
Some crypto deposits may not be supported if they were sent via:
- •Smart contract interactions
- •Contract call transfers
- •DeFi protocols
- •Cross-chain bridges
- •Token swaps sent directly to a wallet address
These transactions may not be recognized as standard wallet-to-wallet deposits and can result in rejection. For best results, always send deposits using a standard wallet transfer, not through automated contracts or protocols.
Security, risk, or compliance checks
In some cases, a deposit may be rejected due to internal security or compliance screening, such as:
- •Risk monitoring alerts
- •Blocked or sanctioned addresses
- •Restricted jurisdictions
- •Suspicious transaction patterns
If this happens, Raseed Support may request your transaction hash (TXID) for further review.
What should I do if my deposit was rejected or returned?
Step 1: Verify the transaction on the blockchain
Use your TXID / transaction hash to confirm:
- •Whether the transaction was successful
- •Which blockchain network was used
- •Which crypto asset or token was sent
- •The destination wallet address
This helps determine whether the issue occurred before or after blockchain confirmation.
Step 2: Re-check your deposit details in Raseed
Confirm the following carefully:
- •Correct crypto asset (e.g., USDT vs USDC)
- •Correct blockchain network (ERC20, TRC20, etc.
- •Correct deposit address
- •Memo or Tag included (if required)
Many rejected deposits happen due to small mismatches in these details.
Step 3: Contact Raseed Support (if needed)
If you’re still unsure why the deposit was rejected or returned, contact Raseed Support and provide:
- •TXID / transaction hash
- •Crypto asset name
- •Network used
- •Deposit amount
- •Date and time of transfer
This allows the team to investigate whether the deposit can be reviewed or recovered.
Important reminder
Crypto transactions are processed directly on the blockchain and cannot be reversed once sent. To reduce the risk of rejected deposits, always verify:
- •Correct coin
- •Correct network
- •Correct address
- •Memo or Tag (when required)