Mastercard 4808 — Account Number Not on File: What It Is and How to Respond

Mastercard 4808 is an authorization-related chargeback covering situations where the transaction lacked proper authorization. The most common trigger is an “account number not on file” response — the card number used in the transaction doesn't match any active account at the issuer.

This can also be raised when a merchant processed a transaction after a declined authorization, or when required authorization was not obtained at all. Unlike fraud disputes, this is primarily a technical compliance issue — and one that can be won cleanly if you have a valid approval code on record.

Common reasons you received this dispute

1. 1Transaction was processed with a card number not recognised by the issuer (key entry error or token mismatch)
2. 2Merchant processed a sale after receiving a Decline response from the authorization
3. 3Authorization was not obtained before settling the transaction
4. 4Card was expired, closed, or not issued by the time of settlement
5. 5Card number was entered incorrectly during a manual key-entry transaction

Can you win this dispute?

Evidence checklist

1. ✅ Required

   Valid authorization approval code and date/time of authorization: The approval code obtained from the issuer before settlement. This is the single most important piece of evidence in a 4808 dispute.

2. ✅ Required

   Transaction receipt showing the account number used: Demonstrates the account number at the time of the transaction matched the authorized account number.

3. ✅ Required

   Settlement record showing the same account number: Confirms the account number was consistent from authorization through to settlement.

4. ⭐ Strongly recommended

   Payment gateway authorization log: A timestamped export from your gateway showing the authorization request and approval, including the approval code and the exact time it was received before settlement.

5. ⭐ Strongly recommended

   Any decline records showing you did not proceed after a decline: If you have records of a previous authorization attempt that was declined and you did not process against it, include those to demonstrate compliance.

How to write your response

Key deadlines

How to prevent this chargeback

1. 1

   Never process after a Decline — implement hard blocks in your POS/gateway: A declined authorization means the transaction must stop. Configure your system to block settlement attempts on any transaction that returned a Decline response. This is the most common and most preventable cause of 4808 chargebacks.

2. 2

   For card-not-present: use full AVS verification to catch transposed card numbers: Address Verification System checks flag mismatches before a transaction is authorized, catching key-entry errors before they generate a dispute.

3. 3

   Reconcile authorization codes against settlements daily: Unsettled authorizations and orphaned settlements are warning signs. A daily reconciliation catches problems before they become chargebacks.

4. 4

   For manual key entry: use a double-entry verification step: Requiring the operator to type the card number twice — and comparing the two entries before authorization — eliminates most transcription errors in manual key-entry environments.

Frequently asked questions

Related reason codes