What evidence should I submit to win a chargeback dispute?

It depends on which side you’re on. If you’re the merchant, your best evidence is the material that directly answers the cardholder’s stated reason for disputing the charge. The card issuer—not your payment processor—usually makes the decision, so follow the deadline and evidence instructions in your dispute notice. (stripe.com)

Evidence to gather

• A short rebuttal: State what happened, why the charge is valid, and how each attached item supports that.
• Transaction records: Receipt or invoice, order details, date and amount, and relevant payment-authentication results.
• Proof of fulfillment: Shipping and delivery records, tracking with delivery confirmation, signed receipt, or— for digital services—account access, login or usage records, and proof the service was provided.
• Customer communications: Relevant emails, messages, support tickets, and any attempt to resolve the issue.
• Relevant terms: The return, refund, cancellation, or subscription terms the customer agreed to, plus evidence of when and how they were shown.
• Evidence tailored to the dispute reason: For example, proof of delivery for “not received”; cancellation/refund records for a cancellation claim; or evidence tying the customer to the transaction for an unauthorized-payment claim. What counts as persuasive evidence varies by reason code and card network. (stripe.com)

Make the submission easy to review

Put the evidence in chronological order, label each item, and explain the point it proves. Keep it concise and relevant; don’t rely on a tracking number alone if you can provide delivery confirmation. Some platforms allow only one submission, so check the portal and deadline before sending. (stripe.com)

If you’re the cardholder challenging a charge, the useful evidence is different: receipts or invoices, messages with the seller, proof you canceled or returned the item, and documents showing what was promised versus what happened. Contact your issuer promptly and use its requested process. In the U.S., for certain credit-card billing-error disputes, CFPB guidance says to send written notice within 60 days after the statement showing the error was sent. (consumerfinance.gov)

If you tell me whether you’re the merchant or cardholder—and the dispute reason—I can suggest a more targeted evidence checklist.

The core principle is to match your evidence to the dispute's reason code. Sources agree that the evidence required to win a dispute depends entirely on addressing that specific claim. If the cardholder says the item never arrived, a delivery record answers that. If they say they never authorized the charge, you need authentication data.

Common evidence by dispute type

• Proof of purchase and delivery (item not received): Include receipts or invoices, tracking numbers, and delivery confirmations. One source also recommends GPS-tagged carrier delivery photos where available, plus proof that the shipping address matches the cardholder's billing address or the address they gave you.
• Unauthorized or fraud disputes: Show AVS (address verification) and CVV/CVC match results. One source notes that a full street-address and ZIP match is strongest. Evidence that 3D Secure was used also helps.
• Services: Signed agreements, completion confirmations, and signed work approvals are the key items. Service disputes are where you need evidence that the work was actually done.
• Digital goods: Server or access logs showing the cardholder logged in or downloaded the product are critical.
• Customer communications: Emails, chats, or texts where the customer acknowledged receipt, expressed satisfaction, or raised no concerns before disputing. Include only the relevant excerpt, with timestamps.
• Policies shown at checkout: Screenshots of your refund, shipping, and terms pages, plus proof the customer accepted them at purchase. Card issuers generally won't follow links, so the screenshots matter.
• Additional charges (travel, hospitality): Documentation explaining the fees and the terms the customer agreed to.

How to present it

• Submit everything in your first response. Card brands generally don't allow new evidence once a case reaches arbitration, and you typically get one submission window.
• Write a concise rebuttal letter and timeline. Explain why the claim is wrong and walk through the transaction and customer contacts in order.
• Make files legible and labeled. Test screenshots at full zoom, and make sure every exhibit has a date and is referenced in your letter.
• Leave out internal notes. Your own CRM notes aren't independently verifiable, so rely on external records where you can.
• Meet the deadline. Your processor or acquirer will list a response date for each case.

Rules and acceptable evidence vary by card network and processor, and the sources above are mostly vendor blogs rather than official card-network rules. Check your processor's dispute guide for the specific reason code. Also keep in mind that even strong evidence doesn't guarantee a win.

