What to do when a swap completes on the blockchain but the exchange says it failed

05 September 2026

You have already sent the funds, and the blockchain shows the transaction as confirmed. The exchange interface says the swap failed. Do not send more crypto. Contact support through the exchange’s official channel and provide the transaction ID.

This situation is more common than most users expect. It is not necessarily a sign of fraud. The mismatch usually happens because the exchange’s internal systems and the blockchain’s confirmation logic are not perfectly synchronized.

Why this happens

Exchanges process swaps in stages. They receive your deposit, check it against their internal records, and then release the swapped funds. When the blockchain confirms a transaction, the exchange’s node or API might not have updated its balance view yet. A brief delay can cause the interface to display "failed" even though the incoming transfer succeeded.

Another cause is a mempool issue. If you sent the transaction with a low network fee, the exchange might have seen it arrive but then dropped it from its internal queue before processing. The blockchain still recorded the transfer, but the exchange never added the funds to your swap order.

The correct first step

Gather the transaction hash from your wallet. Copy it precisely. Go to the exchange’s support page, not to a chatroom or social media comment. Open a ticket and paste the hash. Include the exact amount and the address you sent to. The support team can query their backend and match your on-chain transaction to their internal logs. Most reputable exchanges resolve this within a few hours.

What not to do

Do not send another deposit to the same address hoping it will "push" the first one through. That doubles your exposure. Do not cancel the transaction on your end - once confirmed, you cannot reverse it. Do not trust anyone who messages you claiming to be exchange support. Scammers monitor social feeds for exactly this complaint. They will ask for your private keys or a "verification fee." No legitimate support agent will ever request those.

When the exchange is unresponsive

If the exchange does not respond after 48 hours, you may need to escalate. Check whether the address you used belongs to that exchange or to a different service. It is possible you copied the wrong address. Verify the address against the exchange’s official deposit page, not against a saved bookmark or a pasted string from a third party.

If the address is correct and the exchange still denies receipt, the issue becomes a dispute. Some exchanges have an arbitration process. Others do not. Your recourse depends on the exchange’s jurisdiction and your local laws. Consider this before you trade with any platform.

Preventing this scenario

The safest approach is to send a tiny test transaction first. That step is covered in detail on the sibling page "How to test a swap address with a tiny amount before sending the full deposit." Read it before your next swap. The hub page "Swapping crypto safely" also walks through the full checklist of address verification, network selection, and fee estimation. Those pages exist because no exchange is infallible. The blockchain will record what you sent. Whether the exchange credits it is a separate question. Test first, check afterward, and only escalate when you have proof the funds arrived.

Back to portfolio