The typical instinct is to resist refunds. It's usually wrong. Chargeback fees ($15–25 per event), higher chargeback ratios (which threaten your processor account), and support-time costs generally exceed the refund itself. A more permissive policy is often cheaper.
# The 3-tier policy that works
Tier 1 — Automatic: Refund on request within 7 days of first charge, no questions. Under $200. Handle in the customer portal, not by ticket.
Tier 2 — Fast-track: Refund on request within 30 days for annual plans, prorated. First-time only. Support agent approves in one click.
Tier 3 — Case-by-case: Everything else. Manager-approved. Document reason in CRM.
Automate tier 1 and tier 2. Aggressive automation is what keeps this cheap.
# Why permissive costs less
Model on 1,000 disputed charges:
- Restrictive policy: 20% pursue chargeback. 200 chargebacks × $20 fee = $4,000 in fees, plus lost sale, plus processor risk.
- Permissive policy: 60% refund via self-serve. 5% still chargeback. 100 chargebacks × $20 = $2,000 fees, plus you keep the customer relationship intact for future re-conversion.
The math is not close.
# The wording that reduces abuse
Language matters:
Bad: "All sales are final." (Encourages chargeback as the only recourse.)
Bad: "30-day money-back guarantee, no questions asked." (Invites gaming.)
Good: "Not a fit? Email us in the first 30 days for a full refund. We'll ask why so we can improve." (Sets social expectation, gathers data.)
# Partial refunds — where they belong
Use partial refunds for:
- Prorated downgrades: the difference between old and new plan for remaining time.
- Service disruptions: documented outage credit as a fraction of billing period.
- Feature deprecation: if a customer bought partly for a feature you removed, refund proportionally.
Do not use partial refunds as a retention lever — "here, take 50% back to stay." Discounts on future periods work better and don't dilute your revenue recognition.
# Refund ↔ chargeback timing
If a customer files a chargeback, do not issue a refund. Both process in parallel and the customer gets double their money. Instead:
- Contact the customer immediately, offer the refund contingent on withdrawing the dispute.
- If they don't respond in 48h, fight the chargeback with evidence.
- Never issue the refund until the dispute is resolved.
Most PSPs (Stripe, Adyen) prevent parallel processing, but not all. Verify.
# Revenue recognition
Refunds reverse revenue in the period the refund occurs, not the period of the original sale, under GAAP and IFRS. Track refunds as a contra-revenue line, not a reduction to gross revenue in prior periods. Your finance team will thank you at audit.
# What to measure
- Refund rate by cohort (should be under 5% for healthy SaaS)
- Chargeback rate (must stay under 0.9% or Visa/MC threaten processor closure)
- Time-to-refund (target: under 4 business hours for tier 1)
- Refund → re-conversion rate (some refunded customers re-convert; measure it)