Skip to main content
Blocktape

Crypto markets, protocols and policy

Why is my Polygon deposit pending after it succeeded?

Why does my exchange take so long to credit Polygon deposits? Learn how confirmation thresholds, reorg safety and contract transfers affect crediting.

The Blocktape Editors 3 min read f5e6d4

Why is my Polygon deposit pending after it succeeded?

Your exchange usually credits a Polygon PoS deposit after the transaction reaches its required confirmation count, a safety margin against reorgs that could reverse it. A successful transaction on Polygonscan means the network processed it; it does not mean the exchange’s threshold is met.

What does the exchange wait for?

The exchange waits for its own required number of Polygon PoS confirmations before adding the deposit to your balance. Each exchange sets its own threshold for each network, and the deposit page should show the requirement.

Polygon PoS produces a block about every two seconds, so confirmations can accumulate quickly. A wallet send may show Success on Polygonscan within seconds while the exchange’s counter continues toward its threshold.

Exchanges set confirmation thresholds to reduce the chance of crediting funds that a reorg could undo. Past Polygon PoS reorgs led exchanges to use high thresholds; Heimdall milestones provide deterministic finality, allowing some exchanges to use lower ones.

Contract calls can make a deposit harder for an exchange scanner to detect. A Polygon bridge transfer is a useful case: its smart contract can deliver supported assets to Polygon PoS, and the resulting deposit may appear as an internal transaction rather than a direct wallet send.

Some exchange scanners miss internal transactions from a bridge, DEX or Safe, even when the transfer succeeded on-chain. If your deposit is past the listed confirmation threshold and still missing, contact support with the transaction hash; support may need to credit it manually.

What else can delay or explain a Polygon deposit?

Wrong network or token details, an internal transfer, or paused deposits can explain a delay beyond the confirmation count. A Polygon bridge transfer can also involve separate bridge processing, but this post concerns the exchange’s crediting after the Polygon PoS transaction has landed.

Say you send tokens from your Polygon PoS wallet and Polygonscan shows Success. The exchange page still shows fewer confirmations than required, so waiting is expected; if the count has passed and your balance has not changed, check the network and token, then open a support ticket with the hash.

Use the deposit page’s network and token instructions before sending. If the transaction is confirmed but the exchange has not credited it, the hash lets support locate what its scanner missed.

Questions about Polygon deposits

How do I find my deposit's transaction hash on Polygonscan?

Open the transaction on Polygonscan and copy its transaction hash from the details page.

Is depositing to the exchange on Ethereum faster than on Polygon?

Not necessarily. Ethereum and Polygon PoS have separate confirmation thresholds, and the exchange’s deposit page shows the requirement for each network.

What should a support ticket for a missing deposit include?

Include the transaction hash, asset, amount, network, destination address and approximate send time.

Why does an exchange withdrawal to Polygon take longer than a wallet send?

An exchange may apply its own withdrawal checks and processing steps before broadcasting a transaction. A wallet send does not include those exchange-side steps.

Related stories