Why do cross-chain swaps ask for a return address before you send anything

05 September 2026

They ask for a return address because they cannot guarantee a swap will complete, and if it fails they need somewhere to send your original tokens back. The return address is a fallback, not a forwarding address.

The logic is straightforward but often misunderstood. When you initiate a cross-chain swap - getting an asset from one chain to another without a bridge or a centralised account - you are not sending tokens to an exchange that holds them for you. You are sending them to a contract or a service that will attempt to convert and relay them to a different blockchain. That process can fail at several points.

Why failure is possible

Cross-chain swaps are not atomic. On a single chain, a swap can be designed so that either everything happens or nothing does. Across chains, no such guarantee exists. Your tokens leave chain A, but the corresponding tokens on chain B might not arrive. Reasons include:

• Network congestion on either chain.
• Insufficient gas on the destination chain.
• A price move that makes the swap uneconomical for the provider mid-execution.
• A bug or misconfiguration in the swap contract.

The provider has your tokens. If the swap cannot finish, they need to return them. Without a return address, they would be stuck holding funds they did not intend to keep, and you would have lost them.

What the return address is not

It is not a forwarding address. It is not where the swapped tokens will be delivered. That destination is usually specified in a separate field (often labelled "destination address" or "recipient"). The return address only matters if something goes wrong.

It is also not proof that a swap will succeed. Some users assume that providing a return address is a form of guarantee - that the service is "covering" them. It is not. It is simply a technical requirement for error handling.

How the service uses it

When you submit a swap request with a return address, the service typically stores it alongside the transaction details. If the swap completes normally, the return address is never used. If the swap fails - say, the destination chain transaction reverts - the service will initiate a separate transaction sending the original tokens back to that address.

This means the return address must be on the same chain as the tokens you are sending. If you send Ethereum tokens and provide a Bitcoin return address, the service cannot return them. They would remain stuck.

Why they ask before you send

They ask upfront because they need to associate the return address with your swap before they receive the funds. Once the tokens arrive, the service has limited time to react. Asking for the return address ahead of time lets them automate the fallback without manual intervention. It also prevents a scenario where a user sends tokens without including a return address, leaving no way to recover from a failure.

Some services allow you to omit the return address, effectively accepting the risk that a failed swap means a lost deposit. Most do not, because it creates customer support problems.

What to check

A legitimate service will not ask for a return address that matches the destination address unless you intend to receive the swapped tokens at the same wallet. If the service asks for a single address and claims it will serve as both the return and the destination, be cautious. That design is possible but unusual, and it removes the distinction between a refund path and a delivery path.

If you are unsure, the hub page "Swapping crypto across chains" explains the broader flow and where these addresses fit into the process.

In short

The return address exists because cross-chain swaps can break. The service asks for it before you send to ensure they can give your tokens back if needed. It is a practical safeguard, not a promise that the swap will work.

Back to wrapped assets