At a glance
Tron on Paymos
Supported assets
- USDT Tether USD
Confirmation speed
| Up to $100 | 2 blocks |
| Up to $1,000 | 6 blocks |
| Larger amounts | 19 blocks |
Paymos lets a business accept USDT TRC20 payments on Tron. The customer sends USDT over the Tron network to a dedicated invoice address, and Paymos credits the confirmed amount to the merchant's USDT balance without forced conversion.
Accept USDT TRC20 payments on Tron
Paymos accepts USDT on Tron. USDC, USD1, DAI, XAUT and native TRX are not invoice payment assets on this network in Paymos.
The merchant enables Tron and USDT for a project. At checkout, the customer selects the Tron route and sends USDT from a compatible wallet. Paymos assigns a dedicated deterministic address to the invoice, monitors the network, applies the relevant confirmation policy and updates the payment status.
This page owns the product question: how Paymos accepts USDT on Tron. For token-standard selection, read TRC20 vs ERC20 vs BEP20. For a broader network comparison, use Tron vs Ethereum fees. The complete USDT settlement model is on the USDT payments page.
What must match on a Tron invoice?
The token and network must both match the route displayed at checkout. A payer should send USDT on Tron to the address assigned to that invoice. USDT on Ethereum, BSC, TON or another blockchain is a different payment route even though the token symbol is the same.
The payer should confirm the withdrawal network in the wallet or exchange before sending. Paymos displays the final payment amount and selected network for the invoice. Native TRX is not accepted as payment, but the payer's wallet may require it to cover the blockchain network fee for sending USDT.
How do Tron confirmations work in Paymos?
Paymos uses an amount-aware confirmation policy. The required finality threshold depends on both the network and the payment amount: smaller payments can require fewer confirmations, while larger payments can require a stronger threshold.
Current blockchain conditions affect observed timing, so Paymos does not promise one fixed confirmation time for every Tron payment. A transfer can be detected before it reaches the threshold required for final settlement. The invoice status changes as the payment moves through detection, confirmation and settlement.
Who pays the Tron network fee?
The payer's wallet pays the network fee required to send USDT on Tron. Paymos does not publish one permanent fee amount because blockchain costs vary. The wallet or exchange used by the payer determines the fee required for that transfer.
Paymos covers the network cost of accepting and consolidating the payment. The standard processing fee is 1.0% per settled invoice; Enterprise pricing is 0.3% on request. There is no setup fee, monthly platform fee, monthly minimum, reserve or rolling reserve. An unpaid, expired or cancelled invoice has no Paymos processing fee. See pricing.
USDT remains USDT after settlement
USDT received on Tron contributes to the merchant's single USDT balance. Payments in USDT from other supported networks contribute to the same asset balance rather than creating a separate Tron-only balance.
Paymos does not force conversion to fiat, BTC, ETH or another asset and does not add a hidden markup to the rate. When creating a withdrawal, the merchant chooses an available payout network for USDT. Withdrawal goes to a merchant-controlled address from the whitelist; availability, minimum and network fee are shown for the selected route. That fee is subsidised: the merchant pays less to send than the transfer costs on-chain.
Tron integration options
USDT on Tron can be enabled through the standard Paymos surfaces:
- Hosted Checkout for a Paymos-hosted payment page.
- Embedded Checkout for an iframe inside a website.
- Payment Links for sending invoices without a custom checkout.
- Low-Code SDK for a browser integration.
- POS Terminal for browser-based in-person collection.
- Host-to-Host REST API for a server-controlled payment flow.
- Official CMS plugins for supported commerce platforms.
Sandbox and Production use separate credentials with the same API surface. Merchant API requests use HMAC-SHA256 authentication. Follow the quick-start guide, then enable Tron and USDT in the project configuration.
Payment status and security
The merchant receives payment status through the API and authenticated webhooks. Webhook
requests use timestamped HMAC-SHA256 authentication in the X-Webhook-Signature header.
Failed events can be replayed manually, and up to ten webhook endpoints can be configured
per merchant environment. Read webhook verification before trusting an
event.
Outgoing Paymos transactions are signed on isolated infrastructure. Withdrawals can go only to destination addresses that were added to the merchant's whitelist.
Frequently asked questions
Which assets does Paymos accept on Tron?
USDT is the only invoice payment asset Paymos accepts on Tron.
Can a customer pay a Tron invoice with TRX?
No. TRX is not an invoice payment asset in Paymos. The payer's wallet can still require TRX to cover the Tron network fee for sending USDT.
Can a customer send ERC20 or BEP20 USDT to a Tron invoice?
No. The payer must send USDT on Tron using the route displayed at checkout. USDT on another network is a different payment route.
How many confirmations does a Tron payment require?
There is no single count for every invoice. The confirmation policy depends on the network and payment amount, with stronger finality thresholds available for larger payments.
Does Paymos convert USDT received on Tron?
No. USDT remains USDT in the merchant balance. Paymos does not force conversion to fiat, BTC, ETH or another intermediary asset.
Who pays the Tron network fee?
The payer's wallet pays the fee required to send USDT. Paymos covers the network cost of accepting and consolidating the payment.