Bitget USDC on Polygon not credited: check the token contract and 60 confirmations

What Bitget's Polygon settings showed

Bitget publishes per-network deposit and withdrawal parameters through its public coin endpoint. The USDC response we pulled lists 14 networks. The Polygon row read as follows.

Source: Bitget public USDC coin and network settings (api.bitget.com), retrieved 12:58:20 SGT, 4 November 2026.

The values describe Bitget's network settings at one moment. They do not say anything about your own transfer, and the settings can change. Check the live deposit screen before you send anything new.

Step 1: confirm the token contract

This is the check most people skip. On Polygon, a wallet can hold more than one token with "USDC" in its name. Bitget credits the contract it lists. Circle's USDC contract addresses page gives the native USDC address on Polygon PoS as 0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359, the same address in Bitget's response with different letter case. Ethereum-style addresses are not case-sensitive, so the two strings name one contract.

To read the contract of your own transfer:

1. Copy the transaction ID (TxID or transaction hash) from the withdrawal history of the wallet or exchange that sent the funds.
2. Paste it into Polygonscan, the explorer Bitget lists for this network.
3. Open the token transfer line and click the token name. The token page shows its contract address.
4. Compare that address with 0x3c499c… above, character by character for the first and last six.

Bitget's refund guide describes the same route: enter the TxID in a block explorer, click the token name, and read the contract address. It also warns that the contract address is not the deposit address. People mix the two up on the form, and the application then stalls.

If the contracts match, go to Step 2. If they do not, the deposit falls under the guide's first issue type, "the coin or the network is not supported by Bitget", and Step 4 applies.

Step 2: count the confirmations

Bitget's Polygon row requires 60 confirmations before a deposit is credited. That is a count of blocks, not minutes. To give the number a scale, we sampled Polygon itself through a public node: block 96,708,012 was stamped 12:44:34 SGT and block 96,708,612 was stamped 12:59:34 SGT on 4 November. That is 600 blocks in 900 seconds, or about 1.5 seconds per block, so 60 confirmations took roughly 90 seconds at that pace. Treat that as an observation from a quiet 15-minute window. It is not an arrival promise.

On the explorer, check the status line first. A failed or pending transaction has not delivered anything to Bitget. Bitget's guide is blunt about this case: if the order is still in progress or failed, Bitget has not received the funds and cannot help, so the sending platform is the right contact.

SponsoredBitget

Partner rebate share60%Up to

Check regional eligibility and account terms

→Enter the code when you sign up: nexu888

Sign up on Bitget →Codenexu888Copied

If the explorer shows success and far more than 60 confirmations, and the contract matches, the transfer has done its part on chain. The remaining checks are on the Bitget side.

Step 3: check the address, the amount and the receiving account

Four things can still go wrong after a successful on-chain transfer.

The destination address. Compare the "to" address on Polygonscan with the address on your current Bitget deposit screen for USDC on Polygon. Bitget's deposit guide says it may generate new deposit addresses periodically and tells users not to reuse expired or outdated ones. If you copied an address from an old screenshot, that is the first suspect.

The network label. The sending platform may call this network "Polygon", "MATIC" or "Polygon PoS". What matters is that the transaction sits on the chain Polygonscan indexes. A USDC withdrawal sent on Ethereum, Arbitrum or Base would not show up there at all. The table below, from the same Bitget response, shows how different the settings are across networks, which is one reason a mismatch is easy to miss.

The amount. Exchanges often deduct a withdrawal fee before the funds leave. Compare the amount the explorer shows arriving with Bitget's minimum for the network you used. On Polygon the minimum is tiny, so this rarely bites here; on Ethereum it is about 50 times higher.

The receiving account. Bitget's mobile deposit guide has users choose the destination account, such as Spot or Funding, when they open the deposit screen, and says credited assets appear in the selected account. Before you file anything, look in both. A deposit that went to Funding while you were watching Spot looks missing but is not.

Step 4: when the contract or network is wrong

Bitget's refund guide for uncredited deposits sends these cases to a Self-Service Refund form, reached from the Deposit page on the Bitget website through "Refund of uncredited deposit". For an unsupported coin or network, the form asks for:

• the network the deposit was actually sent on;
• the token contract address, read from the explorer as in Step 1;
• the withdrawal address the funds came from, because any refund is returned to an on-chain address;
• the TxID, and nothing else in that field.

The guide sets two expectations plainly. Not every deposit is eligible, and Bitget says it cannot guarantee recovery in all cases. Processing can take up to 10 working days, depending on how complex the case is and how accurate the submitted information is.

If you are unsure which issue type applies, the form has an "other/don't know" option. For a deposit marked completed on the sending side that still has not appeared, the guide lists possible causes (a wrong or empty memo, a failed Bitget withdrawal bouncing back, or unknown reasons) and points to a support ticket with the transaction proof.

If the USDC came from another exchange

Most missing deposits start as a withdrawal from somewhere else, and that platform holds two pieces of evidence Bitget will ask for. Bitget's refund guide says the TxID can be found in your withdrawal history, and that if you cannot find it, the withdrawal platform is the one to ask. The same guide says that if you cannot confirm which network a deposit was sent on, you should check with the withdrawal platform as well.

So before you contact Bitget, open the sending platform's withdrawal record and copy three fields: the network it used, the full TxID and the amount after fees. Bitget's deposit guide says you can deposit from any external wallet or exchange, provided it supports the same network you selected on Bitget. An exchange that only offers USDC on Ethereum, for example, cannot send to your Polygon address, whatever its menu calls the network.

What not to do while you wait

Do not send the same amount again as a test. Bitget's deposit guide says a blockchain transaction cannot be cancelled or reversed once it starts. A second transfer with the same mistake doubles the problem.

Do not paste your deposit address into the contract field, or your wallet address into the TxID field. The guide warns against both.

Do not trust anyone who offers to "recover" the deposit in a direct message. Bitget's own channels for this are the refund form and the support ticket described in its help center.

The checks, in order

1. Explorer status shows success. If not, contact the sender.
2. Token contract equals 0x3c499c542cef5e3811e1192ce70d8cc03d5c3359.
3. Confirmations are above 60.
4. The "to" address equals your current Bitget Polygon USDC address.
5. The amount received is above 0.009986 USDC.
6. Look in both Spot and Funding.
7. Still missing with everything matching: support ticket with the TxID. Wrong contract or network: Self-Service Refund.

The same order works for other coins with different numbers. Our earlier Bitget SOL deposit check walks through the Solana version, where Bitget's setting was 32 confirmations. For fees, networks and other venue details, see the Bitget profile.

Quick answers

Does 60 confirmations mean 60 minutes?

No. It is 60 Polygon blocks. In our 15-minute sample, blocks came about every 1.5 seconds, which put 60 confirmations near 90 seconds. Network pace varies, so read the live count on Polygonscan rather than a clock.

Is there a fee to deposit USDC on Bitget?

Bitget's deposit guide says Bitget does not charge deposit fees, though network transaction fees may apply. The sending platform may also deduct its own withdrawal fee.

My USDC came from a bridge. Will Bitget credit it?

Only if the token that arrived is the contract Bitget lists for Polygon. Check the contract on Polygonscan as in Step 1. If it differs, use the refund form; eligibility is decided case by case.

How long does a refund take?

Bitget's guide says up to 10 working days, depending on case complexity and the accuracy of the information you submit.

What we could not verify

We did not inspect any individual customer transfer, and no Bitget account screen was opened for this article. The Polygon block timing comes from one 600-block sample on 4 November and will differ at other times. Bitget's settings were read once at 12:58 SGT and may change after publication.