Accept USDC payments on Base

GramPayBot supports native Circle-issued USDC on Base mainnet. The customer sends the supported ERC-20 token to the merchant’s configured EVM address, while GramPayBot monitors the payment without holding it.

• Network:
  Base mainnet
• Chain ID:
  8453
• Token standard:
  ERC-20
• Receiving address:
  0x + 40 hexadecimal characters
• Network fee asset:
  ETH on Base
• USDC contract:
  0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
• Decimals:
  6
• Representation:
  Native Circle-issued USDC

Which wallet address should the merchant add?

Add a public 0x... wallet address you control and have tested on Base mainnet. The same visible address can exist on Ethereum, Optimism, Arbitrum and other EVM networks, but the balances and contracts are network-specific.

Follow the EVM address guide to verify the 42-character address, account control and exchange-deposit rules. The receiving address belongs to the merchant; the contract below identifies USDC.

Verify native USDC, not USDbC or a copy

Circle publishes Base USDC at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 with six decimals in its official USDC contract-address catalog. Inspect the same address in BaseScan.

Do not confuse this native asset with legacy bridged USDC commonly labelled USDbC, nor with a token that copied the USDC symbol. GramPayBot expects the exact Circle contract above. Apply the full token verification checklist.

What the buyer must select

The buyer selects USDC and Base. Ethereum/ERC20, Arbitrum, Optimism and other EVM networks are separate routes even if the wallet shows the same 0x destination or aggregates balances.

A self-custody sender normally pays gas in ETH held on Base, not ETH held only on Ethereum mainnet. An exchange can deduct its own withdrawal fee. Fees change with network conditions and must not be quoted as a permanent amount.

How GramPayBot confirms the payment

The product route is network enum base plus token USDC. GramPayBot checks the Base transfer’s exact contract, configured recipient and invoice amount. A transfer of ETH, USDbC, another ERC-20 or USDC on another network is not this payment.

Open the transaction hash in BaseScan and verify successful status, Base mainnet, token contract, recipient and transfer amount. A wallet screenshot or submitted withdrawal is not final proof.

Wrong network, underpayment and late payment

An identical-looking EVM address does not guarantee recovery from the wrong network. Contract wallets and exchanges may support Base differently from Ethereum. Test the route with a low-value invoice and confirm that the received USDC can be moved.

For USDC on another network, see USDC on Ethereum or USDC on Solana. Review all pairs in the supported-routes hub.