4808: Authorization-Related Chargeback

This guide breaks down everything you’ll need to know about reason code 4808: what it means, why it happens, how to fight it if you have a legitimate case - and more - how to stop it from showing up. Whether you’re seeing these chargebacks for the first time or seeing them on a recurring basis, this is the resource that can help 4808 finally make sense.

What Triggers a 4808 Chargeback in the First Place

A 4808 chargeback can hinge on one core idea: the transaction wasn’t authorized, or the authorization that existed was no longer valid when the charge went through. There are a few ways it can happen, and each one tells a slightly different story about where the process broke down.

The simplest trigger is a missing authorization altogether- this happens when a merchant processes a transaction without approval from the card network or issuing bank first. No approval code means no protection, and that leaves the merchant with very little to stand on if the cardholder disputes the charge.

An expired authorization is another common trigger. Authorizations don’t stay active forever, and if a merchant waits too long to capture the payment after approval, that authorization can lapse. Processing a charge against an expired authorization is treated the same as processing without one.

The third trigger is a transaction amount that exceeds what was authorized. If a customer authorized an amount and the final charge came in higher, that extra amount falls outside the scope of the original approval- this can happen with tips, add-on services, or estimated charges that come in higher than expected.

It’s worth knowing that 4808 didn’t always exist as a standalone code. Mastercard went through a consolidation of its chargeback reason codes starting in 2016, and 4808 absorbed what used to be covered under older codes like 4807 and 4812. The logic behind this was to simplify the dispute process and group related authorization problems under a single code.

Understanding why these triggers matter is actually more helpful than memorizing the list. Authorization exists to protect both sides of a transaction. The issuing bank is confirming that the funds are available and that the card is in good standing. When that step is skipped, incomplete, or outdated, the cardholder’s bank has a legitimate basis to pull the funds back on their customer’s behalf.

From a merchant’s perspective, an authorization is the foundation that holds a transaction together- not a formality. If that foundation has a problem, the whole charge can become vulnerable to dispute regardless of whether the goods or services were actually delivered.

The Key Deadlines That Decide Your Fate With Code 4808

Timing is everything with a 4808 chargeback. Mastercard sets strict windows for when a chargeback can be filed and how long a merchant has to respond, and missing any of these deadlines removes your ability to fight back entirely.

The first deadline to know is the 90-day rule. A bank has up to 90 days from the transaction date to process a 4808 chargeback against a merchant. That dispute filing window can seem long from a cardholder’s perspective, but from a merchant’s side it means a dispute can land well after the original sale.

Once a chargeback hits, the clock starts ticking again. The merchant’s acquirer usually has 45 days to submit a rebuttal or representment. Missing that window means the chargeback stands, regardless of whether the merchant had a valid case.

There are also two presentation deadlines that are in a merchant’s favor and are worth learning about before the next section covers how to use them. A transaction that was authorized and settled within 7 days can sometimes be used to counter the chargeback. There is also a 30-day window for how long a merchant had to present a transaction after authorization - and if the merchant met that window, it strengthens the defense considerably.

The table above is a helpful reference. The 45-day response window in particular moves faster than most merchants expect, and that’s also the case when disputes arrive during busy periods and get buried in other correspondence.

These numbers define what is and isn’t possible before a merchant even starts to build a case.

How Merchants Can Actually Dispute a 4808 Chargeback

Winning a representment can depend on documentation. If you can show that a valid authorization was obtained at the time of the transaction, the chargeback loses its foundation.

The most helpful piece of evidence is an authorization code - the code your payment gateway returns when a transaction is approved, and it proves that the card network greenlit the transaction. Pair that with a full transaction record showing the date, amount, and card details, and you have the foundation of a strong response.

Timestamps matter more than most merchants expect. The timing of your authorization relative to the transaction has to fall within the rules, and this is where disputes fall apart. For a standard authorization, the transaction needs to be processed within 7 days of the authorization date. For a preauthorization, that window extends to 30 days, but you need documentation to prove the preauth was obtained.

There is also a contactless payment exemption worth learning about. Transactions under €50 made via contactless may be exempt from the authorization requirement under card network rules, so if a disputed transaction falls into that category, it’s worth checking if the exemption applies and building your response around authorization proof.

Here is a quick look at how the important rules line up.

Once you have grabbed your evidence, your rebuttal letter needs to connect the dots. Attach your documents and walk the reviewer through how each piece of evidence supports your case.

It also helps to look at your own process. If you can’t quickly find authorization codes for past transactions, that gap is a problem waiting to surface. Good record-keeping is about more than winning disputes - it’s about being ready to defend any transaction amount discrepancy at any time.

Authorization Mistakes That Keep Showing Up (And How to Avoid Them)

Most 4808 chargebacks don’t come from bad luck. They come from the same handful of process gaps that merchants repeat without realizing it.

One of the most common problems is running a transaction on an expired authorization. When there’s a delay between when a customer places an order and when the payment is captured - which happens often in e-commerce and made-to-order businesses - the original authorization can expire before the charge goes through. The window is usually 7 days for card-present transactions and can vary for card-not-present, but a lot of payment systems don’t flag this automatically. That means the transaction processes without a valid authorization and the merchant doesn’t find out until a chargeback lands.

Delayed shipments create a similar trap. If an item ships later than expected, the original authorization is likely stale and a reauthorization is needed - this step gets skipped more than it should, and that’s also the case when teams are busy or order management systems aren’t set to prompt for it.

Another pattern worth mentioning is how authorization replies get recorded. In high-volume environments, declined replies can slip through without being caught in time - especially when systems aren’t configured to halt processing on a decline. The result is a completed transaction with no valid approval behind it.

Here’s a quick look at the most common failure points:

• Capturing payment after an authorization has expired
• Skipping reauthorization when fulfillment is delayed
• Not storing authorization codes with transaction records
• Processing a transaction despite a declined response
• Using estimated amounts that differ too much from the final charge

That last one trips up subscription and service-based businesses. If the amount captured is meaningfully different from what was authorized, the authorization might not be considered valid - even if it was approved at the time.

The reason these mistakes happen is mostly structural. Teams move fast, systems have gaps, and authorization management doesn’t always get the same attention as other parts of the payment process. A periodic review of how authorizations are captured, stored, and flagged for expiration can go a long way toward cutting down on preventable chargebacks.

Keep Your Authorizations Clean, Keep Your Revenue Safe

The mindset change that matters most here is treating authorization as a standard practice instead of a background process. That means staying current on expiration windows, matching settlement amounts to approved amounts, and making sure your systems aren’t quietly retrying or processing transactions in ways that fall outside network rules. Most merchants who have a hard time with 4808 chargebacks aren’t doing anything dishonest - they just haven’t looked closely enough at the difference between how their payments should be flowing and how they actually are.

Chargebacks like 4808 can seem like a penalty for something technical and obscure, but they’re just a signal worth responding to. When they show up, they point directly at a process that needs tightening. Fix the process and the chargebacks follow; it’s not a guarantee against every dispute, but it’s as close to a preventable problem as the payments world has. If you’re also seeing duplicate processing issues alongside authorization errors, that’s worth investigating as a related workflow problem. And if you’re managing authorization issues across multiple dispute types, having a clear response process in place makes a real difference. That’s worth something.