What a failed swap leaves behind and how to recover it

A cryptocurrency swap is not a single transaction. It is a chain of events: you send funds, the exchanger receives them, it checks the amount against a quote, it sends the output to your destination address, and the destination network confirms that output. A failure can happen at any link in that chain. Understanding which link broke tells you whether you can recover anything at all.

When you request a swap on this site, the system generates a unique deposit address and a fixed quote valid for a short window. You send your coins to that address. The exchanger monitors the blockchain for the transaction. Once it sees enough confirmations on the sending network, it processes the swap and broadcasts the output transaction to the receiving network. That output goes to the address you provided.

Most of what people call "failed swaps" are not failures. They are delays. The question Why did my swap get stuck on confirming and how long should I wait comes up constantly. The answer depends on which network you used. Bitcoin requires more confirmations than Solana. The system waits for a safe number of blocks before it treats your deposit as final. That wait can be minutes or hours. If the output network is congested, the swap can appear stuck even after the deposit is confirmed. The swap is still moving. Check the transaction IDs on both block explorers before concluding anything is broken.

A real failure occurs when the deposit arrives but does not match the quote. The most common version: What happens if I send less crypto than the swap quote required. The quote is a specific amount. If you send less, the exchanger sees a deposit that is below the minimum threshold for processing. It will not execute the swap. It will hold the funds. The system can issue a refund, but the refund itself is a transaction with its own fee. That fee comes out of the deposit. If the deposit was small enough, the fee can eat the entire amount. You can recover nothing. Sending exactly the quoted amount, or more, avoids this entirely.

A worse version of the same problem: My swap went below the minimum amount after fees were taken. Network fees are deducted from the deposit before the exchanger counts it. If you sent exactly the minimum, the fee deduction can push the net deposit below the threshold. The swap will not process. The system will attempt a refund. Again, the refund fee may leave nothing. The only safeguard is to send more than the minimum, enough to absorb the fee and still clear the bar.

Two other deposit errors are harder to fix. I sent two deposits to the same swap address by mistake. The swap address is single-use. It expects exactly one deposit. A second deposit to the same address creates a surplus. The exchanger sees a single deposit with too much value. It may process the swap using the combined amount, but the output will be based on the quoted rate for the first deposit only. The extra coins are not swapped. They become stuck. Recovery is possible but requires a manual refund of the surplus. That takes time and requires you to prove ownership of the sending address. If you do not have that proof, the surplus is lost.

I deposited after the swap timer expired and the rate changed. The quote has a timer. Once it expires, the rate is no longer valid. If you send funds anyway, the exchanger receives a deposit with no active swap order. It holds the funds. You must contact support to trigger a refund. The refund will be at the prevailing rate when the deposit was received, not the expired quote. You may get back less than you expected. The system cannot honor a rate that is gone.

If the swap fails after the deposit, the question is Who actually controls the refund when a swap does not complete. The exchanger controls it. The deposit address is a wallet it manages. When a swap fails to execute, the system evaluates whether conditions for a refund are met. If they are, it builds a refund transaction and broadcasts it. No human touches it. The process is automated. That automation has rules. If the deposit is below the refund threshold, the automation will not act. The funds stay in the exchanger wallet. There is no third party who can override the rules.

The automation also sets the timing. How long does a failed swap refund usually take to arrive. The refund is a new transaction on the sending network. It takes as long as that network requires to confirm. Bitcoin refunds can take an hour. Solana refunds take seconds. The system does not control the network. If the network is congested, the refund sits in the mempool. It will confirm eventually unless the fee is too low. The system sets a reasonable fee. You can check the refund transaction ID to watch it progress.

When you need help, the first step is gathering data. What information do I need to give support to trace a missing swap. You need the deposit transaction ID, the destination address you entered, the exact amount sent, and the time you initiated the swap. Without those, support has nothing to search. The system logs every swap by the deposit transaction ID. If you do not have it, support cannot find your swap. That ID is the key. Keep it before you close any browser tabs.

Some things cannot be undone. If you sent to the wrong destination address, the swap executes and delivers coins to that address. The exchanger cannot reverse that. If you sent on the wrong network, the deposit never arrives. Those coins are gone. The system only sees what lands in the deposit address. Everything else is outside its reach.

The page you are reading sits above a live exchange form. You are here because you want to swap. The information above is what you should know before you click. Every link on this page leads to a deeper explanation of a specific problem. Read the one that matches your situation. If you are starting fresh, the most useful thing you can do is send more than the minimum and keep your transaction IDs. Everything else is recovery.