Every dispute arrives with a code that says what the cardholder claimed. That code decides what the issuer will accept as an answer. Here are the Visa, Mastercard, American Express and Discover codes in one place, with the evidence you need to fight each chargeback and the quickest way to prevent it happening again.
Tell us which codes hit you most. We will show you which are winnable, which are preventable, and what each one is costing you.
A reason code is the issuer's one-line summary of the dispute. It is chosen from the card network's own list, and it fixes the rules of the case: how long you have to respond, what evidence counts, and whether the dispute can be answered at all.
Read the code before anything else. Evidence that answers a different code is the most common reason merchants lose cases they should win, and the first thing we check in chargeback representment before we fight a chargeback.
Your disputes, grouped by reason code and category, with the win rate on each and the tool that stops it cheapest. When one code starts climbing, you hear about it.
Most new 13.1 cases have tracking but no delivery confirmation attached. Enable delivery evidence to make them winnable.
Enable delivery evidence| Code | Reason | Disputes | Win rate | Best tool |
|---|---|---|---|---|
| 13.1 | Merchandise / Services Not Received | 88 | 71% | Representment |
| 10.4 | Other Fraud: Card-Absent Environment | 74 | 58% | Alert |
| 4853 | Cardholder Dispute | 52 | 63% | Representment |
| 13.2 | Cancelled Recurring Transaction | 41 | 49% | Visa RDR |
| 4837 | No Cardholder Authorization | 37 | 44% | Alert |
| 12.6.1 | Duplicate Processing | 18 | 12% | Visa RDR |
An illustration of the insights dashboard. Sample data, not a real merchant.
Search by code or keyword, or narrow it to one network or category.
| Code | Name | What it usually means | Evidence that wins it | Best way to stop it |
|---|---|---|---|---|
| Visa chargeback reason codes | ||||
| 10.1 | EMV Liability Shift Counterfeit FraudFraud | A counterfeit chip card was used and the terminal fell back to magstripe or was not chip-enabled. | Proof the transaction was chip-read, or that the card was not chip-capable. | RepresentmentRefund and fix |
| 10.2 | EMV Liability Shift Non-Counterfeit FraudFraud | A lost or stolen chip-and-PIN card was used at a terminal that could not take PIN. | Terminal capability records showing PIN was supported and used. | RepresentmentRefund and fix |
| 10.3 | Other Fraud: Card-Present EnvironmentFraud | The cardholder says they did not authorise an in-store transaction. | Chip read or imprint, a signed receipt, and any identity check made at the counter. | AlertRepresentment |
| 10.4 | Other Fraud: Card-Absent EnvironmentFraud | The cardholder says they did not make an online, phone or mail order. The code friendly fraud uses most. | AVS and CVV match, 3-D Secure result, device and IP linked to earlier undisputed orders, or Compelling Evidence 3.0. | AlertVisa RDRRepresentment |
| 10.5 | Visa Fraud Monitoring ProgramFraud | Visa has placed the merchant in its fraud monitoring programme and the issuer may charge back fraud. | Usually not winnable on evidence. The answer is bringing fraud levels down. | Refund and fix |
| 11.1 | Card Recovery BulletinAuthorization | The card was listed on the recovery bulletin and no authorisation was obtained. | A valid authorisation for the transaction date. | RepresentmentRefund and fix |
| 11.2 | Declined AuthorizationAuthorization | The transaction went ahead even though authorisation was declined. | An approved authorisation code for the same transaction. | RepresentmentRefund and fix |
| 11.3 | No AuthorizationAuthorization | No authorisation was obtained, or it was obtained after the fact. | The approved authorisation record matching amount and date. | RepresentmentRefund and fix |
| 12.1 | Late PresentmentProcessing error | The transaction was settled after Visa's time limit. | Proof it was presented within the limit, or that the account was in good standing. | RepresentmentRefund and fix |
| 12.2 | Incorrect Transaction CodeProcessing error | A credit was processed as a sale, or a sale as a credit. | Records showing the transaction code was correct. | Refund and fix |
| 12.3 | Incorrect CurrencyProcessing error | The transaction was processed in a different currency from the one agreed. | The receipt showing the currency the cardholder agreed to. | RepresentmentRefund and fix |
| 12.4 | Incorrect Account NumberProcessing error | The transaction was posted to the wrong card number. | Proof the account number was correct. | Refund and fix |
| 12.5 | Incorrect AmountProcessing error | The cardholder was charged more than the agreed amount. | The signed or accepted receipt for the amount charged. | RepresentmentRefund and fix |
| 12.6.1 | Duplicate ProcessingProcessing error | The same transaction was charged twice. | Proof the two charges were separate purchases, or that one was already refunded. | RepresentmentRefund and fix |
| 12.6.2 | Paid by Other MeansProcessing error | The cardholder paid by another method and was charged on the card as well. | Proof no other payment was received for the same goods. | RepresentmentRefund and fix |
| 12.7 | Invalid DataProcessing error | Authorisation was obtained with invalid or incorrect data. | Authorisation and settlement records showing the data matched. | Refund and fix |
| 13.1 | Merchandise / Services Not ReceivedConsumer dispute | The cardholder says the order never arrived or the service was not provided. | Carrier tracking to delivery confirmation, signature where required, or proof of service use. | AlertVisa RDRRepresentment |
| 13.2 | Cancelled Recurring TransactionConsumer dispute | The cardholder says they cancelled a subscription and were still billed. | The disclosure they accepted, no cancellation on record, and usage after the date they claim. | AlertVisa RDRRepresentment |
| 13.3 | Not as Described or DefectiveConsumer dispute | The goods or service did not match the description, or arrived damaged. | The product page as it stood on the order date, photos, and your returns policy. | AlertVisa RDRRepresentment |
| 13.4 | Counterfeit MerchandiseConsumer dispute | The cardholder says the goods were counterfeit. | Proof of authenticity from the supplier or manufacturer. | Representment |
| 13.5 | MisrepresentationConsumer dispute | The cardholder says the terms of sale were misleading. | The terms shown at checkout and their acceptance, with the timestamp. | AlertVisa RDRRepresentment |
| 13.6 | Credit Not ProcessedConsumer dispute | The cardholder was promised a refund that never arrived. | The refund ledger, or the policy at checkout showing no refund was due. | AlertVisa RDRRefund and fix |
| 13.7 | Cancelled Merchandise / ServicesConsumer dispute | The cardholder cancelled or returned the order and was not refunded. | The cancellation policy they accepted and proof the return was not received. | AlertVisa RDRRepresentment |
| 13.8 | Original Credit Transaction Not AcceptedConsumer dispute | A credit sent to the card was not accepted by the cardholder or issuer. | Records of the original credit and its acceptance. | Refund and fix |
| 13.9 | Non-Receipt of Cash or Load Transaction ValueConsumer dispute | Cash or a stored-value load was not received. | ATM or load logs showing the value was delivered. | Representment |
| Mastercard chargeback reason codes | ||||
| 4808 | Authorization-Related ChargebackAuthorization | Authorisation was declined, not obtained, or obtained for a different amount. | An approved authorisation matching the transaction. | RepresentmentRefund and fix |
| 4812 | Account Number Not on File (legacy)Authorization | The card number did not exist at the issuer. Now handled under 4808. | Authorisation records showing the account number was approved. | Refund and fix |
| 4831 | Transaction Amount Differs (legacy)Processing error | The amount charged differs from the agreed amount. Now handled under 4834. | The receipt or order for the amount charged. | RepresentmentRefund and fix |
| 4834 | Point-of-Interaction ErrorProcessing error | Duplicate charge, wrong amount, late presentment, wrong currency or paid by other means. | Settlement records showing the charge was correct or already credited. | RepresentmentRefund and fix |
| 4837 | No Cardholder AuthorizationFraud | The cardholder says they did not authorise a card-not-present transaction. | AVS and CVV match, 3-D Secure / Identity Check result, device and IP history. | AlertRepresentment |
| 4841 | Cancelled Recurring or Digital Goods (legacy)Consumer dispute | Billed after cancelling a subscription. Now handled under 4853. | The accepted terms and usage after the claimed cancellation. | AlertRepresentment |
| 4842 | Late Presentment (legacy)Processing error | Presented after the time limit. Now handled under 4834. | Proof of timely presentment. | Refund and fix |
| 4846 | Correct Transaction Currency Code Not Provided (legacy)Processing error | Processed in the wrong currency. Now handled under 4834. | The receipt showing the agreed currency. | Refund and fix |
| 4849 | Questionable Merchant ActivityFraud | Mastercard has flagged the merchant under a compliance or fraud programme. | Usually not winnable on evidence. Address the programme flag. | Refund and fix |
| 4853 | Cardholder DisputeConsumer dispute | Not received, not as described, defective, cancelled, credit not processed and similar claims. | Depends on the sub-reason: delivery proof, the product page, the policy or the refund record. | AlertRepresentment |
| 4855 | Goods or Services Not Provided (legacy)Consumer dispute | The order never arrived. Now handled under 4853. | Carrier tracking to delivery confirmation. | AlertRepresentment |
| 4859 | Addendum, No-Show or ATM Dispute (legacy)Consumer dispute | Disputed additional charges, no-show fees or ATM cash. Now handled under 4853. | The signed agreement or no-show policy the cardholder accepted. | Representment |
| 4860 | Credit Not Processed (legacy)Consumer dispute | A promised refund was not issued. Now handled under 4853. | The refund ledger or the policy showing no refund was due. | AlertRefund and fix |
| 4863 | Cardholder Does Not Recognize: Potential FraudFraud | The cardholder does not recognise the charge. Very often friendly fraud. | The descriptor shown at checkout, the order confirmation, and device or login history. | AlertRepresentment |
| 4870 | Chip Liability ShiftFraud | A counterfeit chip card was used at a terminal that was not chip-enabled. | Proof the card was chip-read. | RepresentmentRefund and fix |
| 4871 | Chip / PIN Liability ShiftFraud | A lost or stolen chip-and-PIN card was used where PIN was not supported. | Proof the terminal supported and used PIN. | RepresentmentRefund and fix |
| American Express chargeback reason codes | ||||
| F10 | Missing ImprintFraud | The card-present charge has no imprint or chip read and the Card Member denies it. | A chip read or card imprint for the transaction. | Representment |
| F14 | Missing SignatureFraud | The Card Member denies the charge and no signature was captured. | The signed receipt, or proof a signature was not required. | Representment |
| F24 | No Card Member AuthorizationFraud | The Card Member says they did not authorise the charge. | Proof the Card Member took part: delivery, contact or authentication records. | Representment |
| F29 | Card Not PresentFraud | The Card Member denies an online or phone charge. | AVS and CVV match, SafeKey result, delivery to the billing address, device history. | Representment |
| A01 | Charge Amount Exceeds Authorization AmountAuthorization | The settled amount is higher than the amount authorised. | An authorisation covering the full amount charged. | RepresentmentRefund and fix |
| A02 | No Valid AuthorizationAuthorization | There was no valid authorisation for the charge. | The approved authorisation record. | RepresentmentRefund and fix |
| A08 | Authorization Approval ExpiredAuthorization | The charge was submitted after the authorisation had expired. | A valid authorisation at the time of submission. | Refund and fix |
| C02 | Credit Not ProcessedConsumer dispute | The Card Member was due a credit and did not receive it. | Proof the credit was issued, or that none was owed under your policy. | Refund and fixRepresentment |
| C04 | Goods / Services Returned or RefusedConsumer dispute | The goods were returned or refused and no credit was issued. | Proof the return was not received, or your return policy. | Representment |
| C05 | Goods / Services CancelledConsumer dispute | The order was cancelled and the Card Member was still charged. | The cancellation policy they accepted and the order history. | Representment |
| C08 | Goods / Services Not Received or Only Partially ReceivedConsumer dispute | The Card Member says the order did not arrive, or arrived incomplete. | Carrier tracking to delivery confirmation and the packing record. | Representment |
| C14 | Paid by Other MeansConsumer dispute | The Card Member paid another way and was charged on the card too. | Proof no other payment was received. | RepresentmentRefund and fix |
| C18 | "No Show" or CARDeposit CancelledConsumer dispute | A no-show fee or deposit was charged after a cancellation. | The cancellation policy accepted at booking and the cancellation record. | Representment |
| C28 | Cancelled Recurring BillingConsumer dispute | The Card Member cancelled a recurring charge and was still billed. | The terms accepted and no cancellation on record before the charge. | Representment |
| C31 | Goods / Services Not as DescribedConsumer dispute | What arrived did not match what was described. | The listing as shown on the order date and your returns policy. | Representment |
| C32 | Goods / Services Damaged or DefectiveConsumer dispute | The goods arrived damaged or did not work. | Proof of condition at dispatch and the returns process offered. | Representment |
| P01 | Unassigned Card NumberProcessing error | The charge was submitted on a card number that does not exist. | Authorisation records showing the number was valid. | Refund and fix |
| P03 | Credit Processed as ChargeProcessing error | A credit was submitted as a charge. | Records showing the transaction type was correct. | Refund and fix |
| P05 | Incorrect Charge AmountProcessing error | The amount charged differs from the amount agreed. | The receipt or order for the amount charged. | RepresentmentRefund and fix |
| P07 | Late SubmissionProcessing error | The charge was submitted after the allowed time. | Proof of timely submission. | Refund and fix |
| P08 | Duplicate ChargeProcessing error | The same charge was submitted more than once. | Proof the charges were separate purchases. | RepresentmentRefund and fix |
| P22 | Non-Matching Card NumberProcessing error | The card number submitted does not match the one authorised. | Matching authorisation and submission records. | Refund and fix |
| P23 | Currency DiscrepancyProcessing error | The charge was submitted in a different currency from the one agreed. | The receipt showing the agreed currency. | Refund and fix |
| Discover chargeback reason codes | ||||
| UA01 | Fraud: Card-Present TransactionFraud | The cardholder denies a card-present transaction. | Chip read or imprint and a signed receipt. | Representment |
| UA02 | Fraud: Card-Not-Present TransactionFraud | The cardholder denies an online or phone transaction. | AVS and CVV match, ProtectBuy (3-D Secure) result, delivery and device history. | Representment |
| UA05 | Fraud: Chip Counterfeit TransactionFraud | A counterfeit chip card was used at a terminal that was not chip-enabled. | Proof the card was chip-read. | RepresentmentRefund and fix |
| UA06 | Fraud: Chip and PIN TransactionFraud | A lost or stolen chip-and-PIN card was used where PIN was not supported. | Proof the terminal supported and used PIN. | RepresentmentRefund and fix |
| AA | Cardholder Does Not RecognizeConsumer dispute | The cardholder does not recognise the transaction. Often friendly fraud. | The descriptor, the order confirmation and the cardholder's purchase history. | Representment |
| AP | Cancelled Recurring TransactionConsumer dispute | Billed after cancelling a recurring payment. | The terms accepted and usage after the claimed cancellation. | Representment |
| AT | Authorization NoncomplianceAuthorization | Authorisation was declined, missing or did not match. | A valid authorisation for the transaction. | RepresentmentRefund and fix |
| AW | Altered AmountProcessing error | The amount was changed after the cardholder agreed to it. | The receipt for the amount charged. | RepresentmentRefund and fix |
| CD | Credit / Debit Posted IncorrectlyProcessing error | A credit was posted as a debit, or the other way round. | Records showing the transaction was posted correctly. | Refund and fix |
| DP | Duplicate ProcessingProcessing error | The same transaction was charged more than once. | Proof the charges were separate purchases. | RepresentmentRefund and fix |
| IN | Invalid Card NumberProcessing error | The transaction was processed on an invalid card number. | Authorisation showing the number was valid. | Refund and fix |
| LP | Late PresentmentProcessing error | The transaction was presented after the time limit. | Proof of timely presentment. | Refund and fix |
| NC | Not ClassifiedConsumer dispute | A dispute that does not fit any other reason code. | Evidence that answers the cardholder's written claim. | Representment |
| PM | Paid by Other MeansProcessing error | The cardholder paid another way and was charged on the card too. | Proof no other payment was received. | RepresentmentRefund and fix |
| RG | Non-Receipt of Goods or ServicesConsumer dispute | The order did not arrive or the service was not provided. | Carrier tracking to delivery confirmation, or proof of service. | Representment |
| RM | Quality DiscrepancyConsumer dispute | The goods or service were not of the quality described. | The listing on the order date and your returns process. | Representment |
| RN2 | Credit Not ProcessedConsumer dispute | A refund the cardholder expected was not issued. | The refund ledger, or the policy showing none was due. | Refund and fixRepresentment |
| No reason codes match that search. Try a code number such as 13.1, or a word such as "fraud". | ||||
Names follow each network's published rules, shortened where they are long. Networks revise their codes and time limits from time to time, and your acquirer's deadlines can be shorter than the network's, so confirm the details on the notice itself.
The table's last column is the short version. Three tools cover almost every code, and together they reduce chargebacks at every stage of the dispute.
Ethoca alerts and Verifi CDRN warn you when a cardholder disputes, before a chargeback is filed. Refund in time and fraud and consumer codes never reach your ratio.
How chargeback prevention alerts workRules you set resolve qualifying Visa disputes automatically at the issuer, so 10.x, 12.x and 13.x cases under your threshold never become chargebacks.
Set up Visa RDR rulesFor the chargebacks that do post, an evidence pack written against the exact code and filed inside the deadline wins the money back.
Win a chargeback with representmentRecurring billing has its own reason codes. Most subscription chargebacks claim the cardholder cancelled and was billed again, or never agreed to the renewal. They are some of the most winnable cases you will see, and some of the easiest to stop early.
To win them, show the recurring terms the customer accepted, that no cancellation reached you before the billing date, and usage after the date they say they left. To prevent them, send renewal reminders, make cancelling easy, and let Visa RDR or chargeback alerts refund the low-value ones before they post.
Friendly fraud is a real cardholder disputing a purchase they did make. It rarely says so. It arrives under a fraud code or a "not received" code, because those are the options the bank offers. The good news: the order history that proves who bought is already in your systems, and the same fraud codes, tracked over time, are the starting point for chargeback fraud prevention.
Answer the code the issuer used, with the evidence that code asks for, before the deadline. Nothing else in the pack matters as much.
How to fight a chargebackGot a code that is not on this list, or one that keeps coming back? Send it over and an analyst will tell you what it means for your business.
Ask a dispute analystSend us three months of disputes. We will break them down by reason code and tell you which chargebacks to prevent, which to fight and which to simply refund. No charge, no obligation.
We reply within one business day.