Three things get called a refund when you rent TRX energy, and only one of them is possible.
The first is paying for energy that never arrived. That is a delivery failure and it is recoverable, because nothing on-chain happened and the obligation is still open. The second is buying energy, not using it, and wanting the difference back. That one is not recoverable at any layer, because there is nothing to give back — the capacity expired. The third is energy that arrived at the wrong address. That is recoverable in principle and depends entirely on whether the provider wants your next order more than it wants the argument.
Almost every dispute in this market is one of those three, mislabelled. Knowing which one you are in decides whether you are negotiating or explaining, and it decides what evidence you need before you write the first message.
The chain has no refund function, and that is the first thing to understand
This is the part that surprises people who rent TRX energy for the first time. TRON’s delegation mechanism has exactly two operations that matter here. One transfers energy from a staked balance to a receiving address. The other takes it back. There is no third operation, no escrow, no partial settlement, and no arbitration.
That means a refund, in the sense a card network understands it, does not exist at the protocol level. What exists is a second delegation, or a transfer of TRX, or nothing. Every commercial remedy in this market is one of those three dressed in different words.
| What the buyer wants | What is technically possible | Who can do it |
|---|---|---|
| Money back for undelivered energy | Refund of the payment, or a fresh delegation | The provider, by choice |
| Money back for unused capacity | Nothing. The capacity expired unused | Nobody |
| Reversal of a delivered delegation | Undelegation, by the delegating side only | The provider, unilaterally |
| Compensation for a failed transfer | A transfer of TRX from the provider | The provider, by choice |
Note the pattern in the third column. Every remedy belongs to the provider. The buyer has no on-chain lever at all — not a timeout, not a dispute window, not a revocation. This is unusual, and it is a direct consequence of how delegation is designed.
What undelegation actually does
When a delegating address calls UnDelegateResource, the energy disappears from the receiving address in the next block. It does not return to a pool. It does not wait. It is gone.
This has two consequences that buyers consistently get backwards.
The first is that the provider can reclaim at any moment, including in the middle of your payment batch, and there is no mechanism by which you can prevent it or lock it. A promise of seven days of energy is a commercial commitment with no protocol enforcement behind it. That is not the same as saying providers break promises — most do not, because the market punishes it. It is saying that the only thing standing between you and a withdrawal is their reputation.
The second is that energy you have already consumed cannot be reclaimed, and energy you have not consumed cannot be preserved. If you rent TRX energy for a day and use it for one transfer, the remaining capacity expires at the end of the day regardless of who does what. There is no balance, no carry-over, no credit.
Scenario one: you paid and nothing arrived
This is the only clean case, and it is clean because the failure is visible on-chain and leaves no ambiguity. It is also the case where the phrase I need a refund is factually correct, rather than a description of regret.
A delegation either exists in the receiving address’s resource record or it does not. There is no partial state and no interpretation. If you paid and the record shows nothing, the provider’s obligation is unmet and the conversation is short.
What makes it messy in practice is timing. Energy usually arrives in seconds, but during peak demand and on some providers’ queued paths it can take minutes, and a buyer who checks at the thirty-second mark concludes they have been robbed when nothing has gone wrong. Our diagnostic order for energy that appears but does not work covers the adjacent case; the rule here is simpler: check twice, twenty minutes apart, before escalating.
The economics are small per incident and large per month. At 1.17 to 2.47 TRX an order, ten missing orders is 12 to 25 TRX. It is not the money that matters, it is the pattern: a provider that misses 3% of deliveries and refunds them promptly is still costing you the retry, the delayed payment, and the reconciliation time.
Scenario two: it arrived, you did not use it
This is the case people argue hardest about and the case with the least room to argue, and it is the most common way to lose money when you rent TRX energy by the month.
You bought 65,000 units for 24 hours at, say, 50 sun. The transfer went out and used 64,285. The remaining 715 units are irrelevant. Or the transfer did not go out at all, and at the end of the 24 hours there is nothing left to return. Either way there is no residual asset — you bought capacity over a window, and the window closed.
The usual complaint is that the capacity was not usable, and the usual cause is a misreading of what a term buys. One delegation of 65,000 units supports one 64,285 transfer no matter whether the term is one hour or thirty days, because energy refills linearly over 24 hours and does not accumulate. A buyer who expected thirty transfers from a thirty-day order has bought a month of capacity and consumed one transfer’s worth. That is not a delivery failure, and no provider will refund it, because they delivered exactly what the order said.
The uncomfortable version of this: if you rent TRX energy monthly for a workload of one transfer a week, you have been overpaying by roughly a factor of four for as long as you have been doing it, and the error is not refundable because it was never an error on their side.
Scenario three: it arrived at the wrong address
This is the one that gets resolved, and it gets resolved fastest when the buyer arrives with the right framing — which is a request to redelegate, not a request to rent TRX energy again at the provider’s expense.
Delegation binds to an address. If the order specified address A and the payment came from address B, B has no energy and burns TRX at 100 sun while A holds capacity it cannot use. The provider did what was asked and the buyer asked wrong — unless the order form defaulted to a stored address, in which case the argument is about the form.
Two facts decide the outcome. First, the energy is still there and still reclaimable by the provider, so a re-delegation costs them a transaction fee and nothing else. Second, they have no obligation to do it. In practice most will, because the marginal cost is roughly zero and the alternative is a public complaint, but that is an incentive, not a right.
The framing that works is not “refund me”. It is “the capacity is idle on address A, it can be redelegated to B at no cost to you, here is the order id and both addresses”. That sentence describes a transaction the provider can make for free, which is a much easier yes than a request for money.
Why a seven-day guarantee is a business term
Many providers advertise a guarantee period, and it is worth reading it next to the mechanism above before you rent TRX energy on the strength of it. It is worth being precise about what it is, because the wording often implies more than the mechanism can deliver.
If the guarantee means “we will not undelegate before day seven”, that is a promise about behaviour, and it is unenforceable on-chain — the provider retains the ability to undelegate at any moment, and you retain no ability to stop them. What makes it credible is repeat business and the fact that a provider who reneges loses more than it gains.
If the guarantee means “if we fail to deliver, we will make you whole”, that is a service-level commitment and it is enforceable in the only way that matters here: whether they actually pay. Which is why the useful question is not what the guarantee says, but what happened the last time it was invoked.
Neither of those is the same as energy that cannot be withdrawn, and no honest provider claims otherwise. The distinction is worth keeping because it changes how much prepayment you are willing to leave on an account.
Building a dispute that gets resolved
If you have to escalate, do it once and do it properly. Four pieces of evidence, in this order. Without all four, you are making an assertion; with them, you are making a case.
- The order record. Order id, timestamp, amount paid, the address you specified, and the term you bought. This is the contract.
- The payment transaction. The TRX transfer that paid for the order, with its block height. Not a screenshot of a balance change.
- The delegation state. The receiving address’s resource record at the time of the complaint, showing either the delegated amount or its absence. This is the part most complaints omit and the part that settles the question.
- The consequence. What the failure cost you — a transfer that burned 6.43 TRX instead of 1.61, a payout that missed its window, a retry. This converts a small claim into a pattern, which is what gets attention.
Send it once, in writing, with the four items and one specific ask. A dispute that ends in “what are you going to do about it” gets a template reply; one that ends in “redelegate 65,000 units to address B or refund 2.47 TRX” gets an action.
What a fair SLA looks like when you rent TRX energy
Most providers publish almost nothing, which is why the terms tend to be discovered rather than read when you rent TRX energy for the first time. The ones worth a long relationship publish four numbers, and you can check all four against your own history.
| Term | Reasonable target | How to verify |
|---|---|---|
| Delivery time, median | Under 60 seconds | Compare payment block time to delegation block time across ten orders |
| Delivery time, worst case | Under 15 minutes | Same, taking the maximum rather than the median |
| Failed order remedy | Automatic redelegation or refund within one hour | Ask what happens, then watch what happens |
| Undelegation notice | None given, so prepay accordingly | Read the terms. If there is a notice commitment, it is a differentiator |
The fourth row is the one that matters most and gets asked least, and it is the reason prepayment size matters more than any clause when you rent TRX energy. Since nothing prevents instant undelegation, the practical protection is not a clause — it is limiting how much value sits on the account at any time. A prepaid balance equal to two days of orders is a business risk you can absorb. A prepaid balance equal to two months is a bet on someone else’s solvency.
Five things to ask before you pay
- Can you show me the delegation transaction for my last order? A provider that cannot produce a txid is reselling something it does not control.
- If delivery fails, do you redelegate or refund, and how long does it take?
- Can I specify the receiving address per order, or is it fixed to my account?
- What happens if I order 65,000 units for 30 days — how many transfers does that support?
- If I want to leave, how much of my prepaid balance comes back and when?
The fourth question is the tell. A provider who answers “one” understands the product. A provider who answers “thirty” is either confused or selling hope, and either answer is useful information before you rent TRX energy from them at volume.
For the mechanics behind all of this — how delegation, expiry and recovery actually work — the guide to renting TRX energy starts from the resource model. If you are deciding whether to stay on small volumes, where fixed costs take over is the companion piece, and the two ways people lose money renting energy covers the failure modes this article assumes you have avoided.