Search
My Cart

Buyers

Writing a strong refund request

The refund-request form has two fields. What you put in them is the only context the reviewer sees, so short, specific, and accurate gets the fastest answer.

What the form asks

On My licenses the "Request refund" action opens a slide-out form with two required fields:

  • Reason for refund - a dropdown. Pick the closest match. The category sets default expectations for what evidence will help and shapes the reviewer's read.
  • Tell us more - a free-text field, 20 to 2000 characters. Specific is faster than long: which version did you install, what failed, what did you expect.

Both fields are required. Empty or too-short submissions are rejected before they reach a reviewer.

Picking a category

Product doesn't match the description
The package's documented behaviour does not match what it actually does. Best evidence: the version installed, the documented behaviour you expected, and what happened instead. Quote the README or changelog line if you have it.
Doesn't work for my use case
The package runs but does not solve the problem you bought it to solve. Best evidence: a short description of what you needed and where it falls short.
Incompatible with my Magento version
The package failed to install, or runs but errors against your Magento version. Best evidence: Magento and package version numbers, and the exact error from the install or runtime logs.
Bought by mistake / duplicate
You bought the wrong package or edition, or already own this package on another project and bought it again. Best evidence: which package or edition you meant, or the order number of the earlier purchase. Usually approved as long as the licence has not been activated.
Reported bug, never fixed
You reported a bug to the vendor and it was not addressed within a reasonable time. Best evidence: when you reported it, where (issue tracker link, email), and the impact on your project.
Found a better alternative
You switched to a different package and no longer need this one. Best evidence: what you switched to and roughly when. Subject to the eligibility window; once installed for a while this is normally treated as a cancellation rather than a refund.
Other (please specify in details)
Anything that does not fit above. Pick this and use the details field to explain. Routed to general review.

What makes a strong details paragraph

Two or three sentences is plenty if they're specific. A useful template:

  1. Which version: "I installed 1.4.2 of acme/foo via composer require."
  2. What you tried: "Followed the README's 'Quick start' section through step 3."
  3. What happened: "Step 3 fails with Class Acme\Foo\Bootstrap not found after bin/magento setup:upgrade."

Avoid:

  • Single-word details ("broken", "does not work"). The reviewer will write back asking for the same context the form already asked for, slowing the decision down.
  • Personal attacks on the vendor. Decisions are based on whether the package matches its description and your reasonable use; tone does not change the outcome but a calm description gets reviewed faster than a wall of complaints.
  • Threats of chargeback. Use the form instead; you get a faster decision and keep your standing with your card issuer.

What happens after you submit

  • Your request shows up on your activity feed straight away.
  • Packagento typically reviews requests within a few business days. If we need more information, you will get an email asking for it; reply directly and we will continue the review.
  • When the request is approved or denied, you receive an email and the result appears on your activity feed.
  • If approved, the refund typically settles to your original payment method on the standard 5 to 10 business day card-network timeline.
  • You can withdraw a pending request from the same licence row using "Cancel request" until a decision is recorded.

Blocked on a money issue? Get in touch through our contact form with your order number - we read the queue daily and can escalate.

See also