Merchants who still swipe chip cards instead of the chip reader could wind up paying for any fraud on those transactions. Back in October of 2015, the payment networks changed who pays for counterfeit card fraud. Before that date, the banks and card issuers covered those costs. After that date, when a customer hands you […]
Visa Response Code 10.2 is a chargeback response code for chip card transactions that aren’t handled during face-to-face sales. It kicks in whenever a customer shows up with a working chip card but the transaction is run as a magnetic-stripe swipe or is manually keyed instead of going through the chip reader like it should. […]
These “other” forms of card-present fraud are usually underestimated exactly because they don’t fit a clean pattern. They can mean merchant manipulation, forced transactions, or plans that blur the line between a legitimate sale and outright theft. For anyone working in payments, risk management, or retail operations, this wider context is what matters. This section […]
Visa’s Reason Code 10.4 is probably one of the most frustrating and expensive types of chargeback disputes that online merchants run into – this particular fraud code shows up whenever cardholders claim they never gave permission for a transaction to happen in the first place – and we’re talking about any situation where the physical […]
Reason code 10.5 should make any merchant sit up and pay attention because it means an enrollment in Visa’s Fraud Watching Program. This is a warning that your fraud levels have crossed into dangerous territory and your payment processing privileges are now in jeopardy. Code 10.5 shows up after your merchant account has developed what […]
Here’s the short version: reason code 11.1 falls under Visa’s Authorization dispute category, which means this chargeback is rooted in how – or if – the transaction was authorized before it went through. Specifically, it means something called the Card Recovery Bulletin, a list that merchants and their payment systems were once required to check […]
Code 11.2 chargebacks happen when you process a transaction even after you have already received a decline or pickup message directly from Visa’s system. These chargebacks can be avoided and the fact that they appear at all says quite a bit about your payment setup. When they continue to show up, it means that you […]
Reason code 11.3 disputes happen when customers feel that the products or services they received don’t match what was first advertised or have arrived in damaged condition. This whole situation becomes even more frustrating because this particular type of chargeback happens more frequently than other dispute categories that merchants see. Along with that lost money […]
Visa Code 12.1 chargebacks are quietly bleeding merchants out of thousands of dollars every month. But the most maddening part about these disputes is that they’re completely preventable with better timing. These automated chargebacks get triggered by Visa’s system whenever a business misses its exact deadlines for transaction processing and the consequences are pretty harsh. […]
Late presentment has to be one of the most preventable chargeback problems merchants run into. It’s also one of the most expensive mistakes you can make. These reason codes are about transactions that sit around too long before settlement turn from what should be normal scheduled sales into automatic liability problems that chip away at […]
Visa reason code 12.2 – officially titled Incorrect Transaction Code – falls into a category of chargebacks that have nothing to do with a customer being unhappy or a stolen card being used. Instead, it can come down to a processing error: the wrong transaction code was applied at the point of sale and the […]
12.Currency chargebacks happen when transactions are processed in the wrong currency or when the automatic currency conversion happens without the customer having said yes first. Merchants who work with international customers or run businesses in tourist areas get hit the hardest because currency mistakes happen all the time during busy transaction periods. What makes this […]
This can happen for a fairly variety of reasons. A manual entry error, a processing system glitch, outdated customer account data – any of these can send a well-intentioned payment to the wrong destination. The cardholder either doesn’t find the charge or never received the funds at all, and a dispute follows. Even merchants with […]
That’s the scenario Visa chargeback reason code 12.5: Incorrect Amount was built for – it exists specifically to protect cardholders when the amount debited from their account doesn’t line up with what was actually authorized at the time of purchase. It’s a simple concept, but the facts – what qualifies, what doesn’t, and how disputes […]
Visa Reason Code 12.5 chargebacks have been steadily draining thousands of dollars from merchant accounts every month, and the especially frustrating part is that most of these losses are completely avoidable when merchants know what to watch for. Cardholders usually review their monthly statement and find the wrong amount on their card, get confused or […]
I’ll walk through the helpful steps for tackling claims that have been submitted more than once or that were already satisfied through another payment source. Whether you’re dealing with an accidental resubmission or a claim covered by a secondary payer, workers’ compensation, or a patient’s out-of-pocket payment, the process for resolving each scenario follows a […]
Visa chargeback code 12.7 shows up when something goes wrong with your transaction data – maybe it’s corrupted, missing important facts or basically invalid in a way that stops the payment system from processing it. What makes this particular chargeback code so annoying is that most of these problems actually come from technical glitches and […]
Customers who pay for something and never receive what they ordered have the right to file a dispute under Visa’s reason code 13.1 – this code covers situations where somebody paid for merchandise or a service but never actually got it delivered. Out of all the different chargeback reasons out there, it’s probably the simplest […]
Visa chargeback reason code 13.2 is when customers file complaints saying they were still charged for recurring payments even after they had already canceled their subscriptions or memberships. It’s a code you need to keep a close eye on when your business relies on any type of automatic billing system – it doesn’t matter whether […]
Sellers and online marketplaces work under consumer protection standards that hold them accountable when merchandise is defective or misrepresented. Knowing how these protections work gives you a real benefit when something goes wrong, and it changes how confidently you can shop, dispute a charge, or demand a refund. This section walks you through the helpful […]
Counterfeiting is a massive and growing problem. According to the OECD, counterfeit and pirated goods accounted for an estimated $467 billion – roughly 2.3% of worldwide imports – as of 2021. To put that growth in perspective, international counterfeit trade stood at around $200 billion in 2005, climbed to $509 billion by 2016, and U.S. […]
Visa chargeback reason code 13.5 covers Misrepresentation – disputes where a cardholder claims the goods or services they received were materially different from what was described at the time of purchase. This is distinct from a simple dispute about quality or satisfaction. The core issue is whether the merchant made a false statement of fact […]
Reason Code 13.6 falls under Visa’s Consumer Disputes category and applies when a cardholder claims they were entitled to a credit – whether from a return, a cancellation, or another agreed-upon refund – but that credit never made it back to their account. It’s the formal replacement for legacy Visa reason code 85, carrying forward […]
This section walks through the procedures for processing cancelled merchandise and services, covering everything from reversing charges to documenting the transaction correctly. Whether you’re handling a one-time purchase or a standard service agreement, doing the accounting right protects your organization and keeps your records clean. These steps help you avoid common errors, ensure quick refunds […]
OCT rejections aren’t always simple. The reasons behind a non-accepted transaction can vary from technical mismatches to compliance-related holds, and each scenario carries its own set of responsibilities and next steps. Knowing how to interpret a rejection and respond appropriately can separate a quick resolution from a prolonged dispute. This section walks through the mechanics […]
Non-receipt of cash or load transaction value is one of the most common disputes in electronic payments and prepaid card systems, and it can happen for a number of reasons. Sometimes the issue is technical – a network timeout, a card reader malfunction, or a processing error that flags a transaction as failed when it […]
Mastercard reason code 4808 covers a category of chargebacks with authorization – meaning the dispute exists because something went wrong (or was skipped) in the process of approval to charge a card. That could mean the authorization expired before the transaction was settled, that the transaction amount exceeded what was approved, or that authorization basically […]
Authorization failures hurt merchant profits every day and Mastercard’s reason code 4808 is one of the main culprits – this chargeback code applies when transactions either don’t have the right authorization approval or when they go over the approved amount without the cardholder’s permission. Merchants who try to process declined transactions or add large tips […]
Falling under the Point-of-Interaction Error category, 4831 is triggered when the amount charged to a cardholder’s account doesn’t match the amount they authorized at the time of the transaction – it sounds simple, but the causes behind it – and the steps to resolve it – are worth exploring in detail, if you’re a merchant […]
Understanding why 4834 happens is the first step toward resolving it efficiently. The causes can vary from system timeouts and retry logic to user error and integration misfires, so the fix isn’t always the same from one case to the next. I’ll walk you through what triggers a 4834 error, how to find which records […]
Error 4834 falls under a category of chargebacks that revolve around how a transaction was captured at the terminal or device level. Unlike disputes because of customer dissatisfaction or fraud, Point-of-Interaction errors are largely technical and procedural in nature. That distinction matters, because it changes how merchants should respond and what steps they can take […]
What triggers this error, and more importantly how you respond to it, can separate a recovered sale from a lost customer – this post breaks down the mechanics behind error 4834, walks through the most common causes, and gives you a path toward resolution – whether you’re a merchant troubleshooting at the counter or a […]
Reason code 4837, officially labeled No Cardholder Authorization, sits under Mastercard’s Fraud dispute category. It applies when a cardholder claims they did not approve a charge – meaning someone else used their card without permission, or the transaction was processed in a way that bypassed authorization. It can happen in card-present environments, like a retail […]
Reason code 4837 is Mastercard’s designation for a type of fraud dispute: No Cardholder Authorization. To break it down, the cardholder is telling their bank that they didn’t make the purchase – and the bank is taking their word for it, at least up front, when pulling the funds back from you. It’s one of […]
That situation has its own reason code in the Mastercard dispute system: 4840 – Fraudulent Processing of Transactions – it’s the code that gets filed when a cardholder believes a merchant processed a transaction – or multiple transactions – without authorization. The customer acknowledges some level of interaction with the merchant, but something about what […]
Most merchants never see this code, and that’s by design – it’s reserved for situations where the card network has determined that something fundamentally problematic is happening at the merchant level – not just a single bad transaction, but a pattern or practice that puts cardholders at risk. If you’re facing a 4849 chargeback, or […]
The 4853 dispute gives cardholders a formal avenue to challenge charges when they believe a product or service didn’t hold up as high as what was promised. That covers a variety of scenarios – from electronics that arrived damaged to services that were never delivered as agreed. The flexibility of this reason code is what […]
A dispute filed under 4854 might mean a credit card billing issue, a problem with a recurring transaction, or a disagreement with an account number change – each carrying its own documentation requirements and response strategies. I’ll break down everything you’ll need to know about Reason Code 4854: what triggers it, what conditions have to […]
For years, Mastercard handled the “Services Not Provided” complaint through chargeback reason code 4855, formally titled Goods or Services Not Provided – it gave cardholders a path to recover funds when a merchant failed to give you what was purchased, and it gave merchants a defined set of rules to either fight the dispute or […]
Mastercard organizes its chargeback system into four main categories, with 21 reason codes spread across them. Code 4859 falls under the Cardholder Disputes category, and unlike some codes that cover large ground, has a narrow, well-defined scope – it applies to three situations: addendum disputes (unexpected charges added after the original transaction), no-show disputes (usually […]
Reason Code 4860, formally known as Credit Not Processed, gives cardholders a formal path to dispute a transaction when a merchant agreed to issue a refund or credit but never followed through – it’s a simple concept, but the facts – what qualifies, what documentation matters, and how merchants should respond – are worth knowing, […]
Reason Code 4862 is Mastercard’s way of flagging a transaction that seems to have been made with a counterfeit card. That usually means the card data was stolen and cloned onto a fake card, which was then used at your terminal. In some cases, it seems like something that went sideways during the authorization process […]
What makes this reason code especially tough is that the transaction may be legitimate. The cardholder may have forgotten about the purchase, not recognized the merchant descriptor on their statement, or – in some cases – not realized a family member used their card. But from the bank’s perspective, uncertainty gets resolved in the cardholder’s […]
Mastercard reason code 4863 applies specifically to card-not-present transactions – think online purchases, phone orders, or any sale where the physical card isn’t swiped or tapped. When a cardholder looks at their statement and sees a charge they don’t remember making, they can dispute it under this code. The important phrase here is “does not […]
Here’s the short version of what’s going on: a cardholder is claiming that a fraudulent transaction took place on a lost, stolen, or never-received card. The card itself had a chip, but – for one reason or another – the transaction was processed in a way that didn’t take full advantage of that chip technology. […]
A01 is an American Express chargeback reason code that gets triggered when a cardholder is billed for more than the amount they authorized – it sounds simple, but the situations that cause it are more varied – and common – than most merchants would like to admit. An honest billing error, a system glitch, an […]
APIs authenticate differently than traditional web applications, and attackers know it. Where a web app might funnel every user through a single login page, APIs expose dozens of endpoints, each making its own assumptions about who is allowed in and how that should be verified. Tokens get reused across environments. Expiration logic gets skipped to […]
American Express assigns reason code A08 when a charge is submitted after the original authorization has expired. Every authorization has a shelf life, and if too much time passes between approval and settlement, Amex treats that captured authorization as invalid. The transaction basically gets processed on a stale approval. That’s enough to trigger a chargeback. […]
Fraud exists within AA – it exists in the margins, in the meetings, and sometimes in plain sight – it wears different faces and operates differently, but the common thread is the same: it takes advantage of a space designed for healing and uses it for personal gain. Saying that out loud can seem almost […]
The “AB” reason code comes into play when American Express determines that a charge was submitted without a valid authorization approval code attached to it. In other words, the transaction either skipped the authorization step entirely, used an expired or incorrect approval code, or was processed in a way that didn’t meet Amex’s authorization requirements. […]
Merchants who process transactions after Discover declines the authorization are automatically liable for chargebacks under Reason Code AC and it’s one of the worst process mistakes in payment processing because it bypasses the security protocols that are in place to protect everyone involved. AC chargebacks are almost impossible to win and the reason for it […]
Reason Code AT disputes from Discover cost merchants thousands of preventable chargebacks every month across hospitality and service businesses. AT gets assigned when merchants process transactions without the right authorization procedures – mainly with addendum charges and no-show fees that show up on customer statements weeks after the first charge. Most merchants have no idea […]
Discover’s “AW” (Altered Amount) chargeback code is triggered whenever the final amount that shows up on a customer’s statement is different from what they originally agreed to pay. Most AW disputes happen because of manual entry mistakes – it’s also the case when it gets busy and staff rush through transactions. Restaurants run into problems […]
Here’s the scenario behind American Express chargeback reason code C02: Credit Not Processed. To break it down, it means a cardholder expected to see a credit or refund appear on their statement and it never did. Whether that’s because the refund was delayed, processed incorrectly, or never initiated at all, the result is the same […]
A C04 chargeback gets filed when a cardholder returns goods or refuses a delivery and then doesn’t receive a refund. That’s a frustrating position to be in, and that’s also the case if you have no record of a return or if the situation is more complex than the customer is letting on. The good […]
C05 is one of the more common dispute types for businesses that work on subscriptions, retainers, or any recurring billing model. A customer cancels a gym membership, a software plan, or a delivery service – and if the charge still comes through, or if the cancellation wasn’t processed cleanly on your end, American Express may […]
Reason code C08 – Goods or Services Not Received – is triggered when a cardholder claims they paid for something but never got it, whether that’s a physical product that never arrived, an online item that was never delivered, or a service that was never rendered. For merchants, a C08 chargeback can seem like a […]
C14, formally labeled “Paid by Other Means,” is filed when a cardholder claims they already settled a transaction through a different payment method – cash, a check, store credit, a gift card, or another card – but their American Express account got charged anyway. From the customer’s perspective, they’ve paid twice for the same thing. […]
If the card in question was an American Express card, there’s a chance you’re looking at Reason Code C18: “No Show” or CARDeposit Cancelled – one of the chargebacks that tends to catch lodging businesses off guard, because from the hotel’s perspective, everything was done by the book. A reservation was made, a deposit or […]
C28 falls under American Express’s Card Member Disputes category, and it specifically covers situations where a customer cancelled a recurring billing arrangement – a subscription, membership, or any other agreement with repeated charges – but was charged again after that cancellation. From the cardholder’s perspective, the math is easy: they cancelled, so they shouldn’t have […]
The C31 reason code falls under American Express’s chargeback framework and carries actual financial consequences for merchants who aren’t prepared to fight back with the right evidence. The claim itself can seem simple, but the facts matter enormously – in how the dispute is evaluated and in what a merchant needs to prove to successfully […]
Credit and debit posting errors can create immediate financial problems and make your customers lose trust in your business fast. Discover’s CD reason code helps sort out these posting errors and protects merchants and cardholders from system glitches and human mistakes. Most of these disputes actually come from refund processing failures or transaction reversal errors […]
Cancelled reservation disputes can be especially tough for merchants because you might be paying a few times what the customer originally spent, and each chargeback brings with it its own set of penalty fees. If too many of these disputes pile up, then your payment processor might start causing you issues or drop you altogether. […]
The F10 error – a missing imprint – is one of the more frustrating citation problems scientists see. It doesn’t mean the source is useless; it means you have some detective work ahead of you. Understanding why imprints go missing is the first step toward figuring out how to recover the information you need. I’ll […]
Whether you’re encountering this for the first time or trying to understand why it’s surfacing in your workflow, the good news is that F14 is usually preventable. The causes are steady, the fixes are straightforward, and knowing what to look for, you can stop it before it becomes a bigger headache. I’ll walk you through […]
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 […]
American Express chargeback reason code F29 is tied to card not present transactions – the kind that happen every day in e-commerce and over-the-phone sales – and it gets filed when a cardholder claims they didn’t authorize a purchase made without their physical card. For merchants who depend heavily on online or remote sales, this […]
P01 is a response code that tells you the card number used in a transaction hasn’t been assigned to an active account – it sounds easy enough, but the causes behind it and the steps needed to resolve it aren’t always simple. Whether you’re a merchant trying to understand a declined transaction or troubleshooting on […]
P03 falls under Amex’s Processing Errors category, and it can come down to a fairly simple mistake: a credit transaction was processed as a charge instead. In other words, a refund or credit that should have put money back in the cardholder’s account ended up pulling money out. From the customer’s perspective, that’s a problem. […]
Every card transaction has a direction. A charge pulls money away from the cardholder and a credit pushes money back to them. The P04 reason code gets triggered when those two directions get swapped – a transaction that was supposed to take money from the customer’s account ends up adding money to it instead. I’ll […]
To break it down, P05 means the amount billed to a cardholder’s account didn’t match the amount they authorized. The merchant charged one figure; the customer approved another. That gap – however it got there – is enough to trigger a dispute, and American Express takes it seriously. Billing discrepancies like this tend to show […]
P07 is an American Express chargeback reason code that falls under the Processing Errors category. To break it down, it means that a transaction was submitted for settlement too long after the original authorization was obtained. Amex sets strict deadlines for how fast a captured transaction needs to make it through the pipeline, and when […]
I’ll walk you through how to find duplicate charges, how to investigate them, and what steps to take to resolve them for the customer. Following this process helps protect the customer relationship and guarantees that your records stay accurate. Before starting, it helps to know what actually counts as a duplicate charge – because not […]
A P23 dispute means American Express has received a complaint from a cardholder who was charged in a currency they didn’t agree to – and now you’re going to either prove the charge was correct or absorb the reversal. In either case, it’s going to need your attention. Currency discrepancies can happen for a number […]
Discover’s “Processing Error” code is for transactions that go through for an invalid card number. It’s fairly rare but they can be devastating – your business can become responsible for the entire financial loss if a transaction goes through with an invalid card number. These errors almost always signal deeper problems in your payment systems […]