Why some failed swaps get an automatic refund and others need a support ticket

07 September 2026

The difference comes down to whether the swap provider's software can detect the failure and locate your funds without human intervention. If it can, you get an automatic refund. If it cannot, the system logs the issue for manual review, and you must open a support ticket.

Automatic refunds happen when the failure occurs at a predictable step in the swap process. The most common scenario is a trade that never reaches the exchange stage. In that case, the provider's software still holds your deposit in an address it controls. It can verify the deposit arrived, see that no outgoing transaction was ever initiated, and simply return the coins to your sending address. The entire process is deterministic - no ambiguity, no missing information. The refund usually appears within minutes to a few hours, depending on blockchain confirmation requirements.

Another case that triggers an automatic refund is when the swap executes on the exchange side but the outgoing transaction to your wallet fails due to a network error or insufficient gas. The provider's system can see the exchange output was not forwarded to you. It can pull those funds back from the exchange balance and try again or issue a return. Again, the funds are in a known location, and the software has the keys to move them.

Support tickets become necessary when the failure is messy or incomplete. For example, if you sent the deposit to the wrong address, or if the deposit amount was below the minimum, the provider's system may have no instructions for that specific input. It might log the transaction as "unrecognized" and flag it for a human operator. Similarly, if the swap partially processed - say, one of two tokens in a multi-leg trade was swapped but the second leg failed - the system may not have a safe automated path to reverse the partial result. Deciding what to return, and to whom, requires someone to inspect the chain state and manually construct a refund transaction.

The hub page "What your wallet signs during a failed swap" explains exactly what the cryptographic evidence looks like in each scenario. That page is worth reading if you want to understand how a support agent verifies your claim based on transaction hashes and signed messages rather than just your word.

A third situation that demands a ticket is when the swap site itself went offline mid-process. The automated refund timer never started because the server never acknowledged the deposit. When it comes back, the system may need to reconcile a backlog of unprocessed orders. Humans have to match deposits to pending swaps and decide who gets refunded first. This can take days, not hours.

Finally, some providers set a threshold for automatic refunds. If the deposit value is very small, the cost of the refund transaction might exceed the deposit itself. Rather than lose money on every tiny swap, they program the system to skip automatic refunds below that threshold and instead batch those cases for periodic manual review. The threshold is rarely published, but it is typically in the single-digit dollar range.

The guiding principle is simple: if the software can unambiguously identify your funds and has a clear path to return them, it will. If the path is blocked, unknown, or would require a decision the software is not trusted to make, the case goes to a human. That human works through a queue. Opening a ticket puts you in that queue.

Back to wallet security