What to do if you switch wallets during a Biswap transfer

If you switch wallets during a Biswap cross-chain transfer, the source-chain transaction you already signed remains on that chain; changing the wallet connection does not reverse it. First, find out whether you approved or broadcast the transfer, then check its status before trying again.

Does switching wallets stop a pending Biswap transfer?

No. Once a transaction has been broadcast, the network processes it independently of the wallet window or website connection. A pending transaction is waiting to be included in a block; it can still confirm after you close a tab, switch accounts or connect another wallet.

There are two different switches to keep straight. Changing the active network changes which chain your wallet is showing, while changing the connected account changes the address interacting with the site. Neither action, by itself, cancels a transaction signed by the original address.

Biswap’s bridge instructions say to keep the wallet on the source network when starting a transfer, such as BNB Chain for a transfer to Ethereum. For a fuller explanation of how Biswap cross-chain transfers work, see the linked guide. The key point here is that the wallet you reconnect should match the address that signed the source transaction.

How can you check where the transfer stands?

Start with the transaction hash, a unique ID for the transaction on its source chain. If you have it in the wallet’s activity list, open it in the block explorer for that chain. If you do not have it, reconnect the original wallet and network, then look in its activity history.

Check whether the source transaction is pending, confirmed or failed. A confirmation means the source-chain step was recorded; it does not always mean the destination-chain tokens have arrived. Cross-chain transfers can involve separate steps on separate networks, so check the bridge’s own status display as well as the source transaction.

• Pending: Wait and check again. Do not start a second transfer just because the wallet interface changed.
• Confirmed: Check the bridge status and the destination address on the destination chain.
• Failed: Check the explorer’s error details and the wallet balance before deciding whether to retry.
• No hash: You may have approved a request without broadcasting the transfer, or the wallet may not have sent it. Check its activity before submitting again.

The balance shown in a wallet app can lag behind the chain, and a disconnected site may not show the transfer at all. Use the address and transaction status as your reference, not just the page’s current connection indicator.

What should you do after connecting a different wallet?

Reconnect the original address if you want to follow the transfer or see its activity in the same wallet. You can use another wallet app to access that address only if you control its recovery phrase or private key; importing those secrets into a new app gives that app control over the funds, so use only a wallet you trust.

If the destination address was set before you signed the transfer, connecting a different wallet afterward does not normally change that instruction. Check the transfer details and destination chain. If you sent tokens to an address you do not control, changing wallets will not redirect them.

Also confirm that the connected wallet is on the network needed for the action you are taking. A wallet may prompt you to switch networks when you reconnect. For example, checking a transfer’s destination balance requires the destination chain; submitting a new source transaction requires the source chain and enough of that chain’s native token to cover its fee.

When is it safe to retry or cancel?

Retry only after you have established that the first transfer was never broadcast or has definitively failed. If it is still pending, submitting another transfer can create a duplicate if the first one later confirms. Compare the sender address, amount, destination address and status before signing anything new.

Some account-based chains allow a pending transaction to be replaced by another transaction from the same address using the same sequence number, often called a nonce. That is a wallet-level action on the source chain; it is not a bridge refund, and it may not work the same way on every network. Do not attempt it unless you understand the wallet’s replacement process and have checked the transaction status.

If the source step confirmed but the destination step remains incomplete, use the bridge status and its support route for that transfer. Keep the transaction hash and the two addresses available. Never share a recovery phrase or private key with someone claiming they need it to release the funds.

For most users, the safest next step is simple: reconnect the original address, check the source transaction, then follow the bridge status to the destination. Switching wallets changes what you can see and control; it does not erase a transaction already sent.