A Polygon PoS Withdrawal Has Three Stages. Find the One Still Pending

A pending Polygon PoS withdrawal is usually waiting at one of three stages: the Polygon burn, a checkpoint on Ethereum, or the Ethereum claim. The distinction matters because each stage has a different transaction, network and next action. A transfer shown as pending in a bridge interface does not, by itself, tell you which stage is incomplete.

For the standard PoS Bridge flow, withdrawing burns the Polygon-side representation of the asset; after the burn is included in a checkpoint, a separate Ethereum transaction exits the bridge and releases the corresponding asset. The comparison of Polygon Bridge exit models covers the broader design choice; here, the useful diagnostic is to match your transaction to the stage it completed. A checkpoint is evidence that Polygon block data has been committed to Ethereum, not a payment or claim sent to your wallet.

What are the stages of a Polygon PoS withdrawal?

A standard PoS withdrawal starts with a burn on Polygon and finishes with an exit transaction on Ethereum, with a checkpoint between them. The first and last steps are wallet transactions you submit; the checkpoint is part of the bridge’s proof process.

• Burn on Polygon: You submit the withdrawal transaction on Polygon. The mapped token is burned there, so it no longer appears as spendable in that wallet on Polygon.
• Checkpoint: Polygon validators commit a range of Polygon blocks to Ethereum. The bridge needs the checkpoint covering your burn before it can verify the withdrawal proof.
• Proof and exit: Once the burn is covered, the bridge can produce the proof required for the Ethereum-side exit.
• Claim on Ethereum: You submit that exit transaction on Ethereum. When it succeeds, the bridge releases the corresponding asset to the destination address.

Some interfaces label the first transaction “withdraw initiated” and the checkpoint “checkpoint arrived.” Labels vary, so use the transaction hash and its network as the more reliable clues. The Polygon hash identifies the burn; an Ethereum transaction hash identifies the final claim. The withdrawal is not complete just because the burn succeeded or the checkpoint became available.

How do I find the missing stage?

Start with the withdrawal’s Polygon transaction hash and check whether the burn succeeded on Polygon. If it is pending in the wallet, or reverted on the chain, the process has not reached checkpoint waiting. If it succeeded, check whether the bridge marks that specific burn as checkpointed. Only after that should you look for an Ethereum claim.

Use the stage and network to decide what to do next:

• Polygon burn is pending: Check the wallet’s transaction status. A submitted transaction that has not confirmed is still at the source-chain stage.
• Burn succeeded, no checkpoint yet: The withdrawal is waiting for the checkpoint that includes its block. Reopening the interface will not create that checkpoint or move the funds to Ethereum.
• Checkpoint arrived, no Ethereum claim: Check whether the interface offers the exit or claim action. If it does, the withdrawal still needs a successful Ethereum transaction.
• Claim submitted but not successful: Inspect the Ethereum transaction itself. A reverted claim has not released the asset; a pending claim is waiting for Ethereum to process it.

A bridge page can also display stale or incomplete status if its indexer is behind or its connection to a wallet or RPC endpoint has failed. Compare the page with the on-chain transaction record before treating a display error as a failed burn. If the chain shows a successful burn but the bridge cannot produce the next step, preserve the transaction hash and use the bridge’s support route.

What can delay the checkpoint or claim?

The checkpoint stage depends on Polygon block data being included in a checkpoint on Ethereum. Until the checkpoint covers the burn, the bridge cannot complete the proof needed for the exit. The wait is not the same as an Ethereum claim sitting in a wallet queue: no claim transaction exists yet if the checkpoint has not arrived.

After checkpointing, the final claim is a separate Ethereum transaction. It can remain incomplete because it has not been submitted, is still pending, or reverted. A successful Polygon burn does not pay the Ethereum gas for that claim. Keep enough ETH available at the address that will submit the exit, and check the claim transaction on Ethereum if the interface says it was sent.

Token and route details matter. The steps above describe the standard PoS Bridge exit flow; an interface may expose a different route or stage names, and not every asset uses identical bridge contracts. Confirm the selected route and the destination address shown for the withdrawal before signing another transaction. In particular, do not repeat a burn simply because the bridge page has not advanced: first verify whether the original Polygon transaction succeeded.

When is the withdrawal complete?

The withdrawal is complete when the Ethereum-side exit transaction succeeds and the asset is released to the stated destination address. A checkpoint alone proves that the bridge can verify the burn; it does not finish the transfer. After the claim succeeds, check the destination address on Ethereum and confirm that the expected asset arrived.

The practical rule is to follow the hashes across both chains: first confirm the Polygon burn, then the checkpoint, then the Ethereum claim. That identifies whether the next step is waiting on bridge proof generation or requires a wallet transaction. It also prevents a common diagnostic mistake: treating “burned on Polygon” as equivalent to “received on Ethereum.”