Payment disputes occur when a cardholder contacts their bank to challenge a transaction, asking for the charge to be reversed. The bank investigates, the merchant gets a chance to respond with evidence, and the card scheme rules on who keeps the money. For a growing eCommerce or subscription business, disputes are not an occasional inconvenience. They are an operational cost that compounds with transaction volume, and businesses that handle them well treat them as a process to manage, not a fire to put out each time one lands.
This article walks through how disputes actually work, why they happen, what they cost beyond the disputed amount, and what a merchant can realistically do to bring the rate down.
What a payment dispute actually is
A dispute is the formal process a cardholder uses to ask their issuing bank to reverse a charge. It sits between a refund and outright fraud, and the three terms get used loosely in conversation but mean different things operationally:
Refund: the merchant voluntarily returns funds. No bank involvement required.
Dispute (chargeback): the cardholder’s bank pulls the funds back from the merchant on the cardholder’s behalf, through the card scheme’s formal process.
Fraud claim: a specific category of dispute where the cardholder states they did not authorise the transaction at all.
Visa and Mastercard each run their own dispute frameworks, with defined reason codes that categorise why a transaction is being challenged (goods not received, goods not as described, duplicate processing, fraud, and so on). The reason code matters because it determines what evidence the merchant needs to submit and how the case gets resolved.
How the dispute process works, step by step
- The cardholder raises the dispute with their issuing bank, usually because they do not recognise a charge, did not receive what they ordered, or believe they were charged incorrectly.
- The issuer reviews the claim and assigns it a reason code, then pulls the funds from the merchant’s acquirer.
- The acquirer notifies the merchant, usually with a deadline (commonly five business days) to respond.
- The merchant submits evidence if they want to fight the dispute: proof of delivery, signed terms, communication records, IP and device data, or anything that supports the transaction was legitimate and as described.
- The issuer reviews the evidence, and either reverses the chargeback (the merchant keeps the funds) or upholds it (the cardholder keeps the chargeback).
- Either side can escalate the case to the card scheme for a final ruling if the case remains contested, though this is relatively rare and usually reserved for higher-value disputes.
The full cycle follows the dispute timelines and processing stages defined by the relevant card scheme. More complex or escalated cases may pass through multiple dispute cycles before reaching a final resolution.
Why payment disputes happen
Genuine fraud is only part of the picture. In practice, disputes cluster around a small number of recurring causes:
- Unauthorised transactions: the card was used without the holder’s knowledge, through theft, a compromised card number, or account takeover.
- Goods or services not received: common in travel, events, and pre-order eCommerce, where there is a gap between payment and delivery.
- Goods not as described: the product or service did not match what was advertised.
- Billing errors: duplicate charges, incorrect amounts, or charges in the wrong currency.
- Friendly fraud: the cardholder made the purchase, received the goods, and disputes the charge anyway, sometimes because they forgot the purchase, sometimes deliberately to avoid paying. This category has become one of the largest drivers of dispute volume across the industry, and it is the hardest to prevent through fraud tooling alone because the original transaction was legitimate.
- Recognition failure: the cardholder does not recognise the merchant name on their statement, often because the billing descriptor does not match the storefront or brand name they expect to see.
That last point is worth dwelling on because it is one of the easiest to fix and one of the most commonly overlooked. A mismatched billing descriptor generates disputes that have nothing to do with fraud or service quality. Aligning the descriptor with the brand name customers actually recognise removes a category of disputes almost entirely.
What disputes cost beyond the refunded amount
The disputed transaction amount is rarely the full cost. Card schemes and acquirers typically apply a dispute fee per case, charged regardless of the outcome, to cover the administrative cost of processing the claim. On top of that:
- Lost goods or services, in cases where the product already shipped or the service was already delivered.
- Operational time, gathering evidence, responding within deadlines, and managing the case through to resolution.
- Dispute ratio risk: card schemes monitor the ratio of disputes to total transactions. Merchants who exceed defined thresholds can be placed into monitoring programmes, face higher processing costs, or, in severe and sustained cases, risk losing the ability to accept cards altogether.
For a business processing a meaningful volume of transactions, a dispute rate that looks small in percentage terms can represent a real and recurring cost once fees, lost goods, and operational time are added together.
How to reduce dispute volume
Reducing disputes is mostly about removing the conditions that cause them, rather than reacting faster once they arrive.
- Make the billing descriptor recognizable. This single change addresses a surprising share of “I don’t recognize this charge” disputes.
- Set clear expectations at checkout. Delivery timelines, cancellation terms, and subscription renewal dates should be visible before payment, not buried in terms and conditions.
- Use authentication where it fits the transaction. 3D Secure 2 shifts liability for certain fraud-related disputes toward the issuer when properly applied, and it is particularly relevant for higher-risk transaction profiles such as travel bookings or high-value purchases.
- Respond to disputes promptly and with strong evidence. Delivery confirmation, signed agreements, customer communication, and device or IP data all strengthen a case. Acquirers and payment platforms vary in the level of support they provide for assembling this evidence, which is worth checking when evaluating a provider.
- Monitor the dispute ratio actively, not just after the acquirer issues a warning letter. Real-time transaction monitoring makes it possible to catch a rising trend before it crosses a scheme threshold.
- Treat friendly fraud separately from genuine fraud. Tightening fraud filters will not stop a customer who made a legitimate purchase and disputed it anyway. Clear communication, itemised receipts, and proactive customer service around order status tend to be more effective for this category.
The acquirer’s role in dispute management
A merchant’s acquirer is not a passive party in this process. As the entity that holds the direct relationship with the card schemes, the acquirer manages the technical flow of dispute notifications, deadlines, and evidence submission on the merchant’s behalf. A principal member acquirer (rather than one operating through a sponsor bank or facilitator) typically has more direct visibility into scheme rules and faster access to dispute data. That visibility matters when a merchant needs to respond within a tight window or understand exactly why a dispute landed in a particular reason code.
At Maayan, dispute handling sits alongside real-time transaction monitoring as part of the acquiring relationship, with direct principal membership of Visa and Mastercard removing the intermediary layers that can slow down evidence submission and case resolution.
Disputes, chargebacks and refunds compared
| Who initiates | Bank involved | Typical cause | |
| Refund | Merchant | No | Customer service decision |
| Dispute/chargeback | Cardholder, via issuer | Yes | Unauthorized charge, item not received, billing error |
| Fraud claim | Cardholder, via issuer | Yes | Card used without authorization |
FAQ
What is the difference between a dispute and a chargeback?
In practice, the terms are used interchangeably. A dispute is the cardholder’s challenge to a transaction, and a chargeback is the mechanism by which the funds are pulled back from the merchant while that challenge is reviewed.
How long does a merchant have to respond to a dispute?
This varies by acquirer and card scheme, but five to ten business days from notification is typical. Missing the deadline usually means automatically losing the case.
Can a merchant prevent friendly fraud?
Not entirely. Clear receipts, proactive order communication, and easy-to-find customer service contact details reduce it, but it cannot be eliminated through fraud filters alone, since the original transaction was genuine.
What happens if a merchant’s dispute ratio gets too high?
Card schemes place merchants exceeding defined thresholds into monitoring programmes, which can involve higher fees, additional reporting requirements, and in serious cases the risk of losing card acceptance.
Does 3D Secure eliminate disputes?
No, but for transactions where it is properly applied, it shifts liability for certain fraud-related disputes from the merchant to the card issuer, changing who bears the cost when such disputes occur.
If you’re managing rising dispute volume
If dispute volume is becoming a recurring cost rather than an occasional one, it is usually a sign that the underlying causes (descriptor mismatch, unclear checkout terms, fraud-screening gaps) need attention, not just faster case responses. The team at Maayan Payments works directly with merchants on transaction monitoring and dispute support as part of the acquiring relationship, and can talk through what is actually driving your dispute rate.
