← All articles

SaaS

Chargeback representment: the evidence pack a small SaaS submits to win digital dispute arbitrations

November 19, 2026

Visa reason codes 10.4 and 13.1 versus Mastercard 4837 and 4853; what dispute analysts at card issuers actually review in 90 seconds; the four-part evidence pack that proves digital delivery; win rates for monthly versus annual subscriptions; and when the network arbitration fee is worth the risk.

A close-up of a person in a dark suit signing a formal legal contract and agreement document with a pen on a desk

When a physical e-commerce store fights a chargeback, it uploads a FedEx tracking slip with a delivery signature and GPS drop-off coordinates. The card issuer looks at the signature, matches the zip code, and closes the case. A software-as-a-service vendor has no parcel, no cardboard box, and no delivery driver. When an annual customer disputes a ,200 renewal or a buyer claims "fraudulent transaction" on a software subscription, winning the dispute requires a completely different mechanism: digital representment.

Representment is the formal legal procedure under card network rules—Visa Claims Resolution (VCR) and Mastercard Dispute Administration—where a merchant re-presents the disputed charge alongside a structured evidence dossier. Most small software companies lose disputes not because the customer was in the right, but because the rebuttal packet was assembled incorrectly. Issuing bank analysts spend roughly 60 to 90 seconds reviewing each case. If you paste an emotional letter, dump unformatted server error logs, or attach a generic terms-of-service PDF without showing explicit acceptance, you will lose.

This guide walks through the exact evidence package required to win digital subscription chargebacks: the reason codes used by banks, the formatting constraints enforced by Stripe and Braintree, how to format server telemetry, win rates across monthly versus annual billing cycles, and when to invoke formal card network arbitration.

The reason code matrix: what the bank actually claimed

Every chargeback arrives tagged with an official reason code assigned by the cardholder's issuing bank. Your rebuttal must directly refute that specific code's legal premise. Submitting proof of product quality when the dispute code is 10.4 ("I didn't authorize this charge") is an immediate forfeiture.

text
Network / Code        Official Category                    Cardholder Allegation              Winning Evidence Standard
--------------------  -----------------------------------  ---------------------------------  --------------------------------------------------------
Visa 10.4             Fraud: Card-Absent Environment       "I did not buy or authorize this" Compelling Evidence 3.0 (2 prior transactions, matching
                                                                                              IP/device) or AVS/CVV match + customer login telemetry
Mastercard 4837       No Cardholder Authorization          "Unauthorized payment / fraud"    3D Secure authentication token (ECI 05/02), IP audit
                                                                                              matching billing address, password reset / login history
Visa 13.1             Merchandise / Services Not Received  "I never received the service"     Account activation timestamp, active login audit log,
                                                                                              export / download records, customer support ticket trails
Mastercard 4853       Recurring Transaction / Not Provided "Service not provided or cancelled" Proof of active access during billing cycle, delivery
                                                                                              of login credentials, cancellation policy consent
Visa 13.2             Cancelled Recurring Transaction      "I cancelled before the renewal"   Terms agreed at checkout, renewal reminder sent,
                                                                                              logins after renewal date, no cancellation in audit log
Mastercard 4841       Cancelled Recurring Transaction      "Recurring billing after cancel"   Prior billing history, no cancellation record in system,
                                                                                              login / feature activity during active period

For fraud claims (Visa 10.4 and Mastercard 4837), Visa's Compelling Evidence 3.0 (CE 3.0), introduced in April 2023, is your highest-leverage defense. Under CE 3.0, if you can prove that the same card made at least two undisputed transactions between 120 and 365 days prior to the dispute, and you can match at least two core data elements (IP address, Customer ID, Device Fingerprint, or Physical Delivery Address, with at least one being the IP address or Device ID), liability shifts back to the issuing bank. On month four of a recurring subscription, a customer cannot credibly claim card fraud if months one through three went through from the exact same residential IP address.

The 90-second evaluation funnel at Stripe and Braintree

Before your evidence reaches the cardholder's issuing bank (Chase, Bank of America, Barclays, Wells Fargo), it passes through payment gateway portals that enforce rigid upload boundaries. Payment gateways do not consolidate arbitrary attachments: they map your files into specific network clearing queues.

