The transaction details
Include the business name, order or booking reference, purchase date, amount paid and item or service name. This makes the request easier to trace.
Use this guide when you know you want a refund but are unsure what details make the request clear enough for a business to act on.
Include the business name, order or booking reference, purchase date, amount paid and item or service name. This makes the request easier to trace.
Say whether the problem is a faulty item, damaged delivery, service not provided, duplicate charge, cancelled order or poor service. One clear reason is stronger than a vague complaint.
Mention receipts, photos, tracking records, screenshots or earlier support messages. If evidence is limited, keep the explanation factual and avoid overclaiming.
Ask clearly for a refund, partial refund, replacement or written response. A refund request is weaker when it never says exactly what the business should do next.
These links connect the guide to the closest template, checklist or builder so users can move to the right next step.
Continue with the closest RequestDraft page for this intent.
Open page →Continue with the closest RequestDraft page for this intent.
Open page →Continue with the closest RequestDraft page for this intent.
Open page →Continue with the closest RequestDraft page for this intent.
Open page →Ask for the outcome that fits the problem and the evidence. The builder lets you state the requested action clearly.
No. A short structured letter with the right reference details is usually stronger than a long emotional message.