Pancakeswap
Pancakeswap quotes can be discarded, remaining allowances can be revoked and some pending transactions can be replaced, but a confirmed result requires a new transaction
Pancakeswap treats a quote, token approval, pending transaction and confirmed swap as separate states. You may edit or abandon a quote, reject a wallet request, replace some pending transactions and revoke a remaining allowance. Once an on-chain swap confirms, its recorded result cannot be edited. Changing the resulting balance then requires another transaction with a fresh price, trading fee and possible network gas.
What's inside
Bottom line: You can discard a quote, revoke a remaining allowance and replace some pending transactions. A confirmed swap needs a separate transaction to change its outcome.
Quotes and routes remain editable before signing
A displayed quote is a proposal rather than a reservation. Its amount, asset choice, route and expected output can change before you authorize anything.
Changing the proposed exchange
Editing either token or the input amount causes the interface to calculate a new quote. The previous output does not reserve liquidity or a price. Review the updated output, fee, route and minimum amount before continuing. Closing the page or rejecting the first wallet request ends the attempt without network gas when no transaction has been broadcast.
Changing route preferences
An available route may use one or several liquidity sources, multiple hops or split execution. Routing controls can exclude some of those paths, but doing so may change the quoted output or leave no usable route. If the chosen combination has no compatible path, adjust the selection or stop. There is no completed exchange to unwind at this point.
Approval and swap signatures create separate commitments
Many tokens require spending approval before a swap. That approval has its own state, so it can confirm even when the later exchange never starts.
Token approval changes an allowance
A token approval authorizes a specified spender contract to use up to the allowance recorded for that token. If the approval confirms and you stop, the remaining allowance may still exist. Lowering or revoking it requires another on-chain transaction and network gas. Disconnecting a wallet only ends the interface session; it does not alter the allowance. Revocation limits future spending and cannot recover tokens already transferred.
The swap request authorizes a different action
After approval, a standard on-chain swap produces a separate wallet confirmation. Rejecting that request prevents the wallet from submitting the exchange. Accepting it allows the wallet to broadcast the transaction, which moves the action into a pending state. A message signature and a transaction confirmation are not interchangeable, so read the request type, spender, amount and network before accepting it.
A pending transaction leaves a narrow replacement window
On nonce-based EVM networks, a wallet may try to replace a pending transaction with another transaction using the same nonce and a sufficient fee. This is a race rather than an undo command. If the network includes the original first, it can confirm before the replacement. Other networks and wallets can use different replacement rules. On an EVM network, an included replacement transaction consumes network gas.
Confirmation fixes the executed state
The transaction receipt separates a settled result from an interface message that may be delayed or stale. Its status determines which recovery path still exists.
A successful receipt preserves the exchange record
A confirmed on-chain swap cannot be reversed by editing the earlier request. The transaction hash, receipt status and recorded transfers remain part of the chain history. A later swap in the opposite direction creates another record instead of erasing the first one. Confirm the result by matching the successful receipt with the expected balance change.
A failed receipt preserves a different record
On an EVM network, a reverted swap does not retain the intended token exchange, although the included transaction can still consume gas. The network processed and recorded the attempt before execution failed. A rejected wallet prompt, local quote error or transaction that was never broadcast has no on-chain receipt and uses no network gas. Correct the cause before deciding whether to submit a new transaction.
A hypothetical swap traces the last reversible point
Every token role, quantity, route and network condition in this hypothetical case is illustrative. A reader enters 286 units of a supported input token, selects a supported output token and receives a quote on a compatible network.
For the normal path, the reader authorizes an allowance of 286 units and confirms that approval. A fresh quote then shows an available route. The reader submits all 286 input units, receives a successful transaction receipt and sees the output token balance change. If the spender uses the full 286-unit allowance, 286 - 286 leaves 0 units of allowance. The approval receipt and swap receipt remain separate evidence.
If the selected token combination lacks a compatible route before signing, no exchange occurs. The reader can discard the quote, choose another supported combination or wait for conditions to change. A refreshed quote replaces the previous proposal; it does not amend an on-chain record.
If the swap has been broadcast but remains pending, network compatibility determines whether a same-nonce replacement is available. When the replacement confirms first, the input balance remains unchanged by the original swap. When the original confirms first, the output balance reflects the completed exchange.
After confirmation, the original swap cannot be changed. The reader reconciles the receipt with both balances, then either keeps the output or requests a new swap in the opposite direction. That second exchange receives its own quote, costs and transaction record.
Open orders and liquidity positions use different exits
An unfilled limit order can be canceled while it remains open. Once filled, cancellation no longer reaches the executed trade. A liquidity position uses another exit: removing part or all of the liquidity through a new transaction. Revoking a token allowance does not cancel an order or withdraw liquidity by itself because each control changes a different record.
The recorded state decides the next action
Start with the evidence that actually exists. A draft quote without a transaction hash needs no on-chain repair. A successful approval receipt means the allowance changed, even if the swap did not follow.
For a pending transaction, inspect its network status and any replacement transaction before acting again. A wallet label can lag behind the chain. Submitting another ordinary swap without resolving an older nonce may add to the pending queue instead of replacing the original action.
A successful swap receipt makes the new balance the starting point for any later choice. A failed receipt calls for examining the error and remaining balances, while an open order or liquidity position needs its own cancellation or removal control.
If you still want a different balance after confirmation, decide whether the new quote, route, trading fee and network gas justify a separate transaction.
Pancakeswap questions, answered
Does rejecting a wallet request cost network gas?
Rejecting a request before the wallet broadcasts a transaction does not use network gas because nothing reaches the chain. The distinction matters when an approval has already confirmed. Rejecting the later swap request leaves that approval in place, and any gas paid for the approval remains spent. Review the allowance separately if you no longer intend to use it.
Can revoking an allowance stop a pending swap?
Revoking an allowance is not a reliable way to cancel a swap that is already pending. The revocation is another transaction, and an EVM network normally includes an account’s transactions in nonce order. A wallet-supported replacement instead competes for the same nonce as the pending transaction. Even then, the original can confirm first if it wins the race for inclusion.
How can I verify whether a replacement transaction won?
Compare the original and replacement transaction hashes on the relevant network. On a nonce-based EVM network, only one transaction from the same account with a given nonce can be included in the canonical chain. Any receipt for the replacement shows that it was included and consumed the nonce, whether execution succeeded or failed. If the original has a receipt instead, the network included it despite the replacement attempt.
Could a failed swap be retried with the same transaction hash?
No, a transaction hash identifies one specific signed transaction. Once that transaction has a failed receipt, editing its inputs would create a different signed transaction with a new hash. Check why the first attempt reverted before retrying. A replacement can reuse a nonce while the original remains pending, but it still receives its own transaction hash.
Will closing the browser halt a submitted swap?
Closing the browser does not halt a transaction that the wallet has already broadcast. The network continues processing it independently of the page. Reopen the wallet or inspect the transaction hash to learn whether it remains pending, succeeded or failed. If no request was signed and broadcast, closing the page merely discards the provisional quote.
Does canceling an open limit order also remove its token allowance?
Canceling an open limit order and changing a token allowance are separate actions. Cancellation changes the order state so it cannot fill as that open order. Any allowance granted to a spender can remain after cancellation until it is used, reduced or revoked. Check both records when the intention is to close the order and remove future spending permission.
Are approval and swap recorded under one transaction hash?
An on-chain token approval and a standard on-chain swap normally produce separate transaction hashes because they are separate actions. The approval changes an allowance, while the swap attempts the exchange. Some routes can use message signatures instead of a separate approval transaction, so identify what the wallet is requesting. Do not treat an approval receipt as proof that the swap completed.