What happens if I send SOL from an exchange to a swap address that expects a wallet

05 September 2026

The transaction will fail, and you will lose the SOL. The exchange's withdrawal system will send the funds to the address you provided, but the swap service's receiving address is not designed to hold or forward tokens - it is a temporary routing address that only works when paired with a return wallet address from the same session.

Here is why that happens.

A swap service that moves SOL between chains does not operate like a personal wallet. When you begin a swap on the exchanger, the system generates a unique deposit address for that specific transaction. That address is linked in its backend to the return wallet address you provided. The exchanger's software monitors that deposit address for an incoming transaction. When it detects one, it reads the amount, executes the cross-chain swap, and sends the output to the linked return address.

The critical detail is that the deposit address is ephemeral. It exists only for the duration of that swap session. It has no private key held by the exchanger for general use. It is not a wallet you can send funds to and then later retrieve. It is a listening post. If you send SOL to that address without having initiated a swap session that generated it, or if you send SOL to an address that was generated for a different session that has already expired, the exchanger's software will not be watching for it. The SOL arrives on the Solana blockchain, but no process claims it and no process forwards it.

Sending from an exchange compounds the problem. When you withdraw from an exchange, you typically enter a destination address and confirm. The exchange's system broadcasts the transaction to the Solana network. If the address you entered was a swap deposit address from a session that is still active, the swap service will see the incoming SOL and attempt to process the swap. But if the address is from an expired session, or if you simply typed an address that belongs to the swap service's infrastructure but did not start a swap, the funds land in an address that has no corresponding swap order. The exchanger has no obligation to monitor that address indefinitely. Some services sweep unclaimed funds after a period, but many do not, and none guarantee recovery.

There is a second scenario. Some swap services use a single receiving address for all incoming swaps, then rely on a memo or destination tag to identify which user sent what. If the exchanger uses this model, sending SOL from an exchange without including the correct memo will also cause the funds to go unclaimed. The exchange may not support memos for Solana withdrawals, or you may forget to enter it. The SOL arrives at the main address, but the exchanger cannot tell which return wallet it belongs to. The funds become stuck.

The safest approach is to always initiate the swap on the exchanger first, copy the deposit address and any required memo directly from the swap interface, and paste them into the exchange's withdrawal form without editing. Never reuse an old deposit address. Never send funds to a swap address from an exchange unless you have an active swap session open on the exchanger that is waiting for that exact deposit.

If you want to understand how the full process works - including why swap rates differ from a DEX and how to choose the right receiving network - read the hub page titled "Using an exchanger to bridge Solana assets across chains." It covers the overall workflow and the trade-offs involved.

Back to layer 2s