Sent Crypto on the Wrong Network? Which Transfers Can Actually Be Recovered?

Crypto sent on the wrong network can sometimes be recovered. Your options depend on who controls the receiving address, whether they can use it on that network, and which token arrived.

A successful transaction means the blockchain processed it. It does not prove that an exchange credited your account or that the recipient can spend the funds. Recovery starts with finding the actual token transfer and identifying who can move those tokens.

Find your recovery route

• Your own wallet: Often recoverable when the funds reached an ordinary account you control on a compatible network. A smart wallet needs a separate check.
• An exchange: Recovery depends on the receiving exchange's tools, custody system, and policy for that exact token and network. Only the exchange can handle its deposit address.
• Another person: They must be able and willing to return the funds. If they gave you an exchange deposit address, they need to contact that exchange.
• A smart contract: Recovery depends on the contract's code and authorized operators. Some contracts can return tokens; others cannot.

The key question is: who can authorize a transfer from the receiving address on the network actually used? An address showing a balance is not enough.

Before attempting recovery, check the transaction

1. Check whether the transfer has actually happened

Open the withdrawal or sending record and copy the blockchain transaction ID, also called the TxID or transaction hash. An exchange's internal withdrawal ID may be different.

• No blockchain transaction yet: The withdrawal may still be inside the sending platform. Check whether it can be canceled and contact that platform immediately.
• Pending on the blockchain: Some wallets can attempt to replace or cancel an unconfirmed transaction. Use the wallet's official instructions. Success is not guaranteed, and speeding up the mistaken transfer would make the problem worse.
• Failed or reverted: Investigate the failure and the sender's balance. This is different from a successful deposit on the wrong network. A failed Ethereum-style transaction can still cost a network fee.
• Confirmed successfully: There is no normal cancel or chargeback button. Recovery usually means making a new transfer from wherever the funds arrived.

2. Use the explorer for the network you actually selected

Check the network in the original withdrawal record, then open its blockchain explorer. For example, Ethereum transactions appear on Etherscan, BNB Smart Chain transactions on BscScan, and TRON transactions on TRONSCAN.

A transaction missing from Ethereum's explorer may simply have happened on BNB Smart Chain. Searching the intended network alone does not establish that the funds disappeared.

If you used a bridge, check its transfer status as well. A completed transaction on the starting network may be only one part of the transfer. Look for the destination transaction or any claim or refund step required by that bridge.

3. Find the actual token recipient

For USDT and other Ethereum-style tokens, open the transaction's token transfers section. Check the recipient, amount, and token contract there.

The main transaction field labeled To may show the contract that runs the token. This is normal: a token transfer calls that contract and tells it which address should receive the tokens. It does not, by itself, mean you sent your money to the token contract by mistake.

Also check what the transaction did. A successful token approval gives permission to spend tokens; it is not itself a payment. A transaction involving several contract calls may contain several transfers.

4. Verify the token and its current location

Record the full receiving address, actual network, amount, and token contract. Compare the contract with the token issuer's or receiving platform's official information for that network. A token name or logo can be copied.

Then check the receiving address's token balance and later transfers. The original transaction proves where the tokens arrived, but they may have moved since then.

If an exchange moved them into another wallet, that can be normal internal handling. It does not prove they were credited to your account. If an unexpected transfer leaves your own wallet, investigate possible compromise before adding more funds.

These checks use public information. You do not need to connect a wallet or reveal a recovery phrase to inspect an address.

Wrong network, unsupported token, and wrong address are different problems

Wrong or unsupported network

You intended to send USDT on Ethereum, but selected BNB Smart Chain. The transfer reached an address on BNB Smart Chain, and the receiving service may not support that chain.

On withdrawal screens, Ethereum (ERC20) commonly means Ethereum mainnet, while BNB Smart Chain (BEP20) means BNB Smart Chain. ERC20 and BEP20 describe token standards. Check the full network name rather than treating the standard alone as a destination.

An address beginning with 0x does not tell you which network to use. Several networks use that format and maintain separate balances.

Unsupported token on the correct network

The network and address may be correct, but the receiving platform does not accept the exact token contract you sent.

For example, native USDC and a bridged version of USDC can exist on the same network. Circle warns that bridged USDC on Arbitrum is not supported by Circle Mint and that mistaken deposits may not be recoverable. Accepting USDC on Arbitrum does not automatically mean accepting every token called USDC there.

