Skip to the article
Onchain Brief

News from across crypto

What Support Needs to Check When a Wallet Swap Is Delayed

A delayed wallet swap is easier to trace when support gets the transaction hash, both networks, and the exact stage where progress stopped, before you retry.

The Onchain Brief Editors3 min read
What Support Needs to Check When a Wallet Swap Is Delayed

A delayed wallet swap is easier to trace when support can see the transaction hash, both networks, and the stage where progress stopped. A swap may involve a token approval, a trade on one network, and, for a cross-chain swap, a transfer to another network. Each step can have a different status.

For background on the cross-chain process, read this explanation of how QuickSwap cuts swap steps. For a delayed swap, the useful question is which step completed and which did not.

What details should I send support?

Send the details that let support find the transaction and match it to your report. Include the wallet address you used, the token names, the amount, and the time you started the swap. Also name the network you started on and, if the swap crosses networks, the one you expected to receive funds on.

  • The transaction hash, a unique ID for an on-chain transaction.
  • A screenshot or copy of the wallet’s status message.
  • The swap or support request ID, if the app gave you one.
  • The time of the attempt and your time zone.

A wallet address alone does not identify a particular swap. The transaction hash is usually the most useful starting point. Share it through the support channel for the wallet or service involved, and never send your recovery phrase or private key.

How can support tell where the swap stopped?

Support can compare the wallet’s message with the transaction record on the network. If the transaction is still pending, it has been sent but has not finished processing. If it failed, the record may show that the network rejected it or that a required step did not complete.

For a cross-chain swap, support should check the source network and the destination network separately. A completed transaction on the source side does not by itself prove that the funds have arrived on the destination side. The service may still be processing the transfer, or the wallet may not yet show the destination token. Ask support which step is confirmed and what status they see for the next step.

Should I retry a delayed swap?

Check the transaction status before starting another swap. If the first attempt is still pending or its outcome is unclear, a second attempt could create a separate transaction and use more funds. If the transaction failed, confirm whether any token approval or other setup step completed before trying again. An approval lets an app use a token up to the approved amount; it is separate from the swap itself.

Ask support for a specific next step: wait, retry, or check a transaction on a named network. The most useful answer will tie that advice to the status of your transaction, not just the wallet’s loading message.