text
Portal Field / Parameter    File Constraints           Mandatory Content For Digital SaaS
--------------------------  -------------------------  --------------------------------------------------------------------
Stripe: customer_commun.    PDF / JPG / PNG, <= 5 MB   Support tickets, onboarding emails, feature requests, chat logs
Stripe: refund_policy       PDF / JPG / PNG, <= 5 MB   Screenshot of checkout showing refund terms + highlighted clause
Stripe: service_docum.      PDF / JPG / PNG, <= 5 MB   Account dashboard screenshot showing user email, plan, creation date
Stripe: uncategorized_file  PDF / JPG / PNG, <= 5 MB   Telemetry logs (IPs, UTC timestamps, session actions) + Cover Sheet
Stripe total packet limit   <= 4.5 MB aggregate        Stripe compresses files; keep original PDFs lean and crisp
Braintree: Document Upload  PDF / PNG / JPG, <= 4 MB   Categorized: Proof of Delivery (Access Log), Terms, Communication
Adyen: Dispute Defense      PDF / JPG / PNG, <= 10 MB  Single combined dossier or split exhibits according to defense guide

The human reviewer reading your packet is an arbitration analyst at the issuing bank. They evaluate dozens of chargebacks each day. They will not read a 60-page PDF containing thousands of lines of raw Nginx access logs. If your evidence is disorganized, illegible, or forces the analyst to hunt for dates, they click "Chargeback Upheld" and move on. Your dossier must lead with a single-page Executive Summary.

The four-part SaaS evidence dossier

A winning digital representment packet consists of an Executive Summary followed by four distinct exhibits. Each exhibit proves one pillar of the transaction: agreement, delivery, engagement, and terms.

The dossier begins with a one-page cover sheet that presents an unbroken chronological timeline connecting the payment to the user's actual identity:

text
========================================================================================
                             EXECUTIVE SUMMARY & TRANSACTION TIMELINE
========================================================================================
Dispute Reference:         dp_1Q8b2xLkdIw92        Disputed Amount:       ,200.00 USD
Cardholder Name:           Jane Doe                Transaction Date:      2026-03-15 14:22:15 UTC
Card Network & Code:       Visa 10.4 (Card-Absent) Processor Reference:   pi_3O9k1mLkdIw92A0
Product / Service:         SaaS Annual Plan (Pro)  Customer Account:      jane.doe@example.com

CHRONOLOGICAL AUDIT TRAIL:
----------------------------------------------------------------------------------------
1. 2026-03-15 14:20:02 UTC: Account created by user jane.doe@example.com from IP 198.51.100.44
   (ISP: Comcast Cable, Location: Austin, Texas, US). Device: Mac OS X / Chrome 134.
2. 2026-03-15 14:22:10 UTC: User selected "Annual Pro Plan" (,200/yr) and explicitly
   checked the mandatory Terms of Service checkbox (Exhibit A: Clickwrap Audit Log).
3. 2026-03-15 14:22:15 UTC: Payment processed. AVS check: Full Match ("Y" - Street address
   and 5-digit zip matched billing records). CVV check: Match ("M"). 3D Secure ECI: 05.
4. 2026-03-15 14:23:01 UTC: Automated invoice #INV-2026-8812 delivered via email to
   jane.doe@example.com (Message-ID: <inv-8812@mail.saas.com>, SMTP Status: 250 OK Delivered).
5. 2026-03-15 to 2026-10-14: User logged into the application 68 distinct times from the
   identical IP address (198.51.100.44) and created 14 project boards (Exhibit B).
6. 2026-08-12 11:04:19 UTC: User submitted support ticket #4419 asking how to invite
   additional team members to her workspace, confirming active use (Exhibit C).
7. 2026-10-18 09:12:00 UTC: Dispute opened claiming "Fraudulent Transaction" 7 months after
   initial payment, despite uninterrupted, active usage. No cancellation requested.
----------------------------------------------------------------------------------------

Following the cover page, attach four clean exhibits:

Exhibit A: Checkout Telemetry & Terms Acceptance. Include a high-resolution screenshot of your checkout form showing the exact text beside the signup checkbox: "I agree to the Terms of Service and authorize an annual charge of ,200 renewing automatically until cancelled." Beside it, provide the database audit row with the user ID, timestamp in UTC, IP address, user-agent string, and terms version hash. Clickwrap agreements with explicit unchecked-by-default boxes are recognized as binding by both Visa and US courts; buried footer links are routinely dismissed.

Exhibit B: Digital Telemetry & Service Delivery Log. This is the heart of the packet for digital products. Show a clean, readable table of application activity spanning multiple months. Include session login timestamps, source IP addresses, browser fingerprints, and recorded application events (e.g. "Created project", "Generated PDF report", "Exported database backup"). When an issuing bank sees that the disputed account generated 400 API requests or exported files from the cardholder's hometown IP address two weeks after the charge, claims of "Product Not Received" or "Fraud" collapse.

Exhibit C: Direct Communications & Billing Notifications. Cardholders often dispute recurring annual subscriptions claiming they forgot or were never informed. Include your automated invoice delivery receipts, the 7-day pre-renewal notification email (with SMTP message-ID and delivery timestamp), and any customer service tickets from Zendesk, Intercom, or Help Scout. If the customer emailed your support desk from the same address to ask a product question, highlight it. A customer cannot claim someone stole their card number to buy software if they were emailing support about how to use the tool.

