Presolve
How to Win Chargebacks: Evidence Requirements & Templates 2026 Guide

How to Win Chargebacks: Evidence Requirements & Templates 2026 Guide

Exact templates, checklists, and step-by-step process to maximize your dispute win rate

·
Presolve Team
Presolve Team
Payment Risk Experts

You just received a chargeback notification. You have 7-45 days to respond. The clock is ticking. What evidence do you need? How do you format it? What wins disputes and what gets rejected? This guide gives you the exact templates, checklists, and step-by-step process to maximize your win rate.

45%
Overall merchant win rate (varies by type)
75-80%
Win rate with automated management
7-45
Days to respond (varies by network)
$191
Average chargeback cost

Understanding Win Rates: The Reality by Dispute Type

Win rates vary dramatically based on the reason code and your evidence quality. Here's what the data actually shows:

Overall Performance:

  • Merchant average: 45% win rate across all dispute types (industry studies)
  • With manual fighting: 45-55% depending on dispute type
  • With automated chargeback management: 75-80% win rate (industry data)

By Dispute Type:

  • Product not received: 55-65% with strong delivery proof
  • Subscription canceled: 50-60% with clear cancellation terms
  • Product not as described: 40-55% (hardest to win, often subjective)
  • Fraud disputes: Lower win rates without strong device/IP evidence

The "80%" Myth:

The commonly cited "80% win rate with proper evidence" refers to merchants using automated chargeback management platforms with AI optimization, not just manually submitting good evidence. Manual submission with proper evidence typically achieves 45-55% win rates.

Visa Compelling Evidence 3.0 Impact:

For Visa reason code 10.4 (fraud), CE 3.0 doesn't guarantee a win rate. Instead, when you meet the criteria (2+ prior undisputed transactions with matching data points), liability shifts entirely to the issuer—meaning the dispute is automatically resolved in your favor. This only applies to fraud disputes, not all chargebacks.

Why Winning Matters (Beyond Just the Money)

Most merchants see chargebacks as simple revenue loss. You lose the sale, pay a fee, move on. But winning disputes isn't just about recovering that one transaction. It's about three critical business metrics.

First, the true cost. A $100 chargeback doesn't cost $100. As we detailed in our $400+ Problem guide, you lose the transaction amount, pay fees, lose the merchandise, waste operational time, and risk penalty programs. The true cost multiplier is 4.61x per dollar lost (LexisNexis Risk Solutions). Winning one $100 dispute recovers $400+ in total impact.

Second, your dispute ratio. Every chargeback counts against your ratio, even if you win. But winning reduces the financial damage and demonstrates to processors that you're actively managing disputes. Keep your ratio under 0.9% to avoid Visa's VAMP penalties starting April 2026. Learn more about how ratios are calculated and their impact.

Third, pattern recognition. Winning disputes teaches you what evidence works. You build institutional knowledge. You identify friendly fraud patterns. You refine your documentation processes. Every won dispute makes the next one easier.

The Representment Process: Step-by-Step

Before diving into evidence requirements, you need to understand the representment process. This is your formal challenge to the chargeback. Here's exactly what happens:

Day 0: Chargeback Filed

Customer contacts their bank. Bank debits the transaction from your account. You receive notification via email and dashboard. The funds are gone immediately.

Day 1-3: Review & Decide

Check the reason code to understand the claim. Determine if it's worth fighting based on transaction value, evidence availability, and win probability. Calculate ROI: recovery amount minus fees and time.

Day 3-7: Gather Evidence

Collect all relevant documentation. Transaction records, delivery confirmations, customer communications, terms of service, authentication data. Organize chronologically and by type.

Day 7-10: Build Response

Write rebuttal text. Compile evidence package. Ensure file sizes meet processor limits. Create clear, labeled attachments. Keep text under 2,000-3,000 characters for most payment gateways.

Day 10-14: Submit

Upload via Stripe Dashboard, PayPal Resolution Center, or processor interface. Double-check all attachments are included. Confirm submission before deadline. Save confirmation receipt.

Day 14-75: Bank Review

Issuing bank evaluates your evidence against cardholder's claim. This takes 60-75 days typically. You cannot submit additional evidence during this period. The decision is final from the bank's perspective.

Day 75-90: Decision

You receive the outcome. If you win, funds are returned and fees waived. If you lose, the chargeback stands. For high-value disputes, you may have 10 days to request arbitration (costly, requires strong evidence).

