USDT · Base · ERC-20
Accept USDT payments on Base
Let buyers pay an invoice with the supported canonical bridged USDT on Base mainnet while funds go directly to your configured EVM wallet.
GramPayBot supports canonical bridged USDT on Base mainnet. The customer sends the supported ERC-20 representation to the merchant’s configured EVM address, and GramPayBot monitors the transfer without holding the funds.
- Network:
Base mainnet - Chain ID:
8453 - Token standard:
ERC-20 - Receiving address:
0x+ 40 hexadecimal characters - Network fee asset:
ETH on Base - USDT contract:
0xfde4C96c8593536E31F229EA8f37b2ADa2699bb2 - Decimals:
6 - Representation:
Canonical bridged from Ethereum
Which wallet address should the merchant add?
Add a public 0x... address you control and have tested on Base mainnet. The same visible address may also exist on Ethereum, Optimism or Arbitrum, but balances and token contracts remain network-specific.
Follow the EVM address guide to check the 42-character address, account control and exchange support. The merchant field expects your receiving wallet, not the USDT contract.
Verify the bridged USDT contract
The supported Base contract is 0xfde4C96c8593536E31F229EA8f37b2ADa2699bb2 with six decimals. It is the canonical bridged representation from Ethereum, not a separately issuer-native Base deployment.
The maintained Superchain Token List records tokens deployed and bridged on Base. Open the exact contract in BaseScan, compare every character and follow the token verification checklist. Do not identify the asset only by its USDT ticker.
What the buyer must select
The buyer chooses USDT and Base. Ethereum/ERC20, Optimism, Arbitrum, BNB Chain and TRON are different routes even if a wallet reuses the same 0x address or shows one combined portfolio value.
A self-custody sender needs ETH held on Base for gas. ETH available only on Ethereum mainnet cannot pay a Base transaction until moved to Base. Fees vary, and an exchange may deduct its own withdrawal fee.
How GramPayBot confirms the payment
The product route is network enum base plus token USDT. GramPayBot checks the Base transfer’s exact contract, configured recipient and invoice amount. ETH, native USDC, another ERC-20 or USDT on another chain does not qualify.
Open the transaction hash in BaseScan and inspect successful status, Base mainnet, token contract, recipient and transfer amount. A bridge initiation or withdrawal request is not proof that the merchant received the payment.
Safe first invoice
Create a low-value test after the wallet or exchange explicitly shows Base support for this USDT contract. Confirm that the received balance can be moved. Wrong-network transfers, underpayments and late payments require separate handling.
For native Circle USDC on the same network, use USDC on Base. Other routes include USDT on Ethereum and USDT on Optimism. See all pairs in the supported-routes hub.