USDT · Solana · SPL token
Accept USDT payments on Solana
Let buyers pay an invoice with issuer-native USDT on Solana mainnet-beta while funds go directly to your configured wallet.
GramPayBot supports issuer-native USDT on Solana mainnet-beta. The customer sends the supported SPL token to the merchant’s configured Solana wallet, while GramPayBot monitors the transfer and updates the invoice. It does not hold the payment.
- Network:
Solana mainnet-beta - Token standard:
SPL token - Receiving address:
Public Solana wallet address - Network fee asset:
SOL - USDT mint:
Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB - Decimals:
6
Which address should the merchant add?
Add a public Solana wallet address you control and have tested for SPL-token receipts. Solana public keys are displayed in base58, but appearance alone does not establish account type, ownership or token support. Do not use a fixed character-count rule as proof.
Read the Solana wallet address guide to distinguish a wallet owner, token account, associated token account and mint. GramPayBot’s payment flow uses the configured merchant wallet as recipient and the supported mint as the token identifier.
Do not paste the Tether mint as your wallet
The mint identifies USDT; the receiving address identifies the merchant. The official USDT mint is Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB. It is not your receiving wallet.
Tether lists USDT on Solana in its supported-protocols catalog. Open the mint in Solana Explorer, compare the complete value and follow the token verification checklist. A copied USDT name, logo or high activity count is not enough.
What the buyer must select
The buyer must select Solana for the USDT withdrawal. Ethereum ERC-20, TRON TRC20 and other networks are separate routes. A self-custody sender normally needs SOL for the transaction and possible token-account creation; an exchange may deduct its own fee. Do not promise a fixed network fee.
The checkout QR follows Solana Pay and contains the merchant wallet, amount, supported SPL mint and invoice reference. The wallet must still show the expected network, token, recipient and amount before approval.
How GramPayBot confirms this route
The product route is network enum solana plus token USDT. GramPayBot inspects confirmed Solana token transfers and matches the exact mint, toUserAccount, invoice amount and transaction signature. It records the destination token account separately. SOL, USDC, a look-alike mint or a transfer to another wallet does not qualify.
Open the transaction signature in Solana Explorer or Solscan and check successful execution, mint, recipient and token balance change. A screenshot or an exchange withdrawal request is not final evidence.
Wrong mint, underpayment or late payment
A token with the USDT symbol but another mint is a different asset. A transfer on another network is also a different route. Underpayments and transfers after expiry require separate review and should not be credited to another order.
For Circle-issued USDC, use the separate USDC Solana route. See the supported-routes hub for every available network.