A USDT card top-up stuck on pending is one of the most common support tickets issuers receive. In the vast majority of cases the cause is not an issuer outage — it is either insufficient block confirmations or the wrong network being selected. Before contacting support, work through the four steps below; most issues resolve themselves.
Step 1: Look up the tx hash on a block explorer
Open your wallet or exchange withdrawal history and copy the transaction hash for the top-up. Paste it into the block explorer for the relevant network (Tronscan for TRC20, Etherscan for ERC20).
- Not found / shows pending: The transaction has not been included in a block yet. This is a wallet-side issue — wait it out.
- Shows Success but confirmation count is low: Keep waiting for more block confirmations.
- Shows Success with enough confirmations, but the card balance has not moved: Proceed to steps 2 and 3.
Step 2: Confirm you selected the correct network
USDT is a multi-chain asset. The two most common networks are TRC20 (Tron) and ERC20 (Ethereum). The card platform only recognises deposits on the specific network whose deposit address it gave you.
- You selected TRC20 on the exchange but sent funds to the issuer’s ERC20 address — the assets have arrived at an address the issuer cannot claim.
- You selected BSC (BEP20) and sent to a TRC20 address — the address format is incompatible and most transactions will fail outright. If a BSC address happens to share the same format as an ERC20 address, the assets exist on-chain but will not be credited to the card automatically.
Each card supports different networks. Check the “Network” field on the issuer’s deposit page and make sure it matches exactly before sending. For network support differences between cards, see the deposit details on /cards/mpcard and /cards/redotpay.
Step 3: Wait for enough confirmations
Many users assume that “Success on the block explorer” means the funds should already be credited, but issuers require additional safety confirmations to protect against block reorganisations:
- TRC20: roughly 20–50 confirmations, approximately 10 minutes.
- ERC20: 12+ confirmations, roughly 3 minutes under normal conditions, though high gas congestion can slow block inclusion significantly.
- BSC / Polygon etc.: policies vary by issuer; 15–30 confirmations is common.
If the on-chain confirmation count is already sufficient but the card balance still has not updated, wait another 10–15 minutes — the issuer’s system polls for incoming transactions at intervals.
Step 4: Contact support with the tx hash
If the balance still has not arrived, open a support ticket. Support staff will always ask for the tx hash — without it they cannot investigate. Include all of the following when you submit:
- Full tx hash
- Network used (TRC20 / ERC20 / other)
- The email address or account ID of the card account you intended to top up
- A screenshot from the block explorer
Wrong-network deposits are the most difficult situation. When two networks share the same address format (e.g., Ethereum mainnet and BSC), the issuer can sometimes recover funds manually, though this comes with a non-trivial fee. If the address formats are incompatible (e.g., ERC20 sent to a TRC20 address), recovery is generally not possible.
Editorial recommendations
Do: Before every top-up, compare the withdrawal address on the exchange and the deposit address on the issuer’s page character by character, and verify the network matches. The first time you use a new card, send 10–20 ₮ as a test before transferring a larger amount.
Don’t: Do not submit the same top-up repeatedly while it is still pending. Do not post your tx hash in public groups or chats looking for help — scammers impersonate support agents. Only use support channels listed on the issuer’s official website or within the official app.
Further reading: What is a U card, Issuer insolvency risk.