Most disputes a merchant can prevent are not won in a representment. They are prevented weeks earlier, in the one line a customer sees on a bank statement. When that line is unrecognisable, the customer does not search for the merchant — the customer calls the bank. This guide is for merchants: what survey data says about that behaviour, the concrete descriptor checklist to apply, and the two companions that make clarity work — proactive messages and a refund path that is easier than a dispute. It does not repeat the format rules or the validation logic: for those, use the Billing Descriptor Validator and its companion Billing Descriptor Guide.
What the survey data says
All figures in this section are survey data from Chargebacks911's 2025 Cardholder Dispute Index, based on a survey of over 1,200 cardholders in the US and UK, as reported in the report's own announcement and independent coverage of it. They describe what respondents said, not Chargeback Clock's own data and not any card network's transaction records.
Survey finding
What it means for a merchant
76% of respondents prefer to resolve disputes through their bank
The bank is the customer's default route. A merchant support path has to be visible and faster than that default, or it will not be used.
Nearly half say they bypass the merchant entirely
Many disputes arrive with no prior contact. The absence of a complaint before the chargeback is normal behaviour, not proof the customer never had a problem.
89% trust their bank to resolve disputes
Customers are not reluctantly disputing. They expect the bank process to work, so a merchant must give them a reason to try the merchant first.
40% say they often do not recognise purchases because of confusing or incomplete billing descriptors
Recognition failure is a large, fixable source of disputes. A descriptor the customer recognises removes the reason for the most avoidable dispute type.
Visa estimates chargeback misuse can account for up to 75% of all chargebacks
The report attributes this estimate to Visa. It frames the scale of misuse, but it is an industry estimate, not a measurement of any single merchant's disputes.
Read together, the pattern is uncomfortable but useful: customers trust the bank, prefer the bank, and in two cases out of five cannot recognise the charge at all. Descriptor clarity addresses the last point directly and gives the merchant a chance on the first two — a customer who recognises the charge and knows who to contact has far less reason to open a bank case.
Why customers go to the bank first
Three causes stack. First, confusion: the statement line shows a legal entity name, a payment processor name, or an abbreviation the customer never saw at checkout. Second, friction: support contact details are buried in an account page, an email footer, or a help centre the customer cannot find from the statement. Third, delay: the customer already waited for delivery, a refund, or an answer, and the bank offers a process with a clear outcome. None of these requires bad faith. A genuine purchase, a genuine statement line, and a genuine delay are enough to produce a chargeback that a clearer descriptor and an earlier message would have avoided.
The merchant angle follows from that: prevention is cheaper than representment not only in fees, but in time. A dispute consumes evidence gathering, a response deadline, and a monitoring-ratio contribution whether it is won or lost. A descriptor fix is a one-time change applied to every future transaction. That asymmetry is why this guide treats descriptor clarity as a prevention measure first and a dispute-response topic second.
The descriptor clarity checklist
Apply every item before changing a descriptor, then test it with the Billing Descriptor Validator rather than judging it by eye. The validator and the Billing Descriptor Guide cover the format rules; this checklist covers what the customer must be able to understand from the line.
Recognisable name: the name the customer saw at checkout — the store or brand name, not only a legal entity or processor name the customer never encountered.
What was bought, in plain words: a short product or service description that matches the order confirmation, so the statement line and the receipt obviously describe the same purchase.
What shows on the statement, checked as the customer sees it: view the exact truncated line as it appears on a statement, not the full text entered in a dashboard. Abbreviations that only make sense internally fail this check.
Support contact on the line or one step away: a phone number or web address the customer can use without logging in, so the statement itself points back to the merchant.
One descriptor per brand or product line: a customer buying from two of your brands should not see one shared name that matches neither purchase.
Subscription flagging: for recurring billing, the descriptor and the pre-renewal message must make the recurring nature and the amount obvious before the charge lands.
Re-check after any change: a new processor, a renamed entity, or a new product line can silently change what appears. Re-validate after each change, and after any rebrand.
What not to do: do not use a descriptor that is technically accurate but unrecognisable, do not hide behind an abbreviation to save characters, and do not rely on the customer remembering a checkout page weeks later. If a stranger shown only the statement line cannot say what was bought and from whom, the descriptor fails — however correct it looks in your own system.
Proactive messages that prevent the call
A clear descriptor answers “what is this charge?” Proactive messages answer it before the question is asked. Send an order confirmation that names the product, the amount, and the exact statement name the customer will see. Send a shipping or delivery update for physical goods, and a delivery confirmation for digital goods. For subscriptions, send a reminder before each renewal stating the amount, the date, and the statement name, with a cancellation link in the same message. Each message should repeat the statement name verbatim — that repetition is what lets the customer match the statement line to a purchase they remember.
Timing matters as much as content. A confirmation sent at purchase, a reminder sent before renewal, and a receipt sent at delivery together cover the three moments a customer is most likely to check a statement and wonder. A single welcome email at signup does not cover a charge six months later.
Make the refund easier than the dispute
Even a perfect descriptor will not stop a customer who wants their money back and cannot get it from you. The refund path must be visible from the order confirmation, must not require a phone call during business hours only, and must state how long the refund takes and where it will appear. When a customer can see the refund route, the bank route loses its main advantage: speed and certainty.
That does not mean refunding every claim. It means deciding quickly and visibly: refund the recognised-purchase confusion cases and the clear merchant errors, and reserve representment for cases where the evidence genuinely supports it. The Fight-or-Refund Decision Calculator compares the two paths for a specific case, and the chargeback cost guide explains why a dispute costs more than the transaction amount. No approach removes disputes entirely, and this guide makes no claim that it does — it reduces the avoidable share, which the survey data suggests is large.
Frequently asked
Survey data says 76% prefer resolving disputes through their bank and nearly half bypass the merchant entirely. Convenience and trust in the bank process are the reported drivers — so the merchant must be easier to reach than the bank.
40% of survey respondents say they often do not recognise purchases because of confusing or incomplete descriptors. A charge the customer cannot recognise is commonly disputed as unrecognised, even when the purchase was genuine.
A name the customer recognises from checkout, a short description of what was bought, and a support contact. The Billing Descriptor Guide covers the format rules and the Validator checks a descriptor against them.
No. It removes the recognition problem, but customers also dispute because they cannot reach support or cannot get a refund. Pair it with proactive messages and a visible refund path.
An order confirmation naming the product and amount, a shipping or delivery update, and a receipt stating the exact statement name. For subscriptions, a reminder before each renewal with the amount and statement name.
In most recognised-purchase and buyer-confusion cases, a refund costs the sale while a chargeback can also add a dispute fee and count toward monitoring thresholds. Compare the two for a specific case with the Fight-or-Refund Decision Calculator.
Sources (checked November 1, 2026): Chargebacks911, 2025 Cardholder Dispute Index announcement (chargebacks911.com, published July 14, 2025) — survey of over 1,200 US/UK cardholders; 76% prefer bank resolution, nearly half bypass the merchant, 89% trust their bank, 40% often do not recognise purchases due to confusing or incomplete descriptors, Visa estimate that misuse can account for up to 75% of all chargebacks — corroborated by independent coverage of the same announcement (The Payments Association, Financial IT, FF News, Digital Transactions, July 2025). All figures are labelled as survey data in this article, not as Chargeback Clock or card-network transaction data.
General information only — not financial or legal advice. Descriptor rules and monitoring thresholds vary by card network, acquirer, and merchant category. Confirm your descriptor format and any dispute-fee exposure with your acquirer before changing a live descriptor.
Chargeback Clock