Response Deadlines by Network

Missing the deadline means automatic loss, regardless of how strong your evidence is. Here are the exact timeframes:

NetworkResponse TimeClock StartsPre-Arbitration
Visa30 days standard (20 days in US/Canada from July 2025)Day after notification10 days
Mastercard45 days for full representment (18 days for info requests)Day of notification45 days
American Express20 days all stagesDay of notificationN/A
Discover30 days for chargebacks (20 days for inquiries)Day of notification10 days

⚠️ Important Nuances:

These deadlines vary based on:

  • Dispute stage: Information requests have shorter windows (Mastercard: 18 days) vs. full representment (45 days)
  • Geography: Visa shortened US/Canada deadlines to 20 days effective July 2025 (previously 30 days)
  • Dispute type: Some categories have different timelines
  • Pre-arbitration: Additional 10-45 day windows after initial response (varies by network)

Always check your specific dispute notification for the exact deadline. Payment processors (Stripe, PayPal, Square) typically notify you 2-5 days after receiving the dispute from the network, which reduces your effective response window. Set internal deadlines 3-5 days before the actual deadline to ensure on-time submission.

Evidence Requirements by Dispute Type

Different dispute types require different evidence. The reason code tells you the customer's claim. Your evidence must directly refute that specific claim. For a complete breakdown of all reason codes, see our Complete Reason Codes Guide.

1. Fraudulent Transaction (Visa 10.4, Mastercard 4837, Amex F29)

Customer's claim: "I didn't make this purchase" or "My card was stolen."

Win rate: Lower than non-fraud disputes without strong evidence. Significantly improves with device fingerprinting, IP verification, and transaction history.

Visa Compelling Evidence 3.0 Benefit:

When you meet CE 3.0 criteria (2+ prior undisputed transactions with at least 2 matching data points: IP address, device ID, shipping address, or user ID), liability shifts to the issuer and the dispute is automatically resolved in your favor. This only applies to Visa reason code 10.4.

Sources: Visa CE 3.0 Guidelines, Kount, Checkout.com

Required evidence:

  • AVS/CVV match results - Proves billing address and card security code matched
  • IP address - Shows transaction originated from customer's location or known device
  • Device fingerprint - Unique device ID matching customer's previous purchases
  • 3D Secure authentication - Password/biometric verification from cardholder
  • Delivery confirmation with signature - Signed receipt at billing address
  • Customer communication - Emails, chat logs showing they acknowledged the purchase

Fraud Evidence Checklist

Required documentation for fraud disputes

  • AVS response code (must show "Match" or "Y")
  • CVV response code (must show "Match" or "M")
  • IP address with geolocation data
  • Device fingerprint or user agent string
  • Signed delivery receipt (if physical goods)
  • 3D Secure ECI indicator (if used)
  • Customer account login history
  • Screenshots of customer's usage (if digital goods)
  • Previous order history showing same IP/device

Presolve Impact: Complete documentation increases fraud dispute win rate significantly.

2. Product Not Received (Visa 13.1, Mastercard 4855, Amex C08)

Customer's claim: "I never got the product/service."

Win rate: 55-65% with strong delivery proof

Required evidence:

  • Tracking number - Must show "Delivered" status
  • Delivery confirmation - Signature required for high-value items ($250+)
  • Delivery photos - Many carriers now provide photo proof
  • Shipping address match - Proof it went to billing address or customer-provided address
  • Delivery date - Within expected timeframe on website

For digital goods/services:

  • Download logs - IP address, timestamp, file accessed
  • Access logs - Login history, usage timestamps
  • Email delivery receipt - Confirmation email was opened (use tracking pixels)
  • Usage evidence - Screenshots showing customer used the service/product

Product Not Received Evidence Checklist

Required documentation for delivery disputes

  • Tracking number with carrier name
  • Delivery confirmation screenshot from carrier site
  • Signature (required for $250+ items)
  • Delivery address matching billing or customer's request
  • Delivery photos from carrier (if available)
  • Expected delivery date from website/order confirmation
  • Customer communication acknowledging receipt
  • For digital: Download/access logs with IP and timestamp

Presolve Impact: Proper tracking and delivery proof wins 55-65% of these disputes.

3. Product Not As Described (Visa 13.3, Mastercard 4853, Amex C31)

Customer's claim: "The product was defective/different than advertised."

