Accept USDT on Ethereum (ERC-20)

GramPayBot supports issuer-native USDT on Ethereum mainnet. The customer sends ERC-20 USDT to the merchant’s configured address, while GramPayBot monitors the transfer and updates the invoice. It does not hold the payment.

• Network:
  Ethereum mainnet
• Token standard:
  ERC-20
• Receiving address:
  0x + 40 hexadecimal characters
• Network fee asset:
  ETH
• USDT contract:
  0xdAC17F958D2ee523a2206206994597C13D831ec7
• Decimals:
  6

Which wallet address should the merchant add?

Add a public Ethereum address you control and have tested for ERC-20 deposits. The same visible 0x... address may also appear in Base, Optimism, Arbitrum or another EVM network, but that does not make their balances interchangeable. Record Ethereum mainnet as part of the route.

Use the EVM wallet address guide to validate the 42-character format, checksum, EOA or contract-wallet behavior and a low-value test. Never provide a seed phrase or private key.

Do not paste the Tether contract as your wallet

The USDT contract identifies the token; the merchant receiving address identifies the destination. Both begin with 0x, so copying the wrong field can look plausible. GramPayBot’s wallet field must contain your address, not 0xdAC17F958D2ee523a2206206994597C13D831ec7.

Tether lists this Ethereum contract on its supported protocols page. Open the exact address in Etherscan, compare every character and confirm that the payment’s token transfer references the same contract. Follow the full token verification checklist; a copied name or logo is not proof.

What the buyer must select

The buyer must choose Ethereum or ERC20 for the USDT withdrawal. TRC20, BEP20, Solana, Base, Optimism and Arbitrum are different routes. The sender needs enough ETH for gas when sending from a self-custody wallet; an exchange may deduct its own withdrawal fee instead.

Ethereum fees vary with network demand. The invoice should not promise a fixed gas price. The buyer should copy the address and amount directly and review the final network label before confirming.

How GramPayBot confirms this route

The expected route is the product network enum eth plus token USDT. GramPayBot checks that the on-chain transfer uses Ethereum mainnet, the supported USDT contract, the configured recipient and the invoice amount. A successful ETH transfer, a different ERC-20 token or USDT on another chain does not qualify.

Use the transaction hash in Etherscan to check status, block confirmations, recipient and the USDT transfer event. Screenshots and exchange withdrawal requests are not final evidence.

Wrong route, underpayment or late payment

A wrong-network transfer is not automatically recoverable even when the address looks identical. Underpayments and payments after invoice expiry require separate handling and should not be automatically credited to another order. Never ask a buyer for a seed phrase to investigate a payment.

If the buyer prefers another asset on Ethereum, use the separate USDC Ethereum route. See the supported-routes hub for every available network.