Accept USDC payments on Solana

GramPayBot supports Circle-issued USDC on Solana mainnet-beta. The customer sends the supported SPL token to the configured merchant wallet, and GramPayBot monitors the transfer without taking custody of the funds.

• Network:
  Solana mainnet-beta
• Token standard:
  SPL token
• Receiving address:
  Public Solana wallet address
• Network fee asset:
  SOL
• USDC mint:
  EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v
• Decimals:
  6

Which address should the merchant add?

Use a public Solana wallet address you control and have tested. A wallet address, token account and mint can all appear as base58 public keys, so syntax alone cannot tell you which role an address performs.

The Solana wallet address guide explains account owner/type checks, associated token accounts and low-value testing. The merchant field expects the wallet used by the payment flow, not the USDC mint.

Verify Circle-issued USDC, not a copy

The supported mint is EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v. Circle publishes it in the official USDC contract-address catalog. Compare every character, then inspect the same mint in Solana Explorer.

Do not search for USDC and trust the first result. Another asset can copy the name, symbol and logo. The decisive check is the full mint from Circle; supply, holders and transaction activity are only supporting signals. Follow the complete token verification guide.

What the buyer must select

The buyer selects USDC and Solana. USDC on Ethereum, Base, Polygon or another network is not the same route even when the exchange shows one combined balance. A self-custody sender normally needs SOL for fees; the amount is variable. An exchange may charge a separate withdrawal fee or impose a minimum.

The Solana Pay QR includes the merchant wallet, amount, USDC mint and invoice reference. Review these fields in the sending wallet before signing.

How GramPayBot confirms this route

The product route is solana plus USDC. GramPayBot matches a confirmed transfer’s exact mint, toUserAccount, invoice amount and transaction signature; the token-account destination is recorded separately. USDT, SOL, another mint or a payment to another recipient is not accepted as this invoice.

Use the signature in Solana Explorer or Solscan to verify execution status, mint, recipient and token balance change. A submitted exchange withdrawal can still fail and is not proof by itself.

If the recipient has no USDC token account yet

Compatible wallets can derive and create the associated token account for the merchant wallet and USDC mint. The sender may see an additional creation step or cost. This is another reason to test the exact wallet and route before offering it to customers; do not substitute the mint or an unrelated token account.

For Tether USDT, use USDT on Solana. See the complete supported-routes hub.