Win rate: 40-55% (harder to win, often subjective)

Required evidence:

  • Product description - Screenshot from your website showing exactly what was advertised
  • Product photos - Images showing the actual product matches description
  • Specifications - Technical specs, dimensions, features listed
  • Customer communication - Any emails where they confirmed satisfaction or didn't mention issues
  • Return policy - Your terms showing customer could have returned if unsatisfied
  • Customer didn't request refund/return - Proof they went straight to bank without contacting you

4. Subscription Canceled (Visa 13.2, Mastercard 4841, Amex C28)

Customer's claim: "I canceled but was still charged."

Win rate: 50-60% with clear cancellation terms

Required evidence:

  • Cancellation policy - Screenshot showing terms (e.g., "Cancel 3 days before renewal")
  • Cancellation request date - When they actually requested cancellation vs. billing date
  • Terms of service - Proof they agreed to automatic renewal terms
  • Usage after cancellation - Logs showing they used service after claimed cancellation date
  • Cancellation confirmation email - (if they canceled correctly, show they were late)

Response Templates (Modern Payment Gateway Format)

IMPORTANT: Modern payment processors (Stripe, PayPal, Square) use structured forms with text boxes, not formal letters. These templates are formatted for gateway text fields with character limits.

Template 1: Fraudulent Transaction

Response Text (Main Explanation Field):

This dispute is invalid. The cardholder authorized this transaction and received the goods/service.

TRANSACTION VERIFICATION:
• AVS Result: Match (billing address verified)
• CVV Result: Match (security code verified)
• IP Address: [IP] from [City, State] - cardholder's known location
• Device ID: [ID] - matches 3 previous undisputed purchases

DELIVERY CONFIRMATION:
• Carrier: [USPS/UPS/FedEx]
• Tracking: [NUMBER]
• Delivered: [DATE] at [TIME]
• Signature: [NAME] at billing address
• Delivery photo attached (Attachment 3)

PREVIOUS TRANSACTION HISTORY:
This customer has completed [NUMBER] previous purchases with no disputes:
• [DATE]: Order #[NUMBER] - $[AMOUNT] - Same IP/device
• [DATE]: Order #[NUMBER] - $[AMOUNT] - Same IP/device

VISA CE 3.0 QUALIFICATION:
This transaction qualifies for Compelling Evidence 3.0:
• 2+ prior undisputed transactions (120-365 days old)
• Matching IP address and device ID
• Liability should shift to issuer per Visa CE 3.0 rules

The evidence proves the cardholder authorized and received this transaction. Request chargeback reversal.

Evidence Files to Attach:

1. Transaction Authorization: AVS/CVV results, IP geolocation data

2. Delivery Confirmation: Tracking screenshot, signature, delivery photo

3. Previous Orders: Order history showing same customer/IP/device

4. Customer Communication: Any emails acknowledging receipt

Formatting Tips for Gateway Text Boxes:

  • Keep total under 2,000-3,000 characters (most gateways have limits)
  • Use bullet points for easy scanning
  • Be direct and factual, not emotional
  • Front-load the conclusion ("This dispute is invalid")
  • Stripe limit: 150,000 characters combined across all text fields

Template 2: Product Not Received

Response Text:

This claim is invalid. The product was delivered to the cardholder's address on [DATE].

DELIVERY PROOF:
• Carrier: [USPS/UPS/FedEx]
• Tracking Number: [NUMBER]
• Delivery Status: Delivered on [DATE] at [TIME]
• Delivery Address: [ADDRESS] (matches billing address)
• Signature: [NAME] (required for orders $250+)
• Delivery Photo: Package on doorstep (attached)

SHIPPING TIMELINE:
• Order placed: [DATE]
• Shipped: [DATE]
• Estimated delivery: [DATE RANGE]
• Actually delivered: [DATE] (within promised window)

ORDER CONFIRMATION:
Customer received order confirmation email on [DATE] with:
• Tracking number
• Estimated delivery date
• Shipping address confirmation

Tracking confirms successful delivery. Request chargeback reversal.

Template 3: Subscription Canceled

Response Text:

This claim is invalid. The customer was billed correctly according to our cancellation policy.

CANCELLATION POLICY:
Our terms clearly state: "Cancel at least [X] days before next billing date."

TIMELINE:
• Next billing date: [DATE]
• Customer canceled: [DATE]
• Days before billing: [NUMBER] days
• Required notice: [NUMBER] days
• Result: Cancellation was [NUMBER] days too late

