What Mastercard reason code 4808 means
The issuer files 4808 when its records do not show an approved authorization that matches the cleared transaction. Mastercard merged several older codes into 4808, including the former warning bulletin and account number not on file codes, so one dispute can cover quite different situations. Some processors still display those legacy codes. The defense is the same: prove that an approval existed, was still valid on the settlement date, and covered the amount you presented.
Typical triggers for a 4808 chargeback
-
A preauthorization for a hotel, rental or marketplace order was captured after it expired.
-
The order shipped late and the merchant captured an old authorization instead of requesting a new one.
-
The authorization was declined but the transaction was still submitted, for example after an offline or stand in approval.
-
The captured amount was higher than the authorized amount beyond what your merchant category allows.
Time limits for Mastercard 4808
For authorization related chargebacks the issuer typically has 90 days from the settlement date, shorter than the 120 days that applies to many other Mastercard codes. Your own response window is set by your processor and is often between 7 and 21 days. In Stripe the exact deadline is the evidence due date on the dispute, and a missed deadline loses the case automatically.
Evidence that wins a 4808 dispute
-
The authorization record with approval code, date, time and approved amount.
-
The clearing record showing the settlement date falls inside the authorization validity period. Under Mastercard rules a preauthorization typically stays valid up to 30 days and other authorizations around 7 days.
-
Proof of an incremental or new authorization when the final amount or capture date changed.
-
Your merchant category and the tolerance it allows between authorized and captured amounts, where one applies.
What to avoid when you respond
-
Do not argue that the customer received the goods. 4808 is about authorization, and delivery proof alone does not answer it.
-
Do not refund after the chargeback posts, because the funds are already withdrawn and you can lose twice.
How to prevent Mastercard 4808 chargebacks
-
Capture authorizations as soon as you fulfill, and track how many days each open authorization has left.
-
Request a fresh authorization when shipping slips past the validity window.
-
Use incremental authorizations for tips, extended stays and add ons instead of capturing above the approval.
-
Never submit a declined transaction, and treat stand in approvals as a risk to review.
How 4808 appears in Stripe
Stripe usually shows Mastercard 4808 under the reason general, and the raw code 4808 always appears in the network reason code field on the dispute. NoChargeback reads that field, pulls the authorization and capture timestamps from the charge, and lines up approval, amount and settlement date. See Stripe chargeback protection and dispute automation.
Rebuttal letter opening for Mastercard 4808
We are responding to the dispute filed under Mastercard reason code 4808. The transaction received an approved authorization from the issuer, shown below with its approval code, date and amount. The transaction was presented for clearing within the validity period of that authorization and for an amount no greater than the approved amount, so the authorization requirement was met.
Can a merchant win a Mastercard 4808 chargeback?
Yes. If you can show an approved authorization that was still valid on the settlement date and covered the captured amount, the issuer has no basis for 4808. The authorization log from your processor is the core evidence.
How long is a Mastercard authorization valid?
Under Mastercard rules a preauthorization typically stays valid for up to 30 calendar days, and other authorizations for around 7 days. Capturing after that window without a new authorization is the most common cause of 4808.
Is 4808 a fraud chargeback?
No. 4808 is a technical authorization dispute. It does not claim the cardholder was absent, so fraud evidence such as IP address or login history rarely helps. Authorization records do.