
Resources arrived but the transfer failed: how to read a TRON receipt
Find the actual transfer’s txID, separate broadcast from solidified confirmation, and inspect contract execution. Distinguish REVERT, OUT_OF_ENERGY and an unknown outcome before paying again.
Resource delivery and transfer success are separate
Energy visible at the sending account shows its resources at query time; it does not prove that a USDT TRC-20 transfer succeeded. Rental delivery and a token transfer are separate events. Inspect the actual transfer’s transaction ID (txID), rather than substituting a payment or resource-delegation record.
Check the network, sender and intended token transfer in a trusted wallet or explorer. The field names below follow TRON documentation and do not assume a particular wallet or platform button.
Confirm the transaction, then inspect execution
A broadcast response of result: true only means that the broadcast call reported no error. It proves neither confirmation nor successful contract execution. GetTransactionById returns the transaction body; GetTransactionInfoById returns post-execution fees, resource usage, status and logs.
For final confirmation, use solidified data: /walletsolidity/gettransactionbyid for the body and, for a contract transaction, /walletsolidity/gettransactioninfobyid for the receipt. /wallet endpoints show the node’s latest view, which is not necessarily solidified. A trusted wallet support team can help interpret these states; querying them requires no signature or transfer.
Choose the next step from the result
- No receipt or missing essential result: record the outcome as unknown and keep querying the original txID. One empty response is not proof of failure. Check for the solidified transaction body first; do not immediately pay again.
- With a solidified contract receipt, check that the top-level result is not FAILED, then inspect receipt.result. SUCCESS means contract execution succeeded. To confirm the token transfer, also match the token, recipient, amount and relevant transfer logs.
- REVERT means contract execution reverted, possibly because a contract condition was unmet. Inspect contractResult and the error details. Return data may lack a readable reason; do not assume an Energy shortage.
- OUT_OF_ENERGY means execution ran out of Energy. Re-estimate using the resources, TRX and fee_limit applicable at the time. Diagnose other errors from their specific receipts; buying more Energy is not a universal fix.
Keep evidence before deciding to retry
In private records, retain the query time, network, original txID, solidified status, receipt.result, error details and resource usage. Redact screenshots before sharing; do not post full addresses or payment details in public groups. Receipt queries require neither a recovery phrase nor a private key.
Teaching scenario: Energy is sufficient now, but the original receipt says REVERT. Investigate contract conditions instead of simply adding Energy. If the outcome is unknown, keep checking the original transaction. Consider a new transaction only after confirming failure and correcting its cause. Later resource delivery cannot change an executed transaction’s result; failure can still consume resources or fees.