What happens when you send a token directly to a swap service on the wrong network

05 September 2026

The token disappears. You do not receive the intended asset on the other chain, and recovering the lost funds is either impossible or requires a costly, time-consuming process that the swap service is not obligated to perform.

Here is why. A swap service that moves assets across chains does not hold a single wallet that works on every network. Instead, it maintains separate deposit addresses for each supported chain. When you send a token to, say, an Ethereum deposit address over the BNB Smart Chain network, the transaction completes on BNB Smart Chain. The swap service’s monitoring software is watching only the Ethereum address. It never sees the incoming transfer. The tokens arrive at a wallet the service does not control for that network, or that it controls but does not monitor for incoming swaps.

The result is a stranded transaction. The tokens sit on the wrong chain in a wallet that either belongs to the service but is not linked to its swap logic, or belongs to a different user entirely. In the first case, the service may eventually notice the balance. Recovery then depends on its policies. Some services will manually retrieve the tokens and complete the swap, but they will charge a fee for the extra work. Others will refuse, citing the irreversible nature of blockchain transactions and the fact that the error was yours. In the second case, where the deposit address maps to another user's account on the wrong network, recovery is effectively impossible.

The mechanism behind this is straightforward. Each blockchain uses a different address format or the same format but a different network identifier. Ethereum and BNB Smart Chain, for example, share the same address format. A user can copy an Ethereum address and paste it into a BNB Smart Chain transaction. The transaction goes through because the address is valid on both networks. The swap service’s software, however, is programmed to recognise only deposits on the specific chain it is configured for. A deposit on BNB Smart Chain to an Ethereum address is simply invisible to the swap engine.

Prevention is simple but requires care. Before sending any token to a swap service, confirm that the network displayed in the swap interface matches the network you are using in your wallet. Most swap interfaces show the target network explicitly. If yours does not, do not proceed. Also verify the deposit address is for the correct chain. Some services generate a different address for each network, even if the address format is the same.

If you have already sent tokens to the wrong network, contact the swap service’s support immediately. Provide the transaction hash, the sending address, the intended destination, and the network used. Some services will help, but none are required to. The longer you wait, the less likely recovery becomes.

This scenario is one of the risks of swapping crypto across chains without a bridge or a centralised account. The hub page that covers that subject in full explains the trade-offs and the mechanics of the alternative methods. Reading it will help you avoid this kind of mistake.

Back to wrapped assets