What Evidence to Submit for a Chargeback Dispute

The most common mistake service businesses make in a chargeback response is submitting everything they have. A stack of invoices, emails, photos, contracts, and screenshots feels like a strong case. To a dispute reviewer, it looks like noise.

The evidence that matters is the evidence that directly answers the specific allegation in the reason code. This guide covers the seven categories of evidence available to service businesses, what makes each one strong or weak, and how to organize your submission so a reviewer can follow your argument.

The Seven Evidence Categories

1. Authorization Evidence

Authorization evidence proves the customer agreed to the charge. For service businesses, this is not a chip insertion or a card swipe. It is the moment the customer confirmed the service, agreed to the price, and authorized payment.

Strong authorization evidence:

• A signed service agreement or contract referencing the payment amount
• A booking confirmation email the customer replied to or acknowledged
• An electronic signature on an estimate or proposal
• A text message or email where the customer confirmed the appointment and price
• A recorded verbal authorization (where legally permitted)

Weak authorization evidence:

• An unsigned estimate
• A generic booking page with no customer-specific acknowledgment
• An internal note saying the customer agreed (no external confirmation)

Authorization evidence is the most important category for "unauthorized transaction" disputes. If you cannot show that the customer agreed to the charge, the rest of your evidence is supporting a claim you have not established.

2. Scope and Terms Documentation

This category covers what was agreed: the service scope, deliverables, timeline, and the terms governing cancellation, refunds, and no-shows.

Strong scope evidence:

• A signed proposal or statement of work with deliverables and pricing
• Terms and conditions the customer acknowledged before payment
• A cancellation policy displayed at the time of booking
• A deposit or no-show policy with written customer acknowledgment

Weak scope evidence:

• A website terms page with no proof the customer saw it
• A policy created after the disputed transaction
• Verbal terms with no written confirmation

3. Fulfillment Evidence

Fulfillment evidence proves the service was actually performed. For product sellers, this is a shipping label and tracking number. For service businesses, it is more varied and harder to standardize.

Strong fulfillment evidence:

• Time-stamped photos of completed work (before and after)
• A signed completion or acceptance form
• Login or access credentials delivered by email
• Calendar records showing the appointment was kept
• GPS or location data showing you were at the service site
• A follow-up email referencing the completed service that the customer responded to

Weak fulfillment evidence:

• An internal calendar entry (no customer confirmation)
• Photos with no timestamps or location data
• A generic "service completed" note with no transaction-specific detail

4. Customer Communication

Communication records show what happened between you and the customer before, during, and after the service. They establish whether the customer complained, requested a refund, or expressed satisfaction.

Strong communication evidence:

• Email threads showing the customer acknowledged the service or expressed satisfaction
• Text messages discussing the service, scheduling, or results
• Voicemail transcripts (with date and time)
• Chat logs from your booking or messaging platform

Weak communication evidence:

• Internal team communications (the customer is not a party)
• Social media comments without context or dates
• A claimed phone call with no record, timestamp, or summary

5. Refund and Credit Records

If the customer alleges a refund was promised but not issued, your records need to show one of two things: (a) the refund was issued and here is the confirmation, or (b) no refund was promised or owed under the terms.

Strong refund evidence:

• Processor or bank confirmation of a completed refund
• Email correspondence showing the refund discussion and resolution
• Terms showing the transaction was non-refundable, with proof of customer acknowledgment

6. Identity and Device Evidence

For "unauthorized" disputes, identity evidence links the customer to the transaction. This is less relevant for in-person services (you saw the person) but critical for remote or digital services.

Strong identity evidence:

• IP address logs matching the customer's known location
• Email address used for booking matching the cardholder's name
• A customer account with login history
• AVS (Address Verification Service) match confirmation from the processor

7. Third-Party Documentation

Independent records from outside your business that corroborate your version of events.

Examples:

• Reviews the customer left about the service (with dates)
• Permit or inspection records confirming work was done at the location
• Supplier delivery records for materials used in the service
• Insurance inspection reports

How to Build an Evidence Index

An evidence index is a one-page document that lists every exhibit you are submitting and maps it to the specific fact it establishes. It goes at the front of your evidence packet, after the narrative.

Structure each row as:

• Exhibit label (A, B, C or numbered)
• Document description (e.g., "Signed service agreement dated March 12, 2026")
• Fact established (e.g., "Customer authorized the $450 charge for deck staining")
• Allegation addressed (e.g., "Unauthorized transaction")

A reviewer who reads the index should understand your entire case in under two minutes without looking at a single exhibit.

Evidence Scoring Checklist

Before including any document in your packet, check these four qualities:

1. Readable: No cut-off screenshots. No blurry photos. No truncated email threads.
2. Transaction-linked: The document references the specific payment, customer, or date in dispute.
3. Authentic: It is an original, not a recreation made after the dispute.
4. Relevant: It directly addresses the stated reason code, not chargebacks in general.

A document that scores 4/4 belongs in the packet. A document scoring 2/4 or lower usually does not, because it adds volume without adding persuasive weight.

What to Leave Out

• Duplicate versions of the same document (submit the clearest copy only)
• Background marketing material about your business
• Character references or testimonials from other customers
• Legal threats or emotional statements about the customer
• Documents from other transactions unless directly relevant to the pattern