Most missing tokens are on another network or hidden from the wallet list. After a Polygon Bridge transfer, check where the destination transaction sent them before trying anything again.
- A completed transfer on Ethereum does not prove the Polygon PoS transfer finished.
- MetaMask shows assets for the selected network, and some tokens need adding to the list.
- Check the destination address and token contract before changing anything.
Check the network and destination transaction first
Your wallet address can be the same on Ethereum and Polygon PoS, but each network keeps its own balances. In MetaMask, select Polygon PoS and check the same account that received the transfer. A balance on Ethereum will not appear while you are viewing Polygon PoS.
Next, look up the transfer using its transaction hash, a unique ID for a blockchain transaction. Search that ID on an Ethereum block explorer, a public site that lists transactions, and check whether the source transaction succeeded. Then use the bridge’s own status information or a Polygon PoS block explorer to check for a destination transaction.
A bridge transfer has a source and destination
A bridge moves supported assets between separate blockchains. For an Ethereum-to-Polygon PoS transfer, the bridge generally locks the original tokens on Ethereum and releases matching tokens on Polygon PoS. Those matching tokens are recorded separately on Polygon PoS, so the Ethereum balance alone cannot confirm their arrival.
Polygon PoS documentation describes the Polygon-side token as a child token: a token representation linked to an Ethereum token. A transfer can therefore look complete on Ethereum while its Polygon PoS transaction is still pending. Check the destination transaction’s result and the receiving address; a successful result should show that the token reached your wallet.
Add the right token if the balance is there
If the Polygon PoS transaction succeeded but MetaMask still shows no token, the wallet may simply not be displaying it. A token contract address is the token’s identifier on one network. The Ethereum token’s address and its Polygon PoS counterpart can differ, so adding the Ethereum address while viewing Polygon PoS may show nothing.
Find the Polygon PoS token address through a trusted source, such as the bridge’s transfer record or the token issuer’s official information. Compare it with the address shown for the destination token on a Polygon PoS explorer. Add that exact address to MetaMask while Polygon PoS is selected, then check the balance again. Ethereum.org’s explanation of the ERC-20 standard notes that token contracts keep track of account balances; a wallet’s token list is only a display of that data.
A common mistake is to add a token with the right name but the wrong contract address. Names and symbols can be copied by unrelated tokens. If the balance is absent from the destination transaction too, adding a token will not recover it; check the transaction status, recipient address, and any bridge message about a pending transfer.
Check the details before taking another action
There can be a cost on both networks: Ethereum transactions use ETH for network fees, while transactions on Polygon PoS use POL. A completed bridge deposit does not necessarily mean you need to send another transaction. Avoid repeating the transfer until you know whether the first destination transaction succeeded.
If the source transaction succeeded and you want supported assets on Polygon PoS, the official Polygon Bridge is the way to move them between those networks. Before acting, ask yourself: have I checked the destination network, the receiving address, and the destination transaction?