Jumper exchange Controls Before and After Submission
Jumper exchange keeps the main choices editable while a route is still under review. You can revise the source and destination networks, tokens, amount, recipient, route or permitted slippage, then obtain terms that match those inputs. Once the wallet submits an execution transaction, its signed instructions cannot be edited. From that point, follow the route status and confirm the output. A multi-step route may still require another wallet action, while a failed outcome may provide a refund or recovery path.
ยท last updated
Quote paths and usable terms
Route creation starts with a same-chain swap or a cross-chain path, depending on the selected networks. A same-chain quote draws on exchange liquidity without a bridge transfer. A cross-chain quote may combine an initial swap, a bridge step and another swap after the funds reach the destination. The selected source token, output token, amount, networks and recipient determine which paths the routing engine can consider.
A supported connection does not guarantee an executable quote. Available liquidity, price impact, provider availability, the requested amount and wallet compatibility can prevent transaction data from being prepared. A route groups the steps, transactions and costs associated with one transfer. Its reviewable terms may include expected output, minimum output, gas estimates, fees and estimated duration. These values describe a proposal rather than a completed exchange.
The boundary between edit and commit
The commitment boundary is the submission of an execution transaction from the wallet to a network. Opening a wallet request does not cross that boundary, and rejecting the request leaves the proposed exchange unsubmitted. A recorded token approval is different: it commits an allowance without completing the swap or bridge. Once an execution transaction has been broadcast, the interface cannot alter its signed instructions, although a multi-step route may still require later wallet actions.
What can still change during quote review?
Quote review still permits changes to the user-selected fields used to construct the proposed route. The editable set commonly includes:
- the source network and input token
- the destination network and output token
- the amount to send
- the receiving address, when a separate recipient is used
- the slippage tolerance that determines the minimum acceptable output
- the selected route when alternatives are available
Each material edit calls for a fresh quote because the old result describes different inputs. Changing only the amount can alter available liquidity, estimated output, fees, gas and the set of usable paths. Changing a token or network creates a different exchange request altogether. The refreshed terms should be reviewed as a new proposal rather than treated as a minor update to the earlier one.
Recipient changes need the same treatment. Confirm that the route review shows the newly entered address on the intended destination network before accepting the wallet request. If the route review still reflects an earlier recipient or route, reject the wallet request and return to quote review. After broadcast, a transaction cannot be redirected to a corrected address.
Parameters across the submission boundary
Six route parameters show how editability ends at submission. The final column identifies the record or constraint that protects the intended result after an input becomes fixed.
| Parameter | Value during quote review | State after submission | Protection or evidence |
|---|---|---|---|
| Source selection | The network and token from which funds will be spent | Fixed in the submitted transaction | Source-network transaction identifier and confirmation record |
| Input amount | The quantity used to calculate routes and estimated output | Fixed by the transaction value or token transfer instruction | Amount recorded in the source transaction |
| Destination selection | The requested receiving network and output token | Cannot be replaced inside the submitted transaction | Receiving-network record and network-specific token identifier |
| Recipient | The connected wallet or a separately entered destination address | Fixed for the route that was submitted | Recipient shown in transaction and receiving records |
| Slippage tolerance | The allowed movement used to derive the minimum output | Enforced by the submitted swap instruction | Minimum-output condition or a failed transaction record |
| Selected route | The ordered tools, steps, estimates and required wallet actions | A submitted step cannot be replaced with a step from another route | Source and destination transaction identifiers plus route status |
The quote remains the place to correct any mismatch between the intended exchange and the transaction being prepared. The wallet request is the last point for checking the actual instruction before submission. Displayed estimates may change when a quote is refreshed, but a refresh cannot modify a transaction that has already reached a network.
Approval as a separate permission
An allowance-based token approval lets a specified spender transfer tokens up to the approved amount; it does not execute the quoted exchange. Editing the amount, choosing another route or abandoning the quote does not automatically remove an approval that was already recorded. Review the spender and allowance in the wallet request before submitting it. A later approval or revocation can change the remaining allowance, but it does not rewrite the earlier approval transaction.
Pending execution and status evidence
During pending execution, follow the source transaction record and route status instead of the earlier editable terms.
Cross-chain tracking distinguishes NOT_FOUND, INVALID, PENDING, DONE and FAILED as separate status values. NOT_FOUND can mean that a valid transaction has not been indexed yet, while INVALID indicates that validation failed. PENDING means the transfer is still moving through its required confirmations or destination processing. The source confirmation record helps separate a delayed status update from a transaction that never reached the network.
Closing the interface or stopping local route handling does not cancel a transaction that was already broadcast to a network.
DONE must be read with its substatus. COMPLETED identifies delivery of the requested token, while PARTIAL records completion with a different token than requested. REFUNDED means the route did not finish as requested and funds were returned. FAILED points to a failure reason or a refund requirement. These outcomes are materially different even when the original quote showed the same intended output.
A fresh quote helps only after the earlier outcome is known; it cannot rewrite a source transaction that remains in flight.
Output mismatch and refund paths
Output verification compares the receiving record with the requested network, token, recipient and minimum acceptable result. A balance display can lag behind an on-chain record, so the destination transaction and network-specific token identifier provide stronger evidence than a symbol alone. If no destination transaction exists yet, the source confirmation and current route status show whether the transfer remains pending.
Partial completion can occur when a cross-chain bridge step succeeds but a later destination swap fails. The receiving record then identifies the token that actually arrived. Any next exchange must start from that observed destination token and its network, using a fresh quote. Repeating the original route without checking the received asset can create a second request that does not match the wallet balance.
Refund handling depends on the tool used by the selected route. Funds are often returned on the source network, while some routes can return them on the destination network. The refund record determines the actual location, token and transaction. Some failures trigger an automatic refund, while others require a manual claim or remain unresolved until the route provider supplies the necessary action.
A same-chain swap has a narrower outcome range because its operations can succeed or revert together, although network gas may still be spent on a failed transaction. A cross-chain path can reach an intermediate state that cannot be undone merely by cancelling the remaining interface flow.
Reconciliation before another attempt
Reconciliation starts with the intended input and output, then checks each surviving record. Preserve the reviewed network and token selections, amount, recipient, minimum output and selected route alongside the source transaction identifier. After submission, add the source confirmation record, destination transaction, received token and any refund record. The comparison should identify whether the observed state matches the request, remains pending or ended through a different asset or refund.
A second attempt should use the assets and network that the records show, not the state assumed from the original quote. Confirmed source execution paired with a pending destination calls for tracking rather than duplication. A PARTIAL outcome calls for a new destination-side decision, while a completed refund supports a fresh request from the recorded refund location. New transactions can address a final outcome, but they cannot revise an earlier commitment.
Jumper exchange - common questions
Does editing the amount remove an earlier token approval?
No. A token approval is a separate permission recorded on its network, so changing the quote does not automatically cancel it. The existing allowance may remain available to the approved spender until it is used, replaced or revoked. Check the recorded spender and allowance rather than assuming that an abandoned quote removed the permission.
Why can a refreshed quote use a different route?
A refreshed quote reflects the inputs and execution conditions available at that moment. Liquidity, exchange rates, gas estimates and provider availability may have changed, or an edited amount may fit a different path. Compare the new minimum output, fees, steps and required wallet actions before treating the replacement route as acceptable.
Can I replace the recipient after the wallet request appears?
Yes, provided the execution transaction has not been submitted. Reject the wallet request, change the recipient and obtain a fresh quote that displays the revised destination. Once the transaction is broadcast, its recipient cannot be edited through Jumper exchange; any later action must follow the outcome recorded for that submitted route.
Do I need native gas for every revised route?
The requirement depends on where the revised route asks the wallet to submit an on-chain transaction. Each such network generally requires enough of its native gas asset unless the displayed route explicitly handles that cost another way. Review the new route because an earlier gas estimate may no longer describe its steps.