Mastercard Reason Code 4808: Authorization Chargeback

What Mastercard reason code 4808 means

4808 is Mastercard’s Authorization-Related Chargeback, the single code that now covers authorization failures. When Mastercard consolidated its Chargeback Guide into four umbrella codes, older authorization codes such as 4807 Warning Bulletin File and 4812 Account Number Not on File were folded in here.

The cardholder may not be involved at all. 4808 is usually raised by the issuer, which says it either never approved the transaction or approved something different from what you presented. The main situations are:

• Required authorization not obtained: the transaction was cleared with no approval, or after a decline.
• Expired chargeback protection period: the approval was valid but too old by the time you captured.
• Amount exceeds the authorization: you presented more than was approved, outside any tolerance your merchant category allows.
• Multiple authorization attempts: a decline followed by a forced or re-routed approval, in some card-present scenarios.

Authorization validity: the trap for ecommerce

Mastercard’s protection period depends on how the authorization was flagged. As a general rule:

If you authorize at checkout and capture only when the order ships, a backorder, pre-order or slow warehouse can push capture past the window. The approval code still exists, but the protection is gone and the issuer may be able to charge back under 4808. Exact rules can differ by region and by merchant category, so confirm with your processor.

Common causes

• Capturing orders after the authorization has aged out
• Split shipments where later captures exceed the remaining authorized amount
• Incremental charges (upgrades, added items, tips) captured without a new authorization
• Offline or stand-in processing during a gateway outage
• Retrying a declined card through a different route without a fresh approval

Evidence that wins a 4808 dispute

1. Approval code, date and amount from your processor’s authorization log.
2. Authorization type (pre-authorization vs final), which determines the protection period.
3. Clearing date showing presentment fell inside that period.
4. Amount reconciliation: the captured amount was at or below the approved amount, or within your category’s permitted tolerance.
5. Re-authorization record if you refreshed an expired approval before capture.

Because the facts are binary, a 4808 response rarely needs a long letter. State the approval, the dates and the amounts, and attach the logs.

How to prevent 4808 chargebacks

• Flag authorizations correctly as pre-authorizations when you know capture will be delayed.
• Re-authorize before capturing any order older than the protection window.
• For split shipments, authorize each shipment or confirm your processor handles partial captures correctly.
• Never force-post a declined transaction.
• Monitor for captures that exceed authorized amounts.

Should you fight or accept?

Fight when you have a valid approval, captured within the protection period, for the approved amount. These cases are among the easiest on the network to win, because the evidence comes straight from system logs.

Accept when there’s no approval on record, the capture was clearly outside the window without re-authorization, or the amount exceeded the approval. No argument changes those facts. Fix the capture timing instead, because the same gap will produce more 4808s. For the broader response timeline, see chargeback time limits.