USDT also has versions represented by bridges or other services. Do not assume every token bearing that name is issued directly by Tether or has the same recovery route.

Incorrect receiving address

You sent to a different address from the one you intended, perhaps an old copied address, a stranger's wallet, or a token contract.

Switching networks cannot give you control of that address. Recovery depends on the actual recipient or an applicable contract or issuer recovery process.

A missing memo or tag is another category. The funds may have reached the right shared exchange address without the information needed to identify your account. Use that exchange's memo or tag recovery process.

If the address, token, network, and required memo all match, check confirmation requirements, deposit minimums, and the receiving platform's deposit status. You may have a crediting delay rather than a wrong-network transfer.

1. The funds went to your own wallet

When an ordinary wallet account can recover them

Many networks use Ethereum-style accounts. These are often called EVM-compatible networks. For an ordinary account controlled directly by a private key, that same key normally controls the same address across those networks.

This is why a transfer to your own Ethereum-style address on BNB Smart Chain may be accessible even when your wallet initially shows nothing. The token balance exists on BNB Smart Chain; your app may be displaying Ethereum.

This applies to the exact account you control. It does not automatically apply to a smart wallet, an exchange address, or a different address created from the same recovery phrase.

How to check safely

1. Open the wallet that controls the receiving account. Compare its full address with the actual token recipient in the transaction.
2. Select the network used for the transfer. If it is missing, follow the wallet maker's instructions to enable it or add its official network settings.
3. Display the exact token. If it does not appear automatically, use the wallet's add-token function with the verified contract address for that network.
4. Check that the account can sign. A watch-only wallet can show anyone's balance. It cannot authorize a return transfer.
5. Plan the destination before sending. Confirm that the next wallet or exchange accepts this exact token on the network where you now hold it.
6. Arrange the network fee. For an ordinary BEP20 transfer on BNB Smart Chain, you normally need a little BNB on that chain. Use the wallet's estimate and leave enough for every required transaction.

Adding a network or token changes what the wallet displays. It does not move or convert the funds. Displaying a token also does not make a fake or unbacked token valuable.

Example: you sent BEP20 USDT instead of ERC20

You withdraw 500 USDT from an exchange to your ordinary personal wallet. You intended to use Ethereum but selected BNB Smart Chain.

The withdrawal record and BscScan show that the token transfer reached your exact wallet address. You open that account on BNB Smart Chain and display the verified token. The 500-token balance appears.

You now have access to the tokens on BNB Smart Chain. If you want the funds on Ethereum, you still need a supported transfer route between networks. Sending to your own address again while using BNB Smart Chain will leave them on BNB Smart Chain.

ETH held on Ethereum does not pay the fee for this BNB Smart Chain transfer. Gas must be available on the network processing the transaction, unless your wallet explicitly offers another supported payment method.

If another wallet app shows a different address

Stop and check the account selection. A recovery phrase can generate many accounts, and different apps can use different settings to choose them. Wallet documentation may call these settings a derivation path.

Restoring the same phrase and seeing an empty account does not prove the original balance is gone. It may mean you have opened a different account. Follow the original wallet maker's recovery instructions and verify the full destination address.

Do not enter the phrase into a website offering to search for the correct account.

If you use a hardware wallet

Check whether the device's normal app supports the network. If it does not, the maker may support connecting the device to another wallet interface.

For example, Trezor documents using a compatible third-party wallet through Trezor Connect to access assets on other supported EVM networks. The device still signs the transactions.

Use the hardware-wallet connection process and verify the selected account. Do not type the device's recovery phrase into a website or software wallet just to make the balance visible.

If your own wallet is a smart wallet

A smart wallet may use contract code to control its receiving address. Holding a recovery phrase, passkey, or signing key for the app does not necessarily let you send directly from that address on another network.

Ask the wallet provider whether the account is deployed and usable on the network you selected. If it is not, use the smart-contract section below. The ordinary network-switching steps may be insufficient.

2. The funds went to an exchange

Contact the receiving exchange. Your exchange deposit address is controlled by the exchange's custody system, even though it appears inside your account.

You cannot import that address into a personal wallet and gain control of it. Customer support also cannot simply give you its private key. Exchange recovery requires a process that works within the platform's custody and security systems.

The sending exchange can supply the withdrawal record and explain which network it used. Once a confirmed withdrawal reaches an outside address, the sender normally cannot pull it back.

Technical access and recovery eligibility are separate

An exchange may recognize an address but lack a supported way to move that token from it on the other network. It may also decline recoveries because of operational limits, security checks, or its service policy.

