When Base USDC Top-Up Doesn't Show Up: Reading the Deposit Transaction Before Opening a Ticket

Why a Base USDC top-up might not appear

When you top up with USDC on Base, the credit to your account depends on detecting a transfer of the correct token to the correct address on the correct network. If any of these details are off, the top-up may not be automatically credited. Before contacting support, you can inspect the deposit transaction on-chain to identify the cause.

Check the transaction status and network

First, confirm that the transaction was successful and occurred on Base.

• Look up the transaction hash on a Base block explorer (e.g., Basescan).
• Verify the transaction status is "Success" and not "Failed" or "Pending".
• Ensure the transaction was sent on the Base network, not Ethereum mainnet or another chain.

If the transaction is still pending, wait for confirmation. If it failed, the funds (minus gas) should remain in your wallet.

Verify the token contract address

USDC exists on multiple chains, and each version has a distinct contract address. On Base, the official USDC contract address is 0x833589fC3FF0bC7206D40B98481AEE1781C7bD8b. If your wallet or exchange sent a different token (e.g., USDC from another chain via a bridge, or a wrapped variant), the system may not recognize it as a valid top-up.

• Confirm the token contract in the transaction details matches the official Base USDC address.
• If you sent a different token, it may not be credited automatically. Contact support with the transaction hash.

Inspect the recipient address

Your top-up must be sent to the deposit address provided by the platform. Sending to the wrong address—even if it's a valid Base address—will not credit your account.

• Check the "To" address in the transaction matches the deposit address shown in your account.
• If you sent to a different address, the funds are likely not recoverable unless that address belongs to the platform.

Confirm the amount and decimals

USDC on Base uses 6 decimals. If you sent an amount that is too small to be detected or if the transaction involved a token with different decimals, the credit may not process.

• Verify the transferred amount in the transaction logs.
• Ensure the token uses 6 decimals (standard for USDC).

Look for internal transactions or contract interactions

If you sent USDC via a smart contract (e.g., a bridge or swap), the transfer might appear as an internal transaction or an event log rather than a direct transfer. The platform may not automatically detect such transfers.

• In the block explorer, check the "Internal Transactions" tab or look for ERC-20 token transfer events.
• If the transfer was part of a contract call, note the transaction hash for support.

What to include in a support ticket

If you've checked the above and still need help, provide:

• The transaction hash.
• The amount and token contract address.
• The destination address you used.
• A screenshot of the transaction details from the block explorer.

This information helps support locate and verify your deposit quickly.

By reading the deposit transaction first, you can often resolve the issue yourself or provide precise details to support, reducing resolution time.