Mastercard routes its chargeback codes through the processor

The workload

A merchant who receives a Mastercard chargeback has to match a four-digit code to a defense, and the code decides what evidence is worth gathering. This entry tried to reach that code list at its source. Every attempt to load mastercard.us and mastercard.com's published rules pages returned an automated-access block in September 2026, across a plain fetch, a browser-identified request, and a text-extraction proxy; the network's own developer portal loaded but returned no readable rule text, only an empty script shell. That is itself a fact about the workload: unlike Visa, whose comparable guide is a plain downloadable PDF, Mastercard licenses its rulebook to acquirers and does not appear designed for a merchant or a script to fetch it cold.

What the documents show

Verified, as a processor's relay rather than Mastercard's own text: Stripe's dispute reason code categories page lists the Mastercard codes it maps into its own dispute categories, including 4860 (Credit Not Processed), 4837 (No Cardholder Authorization), 4870 (Chip Liability Shift), and 4808 (General Chargeback), among dozens more. Stripe states this table sorts codes "into one of eight categories" for evidence purposes; the descriptions attached to each code are Stripe's own gloss, not a copy of Mastercard's rulebook, and should be read that way. Verified, same source type: Stripe's dispute lifecycle page states Mastercard and Visa are the two networks that "no longer" use a pre-dispute inquiry step, and that a merchant's response window runs "usually 7-21 days, depending on the card network," with issuer review taking "usually 60-75 days." Nothing available to this entry gives a Mastercard-specific number inside those ranges, and none of Mastercard's specific reason-code definitions can be treated as verified from Mastercard's own text here, only as Stripe's documented relay of them.

The operating cost

No source available to this entry states a per-dispute fee Mastercard itself charges a merchant; that figure, where it exists, sits in the acquirer's contract, not in anything Mastercard publishes openly. Estimated: the practical cost is staff time spent identifying which of Stripe's eight categories a four-digit Mastercard code falls into before evidence can be assembled, a step Visa's own downloadable guide removes by publishing its category table directly.

The stop condition

Editorial: this research problem stops the moment a business routes Mastercard acceptance through a processor, since the processor already performs the code-to-category translation this entry had to attempt by hand. It resumes as a cost the moment anyone tries to verify a processor's summary against Mastercard's original wording, which requires an acquirer relationship this entry does not have.

• Does the payment processor's dashboard show the Mastercard reason code itself, or only its own translated category?
• Has anyone at this business read Mastercard's own rules text, or only a processor's summary of it?
• Would an acquirer relationship, rather than a processor relationship, surface evidence requirements a processor's summary omits?

Mastercard's chargeback rules govern billions of transactions, but the copy of them a solo founder can actually read in September 2026 is the one their processor chose to publish, not the network's own.