What Evidence Do You Need to Win a Chargeback Dispute?

Evidence is what wins chargeback disputes. Not persuasive writing, not volume, not emotional appeals—evidence. The right evidence, properly formatted and clearly presented, is the difference between recovering revenue and absorbing a loss. Yet most merchants either submit too little evidence, the wrong evidence, or evidence that's so poorly organized the reviewer can't make sense of it.

This guide covers exactly what evidence you need for each type of dispute, how to prioritize it, and the formatting standards that card networks and issuers expect.

Evidence Types by Dispute Category

Delivery Proof (Item Not Received Disputes)

When a cardholder claims they never received their purchase, delivery proof is your primary defense. The strength of your delivery evidence depends on its specificity.

• Carrier tracking records: Full tracking history from shipment to delivery, including carrier name, tracking number, and delivery date/time
• Delivery confirmation: Carrier-confirmed delivery with the delivery address matching the shipping address on the order
• Signature confirmation: Physical or electronic signature from the recipient. Required by Visa for orders over $750
• Delivery photos: GPS-tagged photos taken by the carrier at delivery (available from UPS, FedEx, Amazon, USPS in some areas)
• Proof of matching addresses: Documentation showing the delivery address matches the cardholder's billing address or the shipping address they provided

Authorization Records (Fraud/Unauthorized Transaction Disputes)

When the cardholder claims they didn't authorize the transaction, you need to prove the transaction was legitimately authorized and consistent with the cardholder's behavior.

• AVS (Address Verification) results: Full match on street address and ZIP code is the strongest; partial matches are weaker but still useful
• CVV/CVC match: Proof that the correct card verification value was provided at the time of purchase
• 3D Secure authentication: If the transaction was authenticated through 3DS (Visa Secure, Mastercard Identity Check), this is often sufficient by itself to overturn a fraud chargeback
• IP address data: The IP address used for the transaction, ideally showing it matches the cardholder's geographic region or previous transactions
• Device fingerprint: Device identifier matching previous authenticated sessions from the same account
• Account history: Previous undisputed purchases from the same account, IP, device, or delivery address

Customer Communication (All Dispute Types)

Records of your communication with the customer can be decisive evidence in any dispute category. They show the customer was engaged, informed, and had opportunity to resolve issues directly.

• Order confirmation emails: Timestamped confirmation sent to the customer's email with order details, billing amount, and terms
• Shipping notification emails: Notification with tracking number sent to the customer
• Customer support transcripts: Chat logs, email threads, or phone call records where the customer discussed the order, received assistance, or acknowledged receipt
• Refund correspondence: Any communication about refund requests, return instructions, or resolution attempts
• Post-delivery communication: Any contact from the customer after delivery (product questions, reviews, follow-up purchases) that proves they received and used the item

Terms Acceptance (Cancellation and Recurring Billing Disputes)

• Terms of service acceptance: Timestamped log showing the customer agreed to your terms, including cancellation and refund policies
• Subscription agreement: The specific recurring billing terms the customer agreed to, including amount, frequency, and cancellation procedure
• Cancellation policy disclosure: Screenshot or record of the cancellation policy as displayed at the time of purchase
• Return policy disclosure: Proof the return policy was visible during checkout and in confirmation communications

Usage Logs (Digital Products and SaaS Disputes)

• Login history: Dates, times, IP addresses, and devices used to access the account or digital product
• Feature usage data: Records of the customer actively using the service (pages viewed, actions taken, content created)
• Download records: Proof that digital content was downloaded or accessed by the customer
• API usage: For developer tools or integrations, API call logs showing active usage

IP and Device Data (Fraud Disputes)

• IP address geolocation: Showing the transaction originated from the cardholder's expected geographic area
• Device fingerprint matching: The same device used for the disputed transaction was used for previous legitimate transactions
• Browser and OS data: Matching browser/OS profiles across transactions from the same account
• VPN/proxy detection: If no VPN or proxy was used, note this—it's a positive signal

The Evidence Hierarchy: Strongest to Weakest

Not all evidence carries equal weight. Understanding the hierarchy helps you prioritize what to include and what to lead with in your rebuttal letter.

Evidence Formatting Requirements

Even strong evidence can be rendered useless by poor formatting. Card issuers and processors have specific expectations for how evidence should be presented.

General Formatting Rules

• PDF format: Submit all evidence as PDFs unless your processor specifically requires another format. PDFs are universally readable and maintain formatting across systems.
• Legible resolution: Screenshots must be readable. If a reviewer has to zoom in or squint, your evidence is working against you. Minimum 150 DPI for images.
• Highlight key information: Use red boxes or arrows to draw attention to the critical data points—delivery date, signature, IP address match. Don't make the reviewer hunt for the relevant information.
• Label every document: Name files descriptively (e.g., "Exhibit_B_UPS_Delivery_Confirmation.pdf") and reference them by label in your rebuttal letter.
• Single compiled document: When possible, compile your rebuttal letter and all exhibits into a single PDF with a table of contents. This prevents documents from being separated or lost.
• File size limits: Most processors cap submissions at 10-20MB. Compress images if needed, but maintain legibility.