Exhibit D: Cancellation Policy & Self-Service Accessibility. Show that cancelling is straightforward and available inside the user's account settings without phone calls or dark patterns. Include a screenshot of the "Cancel Subscription" button on the billing page, along with your published refund policy. Proving that cancellation was frictionless demonstrates that the cardholder bypassed your published process to initiate an unearned chargeback.

Monthly versus annual subscriptions: the win rates

The economics of contesting chargebacks differ sharply depending on billing frequency. Below are representative performance benchmarks for small SaaS products (k-k MRR) based on industry dispute data across Stripe and Braintree accounts.

text
Metric / Step                Monthly Subscriptions (/mo)         Annual Subscriptions (,200/yr)
---------------------------  -------------------------------------  ------------------------------------
Average disputed charge      .00                                 ,200.00
Primary dispute reason code  Visa 13.2 / MC 4841 (Cancelled recur)  Visa 10.4 / MC 4837 (Fraud claim) or
                                                                    Visa 13.1 (Services not received)
Base win rate (generic pack) 18% to 22%                             38% to 44%
Optimized dossier win rate   48% to 54% (with CE 3.0 / active logs) 68% to 76% (with full audit telemetry)
Processor dispute fee        .00 opening fee                     .00 opening fee
Counter fee (Stripe US)      .00 (charged to contest)            .00 (charged to contest)
Time required to contest     25 to 40 minutes per packet            45 to 60 minutes per packet
Expected net value of fight  -.50 per dispute (unfavorable)       +.00 per dispute (highly positive)

For a monthly subscription, contesting manually rarely pays. If you win 50% of contested cases, your gross recovery is 0.50 x = .50. Meanwhile, Stripe charges a opening fee (which is never returned) and, since June 2025, a contest fee (refunded only if you win). Losing a contested charge costs you in lost revenue plus in processor fees ( total). Unless you have automated dispute tools like Stripe Smart Disputes or qualify for automatic Compelling Evidence 3.0 matching, manual representment on small monthly subscriptions consumes more founder time than the recovered cash justifies.

Annual subscriptions are the exact opposite. An annual dispute of to ,400 carries massive financial exposure. Cardholders who forget an annual renewal frequently choose "Dispute" in their mobile banking app rather than emailing the vendor for a refund. Because annual customers have months of established login history, database logs, and email delivery receipts, your evidence pack is comprehensive. At a 72% win rate, contesting a ,200 dispute yields an expected positive return of over per case. For annual subscriptions, thorough representment is non-negotiable.

Pre-arbitration and the network gamble

What happens if you submit your evidence pack and the issuing bank still rules against you? The dispute process has three distinct tiers:

text
Stage 1: Initial Dispute (Chargeback)
  --> Customer files dispute; funds pulled from merchant.
  --> Merchant submits Evidence Pack (Representment).
  --> Issuing bank accepts or rejects evidence (takes 30-60 days).

Stage 2: Pre-Arbitration (Second Presentment / Challenge)
  --> If merchant wins, the issuing bank can accept or file Pre-Arbitration.
  --> If merchant loses, merchant can initiate Pre-Arbitration if new evidence exists.
  --> Cost: zsh to  depending on merchant acquirer; no network penalty yet.

Stage 3: Formal Card Network Arbitration
  --> If neither side concedes during Pre-Arb, case goes to Visa or Mastercard arbitration.
  --> A Visa or Mastercard committee reviews the evidence and issues a final, binding ruling.
  --> Cost: .00 to .00 filing fee assessed to the LOSING party.

Formal arbitration operates under a strict "loser pays" penalty. If you take a ,200 dispute to Visa arbitration and lose, Visa charges your acquirer a filing fee (passed directly to your merchant balance), in addition to the lost ,200 and initial dispute fees—costing you over ,730. If you win, the cardholder's issuing bank pays the fee, and your ,200 is restored.

Because of the penalty, never take a chargeback to formal arbitration unless three conditions are met:

1. The disputed transaction is at least ,000. Under , the fee equals or exceeds the amount you are trying to recover.

2. You have new, compelling evidence that was not included in the first round. Visa and Mastercard rules explicitly allow arbitrators to reject cases where the merchant simply resubmits the exact same PDF that the issuing bank already reviewed.

3. You have airtight digital telemetry matching the cardholder's identity: verified 3D Secure authentication tokens, matching AVS/CVV records, and server logs showing active usage during the disputed period.

