If your Polygon bridge withdrawal burned mapped tokens on Polygon but Ethereum shows no receipt, the burn started the withdrawal; delivery still depends on checkpoint inclusion and a successful Ethereum exit. A successful Polygon transaction proves that the tokens left your Polygon balance. It does not prove that Ethereum has released the asset held by the bridge contracts. The gap can be an ordinary waiting stage, or it can mean the final claim transaction has not been sent. The useful question is which record you have: a burn receipt, a checkpoint covering that burn, or a confirmed exit receipt on Ethereum.
The Polygon Burn Starts the Withdrawal
The Polygon burn removes the mapped token from circulation on Polygon and creates the event that the Ethereum exit must later prove. When you deposit a supported asset, the Ethereum side holds it and the corresponding mapped token represents it on Polygon. For a standard withdrawal, burning that representation requests release of the asset in custody. The Polygon PoS bridge cannot treat a falling wallet balance as authority to unlock Ethereum assets; it needs evidence of the particular burn recorded in a particular Polygon block.
Save the Polygon transaction hash and inspect its receipt on a Polygon block explorer. A successful status, the correct token contract, the burned amount or NFT identifier, and the burning address establish what happened on Polygon. The receipt also identifies the block that must be covered by a checkpoint. If the transaction failed, a wallet prompt or a pending transaction is not a confirmed burn. If it succeeded, keep the hash: the withdrawal has moved to the evidence stage.
A Checkpoint Makes the Burn Provable on Ethereum
A checkpoint makes the burn provable by committing a range of Polygon blocks to Ethereum. Your burn first appears in a Polygon block; later, a checkpoint that covers that block is recorded on Ethereum. An exit proof can then connect the burn receipt to its block and that block to the checkpoint. This is the intermediate step that lets an Ethereum contract verify a Polygon event rather than trusting a wallet screen or a bridge status label.
Checkpoint status depends on the burn block, not simply on how long your wallet has shown a lower balance. If that block is outside the latest checkpointed range, a valid exit proof is not yet available. Once the range includes it, the burn can become claimable. Paying more gas for an Ethereum transaction cannot make an uncheckpointed Polygon block enter a checkpoint sooner. The network must publish the evidence before the exit can use it.
Burn, Checkpoint, and Exit Receipts Mark Different States
These three records answer three different questions. The burn receipt says the Polygon transaction succeeded; checkpoint inclusion says Ethereum can verify its block; the exit receipt says the Ethereum release transaction succeeded. In a Polygon to Ethereum bridge withdrawal, the checkpoint is the point at which proof of the burn can be assembled. To complete a Polygon bridge withdrawal, you must submit that proof in an Ethereum exit transaction before the locked asset reaches its destination. A status such as “ready to claim” describes permission to take the final step, not delivery.
Consider two withdrawals of the same mapped token, from the same wallet, with successful Polygon burns and checkpointed blocks. The only difference is that one has a successful Ethereum exit receipt and the other has no exit transaction. The first is complete because the proof was accepted and the asset released. The second is still claimable, even if its Polygon transaction happened earlier. That single missing Ethereum receipt explains why two otherwise similar withdrawals show different wallet balances.
A Ready Claim Still Needs an Ethereum Transaction
A ready claim means someone must submit the exit on Ethereum and wait for that transaction to succeed. Polygon Portal may present this as a claim or completion step. The exit carries the proof of the burn to RootChainManager, which verifies it against checkpoint data and routes the release through the relevant Predicate contract. For a mapped token, the result is the underlying asset leaving Ethereum bridge custody for the withdrawal recipient. Until the Ethereum transaction succeeds, claim readiness is a state you can act on, not an automatic transfer.
Look for an Ethereum transaction hash after approving the claim in your wallet. A wallet signature request that was rejected, or a claim page you closed, creates no successful exit receipt. If a transaction hash exists, its Ethereum receipt tells you whether the exit succeeded or reverted. A confirmed success is the on-chain completion record; then use the recipient address and the asset’s Ethereum contract to inspect the delivered balance. In the Polygon bridge flow, the person completing the withdrawal still needs enough ETH to pay for that Ethereum transaction.
The Remaining Wait and the Risk of Another Burn
The remaining wait depends on checkpoint inclusion and the Ethereum exit; another burn starts a separate withdrawal. Total elapsed time combines Polygon confirmation, checkpoint inclusion, any delay before you claim, and Ethereum exit confirmation. Those stages can add up to minutes or hours, and the part under your control may be the time between claim readiness and submitting the exit. A higher Ethereum gas bid can affect confirmation of an exit you have submitted; it does not replace the checkpoint. If the checkpoint is pending, keep the original burn hash and wait for its block to be included.
Another Polygon to Ethereum bridge burn does not finish the first withdrawal. It creates a separate burn with its own receipt, checkpoint status, and exit, so repeating the action can leave you with two claims to complete. Closing the page or rejecting the later Ethereum claim also cannot cancel a burn that already succeeded on Polygon. Return to the original withdrawal and use its hash to resume the claim once it is ready. This explanation applies to standard mapped-token withdrawals; native-token and other routes may use different exit steps.