SERVICE PROVIDED:
Despite late cancellation, customer continued using service:
• Logged in [NUMBER] times between cancellation request and billing date
• Accessed [FEATURE/CONTENT] on [DATES]
• Downloaded [NUMBER] files after cancellation request

POLICY ACCEPTANCE:
Customer accepted terms on [DATE] during signup:
• Checkbox: "I agree to cancellation policy"
• IP: [IP ADDRESS]
• Screenshot attached showing exact policy language at checkout

Customer failed to cancel within required timeframe per agreed terms. Request chargeback reversal.

Evidence Organization Best Practices

File Naming:

Use descriptive names: 01-AVS-CVV-Match-Results.pdf not evidence.pdf

Chronological Order:

1. Authorization (AVS/CVV, IP, 3D Secure)

2. Order confirmation

3. Shipment notification

4. Delivery confirmation

5. Customer communications

6. Usage logs (if applicable)

Highlight Key Information:

  • Circle tracking numbers in screenshots
  • Highlight matching addresses
  • Arrow pointing to signatures
  • Bold the delivery date

File Size Limits:

  • Stripe: 25MB total
  • PayPal: 50MB total
  • Square: 20MB total
  • Compress large files if needed

Common Mistakes That Lose Disputes

Mistake #1: Too Much Irrelevant Information

Don't upload your entire Terms of Service. Extract only the relevant section (e.g., cancellation policy). Reviewers won't dig through 50 pages.

Mistake #2: Missing the Deadline

Set calendar reminders 3-5 days before the actual deadline. Missing by even one hour = automatic loss. Payment processors often take 2-5 days to notify you, eating into your window.

Mistake #3: Wrong Evidence for the Reason Code

Match evidence to the claim:

  • Fraud → AVS/CVV/IP/device fingerprint
  • Not received → Delivery confirmation with signature
  • Not as described → Product description screenshots
  • Subscription → Cancellation policy and timeline

Mistake #4: Unreadable Documents

Blurry screenshots, dark scans, sideways images all get rejected. Test your uploads:

  • Screenshot at high resolution
  • Use scanners, not phone cameras (if possible)
  • Check that text is legible before uploading
  • Rotate images to correct orientation

Mistake #5: Emotional Language

Avoid: "This customer is clearly lying and trying to steal from us."

Use: "The evidence demonstrates the customer received and used the product before filing this dispute."

Stay professional and factual.

Win Rate Optimization Strategies

1. Prioritize High-Value Disputes

Not every chargeback is worth fighting. Calculate the ROI:

  • Transaction value - What you recover if you win
  • Time cost - 30-60 minutes to gather evidence and submit
  • Win probability - Based on evidence strength and reason code

Fight: $100+ transactions with strong evidence (delivery confirmation, fraud indicators)

Consider accepting: Sub-$50 transactions with weak evidence or "product quality" disputes

2. Track Your Win Rates by Reason Code

Build institutional knowledge. Which dispute types do you win? Which do you lose? Adjust your strategy:

  • If you're losing fraud disputes, improve your AVS/CVV collection
  • If you're losing "not received" disputes, add signature confirmation
  • If you're losing quality disputes, improve product descriptions and photos

3. Use Templates and Automation

Create evidence packages in advance:

  • Transaction data exports with AVS/CVV/IP automatically included
  • Order confirmations with complete product descriptions
  • Shipping confirmations with tracking embedded
  • Terms of service PDF with relevant sections highlighted

4. Document Everything Proactively

The best evidence is collected at the time of sale:

  • Require AVS/CVV for all transactions
  • Enable 3D Secure for high-risk orders
  • Send order confirmations with detailed product descriptions
  • Require signature for deliveries over $250
  • Use email tracking pixels to confirm delivery
  • Log IP addresses and device fingerprints
  • Save screenshots of product pages at time of purchase

The Financial Impact: When Winning Pays Off

Let's look at a real scenario. You process 1,000 transactions per month averaging $150 each. Your chargeback rate is 1.2%.

Without Fighting:

  • Chargebacks/month: 12 (1.2%)
  • Chargebacks fought: 0
  • Revenue recovered: $0
  • Fees recovered: $0
  • Annual recovery: $0

