What Amex Reason Code C02 Means
American Express reason code C02, titled Credit Not Processed, is filed when a cardholder expected a refund or credit to their Amex card but it never appeared on their account. This is the Amex equivalent of Visa 13.6 and Mastercard 4860 — the cardholder is not disputing the original charge, they are asserting that a promised or entitled refund was not delivered.
The dispute arises when a refund was agreed upon but not processed, delayed excessively, issued to the wrong payment method, or when the cardholder returned merchandise and expected a credit that was never submitted. As with all Amex disputes, the 20-day merchant response window is significantly shorter than Visa or Mastercard.
If a refund is legitimately owed and has not been issued, process it immediately rather than fighting the chargeback. The chargeback fee plus ratio damage always exceeds the cost of the refund. Only representment if you have already issued the credit (and can prove it) or have documented grounds showing no credit was owed under your disclosed policy.
Cross-Network Equivalent Codes
| Network | Code | Title | Notes |
|---|---|---|---|
| Amex | C02 | Credit Not Processed | This page; 20-day response window |
| Visa | 13.6 | Credit Not Processed | Direct equivalent; 30-day response window |
| Mastercard | 4860 | Credit Not Processed | Direct equivalent; 45-day response window |
| Discover | CR | Credit Posted as Purchase | Discover's closest equivalent |
Common Trigger Scenarios
- Refund promised but never submitted. A customer service interaction resulted in a refund commitment, but the refund was never actually processed to the payment processor. The cardholder waits a billing cycle and then disputes with Amex.
- Refund delayed beyond one billing cycle. The merchant initiated the refund but due to internal approval delays or batch processing issues, the credit took more than 30 days to appear. Amex cardholders have limited patience for delayed credits.
- Store credit issued instead of card refund. The merchant issued a gift card or account balance when the cardholder expected a refund to their Amex card. Without explicit cardholder agreement to the alternative, Amex sides with the cardholder.
- Return received, credit not issued. The merchant received a returned item but failed to process the credit — due to returns/finance workflow gaps, condition disputes, or restocking fee disagreements.
- Partial refund dispute. The merchant issued a partial refund (deducting restocking fees, shipping costs, etc.) and the cardholder disputes the remainder as an unprocessed credit.
Key Deadlines & Timeframes
| Milestone | Timeframe | Notes |
|---|---|---|
| Cardholder Filing Window | 120 days | From the transaction or expected credit date |
| Merchant Response Window | 20 days | From Amex dispute notification — act immediately |
| Second Review | 20 days | If Amex rules against the merchant, 20 days to request second review |
Evidence You Will Need
- Credit transaction record — the processor confirmation showing the credit was submitted, with processing date, amount, and the Amex card reference number
- Refund confirmation sent to the cardholder — email or notification with timestamp showing when the customer was told about the credit
- Refund policy documentation showing the terms the cardholder agreed to, including any conditions or timelines for credit processing
- Customer communication logs documenting the refund request, your response, and any conditions communicated
- Evidence no refund was owed (if applicable) — non-refundable terms clearly disclosed at purchase, return conditions not met, or the request falling outside your policy window
Learn Exactly How to Package and Present This Evidence
The Service Incorrect Defense Guide covers the exact format for presenting credit evidence in Amex C02 representments, how to handle the already-issued credit scenario, and the cross-network approach for Visa 13.6.
Learn exactly how to package and present this evidence →How Merchants Lose This Dispute
- Missing the 20-day Amex response window. The most common and most avoidable loss. Amex's shorter timeline requires a faster internal dispute triage process. Set immediate alerts for all Amex dispute notifications.
- No processor-level credit record. Verbal commitments and internal notes do not constitute evidence of a credit being processed. You need a transaction ID or batch record from your payment processor showing the credit was submitted on a specific date.
- Substituting store credit for card refund without agreement. Amex cardholders have a strong expectation of card-level refunds. Issuing any alternative without explicit written agreement will result in a C02 dispute that is very hard to defend.
- Slow refund processing with no communication. Even if the refund is in process, an Amex cardholder who hears nothing will dispute faster than cardholders on other networks. Proactive status updates prevent disputes during the processing window.
Get the Step-by-Step Winning Strategy
Our Service Incorrect Defense Guide includes representment language for the already-issued credit scenario, refund operations audit framework, and cross-network strategy for Visa 13.6 and Mastercard 4860.
Get the step-by-step winning strategy →Response Framework Overview
- If credit was already issued: Lead with the processor credit transaction ID, processing date, and amount. Present the refund confirmation email as secondary evidence that the cardholder was notified.
- If no credit was owed: Present your refund policy disclosure at the time of purchase, the customer's agreement to those terms, and documentation showing why the request did not qualify for a refund.
- Address the cardholder's specific claim. If they claim a refund was promised, document whether that commitment was made and under what conditions.
- Show policy acknowledgment. Demonstrate the cardholder was informed of your refund terms before completing the purchase.
Prevention Tips
- Process Amex refunds within 48 hours of approval. Amex cardholders escalate faster than cardholders on other networks. Speed of refund processing directly reduces C02 volume.
- Send automated refund confirmations immediately. The moment a refund is submitted to your processor, send a confirmation to the cardholder with the expected posting date. Informed cardholders rarely dispute while a refund is in transit.
- Always refund to the original Amex card. Never issue alternative credits to Amex cardholders without written agreement. The expectation of card-level refunds is particularly strong in the Amex cardholder base.
- Log all refund commitments in your CRM immediately. Every customer service refund commitment must be tracked and verified as processed. Untracked verbal commitments are the primary source of preventable C02 chargebacks.
Frequently Asked Questions
How is Amex C02 different from Visa 13.6?
Both codes cover the same dispute type — a cardholder expected a refund that never appeared. The differences are network-specific: C02 is filed on Amex cards, Visa 13.6 on Visa cards. Amex gives merchants only 20 days to respond versus Visa's 30 days. Evidence requirements are essentially identical.
What if I issued the credit but the cardholder still filed a C02 dispute?
This is the most winnable C02 scenario. Present the credit transaction record showing the processing date and amount, plus the refund confirmation email sent to the cardholder. If the credit was issued before the dispute was filed, Amex should reverse the chargeback.
Can I issue a store credit instead of an Amex card refund?
Only if the cardholder explicitly agreed to store credit as an alternative. If the customer expected a refund to their Amex card and received a store credit or gift card instead, Amex will side with the cardholder. Always refund to the original Amex card unless the customer affirmatively agrees to an alternative in writing.
How quickly should I process refunds to avoid C02 chargebacks?
Process refunds within 3 business days of approving them. Amex cardholders tend to escalate faster than cardholders on other networks. If a refund will take longer, send a proactive status update with an expected posting date.