F29: Card Not Present

The frustrating part is that a lot of these disputes are preventable. Not all of them, but enough that understanding the mechanics behind F29 can make a real difference in how you see it - and how successfully you fight back. That starts with learning what actually triggers this reason code, what American Express expects from merchants who want to dispute it, and what steps you can take to cut back on your exposure.

I’ll walk you through it. Whether you’ve just received your first F29 chargeback or you’re stuck in a pattern you can’t seem to break, you’ll find helpful, simple guidance here so you can respond with confidence and tighten up your defenses going forward.

What F29 Actually Means and Why Amex Uses It

F29 is an American Express chargeback reason code that falls under their fraud category - it gets filed when a cardholder says their account was charged for a transaction they didn’t authorize - specifically one where the physical card was never present at the point of sale.

“Card Not Present” is a technical way to say the transaction happened without the card being swiped, tapped, or inserted - this covers online purchases, phone orders, or anything where a buyer types in their card details instead of handing the card over. The card itself never changes hands, so there’s no way to verify the person is the cardholder.

That’s why Amex treats F29 as a fraud claim instead of a standard dispute. A standard dispute could be about a billing error, a product that never arrived, or a service that didn’t deliver. Fraud is different - the cardholder is saying they had no involvement in the transaction at all.

This distinction matters for merchants because the bar is higher. With a fraud-based chargeback, you’re not resolving a disagreement between a buyer and a seller. You’re up against a claim that the transaction was unauthorized from the start, which puts the burden on you to show that a legitimate cardholder actually approved the charge.

Amex structures its reason codes this way to separate cases by root cause. The F-series codes are all fraud-related, and F29 is the one that applies specifically to card-not-present environments - it doesn’t mean every F29 claim is genuine fraud - cardholders can and do file these incorrectly - but it does mean Amex has categorized it as a fraud allegation by default.

That framing helps you respond more effectively. When you’re facing a fraud code instead of a service dispute, you know which evidence is going to matter when you build a response.

The Transactions That Tend to Trigger an F29 Chargeback

Any transaction where the physical card isn’t present at the point of sale carries more exposure to this dispute. That covers online checkouts, phone orders, and recurring subscription charges. These channels all share the same weakness: there’s no way to confirm the person placing the order is the cardholder.

Subscription billing is an especially common trigger. A cardholder signs up, forgets about the charge, and then sees it on their statement weeks or months later with no immediate memory of it. From their perspective, it looks like something they didn’t authorize - even if they did.

Phone orders have a similar problem. The merchant takes the card details verbally, processes the payment, and ships the goods. There’s no signature, no chip read, and no real-time confirmation from the cardholder. If that person later denies placing the order, there’s very little to point to as proof.

What cardholders usually claim when they file is simple: they didn’t make the purchase, or they didn’t recognize the charge. Sometimes that’s true - card details do get stolen and used without the cardholder’s knowledge. Other times it’s a billing descriptor that doesn’t match the business name they remember, and the cardholder disputes the charge before investigating more.

That distinction matters because the underlying cause shapes how defensible the transaction is. Actual fraud means someone used stolen card data to place an order, and the merchant had no way to know. A forgotten or unrecognized charge is a different situation, and merchants can sometimes address it with billing descriptors and purchase confirmation emails.

Digital goods and immediate-delivery products also show up in these disputes more than physical goods do. There’s nothing to return and no shipping trail to reference, which makes it harder to show that the transaction was legitimate. High-ticket items are another area where disputes concentrate because the financial incentive to dispute is higher.

The pattern across these is the same: no card, no in-person verification, and a cardholder who says they didn’t approve it. It’s the environment where F29 takes root, and it’s worth understanding the mechanics before getting into what merchants can do once a dispute lands in their inbox.

Your Response Window and What the Timeline Looks Like

Once an F29 chargeback lands, the clock starts instantly. You have 20 days from the filing date to submit your response to American Express. That window does not pause or extend.

