American Express American Express Code

F24: No Cardmember Authorization

This reason code falls under American Express’s fraud-related dispute category, and it carries rules around how disputes are filed, what evidence is required, and how merchants can fight back. Knowing those rules is the difference between absorbing a loss and successfully recovering your revenue.

I’ll break down what F24 means, why it happens, and what you can do - to respond to an existing dispute and to avoid future ones from landing on your plate.

What the F24 Reason Code Actually Means

F24 stands for “No Cardmember Authorization” and it sits inside American Express’s Fraud category. That placement matters. F24 is a fraud-flagged chargeback, which puts it in a different league than a billing dispute or a delivery complaint.

When a cardholder files an F24 dispute, they’re telling Amex they never authorized the charge. They’re not saying the product was wrong or the service was disappointing. They’re saying the transaction shouldn’t have happened at all. Amex takes that seriously, and so does the Fair Credit Billing Act of 1974, which gives cardholders the legal right to dispute any charge they didn’t authorize.

Unauthorized credit card transaction dispute illustration

That federal protection is part of why these disputes carry actual weight. The law exists to protect consumers from fraudulent charges, and Amex’s chargeback process is built to honor it. As a merchant, you’re responding to a claim with legal backing behind it - not just a customer complaint. If you ignore it entirely, understand what happens if you never reply to a credit card dispute before making that choice.

It also helps to know where F24 sits relative to other Amex fraud codes. They each point to a different scenario, so the distinction shapes how you respond.

Reason Code Name What the Cardholder Is Claiming
F24 No Cardmember Authorization They never authorized this specific charge
F29 Card Not Present Their card was used online without their knowledge
F30 EMV Counterfeit Transaction A counterfeit card was used at a chip-enabled terminal
F31 Lost or Stolen Card Someone used their physical card after it was lost or stolen

F24 is the broadest of these - it doesn’t point to a fraud strategy like a counterfeit chip or a stolen card - it just means the cardholder is denying they approved the transaction at all.

The 20-Day Clock Merchants Can’t Afford to Miss

American Express gives merchants 20 calendar days to respond to an F24 dispute. That word “calendar” is doing work here - it means weekends count, holidays count, and there’s no extensions just because the dispute landed on a Friday afternoon.

The clock starts the day Amex notifies you of the chargeback - not the day you open the email. So if a notification sits unread for three days, those three days are already gone.

Miss the deadline and the dispute resolves against you automatically. Amex doesn’t review late submissions or weigh the circumstances. The chargeback stands, the funds go back to the cardholder, and there’s no appeal process to fall back on.

Calendar with urgent deadline marked in red

The table below shows how fast this dispute window moves in practice.

Day What’s Happening Where You Stand
Day 0 Amex files the dispute and sends merchant notification Response window opens
Days 1-5 Notification may sit unread or get flagged as routine Clock is running
Days 6-15 Active response window - evidence can be gathered and submitted Still in play
Days 16-19 Final window to submit a complete response Limited time left
Day 20 Deadline passes Automatic loss if no response submitted

Twenty days is enough time until you factor in internal approvals, tracking down transaction records, and coordination with payment processors - it goes fast. The merchants who respond successfully are usually the ones who treat day one like it matters.

Why Amex Lists No Admissible Evidence for F24

American Express does not list any admissible evidence for F24 disputes in its chargeback rules - not a single item. Most dispute codes have at least some input on what to submit, but F24 is a blank slate.

That’s an actual problem when building a rebuttal. If you don’t know what Amex considers valid proof, merchants are left to guess - and guessing with a chargeback response is not a great position to be in.

In practice, merchants submit the same documents they’d use for other dispute types. A signed receipt shows the cardholder was present for the transaction. An AVS match confirms that the billing address lined up at checkout. Delivery confirmations show the order arrived at the address on file. IP logs can put a device at a location and time. These are all basic pieces of evidence - but Amex has never confirmed that any of them will hold up for F24 specifically.

The ambiguity cuts both ways. A merchant might submit a strong package of documentation and still lose, with no actual explanation of why the evidence fell short. There’s no rubric to check against and no list of what would have made the difference.

ChatGPT screen showing no evidence listed

What makes this especially frustrating is that F24 means a very specific claim: the cardholder says they never authorized the transaction. To counter that, there should be a defined standard of proof. There isn’t.

When the rules don’t tell you how to win, most merchants submit what they have and hope the documentation is enough to change the outcome; it’s persistence without direction - and persistence without direction means lost disputes that may have gone differently with clearer input.

Friendly Fraud and the F24 Abuse Problem

