Chargeback Evidence: The Complete Submission Guide

Why Evidence Quality Determines Outcome

Chargeback disputes are resolved by card network analysts reviewing submissions from both sides — the issuing bank (on behalf of the cardholder) and the acquiring bank (on behalf of the merchant). The analyst is not conducting an investigation; they are reviewing evidence against a defined framework of what constitutes a valid response for the specific reason code.

This means: submitting the wrong type of evidence for a reason code is nearly always unsuccessful, even if the evidence is compelling in isolation. A detailed product description submitted in response to a "goods not received" dispute doesn't address the allegation. A delivery confirmation submitted in response to an "unauthorised transaction" dispute doesn't address the fraud claim. The evidence must match the reason code.

Analysts also process high volumes of cases under time pressure. A well-organised submission — clearly labelled exhibits, explicit connections between evidence and the claim, a concise summary — outperforms a comprehensive but poorly organised package. Length is not a proxy for strength.

Evidence for Goods Not Received Disputes

Applicable reason codes: Visa 13.1, Mastercard 4855, Amex C08, Discover RG. These are consistently the most common dispute category for physical goods merchants — and among the most winnable with proper documentation.

Primary evidence (required where available):

• Carrier tracking record: The complete tracking history from the carrier (UPS, FedEx, USPS, DHL, etc.) showing the package was scanned at delivery. Include the URL or a PDF screenshot of the carrier's tracking page, not just the tracking number. The tracking record should show the delivery date, delivery address, and delivery confirmation.
• Signature confirmation record: If the delivery required a signature, include the signed delivery record with the recipient's signature and name. This is the strongest possible delivery evidence — it's a physical record that someone at the address accepted the package.
• Order confirmation: The order confirmation email or page showing what was ordered, the shipping address, the order date, and the order total. This establishes the transaction facts.

Supporting evidence:

• Delivery confirmation notification: The automated email or SMS sent to the cardholder confirming delivery, timestamped to the delivery event. Demonstrates the cardholder was notified.
• Post-delivery cardholder contact: Any support ticket, email, or chat transcript where the cardholder contacted you after the delivery date — about the product, the order, or anything else. Post-delivery contact is strong evidence the cardholder knew the order arrived.
• Proof of address match: Confirmation that the shipping address entered at checkout matches the address shown in the carrier's delivery record. If the cardholder claims non-receipt to an address they provided, this establishes the package went where they directed it.

For digital goods (no physical delivery):

• IP address of purchase with geolocation data
• Device fingerprint used to access the purchased content
• Account creation record with the email used for purchase
• Post-purchase login timestamps (proving the account was accessed after purchase)
• Download history or feature usage logs showing the product was accessed
• Any support interaction about the product after purchase

Evidence for Unauthorised Transaction Disputes

Applicable reason codes: Visa 10.4, Mastercard 4837/4840, Amex F29/F24, Discover UA01/UA02. These fraud-coded disputes are the hardest to win without 3D Secure authentication — but are winnable with strong evidence of cardholder involvement.

If 3DS2 authentication was used (strongest possible position):

• 3DS2 authentication record with the ECI (Electronic Commerce Indicator) value and authentication value (CAVV/AAV). This single piece of evidence shifts liability to the issuer and should end the dispute in the merchant's favour in most cases.

Without 3DS authentication:

• IP address record: The IP address used to place the order, with geolocation data showing it is consistent with the cardholder's billing address location. An IP address in the same city or region as the billing address supports authorisation.
• Device fingerprint: The device used for the disputed transaction, ideally matching the device used for prior authenticated sessions on the same account. Identical device fingerprints across multiple sessions establish a pattern of legitimate access.
• AVS match: Confirmation from your payment processor that the address entered at checkout matched the card's registered billing address. AVS match is not conclusive but is a positive authorisation signal.
• CVV match: Confirmation that the CVV entered at checkout was correct. Physical knowledge of the CVV is typically required for a cardholder in possession of their card.
• Prior transaction history: Record of previous purchases from the same card number at your merchant — especially prior purchases with no associated disputes. Establishes an existing customer relationship.
• Post-purchase cardholder interactions: Any contact from the cardholder after the disputed transaction: delivery confirmation acceptance, support inquiries, product reviews, or any communication that implies awareness of the purchase.

Visa's Compelling Evidence 3.0 framework (applicable to 10.4 disputes) allows merchants to demonstrate that the same card was used for two or more undisputed prior transactions at the same merchant, with at least two matching data elements (IP address, device fingerprint, delivery address, or account credentials). If this evidence is available, it can shift liability even without 3DS authentication.

Evidence for Not as Described Disputes

Applicable reason codes: Visa 13.3, Mastercard 4853, Amex C31/C32, Discover RM. These disputes claim the product or service didn't match what was advertised. Strong product documentation wins most of these.

