Mastercard reason code 4812: what it means and how to respond
Mastercard 4812 is Account Number Not on File, an Authorization chargeback. Learn when it applies, the response path, evidence, and scheme deadlines.
What Mastercard reason code 4812 means and when it applies
Reason code 4812, “Account Number Not on File,” means that the primary account number, or PANPAN stands for Primary Account Number. It identifies the payment account, usually as the card number, and is the number the issuer looks up when processing an authorization., does not exist. Mastercard places this situation under “Required Authorization Not Obtained,” meaning that the required authorization was not properly obtained.
For the situation identified by 4812, all of these requirements must be present, in this order:
- The issuer tried to honor the transaction. The bank or institution that issued the card must make this attempt before exercising the chargeback right.
- The PAN provided does not exist. The rule covers both a purchase and a refund presented with an account that does not exist.
- The required authorization was not properly obtained. Without a valid approval for that PAN, the merchant cannot show that the transaction met Mastercard authorization requirements.
Source for the requirements: Mastercard Chargeback Guide — Merchant Edition, “Authorization-related Chargeback” and “Required Authorization Not Obtained,” pp. 54 and 60–63.
The current guide does not give 4812 a separate section. It remains an alternate code within the 4808 flow, which consolidates authorization disputes. Mastercard recommends using 4808 and says 4812 will eventually be eliminated. For Debit Mastercard in the Single Message System, the same transition is taking place from 12 to 08.
Source for the relationship between the codes: Mastercard Chargeback Guide — Merchant Edition, p. 63, “Message reason code”.
Who files the dispute and what happens next
The issuer files the chargeback against the acquirer, the institution that processes the merchant’s payments. Under the standard rule, which also applies in the US, the issuer has 90 calendar days from the transaction’s Settlement Date or Central Site Business DateThese are the settlement or central processing dates recorded by Mastercard. The system used for the transaction determines which date starts the clock.. For the Required Authorization Not Obtained condition, the issuer does not need to attach documents or add message text. Regional windows may differ; for example, the issuer has 120 calendar days for ATM and Maestro transactions when both the issuer and acquirer are located in Europe.
If there is a valid basis to respond, the acquirer submits a second presentmentThis is the acquirer’s formal response to the chargeback. The acquirer gives Mastercard the record or basis that invalidates the chargeback. within 45 calendar days of the chargeback’s Settlement Date or Central Site Business Date under the standard rule. The merchant gives the records to the acquirer and does not respond directly to Mastercard.
Source for the deadlines and process: Mastercard Chargeback Guide — Merchant Edition, pp. 62–66.
After the second presentment, the issuer may open a pre-arbitration case. This step is optional, and Mastercard recommends proceeding directly to an arbitration case. With or without pre-arbitration, the arbitration case must be filed within 45 calendar days of the second presentment’s Settlement Date or Central Site Business Date.
Source for escalation: Mastercard Chargeback Guide — Merchant Edition, pp. 73–81.
How to reduce the risk of this code
- Treat the authorization result as the decision. Do not submit the transaction to clearing when the authorization records contain no valid approval for the PAN.
- Keep the record that connects approval and clearingClearing is the stage when the acquirer submits the transaction to Mastercard so settlement can be calculated between participants.. Retain the authorization date, response code, approved amount, cleared amount, and any reversal. These records show whether the approval covered the transaction and whether it was submitted within the applicable chargeback-protection period.
- Do not submit a transaction after fully reversing its authorization. A full reversal cancels the approval. If the transaction is submitted to clearing anyway, it is no longer properly authorized.
Source for the chargeback-protection periods: Mastercard Transaction Processing Rules, Chapter 2, §2.8, p. 49. Source for authorization records and reversals: Mastercard Chargeback Guide — Merchant Edition, pp. 60–66.
Evidence the merchant needs to gather
The acquirer must follow at least one of the paths below. The paths are alternatives and do not need to be combined. Within the chosen path, however, all requirements listed for that path must be met.
- Authorization was properly obtained. Gather the record of a valid, unreversed approval tied to a transaction submitted within the applicable chargeback-protection period. The cleared amount must be within the approved amount and any applicable tolerances. The authorization date and response code go in DE 72DE 72 is the Data Record field in the message sent by the acquirer. For this defense, it records the date and response code of the authorization that approved the transaction.. If the chip approved the transaction offline, include the DE 55DE 55 carries the data generated by the chip. In this defense, it proves an offline approval when the issuer did not authorize the transaction in real time. data or the notation required for that case.
- One authorization covered multiple clearing records. All of these elements are required: the 1403 or 1404 indicator in DE 25DE 25 is the Message Reason Code field in the original clearing record. Values 1403 and 1404 identify parts covered by the same authorization., a combined total that does not exceed the approved amount, and the corresponding text in DE 72.
- The merchant already issued a refund. The refund must already have been processed and must be identified in the timely second presentment with the credit date and Acquirer Reference DataThis is the reference the acquirer creates to locate the credit and connect it to the disputed transaction..
- The chargeback is invalid. It is enough to prove one of these failures: the chargeback does not meet the requirements, was filed after the deadline, duplicates another chargeback for the same transaction, or the PAN and Acquirer Reference Data combination does not match the original clearing record.
Source for the four alternative paths and the requirements within each path: Mastercard Chargeback Guide — Merchant Edition, pp. 64–72.
For the standard path showing that authorization was properly obtained, the defense stays in the message fields and no document package is required. If another path uses documents, the acquirer submits them through MastercomMastercom is the Mastercard system where the issuer and acquirer file the chargeback, response, and case documents.. The PAN must be shown with only the last four digits visible.
Source for documentation and PAN protection: Mastercard Chargeback Guide — Merchant Edition, pp. 59–60 and 65.
Frequently asked questions
What does Mastercard reason code 4812 mean?
It is the message reason code "Account Number Not on File." It covers a purchase or refund presented with a primary account number (PAN) that does not exist and for which the required authorization was not properly obtained.
What requirements must be present for code 4812?
All requirements must be present: the issuer tried to honor the transaction, the PAN provided does not exist, and the required authorization was not properly obtained. The code name alone does not replace these records.
Does Mastercard still allow reason code 4812?
Yes. In the Dual Message System, 4812 may still be used as an alternate code for 4808. Mastercard recommends 4808 and says 4812 will eventually be eliminated. For Debit Mastercard in the Single Message System, the corresponding alternate code is 12, while Mastercard recommends 08.
How can the acquirer respond to a 4812 chargeback?
The acquirer has several independent response paths. It may prove a valid, unreversed authorization; show that one authorization covered multiple clearing records; identify a refund already issued; or show that the chargeback is invalid. One path is enough, but every requirement within the chosen path must be met.
What is the deadline for a 4812 chargeback?
Under the standard rule, including in the US, the issuer has 90 calendar days from the Settlement Date or Central Site Business Date of the transaction. The acquirer has 45 calendar days from the corresponding date of the chargeback to submit the second presentment. Regional variations may apply.
Does the defense require a document package?
Not for the standard path showing that authorization was properly obtained. The authorization date and response code go in DE 72 of the second presentment. If another path uses documents, the PAN must be masked so that only the last four digits are visible.
View all Mastercard chargeback reason codes or return to Knowledge.