Skip to main content

Mastercard 4808 - Authorization-Related Chargeback

Overview​

Used when authorization was required but not properly obtained, or when authorization requirements were not met.

When This Code Applies​

  • Authorization was required but not obtained
  • Offline chip-approved transaction presented more than 7 calendar days after transaction date
  • Refund transaction presented more than 5 calendar days after transaction date
  • Account not in good standing and authorization protection period expired
  • Card-not-present authorization declined by issuer but approved through Stand-In or X-Code
  • Transaction improperly occurred at CAT 3 device
  • Transit First Ride Risk (FRR) claims

Transactions Ineligible for This Chargeback​

  • Properly identified Emergency Cash Advance transactions
  • Properly identified contactless transit aggregated transactions meeting all conditions
  • Taiwan domestic in-flight transactions (per AN 2491)

Time Frames​

RegionChargeback Window
Standard90 calendar days from settlement date
Mainland China5-90 calendar days from settlement date
ATM/Maestro (Europe)120 calendar days from Central Site Business Date

Authorization Protection Periods​

Authorization TypeProtection Period
Preauthorizations30 calendar days
Final authorizations (India domestic)4 calendar days
Final authorizations (all other)7 calendar days
Undefined authorizations7 calendar days

Gratuity Tolerances​

Transaction TypeTolerance
Chip and PIN0%
Contactless0%
QR transactions0%
Final authorization coded0%
Mainland China domestic0%
US domestic card-not-present (MCC 5812, 5814)30%
US domestic card-present30%
All other card-present20%

Currency Conversion Tolerance​

A 10% tolerance exists for currency conversion differences between authorization and clearing dates.

Representment Options​

The acquirer may second present when:

  1. Authorization was properly obtained - Valid authorization exists for the transaction
  2. One authorization covered multiple clearing records - Split shipment or partial fulfillment scenario
  3. A refund was previously issued - Transaction was already credited
  4. The chargeback was invalid - Doesn't meet reason code requirements

Required Documentation​

For ChargebackFor Representment
None requiredProof of valid authorization

Second Presentment Time Frames​

RegionWindow
Standard45 calendar days from chargeback settlement
Costa Rica domestic10 calendar days
Kazakhstan domestic30 calendar days
Nigeria domestic2 business days
Tanzania domestic20 calendar days

Message Text Requirements​

When second presenting, include in DE 72:

  • AUTH MMDDYY/NNNNNN (authorization date and approval code)

Prevention Tips​

Best Practices​

  1. Always obtain authorization before processing - Never process without a valid auth
  2. Clear transactions within protection periods - Don't let authorizations expire
  3. Use proper authorization codes - Distinguish between preauth and final auth
  4. Monitor for Stand-In approvals - These bypass issuer and may be declined later
  5. Track authorization expiration - Set alerts before protection periods end

Common Mistakes​

  • Processing after authorization expiration
  • Not obtaining auth for add-on charges
  • Incorrect authorization amount vs. clearing amount
  • Delayed clearing beyond protection window

Win Rate Expectations​

ScenarioExpected Win Rate
Valid authorization exists70-85%
Authorization expired but valid30-50%
No authorization obtainedUnder 10%
  • 4807 - Warning Bulletin
  • 4812 - Account Number Not on File

Next Steps​

Got this chargeback?

  1. Pull authorization logs → Do you have a valid auth code?
  2. Check auth-to-capture timing → Did you exceed the protection period?
  3. Gather evidence → Representment Workflow
  4. Respond within 45 days (Mastercard)

Prevent future 4808 chargebacks:

  1. Capture within authorization validity window (7 days standard)
  2. Re-authorize if capturing later than protection period
  3. Use proper incremental auth for changed amounts
  4. Review authorization basics

See Also​