No games played can still leave a disagreement
A booster has picked up the order. The buyer wants to cancel. No match has appeared in the history.
Has work started?
It sounds like a simple question until the policy uses a different event from the one the buyer is watching. Assignment, preparation and the first ranked match aren’t necessarily the same boundary. A fair description of a cancellation needs to identify which one the provider relied on.
We compared the published boosting refund pages of EloAscend, DuoBoost.net and BoostRoyal on 18 October 2026. This is a comparison of written stages, not three refunds we requested. Coaching and account sales sit outside the comparison.
The same cancellation request meets different wording
Read each provider’s source for the conditions attached to its entry:
| Provider | Before the boundary | After work has begun | Detail worth asking about |
|---|---|---|---|
| EloAscend | Boosting refund requests may be reviewed before work starts | Started boosting excludes full and partial refunds | What action establishes that work began? |
| DuoBoost.net | Full refund before booster pickup | Partial refund based on delivered work, subject to review | When did pickup occur and what work was delivered? |
| BoostRoyal | Its unstarted condition names no assignment and no fulfilment | The policy describes refunds for undelivered work under its conditions | What stage does the provider assign to this order? |
That table has no winner column. It compares a narrow part of three policies without pretending their products, prices or execution are identical.
The EloAscend, DuoBoost and BoostRoyal profiles provide the wider company context. Their external snapshots aren’t evidence of refund performance.
Build the timeline before arguing about the label
Our proposed order record keeps four entries separate:
- Payment accepted.
- A player assigned or the order picked up.
- The first observable service action.
- The amount of the agreed deliverable completed.
A support message can identify an assignment event. A match history can identify play. A progress record can identify work towards the agreed target. Each describes something different.
If the provider says work began during preparation, ask what preparation the term includes. If the policy doesn’t explain the boundary, say that it remains unclear. Don’t invent a first-match rule on the provider’s behalf, or accept an unexplained label as if it resolved every question.
There is a practical benefit to keeping the entries separate: the reader can follow the disagreement without first choosing a side.
A hypothetical £100 order
Suppose a fictional order costs £100. A player is assigned at 10:00 and a cancellation request arrives at 10:15. The first match would have begun at 11:00.
The amount and times are illustrative. They are not prices or events observed at any of the three companies.
The assignment timestamp may matter under one provider’s published wording. A different provider may ask whether any work has started or how much has been delivered. The timeline alone cannot supply the terms; the terms alone cannot supply the timeline.
Now change the example. The service has partly progressed before cancellation. “Half the job” still needs a unit. Half the matches is not necessarily half the purchased rank route. A partial-refund statement needs a calculation basis before the buyer can check the proposed deduction.
We haven’t assigned a refund amount to either scenario. Doing so would quietly invent a decision none of the sources establishes for this fictional order.
Published remedies and money received are separate findings
The BoostRoyal page also addresses a failure to begin within 72 hours and distinguishes eligible undelivered work from a fully consumed service. Its policy includes a condition for penalties attributed to fulfilment. EloAscend and DuoBoost publish different penalty exclusions. Those differences matter, but they do not establish that a particular penalty would be attributed to a particular order.
Even an accepted request leaves another event to record: the remedy received. Was money returned, was credit issued, or was something else agreed? An approval message is evidence of a decision, not yet of a completed payment.
This article reads commercial policies. It isn’t a determination of statutory rights in a buyer’s jurisdiction. A provider’s page is evidence of what it publishes, rather than the complete answer to every legal question.
Why we won’t turn the table into a refund score
A clearer policy is easier to interpret. That observation shouldn’t become a claim that the provider handles every dispute well.
Measuring refund performance would require actual requests with their original order terms, reasons and outcomes. It would also need enough comparable cases to avoid presenting an unusual success or failure as normal. We haven’t collected that dataset.
The reference table still does useful work. It exposes where a buyer and provider might mean different things by started, then shows which facts a moderator would need to examine.
For future reviews, describe the cancellation stage and the reason given for the decision. Keep sensitive evidence private. GameScoreLab’s review rules apply the same standard to criticism and praise.