Behind a lot of F24 disputes is a situation that has nothing to do with a stolen card or an unauthorized transaction. The cardholder made the purchase themselves, received what they paid for, and then disputed the charge anyway. That’s friendly fraud, and it’s far more widespread than most know.

Research from Visa found that friendly fraud accounts for as high as 75% of all chargebacks; it’s a staggering share, and it looks less like a pattern of isolated incidents and more like systemic abuse.

F24 is especially attractive to this kind of misuse because the claim is so open-ended. A cardholder only needs to say they didn’t authorize the charge - there’s no story to keep straight, no supporting evidence to fabricate. That vagueness makes it harder for merchants to push back with a direct rebuttal.

Frustrated person disputing a valid credit card charge

It also puts merchants in a tough position. You served the customer, completed the transaction, and held up your end of the deal. Then weeks later, a dispute arrives and the burden falls on you to prove something that should never have been questioned.

Some of these disputes come from buyers who regret a purchase and see a chargeback as an easier path than a refund request. Others may be testing the system or might not fully understand that disputing a legitimate charge has real consequences for the merchant. In either case, the merchant pays the price.

It’s also worth mentioning that friendly fraud isn’t always deliberate. A family member uses a card without telling the account holder, or doesn’t recognize a charge from a business name that’s different from the brand they know. These cases still cause an F24 filing, and they still need a response from the merchant.

The structure of F24 - with its minimal evidence requirements on the cardholder’s side - gives cardholders a low barrier to file and leaves merchants with a high burden to fight.

Steps Merchants Can Take Before and After an F24 Dispute

Prevention is where merchants have the most control. A few habits at checkout can make a real difference when a dispute hits later.

Before a Dispute

  • Use CVV and AVS checks on every card-not-present transaction to confirm the buyer has the physical card and knows the billing address.
  • Make sure your billing descriptor - the name that appears on the cardholder’s statement - matches your business name or website. A confusing descriptor is one of the easiest ways to trigger a dispute.
  • Keep detailed authorization records for every transaction, including timestamps, IP addresses, and device data where possible.
  • For high-value orders, consider adding extra verification steps like two-factor authentication or a signed confirmation email.
  • Store order confirmations, delivery records, and any customer communication in a way that’s easy to pull up quickly.

After an F24 Dispute

Once an F24 lands, your window to respond is short and the evidence bar is high. Amex doesn’t publish a complete checklist for what wins an F24 rebuttal, but that’s not a reason to go in light.

  • Write a concise rebuttal letter that explains why you believe the transaction was authorized and legitimate.
  • Attach all supporting documents - the authorization record, IP log, delivery confirmation, and any correspondence with the customer.
  • If the customer interacted with your site after the purchase (logged in, downloaded something, used a service), include that data too.
  • Be factual and direct. Don’t editorialize or make accusations; let the documentation do the work.

There’s no guarantee a well-built rebuttal will win, but submitting a complete response is always better than not responding at all. Amex will decide either way, and you want your side of the story on record.

Don’t Let F24 Catch You Off Guard

Treat dispute prevention as a continuous habit instead of a problem you solve once and forget. Audit your authorization records, make sure your descriptors are recognizable, and make sure your customer service is easy enough to reach that a confused cardholder calls you before they call Amex. Small friction points in the customer experience tend to turn into chargebacks months later.

Surprised person caught off guard by alert

When an F24 dispute does arrive, move faster, document thoroughly, and build your rebuttal around concrete evidence instead of assumptions about what happened. Merchants who recover well from chargebacks are the ones who are already prepared when they do.

Chargebacks are a cost of doing business. Losing them repeatedly is not.

FAQs

What does the F24 reason code mean?

F24 stands for "No Cardmember Authorization" and falls under American Express's fraud dispute category. The cardholder is claiming they never approved the transaction, which carries legal backing under the Fair Credit Billing Act of 1974.

How long do merchants have to respond to F24?

American Express gives merchants 20 calendar days to respond to an F24 dispute. Missing this deadline results in an automatic loss, with no appeal process available.

What evidence should merchants submit for F24?

Amex publishes no official evidence list for F24. Merchants typically submit signed receipts, AVS match confirmations, delivery records, IP logs, and customer correspondence, though no evidence is guaranteed to win.

What is friendly fraud and how does it relate to F24?

Friendly fraud occurs when a cardholder disputes a legitimate charge they actually authorized. F24 is especially vulnerable to this abuse because the claim requires minimal cardholder evidence, making it easy to file falsely.

How can merchants prevent F24 disputes?

Use CVV and AVS checks, maintain clear billing descriptors, keep detailed authorization records, and store order confirmations. Making customer service easy to reach can also prevent cardholders from filing disputes instead of contacting you directly.

Leave a Comment