Settlement continuity
Rent Energy before payout or collection transactions so operations do not stop on fee shortages.
API docs live on docs.eopen.io
Use the external docs as the source of truth for endpoints, fields, auth, and migration notes. Open API docs →
EOPEN
TRON Energy API for Payment Platforms
Support merchant payouts, collection sweeps, and payment settlement on TRON with automated Energy rental and auditable on-chain records.
Design payment flowEnergy Infrastructure for TRC-20 Payments
Predictable fees for payout and collection systems
Payment platforms can use EOPEN to keep USDT settlement flows stable without maintaining large staked TRX buffers for every address.
Payouts
Merchant support
Sweeps
Collection support
API
Automated rental
Tx hash
Audit trail
Payment Platform Fit
Collection-friendly packs
Use larger packs when sweeping from cold or newly funded addresses that have not held USDT before.
Finance-ready records
Keep cost, Energy amount, order status, and delegation hash together for merchant reconciliation.
01
Payments need uptime, not fee surprises
When a merchant payout or collection sweep fails because an address lacks TRX or Energy, support and reconciliation costs rise immediately.
- Automate Energy rental before settlement transactions.
- Use webhook callbacks to update payment order state.
- Keep every Energy delegation verifiable on TRON.
02
Where it fits
EOPEN fits payment processors, merchant payout systems, collection services, and treasury flows that regularly move USDT on TRON.
- Support platform-paid or merchant-paid network fee models.
- Apply custom rates for predictable monthly volume.
- Use isolated pool options where settlement timing matters.
03
Per-transfer cost you can put in an SLA
A payment platform signs up to an SLA: merchants are promised settlement by a certain time, so a transfer that fails for want of Energy is a broken promise, not just a fee. Each USDT payout consumes about 64,285 Energy, and without delegation TRON burns roughly 6.4 TRX to push it through. Renting at around 1.5 TRX per transfer — savings of up to 80% — turns that into a fixed unit cost you can quote with confidence across millions of merchant payouts instead of padding against network surprises.
- Fixed payout cost: ~1.5 TRX rented vs ~6.4 TRX burned per transfer.
- Provision a 500,000-Energy bulk pack ahead of each payout run or collection sweep.
- Keep settlement finality on schedule so no wallet runs out of Energy mid-run.
Next steps
Lock in a fixed ~1.5-TRX cost per merchant settlement and provision a bulk pack before each payout run.
Core API flow
- 1Authenticate the platform with its API key.
- 2Request a bulk quote ahead of a payout or sweep run (a 500,000-Energy pack covers many transfers).
- 3Submit the order and delegate Energy to your payout/collection wallets before the run starts.
- 4Confirm merchant payouts on schedule within SLA, and store each delegation hash with the payment record.
Payment FAQ
Can this support merchant payout products?
Yes. Payment platforms can call the API before payout execution and store the delegation hash with the payment record.
Can we keep fees predictable for merchants?
Yes. Enterprise accounts can use tiered pricing and pre-funded balances to make fee models easier to explain.
What happens if a delegation times out?
Timeout behavior can be handled through order status and callbacks, with operational handling agreed during integration.
Migration & verifiability
Why do I see different field names in old docs vs new docs?
Field naming and migration details are maintained on docs.eopen.io. This page keeps only the payment-platform scenario overview.