With Strategic Fighting:

  • Chargebacks/month: 12 (1.2%)
  • Chargebacks fought: 10 (high-value only)
  • Win rate: 60% (6 won, 4 lost)
  • Revenue recovered: $900 (6 × $150)
  • Fees recovered: $90 (6 × $15 Stripe fee)
  • Total monthly recovery: $990
  • Annual recovery: $11,880

Plus you maintain better dispute ratios, avoid VAMP penalties, and learn what fraud patterns to watch for.

Beyond Fighting: When Prevention Beats Representment

Winning chargebacks recovers revenue. But preventing them saves more time and money. The average dispute takes 45 minutes to fight properly. That's 9 hours per month in our example above (12 disputes × 45 minutes).

Instead of spending 9 hours recovering $990, what if you prevented 70% of those disputes? That's where prevention solutions come in. Analyze transaction patterns to predict which payments will likely become chargebacks. You can proactively refund suspicious orders before the dispute is filed, avoiding the chargeback entirely.

Prevention advantages:

  • Doesn't count against your dispute ratio (refund ≠ chargeback)
  • No dispute fees ($15 saved per prevented dispute)
  • No operational time spent gathering evidence
  • No risk of losing and paying double (refund + chargeback)
  • Keeps you under VAMP 0.9% threshold

Key Takeaways

  • Win rates vary by dispute type: 36.5% for fraud, 56.6% for non-fraud, 75-80% with automated management. Don't expect 80% win rates with manual submission.
  • Response deadlines vary by case type and region: Visa 20-30 days (20 days in US/Canada from July 2025), Mastercard 18-45 days (18 for info requests, 45 for full representment), Amex 20 days all stages, Discover 20-30 days. Missing any deadline = automatic loss.
  • Use modern gateway format, not formal letters: Payment processors use text boxes and structured forms. Be direct, factual, and concise.
  • Match evidence to reason code: Fraud disputes need AVS/CVV/IP. "Not received" needs delivery confirmation. "Not as described" needs product descriptions.
  • Organization matters: Clear filenames (01-AVS-CVV-Match.pdf), chronological order, highlighted key information. Make the reviewer's job easy.
  • Calculate ROI before fighting: High-value transactions with strong evidence are worth the time. Sub-$50 disputes with weak evidence often aren't.
  • Track your win rates: Learn which dispute types you win and which you lose. Adjust your prevention strategy accordingly.
  • Document proactively: Collect evidence at time of sale (AVS, CVV, IP, delivery confirmation). Don't scramble to find it when a dispute hits.
  • Understand the true cost: Winning recovers 4.61x more than just the transaction amount (LexisNexis Risk Solutions).
  • Prevention beats fighting: Even with a 60% win rate, preventing disputes saves more time and protects your dispute ratio better.

Final Thoughts

Winning chargebacks requires three things: understanding what evidence wins, organizing it professionally, and submitting it on time. Use the templates and checklists in this guide to build your evidence packages. Track your results. Refine your approach.

But remember that fighting chargebacks is reactive. The 45% average win rate means you're still losing 55% of disputes. You're spending hours gathering evidence. You're paying fees even when you win (on your ratio, if not in dollars).

The smarter strategy combines both approaches. Fight high-value disputes with strong evidence. But invest equally in prevention. Stay under the 0.9% VAMP threshold. Build better fraud detection. Improve customer communication. Make it harder for friendly fraud to succeed.

Every won dispute teaches you something. Every prevented dispute saves you time. Together, they protect your revenue and your business.

Stop Disputes Before They Happen

Presolve's AI predicts which transactions will become chargebacks before the customer calls their bank. Prevent disputes automatically while you sleep.

Learn More

Sources:

  • Visa, "Compelling Evidence 3.0 Merchant Readiness" (April 2023)
  • Mastercard, "Mastercard Chargeback Guide"
  • Verifi (Visa-owned), "Visa Compelling Evidence 3.0"
  • Ethoca (Mastercard-owned), "2023 Chargeback Outlook Report"
  • Kount, "Visa CE 3.0: Chargeback Compelling Evidence Updates for 2023"
  • Checkout.com, "Visa Compelling Evidence 3.0: New rules explained"
  • LexisNexis Risk Solutions, "True Cost of Fraud Study 2024"
  • Stripe Documentation, "Respond to disputes" and "Dispute evidence best practices"
  • Merchant Risk Council, industry research (2024-2025)
  • Juniper Research, payment fraud analysis