Interestingly, during Pre-Arbitration (Stage 2), issuing banks fold roughly 60% of the time when faced with an uncompromising, professional evidence dossier. Many banks uphold initial chargebacks automatically to protect their cardholder, banking on the merchant giving up. When a merchant escalates to Pre-Arbitration with formal legal telemetry, the bank's risk team evaluates the loss risk and often settles before formal filing.

Copy-pasteable rebuttal template for SaaS vendors

Use this template as Page 1 of your rebuttal packet when fighting digital fraud (Visa 10.4 / Mastercard 4837) or service not received (Visa 13.1 / Mastercard 4853) disputes. Keep the tone clinical, objective, and fact-focused.

text
To: Dispute Resolution Analyst / Arbitration Committee
From: [Merchant Legal Name d/b/a Product Name]
Date: [Date in YYYY-MM-DD format]
Subject: Formal Rebuttal for Dispute [Dispute ID] / Case [Case ID]
Disputed Transaction: 0 USD on [Transaction Date] | Card ending in [Last 4]
Reason Code: [Visa 10.4 Fraud - Card Absent / Visa 13.1 Services Not Received / MC 4837]

OVERVIEW:
We are formally rebutting this dispute. The cardholder, [Customer Name], active user of
[Product Name] under account [customer@email.com], authorized this transaction, accepted
our Terms of Service, and actively utilized the software during the disputed billing cycle.

SUMMARY OF ATTACHED EVIDENCE:
1. Exhibit A - Authorization & Terms Acceptance:
   On [Date] at [Time UTC], the user registered with email [Email] from IP [IP Address].
   Payment was authorized with full AVS match (Street and Zip matched card billing address)
   and CVV match. The cardholder checked an affirmative opt-in box agreeing to our Terms of
   Service (Exhibit A-1), which outlines our annual billing and cancellation terms.

2. Exhibit B - Proof of Delivery & Service Telemetry:
   The digital service was provisioned immediately upon transaction confirmation.
   Our audit telemetry (Exhibit B) records [Number] separate login sessions originating from
   the cardholder's verified IP address ([IP Address]) between [Start Date] and [End Date].
   During this time, the user performed [Number] distinct application operations, including
   [mention key actions, e.g., data export, project creation, dashboard access].

3. Exhibit C - Communication & Notification Record:
   A detailed purchase receipt was delivered to [Email] on [Date] (Message-ID: [Msg-ID]).
   On [Date], our automated system delivered an upcoming renewal notice to the cardholder.
   Furthermore, on [Date], the cardholder contacted our support desk via ticket #[Ticket ID]
   from the identical email address regarding feature configuration, verifying identity.

4. Exhibit D - Accessible Cancellation Policy:
   The cardholder never submitted a cancellation request prior to the billing event.
   As shown in Exhibit D, self-service cancellation is accessible in two clicks from the
   account dashboard. The cardholder bypassed this published procedure.

CONCLUSION:
The attached telemetry confirms that the cardholder authorized the payment, received access,
and actively used the service. In accordance with card network operating regulations, we
respectfully request that the dispute be resolved in the merchant's favor and the funds restored.

Sincerely,
Dispute Operations Team, [Merchant Company Name]
Contact: [Support Email] | [Merchant Phone]

Handling chargeback arithmetic is closely tied to your broader pricing and renewal architecture. If you offer annual subscriptions with steep discounts, review our annual discount calculator to see how deferred revenue and churn intersect. For broader dispute rates and processor fees, consult chargebacks at a small SaaS, and ensure billing notices reach the right desk with our guide on the SaaS billing contact.

Calculate year-one revenue, cash balance versus deferred revenue, and the break-even discount for annual versus monthly subscribers directly in your browser.

Open the annual discount calculator

Sources

Network Dispute Rules & Compelling Evidence: Visa Core Rules and Visa Product and Service Rules; Visa Compelling Evidence 3.0 Merchant Guide (March 2023); Visa Claims Resolution (VCR) Overview; Mastercard Chargeback Guide (updated 2025/2026); Mastercard Dispute Administration Rules.

Processor Dispute Guidelines & Limits: Stripe: Responding to Disputes and Evidence Requirements; Stripe: Dispute Reason Codes and Defenses; Stripe: June 2025 Dispute Fee Updates; Stripe: Compelling Evidence 3.0 Automation; Braintree: Dispute Management & File Specifications; Braintree: Managing Chargeback Documentation; Adyen: Dispute Defense and Attachment Formats.

Arbitration and Win Rate Studies: Mastercard 2025 Global State of Chargebacks Outlook; Helcim Guide to Chargeback Pre-Arbitration and Arbitration Fees; Federal Trade Commission: Restore Online Shoppers' Confidence Act (ROSCA); Electronic Signatures in Global and National Commerce Act (E-SIGN Act).