How to Troubleshoot Missing AAVE Deposits to Binance?
If your AAVE deposit to Binance does not show up in your account, the core check point is to confirm whether you selected the ERC20 (Ethereum mainnet) network when initiating the transfer. Currently, Binance only officially supports AAVE deposits via the ERC20 network. Although AAVE itself is an ERC-20 token, it is also deployed on other chains such as Polygon. Many users mistakenly use other networks for lower transaction fees, which will lead to funds not being credited automatically if you select an unsupported network.
Confirm the Network You Selected for the AAVE Transfer is ERC20
Goal: Go back to the platform you sent AAVE from (your crypto wallet or other exchange) and verify the network you chose when you initiated the withdrawal.
Steps to follow:
Open your wallet or withdrawal history page to check the network used for this AAVE transaction.
Scenario A: You used the Ethereum (ERC20) network. This is the official mainnet for AAVE. If the transaction status shows Success on-chain but the funds have not arrived in your Binance account, proceed to the following troubleshooting steps. The official ERC20 contract address of AAVE is 0x7Fc66500c84A76Ad7e9c93437bFc5Ac33E2DDaE9.
Scenario B: You used other networks such as Polygon or Solana. Binance does not currently support receiving AAVE deposits via the Polygon network, so your funds will most likely not be credited automatically if you used an unsupported chain.
Completion Check: You have confirmed clearly whether this transfer was sent via the ERC20 network or another blockchain network.
Prerequisite: You are able to log in to the platform you sent the AAVE from to view transaction records.
Common Failure Cause: Users often choose networks like Polygon for their lower transaction fees, leading to failed Binance deposits. AAVE is an ERC-20 token but has deployments on multiple chains including Polygon, and AAVE tokens on different networks are treated as separate assets.
Retrieve the TxID From the Sending Platform
Goal: Copy the TxID (transaction hash) of this transfer to check its on-chain status.
Steps to follow:
Withdrawing from an exchange: Log in to the withdrawal platform, go to the withdrawal history page, locate the AAVE transfer, and copy its TxID.
Withdrawing from an on-chain wallet: Open your wallet, find the transaction record for this AAVE transfer, and copy its TxID.
A TxID is a 64-character hexadecimal string that starts with 0x.
Completion Check: You have successfully obtained the TxID of the target transaction.
Prerequisite: You can access and log in to the sending platform normally.
Common Failure Cause: If the sending platform shows "Processing" instead of "Completed", the transaction has not been confirmed on the blockchain yet. Wait until the status changes to "Completed" before proceeding with checks.
Check Transaction Status on the Corresponding Blockchain Explorer
Goal: Use the obtained TxID to look up the real on-chain status of this transfer on the matching blockchain explorer.
Steps to follow:
If you used the ERC20 (Ethereum) network: Open Etherscan (etherscan.io), paste the TxID, and confirm the following details:
Status: Must show Success
Token: Confirm the token transferred is AAVE, with the contract address
0x7Fc66500c84A76Ad7e9c93437bFc5Ac33E2DDaE9
If you used other networks:
Polygon network → Use Polygonscan (polygonscan.com)
BSC network → Use BscScan (bscscan.com)
Completion Check: You have confirmed that the transaction status displays "Success" on the corresponding blockchain explorer.
Prerequisite: You have already obtained the TxID of the transaction.
Common Failure Cause: AAVE is deployed on multiple blockchains, so if you use the wrong blockchain explorer, the transaction will not be found in search results.
Use Binance's Self-Service Recovery Channel If Deposit Still Missing
Goal: If the transaction shows Success on-chain but the funds are not in your Binance account, and you have confirmed you selected the correct ERC20 network, you can submit an application via Binance's self-service recovery feature. This is for cases where the transaction is fully confirmed on-chain but the deposit has not arrived after 1 hour.
Steps to follow:
Per Binance's official guidelines, the self-service recovery feature applies to cases that meet the following conditions:
The on-chain transaction status must be "Confirmed/Success".
If your transaction has Memo/Tag related issues, you can also submit a request via this channel (AAVE transfers usually do not require a Memo/Tag).
Operation steps:
Locate the "Self-Service Recovery for Unreceived Deposits" application entry in the Binance Help Center.
Paste the TxID, the system will automatically fill in information such as the token name, network, and deposit address where possible.
Confirm all information is correct and submit your application.
Check the processing status in the "Application Records" section.
If the self-service recovery channel cannot process your request, contact Binance customer support and provide the following information:
Your Binance account email address
Token name (AAVE)
Deposit amount
TxID of the transaction
The network you selected for the transfer
Completion Check: Your application is submitted successfully, and you get a ticket number or application record for follow-up.
Prerequisite: You have already confirmed the on-chain transaction status is Success.
Warning: If you sent the AAVE via the Polygon network which Binance does not support for AAVE deposits, you can still submit a request via the self-service recovery channel, but whether the funds can be recovered depends on Binance's technical feasibility assessment.
