How to Decline a Refund Request Politely by Email: 10 Templates

Knowing how to decline a refund request politely by email is one of the harder parts of customer support, not because the logic is complicated but because the pressure is real. The customer is already disappointed, and now you have to deliver more bad news—that the refund they expected is not coming. Done badly, a refund denial becomes a chargeback, a one-star review, or a support thread that drags on for weeks. Done well, it closes the loop without burning the relationship.

The ten templates in this post cover every common scenario: the request that arrived two weeks after your policy window closed, the product that was used and consumed before the complaint was filed, the custom work that cannot be reversed, the situation where store credit is the fair middle ground, and the requests that arrive with a chargeback threat already attached. Each template follows the same structure—acknowledge the situation, cite the policy reason once, offer what you can—and uses brackets for the parts you replace with real details before sending.

When to send this#

A refund denial email is the right reply when a request clearly falls outside your published policy and you have the documentation to back it up. It is not the right reply when the customer is describing a genuine defect, shipping damage, or something that failed on your side—those require a different response entirely.

Use these templates when:

• The request arrived after your return window closed and the product is not defective.
• The product was used, consumed, or substantially altered before the complaint was filed.
• The order was custom or personalized and the no-refund terms were disclosed at checkout.
• A digital product has been activated, accessed, or downloaded.
• The item was purchased as a final sale with a clear no-returns notice.
• You cannot verify the purchase because the customer has not provided proof.
• The customer bought through a third-party retailer and the return must run through that platform.

What a good refund denial email contains#

Most refund denials read badly for one of two reasons: they skip the acknowledgment and jump straight to the policy, or they hedge so heavily that the customer is not sure whether the answer is yes or no. A well-structured denial does neither. It opens by showing you actually read the specific request, cites the relevant policy once in plain language, states clearly what you can offer, and closes without ambiguity.

One note on apologies before the templates: do not apologize for having a return policy. You can acknowledge the customer's disappointment sincerely—that is different and appropriate. Apologizing for the policy itself implies it is unreasonable, which signals that an exception might be available and invites exactly the pushback you are trying to avoid.

The 10 templates#

Each template is formatted with labeled fields—Subject, Opening, Reason, Offer, and Close. Replace every bracketed placeholder ([ORDER NUMBER], [PURCHASE DATE], [POLICY CLAUSE], [ALTERNATIVE OFFERED]) with real details before you send. The closer the final email is to the actual situation, the better it lands.

Template 1: Request outside the return window#

The most common denial scenario. The policy was clear at purchase, the product is not defective, and the request arrived too late. Keep this one short—over-explaining reads as defensiveness, and a customer who accepted the policy at checkout already knows the window exists.

Template 2: Used and consumed product#

Applies to consumables—supplements, food, beauty products, cleaning supplies—where the customer used a meaningful portion before deciding the product did not meet their expectations. The policy reason is straightforward: the item cannot be returned in a resalable state. Acknowledge the disappointment without implying the policy is negotiable.

Template 3: Custom or personalized order#

Custom work—monogrammed items, made-to-order products, bespoke services, personalized prints—cannot be resold, which is why the policy is firm once production begins. The one exception worth calling out: if the product contains an error that is your fault rather than a preference change, that is a separate situation and needs a different reply.

Template 4: Partial refund as a compromise#

Use this when a full refund is not appropriate—because the product was partially used, or a minor issue exists that does not justify a full return—but doing nothing would be unreasonable. A partial refund acknowledges shared responsibility without setting a precedent of full reversals on policy-clear situations.

Template 5: Store credit instead of a cash refund#

Some policies allow returns within a specific window for store credit but not cash refunds. Others move to credit-only for late returns. This template is also useful when preserving the customer relationship matters more than the refund amount itself—store credit costs less than a full reversal and keeps the door open for another purchase.

Template 6: Digital product already accessed#

Software licenses, online courses, downloadable files, and e-books all share the same challenge: once accessed, they cannot be returned. This is standard practice across the industry, and most customers accept it when the policy was clear at purchase. Confirm that access actually occurred before sending this template—that record is important if the customer disputes the charge.

Template 7: Final sale or clearance item#

