Before retrying a pending Polygon PoS bridge transfer, check both chain transactions: a withdrawal needs a burn on Polygon and a separate Ethereum claim after a validator checkpoint. Sending the transfer again while the first stage is progressing can create a duplicate transfer or spend gas without fixing the delay.
A pending label does not tell you which step is waiting
“Pending” can mean your wallet has not yet had a transaction included in a block, or that a completed transaction is waiting for the bridge’s next step. These are different situations: the first may need attention to the transaction in your wallet, while the second usually needs time for the cross-chain process.
For an Ethereum-to-Polygon deposit, the Ethereum transaction locks the original tokens in a bridge contract, and an equivalent mapped token is delivered on Polygon. For a Polygon-to-Ethereum withdrawal, the Polygon transaction burns the tokens, then the bridge waits for a validator checkpoint before you submit a claim on Ethereum to release the original tokens.
That is why a successful wallet notification is not always proof that the funds are spendable on the destination chain. The Polygon Bridge moves the tokens through these on-chain stages; a website’s transfer status can lag behind the networks, so confirm the transactions on the relevant chain explorers.
Trace the transfer using its transaction hash
A transaction hash is the unique identifier your wallet shows after you submit a transaction. Copy it and open it in an explorer for the chain where it was sent: Ethereum for a deposit’s first step or claim, Polygon for a withdrawal’s burn.
Check the transaction’s receipt, which records whether the network executed it successfully. Ethereum.org explains that a transaction becomes part of the chain when a validator includes it in a block; a receipt marked successful confirms that on-chain step, but does not by itself confirm delivery on the other network.
Then check the destination wallet on the destination chain. Make sure the wallet address is the same one you intended to use, and look for the token’s balance there. A token can be present but not displayed in MetaMask until you add or select its Polygon token entry; verify the token contract address before treating an unfamiliar token with the same name as the bridged asset.
Use the stage to decide whether to wait or act
If the source transaction is still pending in MetaMask, the bridge has not completed that on-chain step. Check that wallet’s pending transaction and nonce—the account’s transaction sequence number—before considering a replacement; replacing a transaction can change what executes, so do not submit a second bridge transfer just to refresh its status.
If the source transaction succeeded but the destination balance has not changed, wait and check again. Deposits require the bridge’s cross-chain message to be processed; withdrawals wait for a checkpoint, a batch of Polygon activity committed to Ethereum, and then require a separate claim. Polygon Support notes that a pending Ethereum transaction can also be delayed by low gas pricing or network congestion, while a lagging status display can reflect an indexer that has not caught up.
If a withdrawal has reached the checkpoint but the Ethereum claim is still pending, the Polygon tokens have already been burned. Polygon Support says that this withdrawal cannot be cancelled, but the claim can be completed later; keep the burn hash and use the same intended wallet to continue when the Ethereum transaction can be submitted. You will need ETH for Ethereum gas, and POL for transactions you submit on Polygon.
Keep a record before closing the transfer
For a treasury transfer, record the amount, token, source and destination addresses, both chain names, and every transaction hash. This gives the next person checking the transfer enough information to distinguish a slow bridge stage from a wrong address, a failed transaction, or a token that is simply not visible in the wallet.
Use the Polygon Bridge when you need to move a supported token between Ethereum and Polygon, and record the source hash before you wait. The decision rule is simple: retry only when the original on-chain transaction failed or was dropped; if it succeeded, identify the next bridge stage and wait for or complete that stage.
Top comments (0)