Discover tells merchants to call, not read, for dispute rules

The workload

Discover is the fourth major US card network a SaaS founder is likely to accept, usually through the same processor relationship that already carries Visa, Mastercard, and Amex traffic. This entry checked Discover's own fraud-prevention-practices page and its published site sitemap directly for a public dispute or chargeback rules page; none exists among Discover's listed resource pages. Discover's own page confirms the gap itself, directing merchants who want "specific chargeback procedures, reason codes, and deadlines" to "contact Discover directly" by phone or through their service center rather than a published rulebook. The workload, in other words, starts with a phone call or an acquirer relationship, not a document.

What the documents show

Verified, from Discover's own page: the fraud-prevention guidance lists preventive practices — "respond to all chargebacks, even the small ones," obtain authorizations before completing a sale, and use address- and card-verification services — while explicitly stating it is not the source for reason codes or deadlines. Verified, as a processor's relay rather than Discover's own text: Stripe's dispute reason code categories page lists Discover-specific codes it maps for merchants, including 8002 (Credit Not Processed), 4534 (Duplicate Processing), and 4755 (Non-Receipt of Goods or Services), attributed to Stripe's own eight-category system rather than to Discover's original text. Verified, same processor: Stripe's dispute lifecycle page states Discover is one of the networks that "most often" uses a pre-dispute inquiry phase, and that an unanswered Discover inquiry "can turn into unchallengeable disputes" — a harder outcome than an ordinary loss, since the merchant never gets to submit evidence at all.

The operating cost

No figure in these sources states a per-dispute fee Discover itself charges; that number sits in the acquirer or processor agreement, not in anything Discover publishes. Estimated: the real cost of Discover's inquiry design is asymmetric risk rather than a fee — missing the inquiry entirely costs a merchant the right to contest at all, a larger loss than a normal contested-and-lost chargeback.

The stop condition

Verified: an unanswered Discover inquiry becomes unchallengeable, an absolute stop condition set by the network's own process design rather than a judgment call. Editorial: short of that point, the decision to keep contesting small Discover chargebacks is a time-versus-recovery calculation the documents do not resolve.

• Does this business's processor flag a Discover "inquiry" separately from a full chargeback, given what is at stake if it is missed?
• Who at this business is responsible for responding to a pre-dispute notice inside whatever window the processor sets?
• Would calling Discover's own service center, as its site suggests, surface rules the processor's summary omits?

Discover is the network that documents its own dispute rules the least in public, and says so on its own site. What a founder reads about Discover's reason codes is, in practice, whatever a processor chose to publish about them.