Accept USDT payments on Polygon

GramPayBot supports USDT on Polygon PoS 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:
  Polygon PoS mainnet
• Chain ID:
  137
• Token standard:
  ERC-20
• Receiving address:
  0x + 40 hexadecimal characters
• Network fee asset:
  POL
• USDT contract:
  0xc2132D05D31c914a87C6611C10748AEb04B58e8F
• Decimals:
  6
• Representation:
  Canonical bridged through Polygon PoS

Which wallet address should the merchant add?

Add a public 0x... address you control and have tested on Polygon PoS mainnet. A wallet may show the same address on Ethereum, Base or Arbitrum, but balances and token contracts remain separate on every network.

Use 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 Polygon USDT contract

The supported contract is 0xc2132D05D31c914a87C6611C10748AEb04B58e8F with six decimals. Polygon records it as the PoS-mapped USDT representation of Ethereum USDT.

Compare the full address with the official Polygon mapped-token registry and then open that exact contract in PolygonScan. The token verification checklist explains why the USDT name or transfer count alone is not proof.

Payment and confirmation

The buyer selects USDT + Polygon and needs POL on Polygon for gas when sending from a self-custody wallet. GramPayBot matches network enum polygon, token USDT, the exact contract, recipient and invoice amount. USDT sent on Ethereum or another EVM chain does not qualify.

Open the transaction hash in PolygonScan and verify successful status, chain, contract, recipient and token amount. A bridge request or exchange withdrawal screen is not proof of receipt.

Start with a low-value invoice. For Circle-issued USDC on the same network, see USDC on Polygon. You can also compare USDT on Arbitrum or browse all supported routes.