These are three different questions:

• Does the exchange control this address on the network actually used?
• Can its systems safely move this exact token?
• Will its recovery service accept this deposit?

An exchange listing a token for trading answers none of these questions by itself.

What current recovery services demonstrate

Binance: Its global recovery guide includes some unsupported tokens and deposits on unsupported EVM networks as potential recovery categories. It does not guarantee a result. The recipient applies for a deposit into their own Binance account.

Binance reported helping with 38,648 incorrect-deposit recovery cases totaling $48 million during 2025. Those figures cover deposit errors broadly, not only wrong networks. They do not tell you the success rate for your situation.

Coinbase: Its recovery service accepts only certain assets and networks and sends eligible recovered funds to a connected self-custody wallet. It requires the transaction ID, Coinbase receiving address, and actual network. Check the destination wallet carefully before confirming.

At the time of checking, Coinbase's service fee is 5% of the amount above $100, plus network fees. A $1,000 recovery therefore has a $45 service fee before network costs. The fee shown in the actual recovery process is what matters.

Kraken: Its recovery guidance separates unsupported tokens on supported networks from unlisted assets on unsupported networks. Some cases cannot be recovered, and the cost is communicated before recovery work proceeds.

Use the guidance for the exact platform and account you use. Binance and Binance.US have different recovery policies. Availability can also vary by account or region.

Exchange examples and recovery policies were checked on 18 October 2026. Eligibility, fees, and procedures can change.

What to ask the exchange

Open its official missing-deposit or asset-recovery process and provide the evidence listed later in this article. Ask whether it can recover the specific token contract on the specific network to the specific deposit address.

If a tool cannot locate the transaction, first check those details. A transaction that exists on a public explorer may still be outside that tool's supported cases. Ask support whether manual review exists.

Before accepting a recovery, confirm the fee, likely timing, and whether the result will be an account credit or an external refund. A fee estimate is not a guarantee. For a small deposit, the costs can consume much of the recovered amount.

If support declines, ask whether the reason is missing evidence, a technical limitation, or current policy. Keep the answer and transaction details. A future policy change is possible, but there is no promise that it will help an old deposit.

Do not let the refund become a second missing deposit

The original sending address may not be your deposit address. Exchanges often send withdrawals from shared operational wallets.

If the recovery sends tokens back to that shared wallet, the sending exchange may receive them without automatically crediting your account. Coinbase warns against returning a payment to its original sending address, and Kraken says returned withdrawals can require manual recovery.

Some recovery processes allow you to choose a receiving wallet. Others require a return to the original source. Ask which rule applies before proceeding.

• Which token will be returned?
• On which network?
• To which exact address?
• Will the receiving service accept that token and network?
• Is a memo or tag required?

If Exchange B refunds to Exchange A's shared sending wallet, ask Exchange A how it will credit the return. Keep the original and refund transaction IDs and both support records. Recovery is complete for you only when Exchange A identifies the return and credits your account.

3. The funds went to another person

If you sent to someone you know, give them the transaction ID, actual network, token contract, and receiving address.

If they control an ordinary compatible wallet account, they can check the balance on that network and arrange a new transfer. You do not need their recovery phrase, and they do not need yours.

If they gave you an exchange deposit address, the recipient normally needs to open the recovery request from their own account. Your withdrawal record may help, but you cannot manage their exchange account through your own recovery form.

For a merchant or payment processor, contact its payment support team. Include the invoice or payment reference as well as the transaction details. The visible address may belong to the processor rather than the merchant.

If the address belongs to an unknown person, there is no ordinary wallet function that forces a refund. A transaction hash cannot reveal the private key. An explorer label may suggest a service to contact, but it does not prove who controls the address.

Before anyone returns the funds, agree on a destination that accepts the exact token and network. Do not assume the original sending address is suitable.

4. The receiving address is a smart contract

A smart contract follows its programmed rules. The person or company that created it does not automatically have a way to withdraw every token sent there.

Why a successful transfer can still leave tokens stuck

A standard ERC20 transfer can record a balance under a contract's address without asking that contract whether it knows how to return the tokens. The transfer can succeed while the recipient has no usable withdrawal route.

Recovery may be possible if the contract has:

• A withdrawal or rescue function that works for the exact token.
• A general transaction function that authorized owners can use to send it.
• An existing upgrade mechanism through which authorized administrators can add a recovery route.

