A customer emails you: "I never received my order." You check tracking—delivered five days ago. You refund them, move on, and forget about it.

Three weeks later, a chargeback notification lands in your inbox. The same customer. The same order. Now you're out the product, the refund, and a chargeback fee.

This happens more often than most small ecommerce businesses realize. And here's the frustrating part: you had every opportunity to prevent it. The evidence you needed was right there in your support inbox. You just didn't capture it at the right moment.

Industry research consistently shows that chargebacks cost merchants significantly more than the original transaction value when you factor in fees, lost merchandise, and operational costs [1]. But the real damage isn't just financial. Too many chargebacks can get your payment processing suspended entirely.

Your customer support team sits at the front line of chargeback prevention. Every email exchange is a chance to gather evidence, resolve issues before they escalate, and document everything you'll need if a dispute happens anyway.

This guide walks through the exact evidence checklist your support team should follow—before a complaint becomes a chargeback.

Why Chargebacks Start in the Support Inbox (Not the Bank)

Most merchants think of chargebacks as a payment processing problem. They're not. They're a communication problem.

When a customer disputes a charge with their bank, it's usually because one of three things happened:

According to industry data, "friendly fraud"—disputes filed by customers who actually received their order—accounts for the majority of ecommerce chargebacks [2]. These aren't criminals. They're frustrated customers who took the path of least resistance.

Your support team is the last line of defense before that path leads to your bank.

The 24-Hour Window You Can't Afford to Miss

Here's what makes support-led chargeback prevention so critical: customers rarely file disputes the same day they contact you. There's typically a gap—a window where they're still hoping you'll fix the problem.

Merchants who respond to support inquiries within 24 hours see significantly fewer chargebacks than those with slower response times [3]. Not because fast responses magically solve problems, but because they keep the conversation in your inbox instead of the customer's bank portal.

Every unanswered email is an invitation to dispute.

The Chargeback-Prevention Ticket Flow

Before we get to the evidence checklist, let's map out what a chargeback-prevention support workflow actually looks like. This isn't complicated—it's just intentional.

Step 1: Identify High-Risk Tickets Immediately

Train your support team to flag certain ticket types as "chargeback risk" the moment they come in:

These aren't just complaints. They're the exact language customers use when they call their bank. If someone emails you with these phrases, you have maybe 48 hours before they escalate.

Step 2: Respond with Evidence Collection in Mind

Your first response to a high-risk ticket should accomplish three things:

For example, if someone says they never received their order:

"I'm so sorry to hear your order hasn't arrived. I want to get this resolved for you right away.I'm showing tracking number [X] was marked delivered on [date] to [address]. Can you confirm this is the correct shipping address?Also, could you check with neighbors or anyone else at the address who might have accepted the package? Carriers sometimes leave packages in unexpected spots.If we can't locate it, I'll process a replacement or refund—whichever you prefer—within 24 hours."

This response does something crucial: it creates a written record showing the customer acknowledged the delivery address, the tracking status, and your offer to resolve the issue.

Step 3: Document Everything in the Ticket

Every piece of information you gather should go into the ticket itself—not a separate spreadsheet, not your memory. When you need to fight a chargeback later, you'll pull evidence directly from this conversation.

Document:

Step 4: Offer Resolution Before They Ask the Bank

If the issue is legitimate, fix it fast. A $30 refund is infinitely cheaper than a $30 chargeback with a $25 fee, hours of dispute work, and a hit to your chargeback ratio.

If the issue is suspicious—say, a "missing" order with confirmed delivery and no response to your evidence questions—document your attempted outreach and be prepared to dispute.

The Support Team's Evidence Checklist

This is the core of chargeback prevention. Every high-risk ticket should trigger your team to capture these evidence types while the conversation is still active.

Proof of Delivery Documentation

For "item not received" disputes (often categorized under Reason Code 13.1 for Visa or similar codes for other networks), proof of delivery is your strongest defense. But "proof" means more than a tracking number.

Capture while the customer is still emailing:

Ask the customer to confirm:

A customer who confirms their address in email and then disputes claiming they never received the order has given you documented evidence for your representment.

Transaction Authorization Evidence

For "I didn't authorize this" disputes (Reason Code 10.4 for Visa fraud claims, or equivalent), you need to prove the customer made the purchase.

Capture:

In the support conversation:

Customer Communication Records

This is where support teams have a massive advantage over automated systems. Your email exchanges are evidence.

Preserve:

Key moments to document:

Product and Order Documentation

For "item not as described" disputes (Reason Code 13.3 for Visa), you need evidence of what was actually ordered and shipped.

Capture:

In the support conversation:

If a customer emails complaining that a shirt "wasn't the right color" and you have them describe it in writing, then they file a dispute claiming they never received anything—you have evidence of contradiction.

Refund Policy and Terms Acknowledgment

Many disputes happen because customers forgot or ignored your policies.

Document:

This evidence matters most for "I returned it but didn't get a refund" disputes, or when customers try to return items outside your window and then dispute instead.

Evidence for Digital Goods and SaaS

If you sell digital products or software subscriptions, your evidence requirements differ from physical goods. You can't prove delivery with a tracking number—but you can prove usage.

Capture:

For subscription disputes, document the original signup, any renewal notifications sent, and records of the customer using the service between billing dates. A customer who logged in and used your software three times in the billing period will have a harder time claiming they didn't authorize the charge.

The Billing Descriptor Problem (and How to Fix It)

Here's a chargeback trigger that has nothing to do with support quality: customers don't recognize the charge on their statement.

