How to Prepare Dispute Evidence With Transaction Proof™

Strong dispute evidence is not a pile of documents — it is a small set of records that directly answers the claim. Transaction Proof™ helps merchants organize transaction, order, customer, fulfillment, authentication, refund, and communication records into a coherent evidence set. This guide covers how to prepare that set for a chargeback response.

Start With the Dispute Claim

Every evidence decision flows from what the cardholder actually claimed. An "unauthorized transaction" claim is answered with proof of who transacted; an "item not received" claim is answered with proof of delivery. Before collecting anything, identify the applicable reason code and restate the claim in one sentence. The reason code should shape the evidence review — records that would be decisive for one claim are irrelevant for another.

Before You Collect Evidence

Step 1: Confirm the Transaction Record

Anchor the evidence set with the core transaction record: amount, date, merchant account, and payment identifiers that tie every other document to this specific charge. A response built on records that do not clearly reference the disputed transaction loses coherence immediately.

Step 2: Review Authorization and Authentication Data

Collect what the payment itself can prove: the authorization response, AVS result, CVV result, and 3D Secure information where present. Device data and IP information can add context about who placed the order, and customer-account history can show an established relationship with the same person. Not every record listed here exists for every payment — collect what the transaction actually produced.

Step 3: Collect Order and Product Information

Add the order confirmation, the product description as the customer saw it, and any terms acceptance captured at checkout. For claims about what was sold or promised, the product page and terms the customer agreed to are often the most direct evidence available.

Step 4: Add Fulfillment or Usage Records

Show what the customer received or used. For physical goods, shipping confirmation and delivery confirmation tied to the customer's address. For digital goods and services, digital login records, download records, and service usage after the purchase date. Usage evidence is frequently the strongest material in digital-goods disputes because it shows engagement after the transaction being disputed.

Step 5: Review Refund and Cancellation History

Include refund records and cancellation records where they support the response — for example, proof that a claimed "credit not processed" was in fact processed, or that no cancellation was received before a recurring charge. If refund history contradicts the planned response, that is a signal to reconsider responding at all.

Step 6: Add Relevant Customer Communications

Add customer communications that bear on the claim: a support thread acknowledging delivery, a message confirming satisfaction, or correspondence contradicting the dispute narrative. Include only exchanges that relate to this transaction and this claim.

Step 7: Remove Irrelevant or Contradictory Material

Now subtract. More evidence is not always better evidence — reviewers work under time constraints, and contradictory or irrelevant documents can weaken clarity. Remove anything that does not directly address the claim, duplicates another record, or introduces facts that cut against the response.

Step 8: Organize the Final Evidence Set

Order the final set so it reads as an argument: the claim, the direct answer, and the supporting records behind it. Processor formatting and submission rules may vary, so confirm the applicable format and any size or file requirements before submitting. The chargeback representment and evidence guide covers how a response is evaluated once submitted.

Evidence Examples by Dispute Type

Not every listed record is required for every case — the table maps where to look, not a mandatory checklist.

Common Evidence Mistakes

• Attaching every available record instead of the ones that answer the claim
• Submitting chargeback evidence that never references the disputed transaction
• Relying on Compelling Evidence 3.0 for disputes that do not qualify — it applies only to qualifying Visa disputes with the required prior-transaction history
• Including internal notes or correspondence that contradict the response
• Missing the processor's formatting or submission requirements

When to Escalate an Evidence Question

If you are unsure whether a case qualifies for a specific evidence framework, whether a record is appropriate to include, or how chargeback representment rules apply to your situation, contact Payment Defender Support before submitting the response.