When a Wallet QR Code Expires Mid-Swap

If a wallet QR code expires mid-swap, check whether it was for connecting your wallet or for a time-limited swap request before starting again. An expired QR by itself does not show that a transaction was sent or that funds moved.

The key is to separate an expired request from a transaction your wallet has already signed and broadcast.

What does an expired swap QR code mean?

A QR code can carry a wallet connection request, or it can open a payment or deposit request with its own deadline. A connection QR, such as one using WalletConnect, helps the site and wallet establish a session; it is not the swap transaction itself. A payment QR may instead encode an amount, destination or request that the service will accept only for a limited time.

If a connection QR expires before you approve it, the site generally needs to create a fresh pairing request. If you already connected, the QR may no longer matter: the swap can continue through the established session, subject to the quote and any wallet prompts. For background on checking the destination chain and route on a thor swap, see the fuller route guide.

What should you check before trying again?

First, look at the wallet: is there still a pending request, or does its activity show a transaction hash? A request waiting for approval has not necessarily been broadcast; a transaction with a hash may already be on its way, even if the site no longer displays the original QR. Then check the swap page for its current status, quote and destination details.

If nothing was approved and no transaction was sent, refresh or restart the flow to get a new QR or quote. Before approving, compare the asset, network, amount, destination and minimum received with what you intended. A quote can change while you wait, so the replacement may offer a different output or fee.

• QR expired before scanning: reopen the swap flow and use the newly generated request.
• Scanned, but no wallet prompt appeared: check the wallet app and the page status, then request a fresh pairing if the session expired.
• Approved or sent: check wallet activity and the transaction status before retrying, to avoid sending a second swap.

Does a new QR mean the swap has restarted?

Not necessarily; the QR’s deadline and the transaction’s status are separate. A wallet connection can expire while an already-sent transaction continues through the source network, and a swap quote or deposit request can have its own validity rules. The service that created the request determines what happens after that deadline, so don’t assume an old deposit address or quote remains usable.

Costs depend on what has happened. If you have not sent a transaction, generating a replacement request usually does not itself incur an on-chain network fee, though the new quote may have different fees or slippage. If a transaction was broadcast, it may incur a network fee even if the swap later fails; check the interface’s stated refund or failure process before taking another action.

In practice, treat the QR as an entry point, not a receipt. Confirm whether the wallet connected, whether you approved a transaction and whether it was broadcast; then follow the status shown by the wallet and swap service. Retry only when those checks show there is no active transaction to duplicate.