Refund Strategy (Operator Field Manual)
On this page
- Refund vs. fight is a math problem, not a policy debate
- Under $25: always refund. Over $500: fight with evidence. In between: use the grid below.
- Fast refunds prevent chargebacks. A refund costs ~3% of the transaction. A chargeback costs $50-175+.
- Customer support is your best fraud prevention tool. Empower agents to refund without escalation.
- Track refund-to-chargeback ratio. Healthy is 3-5 refunds for every 1 chargeback.
Cold reality: refund fast when it's cheaper than a chargeback, fight when evidence is strong, and route edge cases by ticket size and business model.
The Math: Refund vs. Fight
Every refund-or-fight decision comes down to expected value. Here's the calculation:
Expected cost of refunding = Transaction amount x ~3% (interchange not returned)
+ Staff time to process (~$2-5)
Expected cost of fighting = (1 - Win rate) x Transaction amount
+ Chargeback fee ($25-100, win or lose)
+ Staff time to build evidence pack (~$20-50)
+ Ratio damage (hard to quantify, real)
Worked Examples
$30 order, fraud claim, no 3DS:
| Action | Math | Total Cost |
|---|---|---|
| Refund | $30 x 3% + $3 staff time | $3.90 |
| Fight (25% win rate) | 75% x $30 + $25 fee + $25 evidence work | $72.50 |
Refund. Not even close.
$200 order, "not received," tracking confirms delivery:
| Action | Math | Total Cost |
|---|---|---|
| Refund | $200 x 3% + $3 staff time | $9 |
| Fight (70% win rate) | 30% x $200 + $25 fee + $30 evidence work | $115 |
But if you win (70% chance), you keep $200 and only pay $55 in fees and time. Expected value of fighting = (0.70 x $200) - $55 = $85 net positive. Fight.
$150 order, "not as described," no photos:
| Action | Math | Total Cost |
|---|---|---|
| Refund | $150 x 3% + $3 staff time | $7.50 |
| Fight (20% win rate) | 80% x $150 + $25 fee + $30 evidence work | $175 |
Expected value of fighting = (0.20 x $150) - $55 = -$25. Refund.
Decision Flowchart
This framework focuses on dollar amount and evidence strength. For the reason-code decision, see Chargebacks Overview. For 3DS liability considerations, see Representment.
Refund vs. Fight Grid
By Ticket Size
| Amount | Default | Exception | Reasoning |
|---|---|---|---|
| Under $25 | Always refund | None. | Fee alone exceeds the transaction. |
| $25-$50 | Refund | Fight only with delivery proof + fraud claim | Staff time to fight exceeds potential recovery. |
| $50-$100 | Usually refund | Fight with strong evidence AND high win-rate reason code | Break-even zone. Evidence quality decides. |
| $100-$500 | Evaluate evidence | Fight with strong evidence; refund if evidence is weak | Worth the effort when evidence is solid. |
| Over $500 | Fight with evidence | Refund only if zero evidence exists | Almost always worth attempting. |
By Business Model
| Type | Refund Bias | Why | What Changes the Calculus |
|---|---|---|---|
| Digital goods | High | No physical delivery proof; hard to prove customer received it | Device fingerprint matching (CE 3.0) or download logs |
| Physical goods | Low | Shipping confirmation and tracking are strong evidence | Missing or ambiguous tracking weakens your case |
| Services | Medium | Subjective "quality" claims are hard to disprove | Signed contracts, completion photos, or time logs help |
| Subscriptions | High | Cancellation-related disputes are hard to win without clear proof | Timestamped cancellation logs, confirmation emails, renewal notices |
By Dispute Reason
| Reason | Default | Win Rate | Notes |
|---|---|---|---|
| "I don't recognize this" | Refund | 5-15% | This is a billing descriptor problem. Fix the descriptor; don't waste time fighting. |
| "I cancelled" | Refund unless proof exists | 20-40% | Cancellation timestamp + confirmation email wins this. Without those, refund. |
| "Product not as described" | Evaluate | 15-30% | Product photos, specs, and terms help. Subjective claims are hard. |
| "Never received" | Fight with tracking | 60-80% | Tracking to billing address is strong evidence. This is your most winnable category. |
| "Duplicate charge" | Verify and refund if true | N/A | Easy to confirm. If it's actually a duplicate, refund immediately. |
| "Fraud" | Fight with CE 3.0 data | 10-25% (no 3DS), 50-70% (with 3DS/CE) | Device match, 3DS authentication, or Visa CE 3.0 data makes this winnable. |
By Customer History
| History | Approach | Reasoning |
|---|---|---|
| First-time customer | Lean toward refund | Preserve the relationship. A refund might earn a repeat customer. |
| Repeat customer, first dispute | Refund + benefit of doubt | Good customers have bad days. Don't punish loyalty for one incident. |
| Customer with 2+ prior disputes | Evaluate carefully, document pattern | Possible friendly fraud abuser. |
| Known abuser (3+ disputes) | Fight and document | Build a pattern file. Consider blocking from future purchases. |
Support as Risk Control
Your support team prevents more chargebacks than any fraud tool. A customer who can reach you doesn't need to call their bank.
Empowered Refund Authority
Give support agents authority to refund up to a threshold without manager approval:
| Volume | Suggested Threshold | Why |
|---|---|---|
| Under $100K/month | $50 per refund | Covers most small-ticket issues instantly |
| $100K-$500K/month | $100 per refund | Matches typical order value |
| $500K-$1M/month | $150 per refund | Reduces escalation queue |
| Over $1M/month | $200+ per refund | Speed at scale |
The math: If an agent refunds a $75 order that would have become a chargeback, you saved ~$70 (the chargeback fee + staff time for representment - the refund's interchange cost). Every "unnecessary" refund that prevents a chargeback is a net positive.
Response Time SLAs
| Channel | Target | Why This Matters |
|---|---|---|
| Phone | Under 2 minutes hold | Calling the bank takes 3 minutes. Beat them to it. |
| Live chat | Under 1 minute | Same urgency as phone. |
| Under 4 hours | Before the customer gives up and disputes. | |
| Social media | Under 2 hours | Public complaints escalate fast. |
If your response time is measured in days, customers go to their bank instead. Every day of delay increases the probability of a chargeback.
Scripts That Prevent Chargebacks
"I don't recognize this charge":
"I can see the charge you're asking about. It's from your order on [date] for [item], and it shows on your statement as [descriptor]. I can send you a copy of the receipt. Would you like a refund, or does that clear things up?"
"I want to cancel":
"Done. I've cancelled your subscription effective immediately. You won't be charged again. Your confirmation number is [number]. Is there anything else?"
"This isn't what I expected":
"I'm sorry to hear that. I can process a full refund right now, or if you'd prefer, I can send a replacement. What works best for you?"
The pattern: acknowledge the problem, offer a solution, execute immediately. No transfers, no hold music, no "let me check with my manager."
Seasonal Adjustments
Refund strategy isn't static. Adjust thresholds based on seasonal patterns:
| Season | Adjustment | Why |
|---|---|---|
| Nov-Dec (holiday) | Raise refund threshold by 50% | Gift purchases, higher returns, "I didn't order this" from gift recipients |
| Jan (post-holiday) | Keep elevated for 30 days | Returns peak in January; chargebacks from holiday purchases start arriving |
| Major sale events | Temporarily raise refund authority | Volume spike + impulse purchases = more buyer's remorse |
| Subscription renewal dates | Staff up support | Renewal batch = spike in "I cancelled" complaints |
Test to Run (2 Weeks)
Refund threshold experiment:
- Calculate your current average chargeback cost (fee + staff time + lost transaction amount x loss rate).
- For the next two weeks, refund any dispute request under that amount immediately, no questions asked.
- Track: number of refunds issued, number of chargebacks received, total cost of refunds vs. estimated cost of chargebacks those refunds prevented.
- After two weeks, compare your chargeback count to the prior two-week period.
Success criteria: Chargebacks decrease by more than refunds increase (in dollar terms). If they don't, your chargebacks aren't coming from refund-preventable scenarios, and you need to look at fraud rules or billing descriptors instead.
Metrics to Track
| Metric | What It Tells You | Target | Red Flag |
|---|---|---|---|
| Refund rate | Overall return/refund volume | Under 5% | Over 8% suggests product or expectation issue |
| Refund-to-CB ratio | Are you refunding enough to prevent disputes? | 3-5:1 | Under 2:1 means disputes are filling the gap |
| Time to refund | How fast you process | Under 3 business days | Over 7 days = customers give up and dispute |
| Win rate by reason code | Where fighting pays off | Varies by code | Below 20% on any code = stop fighting that category |
| Cost per chargeback | True all-in cost including staff time | Track, don't target | Use to calibrate your refund threshold |
The Monthly Refund Review
Once a month, spend 15 minutes on this:
- Pull your refund-to-chargeback ratio. If it's under 3:1, you're probably not refunding enough.
- Check win rate by reason code. Stop fighting categories where you win less than 20%.
- Review your top 5 refund reasons. Are they product issues, shipping issues, or billing confusion? Each has a different fix.
- Spot-check 5 chargebacks that were previously refund requests. These are failures - the customer asked for a refund, didn't get one (or got it too slowly), and disputed instead. Fix the process.
- Update your refund threshold. If your average chargeback cost has changed (new processor fees, different win rates), recalculate the break-even point.
Scale Callout
| Volume | Focus |
|---|---|
| Under $100K/month | Default to refund under $100 unless high-risk pattern. Document cancellations. Empower one person to issue refunds same-day. |
| $100K-$500K/month | Add reason-code routing. Implement renewal reminder emails for subscriptions. Capture delivery proof on all physical goods. Track refund-to-CB ratio monthly. |
| $500K-$1M/month | Dedicated dispute owner. Evidence packs by reason code. Alert on ratio approaching 0.75%. Seasonal threshold adjustments. |
| Over $1M/month | Automated refund processing for low-ticket items. Abuse detection on serial refunders. Tiered customer treatment based on history. Real-time chargeback ratio monitoring. |
Where This Breaks
- No cancellation proof for subscriptions. Add renewal reminders, cancellation confirmation emails, and timestamp logs. Without these, every "I cancelled" dispute is a loss.
- Partial shipments or backorders without customer communication. If the customer ordered 3 items and you shipped 2, tell them before they assume you shorted them.
- Refund promises without follow-through. Support says "we'll refund you" but finance never processes it. The customer waits a week, then disputes. Track refund fulfillment rate.
- International shipping with weak delivery confirmation. Domestic tracking that shows "delivered" wins cases. International tracking that shows "in transit to destination country" does not. Use a carrier with delivery confirmation in the destination country, or accept higher refund rates on international orders.
- "No refund" policies on digital goods. A strict no-refund policy doesn't prevent chargebacks; it causes them. The customer's bank doesn't care about your policy. Offer refunds within a reasonable window (24-48 hours for digital goods) and your chargeback rate will drop.
Next Steps
Setting up triage grid?
- Apply the decision flowchart - Route by amount and evidence
- Implement by scale - Right-sized for your volume
- Track monthly metrics - 15-minute monthly check
Empowering support?
- Set refund authority thresholds - Agents refund without escalation
- Set response time SLAs - Beat the bank
- Use the scripts - Consistent, fast resolution
Fighting specific disputes?
- Check reason codes - What evidence defeats each
- Build evidence packs - By reason code
- Follow representment guide - Full workflow
Related
- Refund Policy Design - Policy design and customer-facing language
- Refund Fraud - Abuse patterns and prevention
- Chargeback Prevention - Reducing disputes
- Winning Evidence - Fighting chargebacks
- Compelling Evidence - Evidence types by reason code
- Representment - Full representment guide
- Chargeback Metrics - Tracking dispute rates
- Fraud Metrics - Fraud rate tracking
- Subscriptions & Recurring - Subscription refund scenarios
- Friendly Fraud - First-party abuse patterns
- Reason Codes - Understanding dispute types
- Experimentation - Testing approaches
- Alerts Configuration - Setting up alerts
- Running Fraud Operations - Operational cadence