Why Treasury Transfers Open the Wrong Mobile Browser

A mobile wallet can approve a treasury transfer in one app while the related web page opens in a different browser with no active session. The wallet and browser keep separate connection details, so an approval can succeed even when the page that started the transfer appears disconnected.

Why does a wallet open the wrong browser?

A wallet link asks the phone to open an app or a web page. The phone follows the link’s settings, the wallet’s support for that link, and the app that started the request. If the link comes from a chat app or email, it may open in that app’s built-in browser. If it comes from a wallet notification, it may open the wallet’s own browser.

Each browser keeps its own tabs, cookies and site data. Those details help a site remember that a wallet has connected. Moving to another browser can lose that connection, even if the wallet app still shows the account. A thor swap transfer has the same split between a site session and wallet approval; the linked guide explains the checks around a cross-chain move. The key point is that a wallet prompt does not prove the page is open in the browser where the team began.

What does a mobile wallet session remember?

A wallet session is the temporary link between a web page and a wallet. It lets the page ask the wallet to show an account or prepare a transaction. It does not necessarily carry over when the page opens in another browser, and it does not mean a transfer has happened.

The transfer itself is a separate step. A treasury tool may prepare transaction details, then send a request to the wallet. The wallet shows details for review and asks the signer to approve. Depending on the setup, the page may need to return to the original browser to update its status. If it cannot, the wallet may still show a pending or completed action while the page looks unconnected.

How can a treasury team keep the session clear?

For routine work, use one agreed path from the treasury page to the wallet and back. A team can reduce confusion by checking which browser holds the active page before requesting a signature. It also helps to confirm the wallet account and network shown in the prompt, then compare the destination and amount with the prepared transfer.

• Open the treasury page in the browser the team normally uses.
• Start the transfer from that page, rather than reopening an old wallet link.
• Review the destination, amount and network in the wallet prompt.
• Return to the original browser and check that it records the result.

If the wallet opens a different browser, stop and return to the original page before trying again. Avoid approving a second request until the team can tell whether the first one was signed or sent. For most teams, a consistent browser path is simpler than trying to keep several mobile sessions in sync.