Final sale items carry a no-returns disclosure at the point of purchase. The main risk in this denial is a customer claiming they did not see the notice—having a link to the archived product page or a screenshot of the listing strengthens your position considerably. If the item arrived genuinely damaged, that is a separate issue from the final-sale status.

Template 8: No proof of purchase#

A refund without a verifiable transaction is a claim you cannot safely approve, both for fraud prevention and for accurate accounting. This template keeps the door open for the customer to provide documentation while being clear that you cannot proceed without it. If you can look up the order on your end using the customer's name or email, offer to do that—it is faster for everyone.

Template 9: Purchased through a third party#

Customers who bought through Amazon, Etsy, a retailer, or a distributor need to file for refunds through that platform—you may not even have the transaction in your own system. This template redirects them to the right channel without leaving them stuck, and keeps you available for anything that falls within your actual scope.

Template 10: Borderline case — declining a sympathetic request#

The hardest scenario: a customer with a legitimate reason—a family emergency, an oversight, a shipping delay outside their control—asking for an exception your policy does not allow. Acknowledging that the situation is borderline while still holding the line is the right approach. It signals the decision was considered, not automated, and that matters to how the customer receives a no.

The hard version: chargeback threats and review leverage#

Some refund requests arrive with leverage attached: a chargeback threat ('I'm disputing this with my bank'), a review threat ('I'll post a one-star review right now'), or both at once. The instinct—to panic into an exception, or to get defensive—produces worse outcomes than treating the underlying request on its merits.

The right move is to separate the threat from the complaint. Address the refund request exactly as you would without the threat attached. If the request falls outside your policy, the answer is the same whether or not a chargeback was mentioned. Then address the threat separately, briefly, and in a tone that does not match the escalation.

On chargebacks specifically: when a dispute is filed, the card issuer asks for evidence from both sides. Stripe's dispute documentation identifies written refund policy disclosure, delivery confirmation, and customer correspondence as key evidence types for merchant responses. A well-documented denial—clear policy shown at checkout, delivery record, your email thread showing you responded promptly—puts you in a much stronger position than no documentation at all. Reversing a policy-based denial purely because a chargeback was threatened only makes sense if your documentation is weak; it is not the right move when the paper trail is solid.

On review threats: resolving a refund request in exchange for a review takedown or the promise not to post is something to avoid. It can violate the terms of service of most review platforms, and a screenshot of that offer tends to become the review itself. Resolve on the merits of the order; the review is the customer's decision to make separately.

When the chargeback threat arrives in the same email as a refund request your policy does not cover, here is how to respond:

What to do if the customer does not reply#

A customer who reads a refund denial and goes quiet is, most of the time, accepting the outcome. Silence after a clear, factual denial is not a signal to re-open the thread. If you offered an alternative—store credit, a partial refund, troubleshooting help—and they did not respond, a single short follow-up after five to seven days is reasonable. If they still do not reply, the thread closes.

What you should not do is follow up with escalating offers. If the original denial offered store credit and the customer ignored it, following up with a cash refund suggests that persistence is the correct strategy. Hold the position you stated in the first reply.

Keep the denial email and the full conversation for at least as long as the relevant chargeback window for the card network. Chargeback windows vary by card type and reason code, but as a practical rule, retain records for at least six months. If a dispute is filed later, the denial email—showing you responded clearly, quickly, and with a documented policy reason—is the most useful piece of evidence you can produce.

Handling refund denials at volume#

Writing a context-specific refund denial—one that names the actual order, cites the right policy clause, and offers the appropriate alternative for that scenario—is manageable for one or two requests a week. At higher volume, the blank-page problem and the pressure of a frustrated customer waiting on a reply start compressing quality. The drafts get generic, acknowledgments get skipped, and the tone drifts toward the policy-quoting version that tends to escalate rather than close.

We build AI Emaily, an AI-native email client for Gmail, Outlook, and standard IMAP. In Copilot mode, it reads the thread and drafts a denial specific to the situation—order details, the relevant policy clause, the appropriate alternative, and a tone drawn from the personal Context you configure—then holds the draft for your review before anything sends. In Autopilot mode, clear-cut out-of-window requests with delivery confirmed can send within rules you define; anything emotionally charged stays in Copilot review. Both modes include undo and a full audit trail so you can see exactly what went out and reverse a draft if needed.