• Product listing screenshot: A screenshot or PDF of the exact product page as it appeared at time of purchase, including all photographs, specifications, dimensions, materials, and any relevant disclosures. The listing should establish what the cardholder saw before buying.
• Order confirmation: Shows precisely what the cardholder ordered — confirming they selected the item that was shipped, not a different variant.
• Packing or shipping record: Invoice, packing slip, or warehouse record showing the exact item shipped. Ideally includes the item SKU or identifier that maps to the listed product.
• Photographs of the shipped item: Photos of the product before packaging (if available in your fulfilment workflow) confirming condition and matching the listing.
• Pre-purchase communication: Any email or chat exchange where the cardholder asked questions about the product before purchasing — and your responses confirming product specifications. Demonstrates the cardholder was informed about what they were buying.
• Post-purchase communication: Any support interaction about the product, including customer complaints. If the customer complained about quality but did not return the item or pursue a return through your normal process, this can be relevant context.

Evidence for Cancelled Subscription Disputes

Applicable reason codes: Visa 13.2, Mastercard 4841, Amex C28/C18, Discover AP. Subscription disputes require documentation of authorisation, absence of cancellation, and renewal communication.

• Sign-up record: Confirmation that the cardholder created the subscription on a specific date, including the subscription terms displayed at sign-up (recurring amount, frequency, cancellation policy) and a record of the consent action (checkbox, button click, or signed agreement).
• Account activity log: Log showing the cardholder's account was active, never cancelled, and accessed after sign-up. If the cardholder claims to have cancelled, the absence of a cancellation record in the activity log is your counter-evidence.
• Renewal reminder email: The notification sent to the cardholder before the disputed charge, including the date sent, the renewal amount, the billing date, and the cancellation link. Demonstrates the cardholder had advance notice and an opportunity to cancel.
• No cancellation request record: Explicit statement (or export from your subscription management system) that no cancellation request was received from this account before the disputed charge date.
• Usage records: If the subscription involves a service the cardholder used (SaaS, streaming, content access), login activity and feature usage after the disputed charge can establish that the cardholder was actively using the service they're claiming not to have authorised.
• Prior undisputed charges: Record of previous subscription renewals from the same card with no prior disputes. Establishes a pattern of accepted recurring billing.

Collecting Evidence Systematically

The biggest limitation for most merchants isn't willingness to contest chargebacks — it's that the evidence doesn't exist because it wasn't collected at the time of the transaction. Strong chargeback defence is built at the point of sale, not when the dispute arrives.

At transaction time: Capture and retain IP address, device fingerprint, AVS confirmation, CVV confirmation, and the checkout flow state. These are typically available through your payment processor dashboard but should also be stored in your own systems for quick retrieval.

At fulfilment: Log the carrier and tracking number for every physical shipment. Retain a copy of the packing slip. For high-value orders, use signature confirmation and retain the signature record.

Post-delivery: Send delivery confirmation notifications — these create a timestamp of cardholder notification and a record in your system. Retain all customer service interactions — every ticket, chat, and email is potential future evidence.

For subscriptions: Log sign-up date, accepted terms, renewal notifications sent, and account status changes. These records should be exportable for any account within seconds of receiving a dispute.

Assembling the Submission

Once evidence is collected, the submission must be assembled clearly:

1. Write the rebuttal letter first — it frames the evidence and connects each exhibit to the allegation.
2. Label every exhibit with a letter (A, B, C...) and a descriptive name ("Exhibit A — Carrier Tracking Record"). Use the same labels in the letter and on the document.
3. Order exhibits in the sequence referenced in the letter — the analyst should be able to follow the letter and find each exhibit in order.
4. Keep the total submission concise. Submit only evidence relevant to the specific reason code. Irrelevant documents dilute the submission without adding persuasive value.
5. Submit as early as possible within the response window. Filing on day 1 rather than day 25 signals confidence and leaves time for any follow-up from the acquirer.

File format requirements vary by processor — most accept PDF, and some accept JPEG for single-document exhibits. Confirm the format requirements with your acquiring bank or processor's dispute portal before assembling the final package.

What Evidence Cannot Do

Evidence wins disputes — but only disputes that can be won. Some chargeback types are structurally difficult to win regardless of evidence quality:

True fraud without 3DS: If a card was genuinely stolen and used on your platform without 3DS authentication, the absence of authentication data leaves the merchant in a weak position. Strong IP and device evidence can win these cases, but the win rate is lower than for other dispute types. Prevention (3DS2) is more cost-efficient than response for this category.

Merchant processing errors: Duplicate charges, incorrect amounts, and charges after cancellation are legitimate disputes. The appropriate response is a refund before the dispute reaches the network — not a representment.

Late submissions: Evidence submitted after the response deadline is rejected automatically. No amount of compelling evidence overcomes a missed deadline.

For disputes that are unlikely to win — or where the transaction amount doesn't justify the response effort — acceptance is the correct decision. Tracking win rates by reason code and transaction amount creates the data needed to make this judgement accurately rather than accepting or contesting blindly.