Sent Crypto on the Wrong Network to Binance.US? How Deposit Recovery Works

If crypto you sent to Binance.US never showed up, its Deposit Recovery Tool can find and return some missing deposits without you having to contact support. Binance.US says processing typically takes a few business days, and it charges a 5% processing fee. The tool helps when a deposit was sent without a memo, with the wrong deposit details, or during network problems. It can’t recover unsupported tokens, supported tokens sent on a network Binance.US doesn’t support, transfers from smart contracts or bridges, or crypto sent to an address Binance.US doesn’t own.

This guide shows what can and can’t be recovered, how to use the tool, why requests get rejected, and how to avoid wrong-network deposits. It’s based on Binance.US’s help center and terms, checked on October 2, 2026.

What Binance.US can and can’t recover

Binance.US’s pages aren’t fully consistent about unsupported tokens. The recovery article says newly listed assets “will become available to recover,” but other help pages and its terms say Binance.US can’t recover unsupported assets and has no responsibility to try. Don’t count on an unsupported token ever coming back.

How to use the Binance.US Deposit Recovery Tool

Before you start, have these ready:

• the transaction ID (TxID or hash) of the deposit, found in the transaction history of the wallet or exchange you sent from
• a screenshot of the transaction from that wallet or exchange (Binance.US rejects block explorer screenshots)
• confirmation that the network you used is supported by Binance.US for that coin

How much Binance.US deposit recovery costs

Binance.US charges a 5% processing fee and deducts it from the deposit before returning it. On a $1,000 USDC deposit, for example, you’d get back $950 worth of USDC. The fee is shown on the Confirm Details screen before you accept.

The help center ties the 5% fee to deposits sent without a memo, while the tool’s own page says it returns deposits “for a 5% processing fee” without that limit. Binance.US doesn’t publish a minimum amount or a maximum processing time beyond “a few business days.”

Why Binance.US rejects recovery requests

Binance.US lists these reasons:

• the deposit was already credited, often after network maintenance ended
• the token, or the network it was sent on, isn’t supported
• the transaction wasn’t sent to a Binance.US address
• your account isn’t advanced verified (required for deposits sent without a memo)
• the details were entered incorrectly, for example a block explorer link instead of the transaction hash, the wrong token or network, a non-Binance.US address, or the USD or USDT value instead of the actual token amount
• the supporting screenshot came from a public block explorer instead of the wallet or exchange you sent from

Which networks Binance.US supports for popular coins

According to Binance.US’s listings page (updated September 9, 2026):

These lists change. In the Binance.US app, supported networks for a coin appear in the drop-down menu directly above your deposit address; if a network isn’t listed there, don’t use it.

These coins need a memo as well as an address: Band Protocol (BAND), Cosmos (ATOM), Fetch.ai (FET), Hedera (HBAR), IOST, Kava (KAVA), Polymesh (POLYX), Stellar (XLM), WAX (WAXP), and XRP. Other wallets may call the memo a tag, tag name, digital ID, label, or note. Binance.US uses a limited number of shared deposit addresses for coins like XRP, which is why the memo matters.

Deposits sent during network maintenance

Binance.US’s recovery page says deposits affected by network maintenance are credited automatically once the maintenance ends, so you don’t need a recovery case. Some maintenance notices say otherwise, though. Binance.US’s notice for wallet maintenance on March 19, 2026 said deposits made during the upgrade “will NOT be credited” and would be lost, and a May 2026 notice said deposits of four tokens on networks it was dropping wouldn’t be credited.

Before you send, check binance.us/status (opens in a new tab) and Binance.US’s announcements, and don’t send while a coin’s network is under maintenance.

Retired Binance.US deposit addresses

Binance.US changed its deposit addresses for more than 30 networks in 2026, and it warns that crypto sent to an old address may be permanently lost. For Chiliz (CHZ), for example, the network now appears as CHZ2, and CHZ sent to a retired address after October 14, 2026 can’t be recovered. If you’ve saved your Binance.US address in another wallet or exchange, copy the current one from the Binance.US app or website instead.

How to avoid wrong-network deposits

• Check Binance.US’s supported coins and networks before you send anything.
• Copy the deposit address from the official Binance.US app or website each time.
• Pick the same network on both sides of the transfer.
• Add the memo or tag for coins that need one.
• Send a small test first for large amounts. Binance.US’s own terms recommend test deposits when you’re unsure whether a coin is supported.
• Don’t send bridged or wrapped tokens, or transfers from smart contracts or cross-chain swaps, unless Binance.US lists that exact token on that exact network.

Crypto deposits to Binance.US are free.

Can Binance.US reverse a withdrawal?

No. Binance.US says the moment crypto leaves your account, the transaction can’t be canceled or reversed, and its recovery tool doesn’t cover withdrawals. If you sent crypto from Binance.US to the wrong place, contact the support team of the wallet or exchange that received it. If it went to an address nobody controls, it’s gone.

Beware of recovery scams

If you’ve lost crypto to a scam, Binance.US says to contact its support team and report the case to the FBI’s Internet Crime Complaint Center (IC3) (opens in a new tab). Our guide to where to report a scam lists other places to report it.

Related Binance.US problems

• Your withdrawal is stuck: Binance.US withdrawal pending or on hold
• Your account is restricted: Binance.US account restricted
• Check whether your state is supported: Binance.US available states