Your billing descriptor—the name that shows up on credit card statements—might say something like "STRIPE* YOURCOMPANY" or your legal business name that customers have never seen. They see an unfamiliar charge, assume fraud, and dispute.

Your support team should:

If someone emails asking "what is this charge for," you have about 12 hours before they call their bank. Make sure the answer is clear and immediate.

Refund vs. Dispute: The Decision Framework

Not every complaint should end in a refund. And not every refund request should be granted just to avoid a dispute. Here's how your support team should decide:

Refund Immediately When:

Investigate Further When:

Prepare for Dispute When:

Document your decision in the ticket. If you end up fighting the chargeback, you'll need to explain why you didn't refund—and "they stopped responding after I offered a full refund" is a compelling reason.

What to Capture in Real-Time (Before They Stop Responding)

Once a customer files a dispute, they often go silent. The bank handles it now. You've lost your chance to gather evidence directly.

That's why the critical window is while they're still emailing you. Use that time to get:

Confirmations on record:

Photos and documentation:

Resolution acceptance:

If they accept your resolution in writing and then dispute anyway, you have evidence that the issue was already resolved.

Building Dispute-Ready Documentation into Daily Operations

Chargeback prevention isn't a separate process. It's embedded in how your support team handles tickets every day.

Create Templates That Collect Evidence

Your saved replies for common issues should include evidence-gathering questions by default:

For "I never received my order":

For "I don't recognize this charge":

For "This isn't what I ordered":

Train for Dispute Awareness

Every support team member should understand:

This isn't about turning your support team into fraud investigators. It's about giving them the awareness to protect your business while still delivering great service.

Audit High-Risk Tickets Weekly

Spend 15 minutes each week reviewing tickets that were flagged as chargeback risks:

When the Dispute Happens Anyway

Sometimes you do everything right and the chargeback still comes. Here's what your support documentation gives you:

For representment (fighting the chargeback):

What payment processors want to see:

Your support inbox is a goldmine of dispute evidence—but only if you captured it when it mattered.

Quick-Reference Evidence Checklist

Here's a condensed checklist your team can reference for every high-risk ticket:

For "Item Not Received" Claims:

For "Unauthorized Transaction" Claims:

For "Item Not as Described" Claims:

For Digital Goods/SaaS:

Your Next Step

Chargeback prevention isn't about complex software or fraud detection algorithms. For most small ecommerce businesses, it's about responding fast, asking the right questions, and documenting everything.

Your support team already has the skills to do this. They just need the framework.

If your current support setup doesn't include chargeback-prevention training or consistent evidence capture, you're leaving money (and your payment processing relationship) at risk.

Evergreen Support provides email-first support coverage with trained agents who follow a dispute-prevention SOP—so you're protected before chargebacks happen, not scrambling after. Book a call to learn how we can help your team capture the evidence that keeps your business safe.

Frequently Asked Questions

How quickly do I need to respond to prevent a chargeback?

Most customers wait at least 24-48 hours before escalating to their bank, which means responding within a few hours gives you the best chance to resolve the issue directly. Research consistently shows that sub-24-hour response times significantly reduce dispute rates [3]. Once a customer decides to file a dispute, they rarely wait for your email.

Can I fight a chargeback if I already issued a refund?

Yes, and this happens more often than you'd expect. If a customer accepts your refund and then also files a dispute, you have strong evidence for representment. Document the refund date, amount, and the customer's acceptance in writing. Submit this along with proof that the refund was processed—most card networks consider this double-dipping and will rule in your favor.

What's the difference between a chargeback and a refund request?

A refund request comes directly to you, and you control the outcome. A chargeback goes through the customer's bank, costs you fees regardless of outcome, counts against your chargeback ratio, and can threaten your payment processing if the ratio gets too high. Always try to resolve issues via refund before they become disputes—it's cheaper and less damaging.

How long do I have to respond to a chargeback?

Typically 7-30 days depending on the card network, but check your payment processor's notification for the exact deadline. However, the real deadline that matters is before the chargeback is filed. Once you receive the notification, you're already on defense. Proactive support practices prevent chargebacks; representment just tries to recover from them.

What is a good chargeback win rate?

Industry averages for representment success hover around 20-30%, though merchants with strong documentation practices can achieve higher rates. The more important metric is your chargeback ratio—most processors want this below 1% of transactions. Winning disputes helps, but preventing them in the first place is far more effective for protecting your merchant account.

Should I blacklist customers who file chargebacks?

Consider it carefully. Some chargebacks are legitimate (actual fraud, genuine non-delivery). But customers who file friendly fraud disputes—especially after accepting a resolution—should be flagged. Many merchants maintain internal lists of customers who have filed questionable disputes and decline future orders from them. Your payment processor may also provide fraud prevention tools that help identify repeat offenders.

Experience, Expertise, Authority, and Trust

This guide was developed by Evergreen Support's team, which specializes in email customer support for small ecommerce and SaaS businesses. Our agents handle thousands of support tickets monthly and are trained in chargeback-prevention protocols that protect our clients' payment processing relationships. We work directly with business owners who've experienced the cost of preventable disputes—and who now rely on systematic evidence capture to avoid them.

Cited Works

[1] LexisNexis Risk Solutions — "True Cost of Fraud Study." https://risk.lexisnexis.com/insights-resources/research/true-cost-of-fraud-study

[2] Visa — "Visa Dispute Monitoring Program Guidelines and Merchant Resources." https://usa.visa.com/support/small-business/dispute-resolution.html

[3] Merchant Risk Council — "Global Fraud and Payments Survey." https://merchantriskcouncil.org/resource-center/surveys