TRONowStart with the transaction receipt
A TRX charge does not by itself mean the Energy rental failed. Check the USDT transaction’s execution status and fee details, then compare the sending wallet and the rental delivery. Keep the rental payment hash and the USDT transfer hash separate.
Match the symptom to the next check
Stop automatic retries while the result is unclear. Use the order status and the wallet’s current resources to decide the next step.
| What you see | What to check | Next step |
|---|---|---|
| Paid, but no Energy yet | Rental order status and delivery address | Wait for delivery or contact support with the payment hash. |
| Energy in a different wallet | USDT sender versus Energy recipient | Use the intended sending wallet; do not resend an order blindly. |
| TRX charged on the USDT transfer | Receipt fee breakdown and available Energy | Distinguish Energy from Bandwidth charges. |
| Failed or pending transfer | Execution receipt and transaction status | Resolve the existing transaction before submitting another. |
Energy and Bandwidth are different
Renting Energy does not provide Bandwidth. A smart-contract transfer can consume both resources; when resources are insufficient, TRX may still be burned. Do not interpret a rental quote as an all-inclusive guarantee of the transfer’s network fees.
Check delivery before sending USDT
In wallet checkout, Energy is delivered to the payment wallet. Confirm that this is also the wallet sending USDT. TRONow currently quotes a one-hour rental. Check that delivery has completed and the resources remain available; payment success and order acceptance are intermediate steps.
Read the result instead of guessing
On Tronscan, open the USDT transaction to inspect its result and fees. Developers can use wallet/gettransactioninfobyid for the execution receipt. A transaction hash is an identifier, not proof of success. An empty result needs further checking rather than a new payment.
What to send to support
Use the website’s official contact link. Provide the order ID if available, payment transaction hash, USDT transaction hash, public wallet address and approximate time. Never send a private key, seed phrase or API secret. For an API timeout, query by client_order_id before retrying the same order.