Why Does a Bridge Show as Completed but My Wallet Still Shows the Old Token?

06 November 2026

A bridge transaction that shows as completed on the source chain but leaves your wallet unchanged usually means the destination-side token was never added to your wallet's token list, or the bridge minted a non-canonical token that your wallet does not automatically recognize. The bridge itself worked correctly; the problem is that your wallet does not display the new token without manual action.

The token list problem

Most wallets (MetaMask, Trust Wallet, Rabby) maintain a curated list of token addresses. When a bridge sends you a token that is not on that list, the wallet shows nothing. The balance exists on-chain, but your wallet has no entry to display it.

This happens because: - The bridge delivered a wrapped version of the token that is different from the canonical token on the destination chain. - The bridge uses a newer token contract that the wallet provider has not added to its default list. - You bridged to a chain where the token is rarely used, so no wallet list entry exists.

Step-by-Step: how to see your tokens

1. Confirm the Transaction Succeeded On-Chain

Open a block explorer for the destination chain. Paste your destination wallet address. Find the incoming transaction from the bridge contract. If the transaction shows a transfer of tokens to your address, the tokens are there.

2. Add the Token Contract Address Manually

You need the contract address of the token the bridge minted. Get it from:

• The bridge interface: most bridges show a "Add token to wallet" button after a transfer. Click it.
• The block explorer: look at the "To" field in the token transfer event. That address is the token contract.
• The bridge documentation: some bridges publish a list of their deployed token addresses per chain.

In your wallet, use the "Import Token" or "Add Token" feature. Paste the contract address. The symbol and decimals usually auto-fill. Confirm. The balance appears.

3. Check if You Received a Bridge-Wrapped Token vs. the Canonical Token

Some chains have an official, canonical version of a token (for example, USDC on Arbitrum issued by Circle). A bridge might mint its own wrapped version (for example, "Wormhole USDC" or "Stargate USDC"). Your wallet might already show the canonical token but not the bridge-wrapped one.

To tell the difference, look up the canonical token address for that chain on a site like DeBank or the chain's official bridge page. Compare it to the token address the bridge gave you. If they differ, you hold a bridge-wrapped token. You can swap it for the canonical version on a decentralized exchange, or bridge it back.

4. Verify the Token Has Not Been Blacklisted

Some bridges blacklist tokens that were involved in hacks or sanctions. If the token was flagged after your transfer, your wallet might refuse to display it. Check the token contract on the block explorer for any "blacklist" function calls. If blacklisted, contact the bridge team or swap the token on a decentralized exchange that does not enforce the blacklist.

Why the Bridge Shows "Completed" But Your Wallet Does Not

The bridge considers a transfer complete when the destination transaction is confirmed on-chain. That is the bridge's responsibility. The bridge has no control over whether your wallet displays the token. Wallets are independent software that decide what to show based on their own token lists.

This is not a bug. It is a design limitation of how wallets and bridges interact.

What to Do If Adding the Token Does Not Work

• Clear your wallet's cache and restart it. Some wallets cache token lists and may not refresh after you add a new token.
• Use a different wallet interface. If MetaMask does not show the token, try Rabby or Zerion. They may have better token list coverage.
• Check the token on a portfolio tracker like DeBank or Zapper. These tools show all tokens at an address regardless of wallet token lists. If the token appears there, your wallet is the problem.
• If the token does not appear on any block explorer or portfolio tracker, the bridge transaction may have failed silently. In that case, follow the site's guide on "Bridge Transfer Stuck What to Do When Your Claim Never Arrives."

A note on approval phishing

If you connected your wallet to a fake bridge website before this transfer, the "completed" status might be a cover for a drain. The fake bridge shows a fake completion screen while a separate approval transaction allows the attacker to move your tokens. If you did not manually verify the bridge contract address before approving, revoke all token approvals immediately. See the site's guide on "Fake Bridge Websites How Approval Phishing Scams Drain Your Wallet."

When to contact support

Only contact bridge support if: - The destination transaction does not exist on the block explorer despite the source chain showing a completed transfer. - The destination transaction reverted (failed) and the bridge interface still shows completed. - You added the correct token address and the balance is zero on both the wallet and the block explorer.

In most cases, adding the token address manually solves the problem within two minutes.

Back to bridges