If you miss that 20-day deadline, the chargeback usually sticks. There is no standard appeals path for late submissions, so the funds go back to the cardholder and the dispute closes against you. That is the main reason to act as soon as you receive the notification, even if you feel confident you can win the case.

Once you submit your evidence, Amex takes over. Their review period runs between 20 and 30 days, which means the full process from the filing date to a final choice can take anywhere from 40 to 60 days. Here is how that breaks down in practice.

Stage	Who Acts	Timeframe
Chargeback filed	Cardholder/Amex	Day 0
Merchant response window	Merchant	Up to 20 days
Amex review period	American Express	20-30 days
Final decision	American Express	40-60 days total

One thing worth knowing about this timeline is that your 20 days is the only part you control. The Amex review period is fixed on their end, and there’s nothing you can do to speed it up once your response is in. So the best use of your time is to build a well-organized response instead of rushing something through and hoping to add to it later.

It also helps to keep an eye on how notifications come through for your account. Some merchants receive chargeback notices by email and some through their payment processor’s portal, and delays in finding those notifications can eat into your 20-day window without you even knowing it. Setting up alerts through your processor is a helpful way to stay on top of incoming disputes so your response time stays good.

Building Your Case - Evidence That Actually Holds Up

Before you put together a response, check one thing first: if your business is enrolled in Amex’s Fraud Full Recourse program, you can’t submit Compelling Evidence for an F29 claim at all. Amex will decline it outright. It’s worth confirming with your payment processor before you spend time collecting documents.

For everyone else, the goal is to show Amex that the legitimate cardholder was the one who made the purchase. Generic transaction records won’t do it. You need evidence that connects the cardholder to that order.

What to Pull Together

AVS and CVV match results are a good starting point because they show the person who placed the order had access to the billing address and the physical card. An IP address log with the transaction date is also useful, and you can combine it with device fingerprint data that links back to the cardholder’s known device. Signed agreements or saved account profiles that the cardholder created can help establish that they had an active relationship with your business.

For physical goods, delivery confirmation with a signature is worth including. For online products, access logs that show the content was downloaded or used after purchase are a basic substitute. The important thing is to show activity that only the actual cardholder could plausibly have taken.

A Note on Certain MCC Codes

Merchants with MCC codes 5815, 5816, 5817, or 5818 - which cover online goods like music, games, and software - have to follow mandatory documentation rules when responding to F29. These merchants need to submit device ID data, customer account details, and transaction-level logs as a baseline - it’s not optional. Amex sets a higher bar here because online goods have no physical delivery trail to fall back on.

Why Some Evidence Gets Rejected

Amex will set aside evidence that feels circumstantial or that could apply to any transaction. A screenshot of a completed payment gateway transaction, just to give you an example, does not prove the cardholder authorized it. What gets rejected most is documentation that confirms the sale happened instead of documentation that confirms who made it.

Amex also expects the evidence to be legible, timestamped where applicable, and directly tied to the disputed transaction reference number. Submissions that are disorganized or missing that connection are usually written off without much consideration.

Keeping F29 Chargebacks From Becoming a Pattern

On the front end, a few targeted changes can meaningfully cut back on your exposure:

• Use strong authentication tools like 3D Secure to shift liability and add a verifiable layer of cardholder confirmation at checkout.
• Tighten your fraud screening with velocity checks, device fingerprinting, and AVS/CVV verification to catch suspicious orders before they ship.
• Clarify your billing descriptors so customers immediately recognize the charge - confusion is one of the most common reasons a legitimate transaction turns into a dispute.
• Document everything at the point of sale, because the evidence collected upfront is the same evidence that wins representments later.

Take an honest look at your latest setup. If your authentication is weak, your descriptors are vague, or your fraud filters haven’t been reviewed recently, you’re likely more exposed than you think. The next F29 chargeback is avoidable, but only if you make the adjustments now, before it arrives.