What to say when the refund is yours to give
Walk away with a fixed three-part message and a real deadline to close out any refund you owe, the same day you confirm it.
By Yodai · Published on September 6, 2026 · Updated on October 12, 2026
Some refunds aren't up for debate: you canceled the session, or the order arrived broken. What's not always as clear is what you actually write to the customer the moment you confirm the refund, and whether a quick 'okay, I'll refund you' is enough before you move on.
The issue isn't whether the refund is justified. It shows up again if you take too long to respond, or if you say 'let me look into it and get back to you' just to buy time. That's when the customer starts wondering if they'll actually get their money back. A customer who's unsure writes again, then again, and ends up leaving a bad review even if you refund every last cent.
A refund that's yours to give gets closed with a set message and a set timeline. You don't improvise it every time it happens, and that's the difference between a business that builds trust and one that loses it message by message.
The message that confirms, not the one that half-promises
The message needs three parts, and none of them is optional: that you're approving it, the exact amount, and when they'll see it. Leave out the "when," and you've written half a promise, and half promises lead to the follow-up message: 'So when exactly is this coming?'
You don't need to over-explain. If the mistake is on you, 'you're right' is enough. Explaining three times why the refund is owed makes you sound unsure, and if you're unsure, the customer gets unsure too. You don't need a long apology either: one line acknowledging it, then go straight to the specifics, which is what the customer actually wants to read.
Always write the amount with the dollar sign and don't round it off: '$45,' not 'about 45 dollars.' An exact number sounds like it's already settled in your system, not like you're calculating it as you type.
State the timeline using the bank's number, not your own
There are two different clocks here, and it's best not to mix them up: the time it takes you to hit the refund button, and the time it takes the customer's bank to move the money. You control the first one, and it should happen the same day. Nobody at the business controls the second one, and it varies depending on the payment method and the customer's bank.
The timeframe you give the customer is the second one, not the first. If you tell them 'you'll have it tomorrow' because that's when you process it, and the bank takes a week, you're the one who looks bad, not the bank. Always give the wider window your payment processor quotes for that payment method (for cards processed through Stripe, for example, the customer sees the refund roughly 5 to 10 business days later, depending on their bank), so that if there's any surprise, it's a good one.
This applies to PayPal just as much as to a card processor: the 'refund processed' notice the customer sees from their bank doesn't depend on what time you clicked the button, it depends on that institution's settlement cycle.
- 1Confirm the same day
A 'you're right, I'll refund you' the same day the message comes in, before it slips onto your to-do list and gets lost among ten other conversations. - 2Process it right away
From the original charge: if it was a card, use your payment processor's refund option on that charge; if it was Venmo or a bank transfer, send it back the same way, manually. Don't put it off for 'when you get a free minute': that minute turns into a week. - 3Give the bank's timeline
The one your payment processor quotes for that method: for cards through Stripe, about 5 to 10 business days. That's the bank's number, not an optimistic date you made up. - 4You close the conversation
Once the money's out, let them know before they have to ask: 'It's done, you'll have it in the next few days.' That last message is what prevents the next one.
What gets recorded without you having to do a thing
When you refund from the original charge in your payment processor, the refund gets recorded right alongside that transaction, with its date (in Stripe, also with the reason you select when you process it), so you don't have to keep a separate spreadsheet. If the customer asks weeks later, 'When exactly did you refund me?', you don't have to reconstruct it from memory: you just open it up and there it is.
That habit of always refunding from the same place, and never on the side with a standalone transfer that leaves no trace on the charge, is what will save you time on the day you have to explain a specific transaction, whether to the customer or to anyone else who asks.
- The bank already has a record of the charge, so you don't need to ask for new information
- For cards through Stripe, about 5 to 10 business days, depending on the customer's bank
- It's the route any payment processor expects
- It doesn't create a strange deposit the customer has to figure out
- Only when the refund to the original method fails. An expired card isn't enough on its own: according to Stripe, the customer's bank usually credits the refund to the card that replaced it
- You need to ask for the account and routing number and the account holder's name, and that adds a step and a day of waiting
- It still works, as long as you keep the receipt
Which one to pick: Always refund to the original method if your processor allows it: it's the one the customer recognizes, and it won't trigger a message asking where an unexplained deposit came from. Switch to a bank transfer only when the refund to the original method fails, and keep the receipt just like you would for any outgoing payment.
- You have the three-part message down: you accept, how much, and when
- The payment gets processed the same day you confirm it, not whenever you find a minute
- The timeline you give is the bank's, the one your payment processor quotes for that method, not a date you made up
- You refund to the original payment method unless the refund fails
- Your payment processor keeps the refund recorded alongside the charge, so you don't have to log it separately
Test yourself
Answer before opening each one. If one gives you trouble, go back to the section that explains it.
1. A customer writes on Monday asking for $60 back for a class you canceled because of a problem with the venue, and you already know it's your responsibility to refund it. What do you say back that same Monday?
The three-part message, the same day: that you're approving it, the exact amount of $60, and the bank's timeline, not a date you made up. Leaving it at 'let me look into it and get back to you' is exactly what triggers the follow-up message of doubt.
2. The customer paid with a card that has since expired, and you owe them $120. Which method do you use to refund them, and what do you ask for?
To the same card, from your payment processor: according to Stripe, the customer's bank usually credits the refund to the card that replaced the expired one, so you don't need to ask for anything. Only if the refund fails do you switch to a bank transfer: you'll ask for their account and routing number and the name on the account, and keep the receipt just like you would for any outgoing payment.
3. You process the refund the same day, but you don't tell the customer until they ask, three days later, whether it's done. The money did go out on time. What went wrong?
There's one message missing: letting the customer know the moment the money goes out, without them having to ask. Even when the payment was correct and on time, silence reads as a broken promise, and that's what pushes a calm customer to complain through a different channel.
That's the message for when the refund is on you. When it isn't, you need a very different one: saying no without shutting the door on the customer.
NextHow to say no without losing the customer