Screenshot Best Practices

• Include the browser URL bar to prove the source of the information
• Include timestamps visible in the screenshot
• Capture the full context—don't crop so tightly that it looks manipulated
• If the relevant information is on a long page, take multiple screenshots and annotate each one

Common Evidence Mistakes

These are the errors we see most frequently in losing dispute responses. Each one is avoidable.

• Submitting evidence for the wrong reason code: Sending delivery confirmation for a "not as described" dispute doesn't address the actual claim. Match your evidence to the specific reason code.
• Illegible screenshots: Low-resolution captures, tiny text, or heavily compressed images that reviewers can't read. Always test your screenshots at 100% zoom on a standard monitor.
• No rebuttal letter: Submitting a stack of documents without a letter to explain what they prove and how they connect. The reviewer shouldn't have to guess your argument.
• Generic evidence packages: Using the same evidence package for every dispute regardless of reason code. Each category requires different proof points.
• Including irrelevant documents: Submitting 50 pages when 5 would do. Volume doesn't equal quality. Every document should serve a specific purpose in your argument.
• Missing timestamps: Evidence without clear dates and times (especially customer communication and delivery records) loses credibility and context.
• Unlabeled exhibits: Unnamed files or documents that aren't referenced in the rebuttal letter. If it's not connected to your narrative, it might as well not exist.
• Submitting internal notes as evidence: Internal CRM notes are not independently verifiable. They're your own records about yourself. Use external, verifiable evidence wherever possible.

Evidence Checklist by Dispute Type

Use this checklist to ensure you're gathering the right evidence for each dispute category before assembling your response.

Item Not Received (Visa 13.1 / MC 4855)

• Carrier tracking record with delivery confirmation
• Proof delivery address matches cardholder's address
• Signature confirmation (required for orders over $750)
• Shipping notification email sent to cardholder
• Order confirmation with shipping address
• Delivery photo (if available)

Unauthorized Transaction / Fraud (Visa 10.4 / MC 4863)

• 3D Secure authentication record
• AVS and CVV match results
• IP address and geolocation data
• Device fingerprint matching previous sessions
• Account history showing prior undisputed transactions
• Delivery confirmation to cardholder's address
• Post-purchase customer communication

Not as Described / Defective (Visa 13.3 / MC 4853)

• Product listing/description as displayed at time of purchase
• Product photos matching the listing
• Terms and return policy accepted at checkout
• Customer communication (any complaints and your responses)
• Refund or replacement offer documentation
• Quality control records (if applicable)

Credit Not Processed (Visa 13.6)

• Refund processing record with timestamp
• Return policy terms accepted at purchase
• Communication about the refund (emails, chat)
• If no refund was owed: evidence of policy terms and why the request was outside policy

Cancelled Recurring (Visa 13.2 / MC 4841)

• Subscription terms accepted at signup
• Cancellation policy disclosure
• System logs showing no cancellation was processed (or the cancellation date)
• Usage logs during the disputed billing period
• Pre-billing notification emails
• Billing confirmation emails

Frequently Asked Questions

Can I use screenshots of my own internal system as evidence?

Internal system screenshots (CRM records, order management logs) are acceptable as supporting evidence but are considered weaker than third-party records. A carrier's tracking page is more credible than your internal shipping log because it's independently verifiable. Use internal records to fill gaps, but lead with third-party evidence whenever possible.

How many pieces of evidence should I submit?

Quality over quantity. A typical winning response includes 4-7 pieces of relevant evidence: a rebuttal letter, 1-2 strong primary evidence items (delivery confirmation, authorization records), and 2-4 supporting documents (communication records, terms acceptance, order details). Submitting 20+ documents usually indicates you're including irrelevant material that dilutes your strongest evidence.

What if the carrier shows delivery but the customer says they didn't get it?

Carrier delivery confirmation is strong evidence, especially with a signature. If the carrier confirms delivery to the correct address, you have a solid case. Strengthen it by showing the delivery address matches the billing address (AVS), including the tracking history, and adding any delivery photos available. For orders over $750, Visa requires signature confirmation—without it, carrier tracking alone may not be sufficient.

Is email evidence admissible in chargeback disputes?

Yes. Email correspondence is widely accepted as evidence in chargeback disputes. Emails where the customer acknowledges receipt, discusses the product, requests support, or makes any statement that contradicts their dispute claim are particularly valuable. Include full email headers showing sender, recipient, date, and time. Screenshot the emails rather than forwarding them to preserve the original formatting and headers.