Metamask swap
MetaMask swap tracks a current quote through authorization to the transaction status and output balance you verify
A MetaMask swap reaches a verifiable end state only when execution succeeds and the intended output balance reflects the result. Review the asset identities, route, output floor and costs before signing. After submission, treat the transaction record and resulting balance as completion evidence, not the earlier estimate.
Table of contents
Bottom line: A swap is complete only when execution succeeds and the intended output appears in the selected account and network.
Using a Current Quote or Requesting a Fresh One
One quote applies to the exact account, input token, output token, amount and network selection used to request it. MetaMask compares available liquidity sources and filters options that its checks indicate are unlikely to execute. The displayed route is therefore a time-sensitive offer for that request. Changing an asset, network or amount creates a new request rather than editing the old result.
Keep the selections unchanged while you read the quoted output, costs, price impact and slippage information. Continue only while those terms remain acceptable. A fresh confirmation screen may update the network fee because network demand can change before broadcast.
If the quote expires, the route becomes unavailable or fetching fails, do not continue from that offer. Return to the swap form, confirm the same asset identities and request a fresh quote. Stop if compatibility is wrong or no route appears. Repeated confirmation attempts do not repair an expired offer, and raising slippage changes the protection rather than restoring the original terms.
Quote Terms Before Authorization
The quote is the last review point before approving token access or signing the swap transaction. It should identify a compatible input and output pair and show enough information to judge the expected result.
Asset and Network Identity
Asset identity includes the token contract or native asset, its network and its role as input or output. A familiar symbol alone cannot establish that identity because similar symbols can exist on different networks or contracts. For a cross-network selection, the source and destination networks also form part of the request. If any identity is wrong, abandon the quote and correct the selection before authorizing it.
Output Floor, Fees and Route
The output estimate describes what the quoted route expects to deliver, while the minimum received figure sets the lowest acceptable output under the selected slippage tolerance. Price impact reflects how the requested exchange affects the available market price. Read the network fee and MetaMask fee as separate costs shown with the quote. Their display does not turn the output estimate into a fixed promise if market or network conditions move.
Authorization Before the Exchange
The authorization boundary depends on what the confirmation request actually permits. A token approval can grant a specified contract permission to spend the input token up to the displayed allowance. That approval does not exchange the asset by itself. The swap transaction is the request that uses the route and attempts the exchange, so an approval record alone is not evidence that output arrived.
Some routes need an approval before the exchange can proceed, while an existing sufficient allowance can remove that separate request. Read the account, network, action and spending amount on every confirmation. Rejecting a request leaves the exchange unsubmitted. After submission, use the transaction record to check a same-network swap. For a cross-network route, also verify the destination status and credited output before treating the swap as complete.
A Hypothetical Completion Check
The account, network, input and output tokens and all quantities in this hypothetical example are invented. Before any signature, the output contract and network must match. Completion requires both a successful record and credited output.
- Before signing, the selected account holds 7.4 input units, and the intended output contract is already identified on the same network. A quote shows 18.62 expected output units, an 18.31 minimum and separately displayed fees.
- The compatibility check confirms that the account, network and token contracts match the intended exchange. If the output contract or network differs, the reader stops without signing and corrects that selection before requesting another quote.
- For submission, the reader reviews any approval request, authorizes only the displayed input allowance and then signs the exchange transaction. The resulting transaction hash identifies the submitted action.
- At confirmation, the record reaches successful status, and the intended output balance increases by 18.47 units. That increase is 0.16 units above the 18.31 minimum, so the record and balance agree. A failed record instead ends the attempt and requires a new quote.
If the successful record contains the output transfer but the wallet does not display the token, adding the already verified output contract is the smallest reversible display fix. It does not repeat the exchange or change the on-chain result.
Transaction Status as the Final Record
A confirmed, successful on-chain transaction cannot be reversed through MetaMask. Use the transaction record, rather than a stale quote or notification, to judge status.
Pending Is Unfinished
A pending record means the submitted transaction has not reached a final result. The transaction hash can be inspected on the appropriate network explorer, where its presence distinguishes a broadcast transaction from a wallet-only display problem. Do not count expected output while the record is pending. Another transaction from the same account may also wait behind an older pending nonce on networks that order account transactions this way.
Failed and Successful Records
A failed swap transaction means that action did not complete, even if an approval succeeded earlier. For a same-network swap, compare the successful execution record with the credited output. For a cross-network route, also verify the destination status and output. In either case, the records and balance must match the intended output asset, account and network.
Output Evidence Beyond the Wallet Display
The relevant execution records show whether the submitted actions succeeded, while the destination balance shows what the intended account received. Together, they should match the intended output asset and network.
A delayed or missing wallet display does not by itself prove that execution failed. First inspect the relevant transaction record for the intended output transfer.
Next, confirm that the wallet is viewing the same account and network used for the exchange. These checks isolate a display issue without submitting another swap.
An uncommon token may need to be added to the wallet display using its verified contract. Adding that display entry reveals an existing balance; it does not create a token or repeat the exchange.
A Deliberate Exit After Verification
Verification is complete when the required execution records show success, the token identity matches and the intended account shows output that meets the quoted minimum. Save the transaction hash or hashes if a later display or accounting question requires the execution record.
Do not submit another swap once those checks agree. A remaining token allowance is a separate permission decision, and a new transfer or swap is a separate transaction. Base the next decision on the verified output balance, not the superseded quote.
Metamask swap: the short answers
Can a Fresh Quote Select a Different Liquidity Source?
Yes. MetaMask compares the quotes available at the time of each request, so a refreshed request may return a different route or source. That does not alter an earlier submitted transaction. Compare the refreshed output, minimum received, price impact and fees as a new offer before authorizing it.
Does a Visible Wallet Balance Guarantee That a Swap Quote Will Appear?
No. A displayed balance indicates that the account holds the token on the selected network. A quote also requires the token to be supported and the underlying market to have enough liquidity for a route. Adding a custom token changes the wallet display only; it does not create that liquidity.
Why Can the Fee Balance Decrease When the Swap Transaction Fails?
The network can still charge for computation used to process a submitted transaction, even when the exchange logic ultimately fails. That fee compensates the network participants that process transactions; it does not buy output tokens. An earlier approval can also carry a separate network fee if it was submitted as its own on-chain transaction.
Is the Fiat Value Fixed When the Output Transaction Succeeds?
No. A successful record shows the transferred token amounts and execution status, not the token's later market valuation. Wallet and explorer fiat estimates can move after execution or use different price data. Reconcile the output quantity against the transaction record before treating a changing fiat display as an execution problem.
Can the Quote Cover the Network Fee With a non-native Token?
Sometimes. MetaMask can deduct the network cost from the input token for eligible swaps on supported networks. The quote should show that treatment before authorization. If the confirmation shows neither that treatment nor fee sponsorship, the account needs an accepted fee asset for the network.
Updated ·