
The workload
When a subscriber disputes a card charge, the workload lands on whoever answers the payment processor's request first. Visa's own Dispute Management Guidelines for Visa Merchants, dated June 2024, tells a merchant to "promptly supply all available details including relevant documentation at the initial dispute notification" and warns that missing a deadline "may potentially lead to unfavorable outcome of the case." For a one-person SaaS business this is unpaid, unscheduled work: pull an invoice, a login-timestamp log, a signed terms-of-service acceptance, and a delivery record, then upload it before a clock the guide does not print a single number for. Visa states plainly that timeliness "may vary depending on your acquirer" — the actual countdown lives in the processor's dashboard, not in Visa's own text.
What the documents show
Verified: Visa's guide organizes every dispute a merchant receives into four numbered categories — Fraud (condition 10.x), Authorization (11.x), Processing Errors (12.x), and Consumer Disputes (13.x) — each with its own definition and required evidence, covering conditions from 10.1 EMV Liability Shift Counterfeit Fraud to 13.9 Non-Receipt of Cash at an ATM. Verified, same document: a dedicated section describes a compelling-evidence framework, under which documentation "meeting the Compelling Evidence criteria" can resolve certain fraud disputes. Verified: Visa's own dispute-resolution overview page tells merchants to submit transactions "ideally within one to five days of the transaction date," and for anything beyond that to "contact your acquirer/processor." Verified, as a processor's summary rather than Visa's rulebook: Stripe's account of how disputes work states Visa is one of two networks, with Mastercard, that "no longer" runs a pre-dispute inquiry stage, and puts a merchant's response window at "usually 7-21 days, depending on the card network."
The operating cost
Neither Visa document prices the labor. Estimated: an evidence packet taking 30-60 minutes to assemble per dispute, multiplied across a subscription base's chargeback rate, is this workload's real recurring cost — a calculation of this entry's own, not a number either source states, and it excludes any dispute fee a processor charges regardless of outcome.
The stop condition
Editorial: the workload stops being worth fighting per-dispute once a founder's win rate on a given reason code stays low across several cycles, since Visa's compelling-evidence path rewards specific, repeatable proof over argument. Visa's own text names no such threshold; it only names the categories and warns that a missed deadline forfeits the case automatically.
- Does the acquirer's dashboard show the actual response deadline for each dispute, or only Visa's category name?
- Which of the four dispute categories account for most of the disputes this business actually receives?
- Is the evidence Visa's compelling-evidence table asks for already captured automatically at checkout, or does someone have to go find it after the fact?
A dispute is not one event with one clock; it is a category, a deadline set by an intermediary, and a documentation standard published by the network. Reading Visa's own guide narrows the first and third. The second still belongs to the acquirer.
Sources & reading trail
Visa's own four dispute categories (Fraud, Authorization, Processing Errors, Consumer Disputes), the compelling-evidence framework, and the statement that response timing varies by acquirer.
Source published: 1 June 2024 · Retrieved: 16 September 2026
Visa's own guidance to submit transactions within one to five days and to direct specific dispute questions to the acquirer or processor.
Source published: Not established · Retrieved: 16 September 2026
A processor's own description of typical 7-21 day merchant response and 60-75 day issuer review windows, and that Visa and Mastercard no longer use a pre-dispute inquiry phase.
Source published: Not established · Retrieved: 16 September 2026
Vendor documentation, regulator records and founder-published documents establish the entry; the workload reading and the stop condition are Solo Product Office editorial analysis. This retrospective draft does not imply the site published on the event date.