When transferring native tokens from a Smart Account (smart contract wallet) to a centralized exchange (CEX), your deposit may not always be automatically detected and credited to your exchange account.
This is a known compatibility issue affecting certain centralized exchanges and is not specific to Ambire Wallet.
Why does this happen?
Some centralized exchanges do not properly detect internal transactions (smart contract calls) used to transfer native tokens from Smart Accounts. Unlike regular transactions initiated by externally owned accounts (EOAs), Smart Accounts can transfer native tokens through smart contract execution.
Although the funds are successfully transferred on the blockchain and received at the exchange's deposit address, the exchange's deposit monitoring system may fail to recognize the transfer and credit your account.
This issue may affect native tokens such as ETH, BNB, AVAX, and other native network currencies.
Important: This issue concerns native token transfers. Standard ERC-20 token transfers are generally detected correctly, even when sent from Smart Accounts.
Which wallet types may be affected?
The issue primarily affects Smart Accounts (smart contract wallets), including:
Ambire Wallet v1 accounts (legacy Web Wallet accounts)
Ambire Wallet v2 accounts (created with the browser extension or the new mobile app)
Safe accounts and other smart contract wallets
Regular EOA wallets are generally not affected, even when using EIP-7702 delegation (Smarter EOAs), provided the native token transfer is executed as a standard EOA transaction rather than through a smart contract call.
The key difference is how the transaction is executed, rather than which wallet application is being used.
Which exchanges are affected?
This issue has been reported with several major centralized exchanges, including Binance, Coinbase, HTX, KuCoin, Gate.io, and others.
However, exchange support and deposit detection mechanisms may change over time. Not all deposits to these exchanges will necessarily be affected.
We recommend confirming that your exchange supports native token deposits originating from smart contract wallets before making a transfer.
What should I do if my deposit is not credited?
If you've sent native tokens from your Smart Account to a centralized exchange and the deposit hasn't appeared in your exchange balance:
Verify the transaction: Check the transaction on the relevant blockchain explorer and confirm that it was successful and the funds reached the correct deposit address.
Contact the exchange's support team: Explain that the deposit originated from a smart contract wallet and may have been processed as an internal transaction.
Provide the transaction details: Share the transaction hash, network, token, amount, and receiving address to help the exchange locate your deposit.
Contact Ambire Support: If you need additional assistance, reach out to our support team and share your exchange support ticket.
In most cases, the issue is not with the blockchain transfer itself but with the exchange's ability to detect and credit it. The exchange must investigate and manually credit or recover the deposit where possible.
How can I avoid this issue?
Before sending native tokens from a Smart Account to a centralized exchange, make sure the exchange supports deposits originating from smart contract wallets and internal transactions.
If you're unsure, contact the exchange's support team before transferring your funds.
You can also consider using a regular EOA wallet as an intermediary, transferring your native tokens there first and then sending them to the exchange through a standard EOA transaction.
Note: Always verify the supported network, token, and deposit address before making a transfer. Successfully transferring funds on-chain does not guarantee that a centralized exchange will automatically credit the deposit.