Blog
Notes from the desk that routes energy for USDT payouts. Where the guides explain how TRON prices a transfer, these posts are about running payouts with that knowledge: what to hand the API, what comes back when something goes wrong, and which failures are worth catching before money moves.
How a wallet sends USDT without holding TRX
The burn beside a USDT transfer is not a fee anybody set — it is the network charging for energy the account does not have. Rented energy, the few-minute window it arrives in, and three ways to arrange it: send it yourself, hand us a signed transaction, or charge the wallet ahead of time.
Why USDT transfers fail
Four failures a payout desk meets over and over: no energy on the sender, a recipient that has never held USDT, a frozen recipient, and a sending wallet that was never activated. How to see each of them before the money moves, and what our statuses and refund rules say when delivery does fail.
Batch USDT payouts, up to 500 at a time
One order can carry up to 500 transfers. The estimate-first workflow, the per-recipient warnings that come back with it, what partially_completed means for the invoice, and the pair — webhooks and an idempotency key — that makes a payout pipeline safe to retry.