ZocumentsOn this page
The codes merchants most often need to untangle
| Code | Current or historical context | Practical reading |
|---|---|---|
| 4808 / 08 | Authorization-related chargeback. | Check the authorization record, transaction type, and the reason the issuer says authorization was missing or invalid. |
| 4812 / 12 | Account Number Not on File; Mastercard says these older forms will eventually be eliminated in the contexts where it recommends 4808. | Do not confuse this with a merchant being listed in MATCH or with a customer simply not recognizing a charge. |
| 4849 / 49 | Questionable Merchant Activity in fraud-related chargeback contexts. | Read the notice and network stage carefully; this is not a generic label for every fraud allegation. |
| 4853 / 53 | Cardholder Dispute. The 53 form is used in some debit or single-message contexts for defective/not-as-described disputes; Mastercard recommends 4853 in the dual-message flow. | Use the actual claim—quality, description, receipt, cancellation, or another issue—to choose evidence. |
| 4855 / 55; 4859 | 4855 Goods or Services Not Provided and 55 Non-receipt of Merchandise may still appear in particular flows but will eventually be eliminated. 4859 is a limited Addendum, No Show, or ATM Dispute form that is also being phased out. | For 4855/55, check the message system and delivery or service claim. For 4859, confirm that the notice actually concerns an addendum, no-show, or ATM transaction. |
| 4860 | Credit Not Processed; Mastercard identifies it as a legacy code being eliminated in some flows. | Use the refund, cancellation, and credit records from the existing credit-not-processed guide. |
MATCH is not a chargeback reason code
Mastercard MATCH is a merchant-screening system used by acquirers. A MATCH search, a merchant listing, or a question about whether an acquirer listed a terminated merchant is a compliance or onboarding issue—not proof that a transaction was charged back under code 4808, 4812, 4849, or 4853.
Read the case in the right order
- 01Identify the message system
Ask whether the case is a Mastercard dual-message transaction, a single-message debit transaction, or a processor abstraction.
- 02Identify the stage
Separate first chargeback, second presentment, pre-arbitration, arbitration, and compliance. The same number does not mean the same action at every stage.
- 03Translate the claim
Write the cardholder's actual allegation in one sentence before collecting records.
- 04Follow the acquirer form
Use the evidence fields and deadline on the live case. The Mastercard guide is a rules reference, not the upload form.
For a current network reference, use Mastercard's Chargeback Guide Merchant Edition. Then use the broad reason-code directory to move from a network label to the records a reviewer can actually verify. When the claim is clear, the chargeback response and rebuttal template and response packet guide can help organize that evidence before you return to the processor.