If none applies, the project team may be unable to help. A token issuer may have a separate intervention process in limited cases, but ordinary wallet settings cannot add missing contract functionality.

This includes sending tokens to the token contract itself. First confirm that the contract was the actual token recipient, rather than merely the main transaction's To address.

A smart wallet may be recoverable even if it does not exist on that chain yet

Some smart wallets have an address that can be calculated before their contract is created. Funds can arrive at that address on another network before the wallet has been deployed there.

The wallet provider may be able to create the correct wallet at that exact address and restore access. This depends on its original setup and on the required deployment contracts being compatible and available on the second network.

Safe documents this kind of recovery, but it is not possible for every Safe or every network.

A less obvious problem is the original signer list. Recreating a Safe on another network can restore its initial owners and required number of signatures. Later changes on the first network do not automatically carry over. If the original signing keys were lost or compromised, recovery may be blocked or unsafe.

Ask the provider to check the deployment and ownership history before proceeding. Creating a random new contract or wallet does not let you claim an arbitrary address.

What the project team needs to check

• Is the correct contract deployed at this address on the actual network?
• If not, can that exact wallet still be deployed there?
• Which owners or signers would control it?
• Does its code allow this exact token to be moved?
• Are the tokens still at the address?

An explorer showing no contract code is not conclusive. It might be an ordinary account, an unused address, or the future address of a smart wallet. A contract label also does not fully explain how an account is controlled. Use the wallet provider's documentation and a case-specific review.

Contact the official project team promptly. Some routing contracts are not designed to hold balances safely. Uniswap warns that tokens left at certain router addresses can be used by later transactions. Do not assume every contract deposit will remain available while you decide what to do.

What about TRC20, Bitcoin, Solana, or BEP2?

TRC20 instead of ERC20 needs a different assessment

The ordinary EVM recovery steps do not cover every combination of networks. TRON, Bitcoin, Solana, and other systems can use different address formats, account rules, or signing keys.

If a withdrawal form rejects the address, do not alter it to force the transfer. If the transfer already happened, identify the real receiving address from the blockchain record and ask the receiving wallet or platform to assess it.

Different address systems do not make every case impossible. TRON's developer documentation shows that, for the same public key, its address is related to an Ethereum address. However, the default TRON and Ethereum accounts from one recovery phrase may use different keys.

That is a reason to get an exact technical assessment, not a general recipe for converting addresses. Changing how an address is written does not move funds between networks or grant control of them.

BEP2 is not BEP20

BEP2 belongs to the retired BNB Beacon Chain, which uses addresses beginning with bnb1. BEP20 is associated with BNB Smart Chain and its Ethereum-style addresses.

Old BEP2 and BEP8 tokens have a separate recovery process, limited to eligible assets linked to a corresponding token on BNB Smart Chain. Since 1 July 2026, BNB Chain's hosted recovery tool has been discontinued in favor of a locally run self-service tool. Follow the current official instructions rather than an old guide to a retired tool.

Can Tether recover USDT sent on the wrong network?

Sometimes Tether can assess a recovery that the receiving wallet or contract cannot handle. This is a limited issuer service, not a universal USDT refund system.

Tether lists certain contract mistakes and other destinations it considers recoverable. It asks users to seek help from the receiving party first.

Its published conditions include:

• The request must exceed $1,000.
• You must qualify for Tether's services and become a verified user.
• Tether decides whether a recovery is technically feasible and whether to attempt it.
• Tether publishes a fee of up to 10% of the recovery amount or $1,000, whichever is greater. The fee is deducted from recovered funds. Confirm your actual quote before proceeding.
• A request can take months, with no guaranteed outcome or deadline.

Check who issued the exact token. A bridged or pegged version carrying the USDT name may depend on another service, so Tether's process may not apply.

Keep the transaction ID, destination, amount, explanation of the mistake, and records of previous recovery attempts. Provide addresses and transaction IDs as text, even if you also attach screenshots.

How to move accessible funds to the intended network

Once you can spend the funds, you may not need any further recovery service. You can keep them on the current network if that suits your needs. Moving them elsewhere is a separate decision.

If you need a different network, two possible routes are:

• An exchange that accepts the exact token on the current network: Deposit using the receiving details shown for that network, wait for the account credit, then withdraw using the intended network. Check both deposit and withdrawal availability before sending.
• A bridge that supports the exact transfer: Confirm the starting token, destination token, both networks, fees, and receiving address in the bridge's official interface.

