TRX is the native coin of the TRON blockchain. Most people meet TRON through USDT, because a large volume of Tether transfers runs on it. Anyone who sends USDT on TRON needs TRX for fees, which means a lot of crypto users have a TRX balance sitting in their wallet. Letting them spend it at your store is a low-effort addition.
Should I accept TRX if I already accept USDT TRC20?
It is worth considering, for three reasons:
- Zero extra setup. TRX and USDT TRC20 share the same T-address and the same TronGrid connection in Payfim.
- Leftover balances. Customers often hold small amounts of TRX they would happily spend.
- Cheap for the payer. A plain TRX transfer is lighter than a token transfer, as explained below.
The downside is volatility. TRX is not a stablecoin. If you would rather receive dollars, keep USDT as the headline option and list TRX as an extra.
How are TRX transfer fees calculated?
TRON uses resources instead of a simple fee. A plain TRX transfer consumes bandwidth, roughly proportional to the size of the transaction. According to TRON's developer documentation, each account can use up to 600 free bandwidth over a rolling 24-hour window. A single ordinary transfer typically fits in that allowance, so a customer who does not send often may pay nothing at all. Once free bandwidth is used up and none is staked, the network burns a small amount of TRX from the sender instead.
Token transfers such as USDT also need energy, which is why they cost more than plain TRX transfers. OpenChainBench's September 2026 snapshot put TRON's median native transfer fee at under ten cents.
Sending TRX to an address that has never been used before can cost the sender extra, because the transfer also activates the new account. Your receiving address is reused for every order, so this only matters for the very first payment.
How quickly do TRX payments settle?
TRON produces a block about every three seconds. Payfim asks TronGrid only for transactions it reports as confirmed (solidified), which are irreversible. The wait between the customer sending and the order updating is typically under a minute, bounded mostly by how often your gateway's cron job runs (every minute is recommended; see the cron guide).
Where should I receive TRX?
Use a TRON wallet where you hold the recovery phrase: a hardware wallet with TRON support, or a well-known non-custodial TRON mobile or browser wallet. Keep a few TRX in it permanently, so that when you later move USDT out you have resources to pay for it.
Avoid exchange deposit addresses. They can change, and exchanges may apply minimum deposit rules to small payments.
TRX setup in Payfim
| Setting | What to enter |
|---|---|
| Address (TRON row) | Your T-address: T plus 33 base58 characters |
| Confirmations | Leave empty; only solidified transactions count |
| TronGrid API key | Optional, under Blockchain APIs → TRON · USDT-TRC20; free at trongrid.io |
| API endpoint (advanced) | Only if you run your own TRON node or proxy |
Switch the TRON row on, click Save wallets and Test. Each open invoice gets a TRX amount with a unique fraction (TRX shows six decimals), which is how Payfim matches payments to orders on your shared address.
Why does the TRX amount have so many decimals?
All your TRX invoices share one address. To know which order a payment belongs to, Payfim adds a tiny, unique fraction to each open invoice, worth at most about 5 cents by default. The result is an amount like 25.004213 TRX. When a transfer arrives, the gateway matches it on that exact figure, and a transaction that has paid one invoice can never be used for another.
The QR code for TRX encodes your address only. Customers should paste the amount using the copy button rather than typing it, which avoids rounding.
What can go wrong?
- Customers sending TRX from an exchange on another network. Some exchanges also offer TRX as a token on other chains. Only TRX on the TRON network is detected.
- Rounded amounts. Sending 25 TRX when the invoice says 25.004213 TRX is within tolerance; a shortfall larger than 0.5% makes the invoice underpaid.
- Throttling without a key. On busy days TronGrid can slow unauthenticated requests. Payments are not lost, just detected later. A free key avoids this.
- Confusing TRX and USDT rows. Same address, two coins. The customer picks which one at checkout, and the invoice expects that coin only.
If something does not look right, the gateway's invoice view shows the transaction hash, confirmations and amount received for each payment, with a link to the TRON explorer. That is usually enough to see whether the customer sent the wrong amount, the wrong coin or nothing at all. The troubleshooting guide lists common error messages.
Related reading
For the strategy side of TRON stablecoin payments, read accepting USDT TRC20 on your store. OpenCart and PrestaShop merchants can enable TRX from the OpenCart extension or the PrestaShop module.
Sources
Third-party facts were checked on the date shown above. Prices and features of other services change - always confirm on their official pages.