How long can a manual refund from a swap support team really take

07 September 2026

There is no fixed time. A manual refund can arrive within hours, stretch to weeks, or never come at all.

The variation depends on three factors: whether the support team actually controls the funds, how they verify ownership, and how many other failed swaps are ahead of yours in the queue. Each factor introduces uncertainty that compounds the wait.

What determines the timeline

Control of the funds. Some swap sites hold deposited crypto in hot wallets they manage directly. Others route through liquidity pools or third-party contracts where the site does not hold a private key that can initiate a return. If the site controls the wallet, a manual refund can be fast - sometimes minutes - because one person clicks "send." If the funds are stuck in a contract or a pool, the team must first extract them, which may require a developer to write and sign a transaction, test it, and then broadcast it. That step alone can add a day or more.

Verification of your claim. The team must confirm you are the person who sent the deposit. They typically ask for the transaction ID, the sending wallet address, and sometimes a signed message proving you hold the private key. If you respond immediately with clear evidence, verification may take an hour. If you send a screenshot of a block explorer page instead of the actual TXID, or if the wallet address you provide does not match the sender, the team will ask again. Each round of clarification adds another business day, sometimes longer if support works on a part-time schedule.

Queue size and staffing. Most swap sites run support with one or two people. A site processing hundreds of swaps per day may accumulate dozens of failed transactions requiring manual intervention. The team prioritizes by value, by how long the case has been open, or simply by the order tickets arrived. If you are ticket 47 and the team resolves ten per day, your refund takes roughly five days assuming no new failures arrive. New failures do arrive.

The blockchain itself. If the refund transaction must clear a congested network, the broadcast may sit unconfirmed for hours. The support team typically waits for a minimum number of confirmations before marking the case closed. They will not tell you "it is sent" until they see the network accept it. That final step can add another hour to a day depending on fee markets and block space.

When the refund never comes

Some teams disappear. A support email goes silent, the site goes offline, or the person handling refunds stops showing up. In those cases the manual refund never happens. The funds remain in a wallet the site controls or are locked in a contract forever. There is no deadline that forces a response.

Other teams simply decide not to refund. They may claim the transaction succeeded from their side, point to a blockchain explorer showing the outgoing transfer, and close the ticket. If the outgoing transfer went to an address you did not provide, or if the amount is wrong, the refund process has effectively ended. Your recourse is zero - no court, no regulator, no arbitration clause in the terms of service that favors you.

What you can do while waiting

Reopen the ticket once per week with a single update. Do not send the same message every day. That buries your case in notifications and annoys the person who might process it. Provide exactly what they ask for the first time. If they request a signed message, sign it correctly and paste the result. If they want the exact UTXO, give them the TXID and output index.

If two weeks pass with no reply, the refund is unlikely to arrive. At that point the question shifts from "how long" to "what can I recover." That is where understanding what your wallet signed during the failed swap becomes the relevant next step. The hub page under this set covers exactly that: what signatures you gave away, what access you authorized, and whether the site can still move your funds even after a failed swap.

Back to wallet security