The account shown inside a swap application can differ from the account you most recently selected in the wallet. Check the connected address and the signing request directly before assuming the application followed your selection.
MetaMask’s connection guidance allows users to choose which accounts and networks an application can access. An existing connection can therefore have a narrower or different selection than the wallet’s full account list.
Resolve the mismatch before signing
- Cancel any unreviewed request from the wrong account.
- Open the application’s connection details and compare the full address.
- Adjust the connection permissions or reconnect the intended account.
- Refresh the quote and inspect the signer shown in the new wallet prompt.
Then check the output recipient separately. Some applications allow a recipient different from the signer; fixing one field does not necessarily fix the other.
What about an approval already made?
Permissions belong to the account that granted them. An approval from account A does not authorize tokens held in account B. Review the unwanted account’s allowance if you no longer need it.
If a swap already executed from the wrong account, reconcile that account’s receipt and balances. Changing the selected wallet account does not move the output. Do not import recovery phrases into a new site to “link” the accounts; connection settings and token ownership are different matters.
Sources & verification (2)
Source-check date is recorded in the article details. URLs are provided for manual verification. Use Copy to keep this page open.
- How to connect to a dapp
Account and network permissions are part of the dapp connection.
https://support.metamask.io/more-web3/dapps/connecting-to-a-dapp - ERC-20: Token Standard
Allowance, spender, transferFrom, metadata and approval event semantics.
https://eips.ethereum.org/EIPS/eip-20