A08: Authorization Approval Expired

I’ll talk about what A08 means, the scenarios that cause it to show up, how to build a representment case if you believe you have a legitimate path to fight it, and - most importantly - what you can do to prevent it from happening again. If you’re dealing with one of these, you’re in the right place.

What American Express Reason Code A08 Actually Means

American Express groups its reason codes into five categories: Authorization, Fraud, Processing Errors, Card Member Disputes, and Inquiry/Miscellaneous. A08 sits in the Authorization category, which covers disputes related to how a transaction was approved - or in this case, how it wasn’t captured in time.

The core issue with an A08 chargeback is simple. A merchant got authorization approval for a transaction but then captured the payment after that authorization had already expired. At that point, the approval is no longer valid, and American Express treats the charge as unauthorized.

Authorization approvals don’t last forever. When a merchant requests authorization, they’re given a window to complete the transaction, and that window changes depending on the type of business. Most merchants need to capture payment within 7 to 10 days, but some categories get a longer runway based on their merchant category code.

If a transaction falls outside that window, the original approval no longer covers it. Capturing payment after that point means there’s no valid authorization on file, which is what triggers an A08.

Authorization and capture are two separate steps in the payment process. Authorization confirms that a card is valid and that funds are available at that moment. Capture is when the merchant collects the money. The difference between these two steps is where A08 chargebacks come from.

Merchants who batch-process transactions at the end of the day or week can be especially vulnerable if any authorizations in that batch are older than their validity period allows. The same danger applies to delayed shipments where a merchant authorizes a card at purchase but waits to capture until the order ships - a situation that can also affect how you manage your credit card dispute window.

The Situations That Typically Trigger an A08 Chargeback

Some business models run a actual danger of this code because of how their transactions are structured. Travel, hospitality, and pre-order retail all share something in common: there’s usually a difference between the second a customer pays and the second a charge actually goes through.

Hotels are a good example. A property will place an authorization hold at check-in, but if the guest’s stay runs longer than expected or checkout gets delayed, that original authorization can expire before the final charge is captured. The hotel might not even know the hold has lapsed until the transaction fails or a dispute lands in their queue.

Delayed shipments create a similar problem for retailers. A customer places an order, the merchant authorizes the card right away, and then a backorder or supply delay pushes fulfillment out by weeks. By the time the item ships and the merchant tries to capture the payment, the authorization window has already closed. Pre-order businesses are especially vulnerable here because the delay is built into the model from the start.

Subscription billing can also trigger an A08 when there’s a timing mismatch between an authorization and the charge cycle - it will happen when a free trial period runs longer than planned or when a billing date changes because of a system error.

Manual processing is another culprit worth mentioning. Smaller merchants who manage transactions without automated payment systems might not capture funds the same day they authorize them. A few days of administrative lag is all it takes for the window to close.

The throughline across these scenarios is that the merchant had every intention of a legitimate transaction. The customer agreed to the charge, the goods or services were delivered or on the way, and the business did nothing wrong in terms of intent. The problem is purely procedural - the clock ran out before the capture happened.

That’s what makes this code different from fraud-related chargebacks. There’s no deception involved on either side - it’s a timing failure, and the business models most exposed to it are the ones where fulfillment or finalization takes time.

How the Dispute Window and Response Timeline Work

Once a cardholder or their bank flags a transaction, the clock starts running. They have as long as 120 days from the transaction date to file an A08 chargeback, which gives them a fairly wide window to act.

When the dispute lands on your side, your window is much smaller. Merchants get 20 days to respond, and that deadline is firm. Missing it means the chargeback is automatically resolved in the cardholder’s favor, and you lose the funds with no more recourse; it’s a hard stop, not a technicality.

After you submit your response, the issuer and card network take over. Resolution usually lands between 40 and 60 days, though it can stretch longer in tough cases. You won’t have much visibility into that process, so your response needs to do the heavy lifting on day one.

The 20-day window is where most merchants run into issues. Disputes can get buried in inboxes or routed to the wrong person, and by the time someone realizes what happened, the deadline has already passed. An internal process for catching these notifications fast helps stay away from that outcome.

It’s also worth knowing that you can’t submit extra evidence after the response window closes. Whatever you send in that 20-day period is what the issuer will base their decision on, which is why the quality of your rebuttal matters from the start.

Building a Rebuttal That Actually Holds Up

A generic rebuttal letter is not going to cut it with an A08 dispute. Issuers have seen the boilerplate responses and they are looking for something more concrete than “the transaction was legitimate.” Your job is to show them why the authorization was valid and why the charge should stand.

The most important thing to know is what the issuer needs to see. They are not looking to side with whoever argues loudest - they want documentation that tells the story of the transaction. That means pulling together records that connect the authorization to the sale in a way that leaves little room for doubt.

Start with your authorization records. You want the approval code, the timestamp and the card data that was captured at the point of sale. If the authorization and the settlement amounts match, that matters too - discrepancies between those two figures can undermine an otherwise good response.

From there, layer in your supporting documents. You want to build a timeline that the issuer can follow without effort.

Merchants lose these disputes not because the evidence is weak, but because the response does not connect the dots. Submitting a receipt without an authorization record, just to give you an example, leaves the issuer to make assumptions you don’t want them to make. Walk them through it piece by piece.

Keep your written response direct and factual. State what happened, reference each part of evidence by name and explain what it shows. One focused page is more persuasive than three pages of explanation that buries the important facts.

Keep Your Authorizations from Aging Out

Winning a representment on an A08 case is possible, but the stronger play is keeping these disputes from reaching that stage. If your fulfillment process pushes past standard authorization windows, build re-authorization into your workflow before capture. If you work in a category with extended hold laws - like lodging, car rentals, or delayed delivery - double-check that your processing setup is correctly configured to take advantage of the provisions. Small operational adjustments made upstream can remove a large share of these disputes downstream.

As a quick reference, keep these prevention habits in mind:

• Re-authorize before capturing any transaction where fulfillment or shipment has been delayed beyond the standard authorization window.
• Know your network-specific timelines - Visa, Mastercard, American Express, and Discover each set their own expiry rules, and your MCC may affect those limits further.
• Sync your fulfillment and payment capture workflows so authorizations aren’t sitting idle while orders remain in processing queues.
• Audit your systems periodically to catch patterns where captures are consistently running late relative to authorization timestamps.
• Train your team on what authorization expiry means operationally, not just as a technical concept.

Merchants who treat authorization management as an active part of their payments strategy - instead of something that happens automatically in the background - are far less likely to see A08 chargebacks pile up. The laws are knowable, the timelines are manageable, and with the right processes in place, this dispute reason can become largely avoidable.