What to Say When a Buyer Wants a Refund: Ready-to-Copy Scripts
Nobody teaches you what to say the first time a buyer DMs asking for their money back. Most creators freeze, feel guilty, and either refund everything on autopilot or ghost the message for a week and hope it goes away. Both are bad moves.
The refund conversation is a skill. And like every skill, it’s easier once you have a script. This post has four — one for each situation you’ll actually see — with the exact language you can copy, paste, and adjust.
Situation 1: “I changed my mind.”
The message reads: “Hey, I bought your set yesterday but I’d like a refund. I changed my mind.”
No specific complaint. No claim the file is broken. Just buyer’s remorse.
The wrong move: immediate refund. You’ve delivered a watermarked digital file, they’ve downloaded it (check your dashboard), and cash back after delivery sets a precedent your future self will pay. If you refund freely for change-of-heart, word gets around, and you’ll get one of these a week.
The script:
Hey [name] — I hear you. Because the files were already downloaded, I can’t refund to your card, but I can offer you store credit worth 100% of the purchase you can use toward any of my other sets. Which sounds good?
Why it works: You’re not saying no. You’re offering a real alternative. Most buyers take the credit and are happy. The ones who insist on cash back are almost always the ones you don’t want as future buyers anyway.
Situation 2: “The link is broken.”
The message reads: “I bought your set and the download link doesn’t work.”
This is the most common refund message and 80% of the time the “broken” link is fine — it’s in their spam folder, or they clicked it on their phone which blocked the download, or they entered their email wrong.
The wrong move: asking them to prove the link is broken. That’s cheap for you and expensive for them, and it makes you look defensive.
The script:
Ouch, sorry about that. I just re-sent the link to [email] — check your inbox and spam folder in the next 5 minutes. If it still doesn’t work, screenshot what you see when you click it and I’ll dig in from my end.
Why it works: You’ve fixed 80% of these tickets in one message. The other 20% who come back with a real problem now have a screenshot you can work from, and they know you’re taking it seriously.
Situation 3: “Not what I expected.”
The message reads: “I bought your set and it wasn’t what I expected. Can I get a refund?”
This one’s the trickiest. If your preview was misleading, they have a real complaint. If it wasn’t, they’re either fishing for a free set or genuinely surprised in a way that wasn’t your fault.
The wrong move: refunding without asking what they expected. You lose the opportunity to fix a preview that’s confusing to future buyers.
The script:
Sorry the set didn’t land for you. Can I ask — what were you expecting that you didn’t see? I want to make sure the preview shows the right thing to future buyers.
Then, based on their answer:
- If the preview was misleading → refund + fix the preview + thank them for the feedback.
- If the preview was accurate and they just didn’t like the set → polite decline. “I’m sorry the set wasn’t what you’d hoped for. Because it was delivered as previewed, I’m not able to offer a refund on this one, but I appreciate you letting me know what didn’t land.”
Why it works: you’ve turned a refund into product feedback. Either you learn something about your previews, or you decline with a clear reason grounded in the facts.
Situation 4: “I’ll chargeback.”
The message reads: “Give me a refund or I’ll chargeback.”
This is a threat, and threats need to be defused fast.
The wrong move: trying to talk them down or arguing the chargeback would fail. Even a chargeback you win costs you money — $15 processor fee, a hit to your chargeback ratio, and hours of your time gathering evidence. And chargebacks over a certain frequency get your Stripe/CCBill account flagged, which is a much bigger problem than a $30 loss.
The script:
Refund is on the way — should be back in your account in 3–5 business days. If there’s anything I could have shown better in the preview that would have helped you avoid this purchase, I’d genuinely appreciate the feedback.
Then process the refund immediately. Don’t argue.
Why it works: A refund costs you the sale. A chargeback costs you the sale + $15 + a hit to your processor rating + your time. The math is stark: refund immediately.
The “any feedback?” line is optional but useful. Some threat-refunders will actually give you honest feedback once they’ve gotten what they wanted. Some won’t. Either way, you’ve closed the loop cleanly and no chargeback lands.
The overall pattern
Look at the four situations side by side and a pattern emerges:
- Change of heart → credit, not cash.
- Broken link → fix first, ask later.
- Not what expected → understand before deciding.
- Chargeback threat → refund immediately.
The through-line: match the response to the situation, don’t apply one policy to all four.
What to write down BEFORE the refund message lands
Save yourself the panic-typing:
- Your default position on refunds. Public, on your storefront. “All sales final after download, but I’m happy to work with you on store credit if something isn’t right.” This alone prevents 50% of refund requests.
- Your chargeback threshold. If you know your Stripe/CCBill account starts getting flagged at 1% chargebacks, refund anything at all threatening a chargeback below that ratio.
- Your bank of copy-paste responses. Save these four scripts. Update them as you learn what works with your specific buyer audience.
The refund conversation is a skill. Now you have the scripts.
Bottom line
Four refund scripts. Four different situations. Save them, paste them, adjust the tone to your voice. The next refund message that lands, you already know what to say.
