C02: Credit Not Processed

If you’re reading this after receiving a C02 chargeback, you’re in the right place - this post breaks down what this reason code means, why it happens, what American Express expects from merchants, and how to either fight the dispute or stay away from it altogether next time. We want to give you a path forward - no guessing, no unnecessary stress.

What Triggers a C02 Chargeback in the First Place

A C02 chargeback happens when a customer believes they were owed a credit that never showed up on their account. The dispute is the customer’s way of saying they were promised money back and never got it.

The most common situation is a refund that a merchant agreed to but never actually processed. A customer returns a product, gets a confirmation email, and then checks their statement a week later to find nothing there. At that point, filing a dispute is the only move left.

Returns that went through on the merchant’s side but didn’t reach the card are another big one - this happens more than merchants expect - the return is logged in the system, maybe even accepted at a physical store, but the credit never gets pushed through to the card network. From the customer’s view, the money just disappeared.

Cancellations are also a standard trigger. A customer cancels a subscription or an order, sometimes with a confirmation number in hand, and still gets charged with no refund to follow. The difference between what the merchant’s system shows and what the customer’s bank shows is where C02 disputes are born.

Here’s a quick look at the scenarios that come up most:

Partial refund disputes fall into this category too. If a customer expected a full refund and only received part of it without any explanation, that gap can become a reason to escalate through their bank.

What these share is a breakdown in follow-through - not necessarily bad intent, but a failure to complete the transaction cycle from the customer’s perspective. When these situations arise, merchants should also be aware of the credit card dispute window and how quickly customers can act.

The C02 Dispute Timeline You Need to Know

Once a C02 dispute is filed, a clock starts - and every party in the process has a deadline to hit. Miss yours and you lose the ability to fight back, no matter how strong your case is.

Cardholders have as long as 120 days from the transaction date to file a C02 dispute with American Express; it’s a fairly long window on their end, which means a chargeback can land in your lap months after the original transaction, at a point you may have already assumed everything was fine.

Once the dispute reaches you, things move much faster. Merchants get 20 days to respond with evidence; it’s not a lot of time to pull records, write a rebuttal, and get everything submitted - so when you receive a dispute notice, treat it as urgent.

After you submit your evidence, American Express takes 20 to 30 days to review it and decide. The full resolution process - from your response to a final outcome - usually runs 40 to 60 days. That waiting period can seem long, but there’s nothing to do on your end except make sure your submission was complete and accurate before the deadline.

The part that hurts merchants most is the difference between when a transaction happens and when the dispute arrives. You could be looking at records from three or four months ago, which makes documentation harder to track down quickly. Well-organized records are what make those 20 days workable instead of stressful.

If you miss the merchant response window, American Express will probably rule in the cardholder’s favor automatically. The deadline is firm.

How to Fight a C02 Chargeback With Evidence That Actually Holds Up

The Fair Credit Billing Act of 1974 gives cardholders the legal right to dispute a charge they believe was not credited; it’s the foundation every CO2 chargeback is built on, and your job is to show the bank that the credit was handled correctly on your end.

The strongest rebuttals are built around documentation that tells a clear story. You need to show that the refund was processed, that it was communicated to the customer, and that the timeline was reasonable. If any part of that chain is missing, the bank is likely to side with the cardholder.

Evidence That Carries the Most Weight

A refund confirmation email sent to the customer is one of the most direct pieces of proof you can submit. Pair that with your transaction records showing the credit was issued, and you already have a good base to work from. Communication logs - like support tickets or chat transcripts - help fill in the context around when the customer first raised the concern and how your team responded.

Where Merchants Go Wrong

The most common mistake is submitting documentation that’s incomplete or hard to follow. Banks review disputes, and a rebuttal that is going to need too much interpretation is easy to dismiss. Be direct about what each document proves and how it connects to the disputed transaction.

It is also worth looking critically at your own records. If there’s a difference between when the refund was processed and when it was communicated to the customer, that gap will work against you. Tighten up that story before anything gets submitted. You can also review our credit not processed response template to see how a well-structured rebuttal comes together.

Vague language in a rebuttal letter is another weak point. Phrases like “a refund was issued” without dates or reference numbers leave too much room for doubt. Specific facts are what make a response credible.

When the Chargeback Is Valid and a Refund Was Genuinely Missed

Not every C02 chargeback is worth fighting. Sometimes the customer is right and the refund just never made it through; it’s not worth spending time building a dispute case.

Internal breakdowns like to show up more than most merchants expect. A refund gets approved verbally but no one processes it. A system glitch logs the transaction without completing it. A staff member works with the return but marks the wrong order. These things happen, and that’s also the case in smaller operations where one person is juggling quite a bit at once.

The better move in these cases is to accept the chargeback instead of fight it. Disputing a chargeback you’re likely to lose costs you time and usually an extra fee on top. If the refund was legitimately missed, accepting it faster is the cleaner path.

What matters more is figuring out how the gap happened so it doesn’t repeat. A quick audit of your refund workflow can show quite a bit. Look at where refunds are approved, who has access to process them, and how your team confirms completion. If any of the steps use memory or informal communication, that’s where things break down.

A Few Internal Checks Worth Running

You don’t need a complex system to catch these problems early. A few basic checkpoints go a long way.

Running through this list after a chargeback arrives can tell you within a few minutes if the dispute has merit. If it does, you have your answer.

Refund management gets messy at volume, and that’s not a failure on your part - it’s a reality of running transactions at scale. The goal isn’t a perfect record. The goal is a process that catches mistakes before a customer has to escalate to their bank to get their money back.

Keeping C02 Chargebacks From Becoming a Pattern

The triggers, timelines, and evidence requirements covered here all point back to the same root issue: a gap between the refund being promised and the customer seeing it. That gap may live in your processing system, your communication with the customer, or your internal refund workflow, and it’s worth finding before the next dispute arrives - not after.

Take a close look at your latest refund process. Ask if customers are being notified when a credit is issued, if your processing timelines are realistic, and if your team has a record of what was promised and when. Closing those gaps is the most effective way to avoid C02 chargebacks from becoming a recurring problem - and to make sure that if you do fight one, your evidence is already in order.