To win a chargeback dispute, you must submit "compelling evidence" that directly contradicts the specific reason code provided by the cardholder’s bank. There is no single "magic" document; success depends on matching your evidence to the specific claim being made.

1. Identify the Reason Code

Every chargeback comes with a reason code. Before collecting documents, look at the code to understand exactly what the customer is claiming (e.g., "Item not received" vs. "Unauthorized fraud"). Do not use a generic response package.

2. Common Evidence by Category

Tailor your "evidence packet" based on the nature of the dispute:

• For "Item Not Received":
  • Proof of delivery (carrier tracking number showing "Delivered" status).
  • Documentation linking the shipping address to the address provided at checkout.
• For "Unauthorized/Fraud" (Customer claims they didn't make the purchase):
  • AVS (Address Verification System) and CVV match results from the transaction.
  • IP address and device fingerprinting data from the time of purchase.
  • Proof of prior undisputed transactions from the same user.
• For "Merchandise Not as Described/Defective":
  • Clear photos of the product before shipping.
  • Copy of your return/refund policy (highlighting the specific clause the customer violated).
  • Correspondence (emails/chat logs) showing the customer never attempted to contact you for a resolution before filing the chargeback.

3. Essential Elements of a Winning Response

When you submit your evidence, include a rebuttal letter. This is a concise cover letter that frames your evidence for the bank.

• Be Professional: Keep the tone factual, objective, and unemotional. Never accuse the customer.
• Structure Your Letter:
  • Case Details: Include the Merchant ID, Case Number, and Acquirer Reference Number (ARN).
  • Point-by-Point Rebuttal: Directly address the customer's claims using your evidence.
  • Exhibit List: Clearly list and label each attached document (e.g., "Exhibit A: Proof of Delivery").
• Formatting: Follow the card network’s guidelines. Keep files under the size limits (e.g., Visa often has a 2MB limit) and ensure everything is in a clean, readable format like PDF or JPEG.

4. Critical Best Practices

• Meet the Deadline: This is the most common reason merchants lose. If you miss the response window (often 20–45 days, but sometimes shorter), you lose automatically.
• Don't Overload: Only include evidence relevant to the dispute. A massive, disorganized file can make it harder for the reviewer to find the proof they need.
• Mask Sensitive Data: Ensure you mask full credit card numbers in your documentation (e.g., 555555******0000) to remain compliant with data security rules.

Bottom Line: Your goal is to make the decision as easy as possible for the bank representative by clearly proving the transaction was legitimate, authorized, and fulfilled as promised.

There’s no single evidence packet that wins every chargeback—the strongest response directly answers the specific reason code and the customer’s claim. Check your processor’s deadline and evidence checklist first; response windows are often short, and a late or missing response can result in an automatic loss. ¹³

Commonly useful evidence, depending on the dispute:

• Unauthorized or fraudulent payment: signed receipt or contract, AVS/CVC results, relevant device or IP data, and records connecting the customer to the purchase. Include only what’s relevant and allowed by your processor. ⁴
• Goods or services not received: shipping and delivery confirmation showing the address, or records proving the service was provided or made available. ⁴¹¹
• Refund or credit not processed: refund confirmation, processor records, and communications explaining the refund. ⁵
• Canceled service, subscription, or refund denied: the terms and cancellation/refund policy shown at checkout, proof the customer accepted them, cancellation records, and relevant customer communications. ⁴
• Duplicate or incorrect amount: receipts, invoices, and transaction records showing the correct charge and why it was made.

Make the submission easy to assess: write a brief, factual summary that addresses the dispute claim; arrange documents chronologically; label each item; and submit through your processor before its deadline. Include only evidence that supports your response, and follow the processor’s file and privacy requirements. ¹⁴

No evidence guarantees a win. If the customer’s claim is valid, accepting the dispute may be the better choice. If you share the dispute reason and whether this was a physical good, digital product, or service, I can suggest a more targeted checklist.