A bridge needs access to the funds being sent. It cannot recover a balance from an exchange address or contract you cannot authorize.

Bridge outputs can be a different token version from the one your final recipient accepts. Check the destination contract before continuing. Follow the bridge's actual transfer process; sending tokens directly to a contract address may not initiate a bridge transfer.

Where practical, test a small amount first, while staying above any deposit or transfer minimum. Wait until that test is usable at the final destination. A blockchain confirmation alone does not establish that an exchange accepted it.

Evidence to prepare for a recovery request

Collect the following before opening a ticket:

• The blockchain transaction ID, copied as text.
• The network actually used and the network intended.
• The exact token contract on the actual network, plus its displayed name.
• The amount that reached the address, which may differ from the withdrawal amount after fees.
• The full sending and receiving addresses.
• The transfer date and time, including the time zone.
• The sending wallet or exchange, and the receiving wallet or platform.
• The recipient's account deposit instructions, including any required memo or tag.
• The withdrawal record from the originating wallet or exchange.
• Earlier ticket numbers, attempted fixes, and any refund transaction ID.

A public explorer record proves that a transaction exists. It does not prove that the person submitting it owns the funds. A platform may require account records, identity checks, or a video showing the withdrawal history.

Supply private account evidence only through official support channels. Keep passwords, recovery phrases, private keys, and authentication codes out of screenshots and recordings.

Copy this support-request template

Subject: Wrong-network deposit recovery request: [token], [actual network], [transaction ID]

I sent [amount and token] to [receiving address] on [actual network] at [date, time, and time zone]. I intended to use [intended network]. The blockchain shows [status], but [the deposit was not credited / the receiving wallet cannot access it].

• Transaction ID: [paste the full blockchain transaction ID]
• Token contract on the actual network: [paste the full contract address, or state that it was a native coin]
• Sending address and service: [address and wallet or exchange]
• Receiving address and account: [address and relevant account reference]
• Amount received on the blockchain: [amount]
• Memo or tag: [what was required and what was entered, or not applicable]
• Evidence attached: [withdrawal record and relevant deposit instructions]
• Previous recovery attempts: [brief description and ticket numbers]

Please confirm whether you control this address on the network used and whether this exact token is eligible for recovery. If it is, will you credit the account or issue a refund? Please confirm the fee, expected processing time, and the token, network, address, and memo requirements for any refund.

If the funds must return to the original sending address, please confirm this before proceeding so I can coordinate with the sending platform. If recovery is unavailable, please explain whether the reason is missing evidence, a technical limitation, or current policy.

When recovery may be impossible, and when to stop

A transfer can remain visible forever without anyone having a practical way to spend it. Common barriers include:

• No accessible controlling key: Nobody you can reach can authorize spending from the actual destination, or the necessary keys have been permanently lost.
• No usable contract route: The receiving contract cannot transfer the token, and there is no authorized upgrade, deployment, or issuer intervention available.
• No exchange recovery service: The platform cannot or will not recover that combination. This is a service limit, not necessarily proof of a mathematical impossibility.
• The funds were taken or spent: The original address no longer holds them. A theft or dispute needs a different response. Check later transfers first, since an exchange moving funds internally does not itself mean they are lost.
• The asset or network no longer works as needed: Access to an address cannot restore a failed token's backing, restart a retired chain, or create a missing redemption route.

Ask for the reason before accepting a vague claim that recovery is impossible. Equally, do not pay for repeated attempts that cannot identify a credible recovery mechanism.

Avoid losing more money during recovery

• Keep recovery phrases and private keys secret. They can expose other assets controlled by those keys, including assets on other networks. A recovery phrase can also expose other accounts derived from it.
• Open support from the platform's official app or website. Unsolicited messages and search ads offering guaranteed recovery are not proof of a real service.
• Understand what you sign. A legitimate process may request a wallet-ownership signature. A spending approval or account permission can authorize much more. Read the request and verify the service.
• Verify fees inside the official recovery process. Real services can charge fees. A stranger demanding a tax, activation deposit, or repeated release payments has not established a recovery route.
• Add gas only after confirming control. If fresh gas immediately leaves your wallet unexpectedly, stop topping it up and investigate a possible sweeper bot.
• Keep the final transfer plan specific. Confirm the token, network, address, and any memo again before sending or approving a refund.

Before a future transfer, start with the recipient's current deposit instructions, match the exact network and token, and verify the full address. When testing, wait for the recipient to confirm that the funds are actually usable before sending the rest.