Reading the numbers that arrive with a payment dispute
| posted | descriptor | amount | status | code | clock |
| 08 SEP | MERCHANT DESCRIPTOR | −148.00 | DISPUTED | 13.1 | day 0 |
A dispute reaches a merchant as a four-character code and an amount — no sentence, no explanation. The code is the whole allegation, and it decides which documents will win the case and which are irrelevant. This page reads the four families of codes, the evidence each one demands, and the federal rule sitting behind consumer credit-card disputes in the United States.
Written for anyone who has to answer one: a small merchant, a bookkeeper, or a cardholder trying to work out what their own bank filed on their behalf. It quotes only published rules and cites them.
When an issuing bank pulls funds back from a merchant, it selects a numeric reason code and submits it with the chargeback. Wikipedia's summary of the mechanism puts it plainly: with each chargeback the issuer selects and submits a numeric reason code, and codes vary by network but fall into four general categories — technical, clerical, quality, and fraud.
That single field does more work than anything else in the case. It sets what the merchant must prove. A signed delivery confirmation answers a "goods never arrived" claim and does nothing at all for a duplicate-billing claim, where the only relevant document is the second posting itself. Merchants who lose disputes they should have won usually answer the story they imagine rather than the code they were sent.
The amount is the second field that matters, because a partial dispute and a full dispute are different arguments. A cardholder who received three of five items disputes the value of two; a response that defends the whole order misses.
The transaction should not have been completed in the form it was. Nobody is accused of anything; the message is that the plumbing produced an invalid charge.
The charge is legitimate but wrong in size, count, or timing. The most common variant is a refund the merchant believes it issued and the cardholder has not seen.
The cardholder says the goods or services were not delivered, or were materially different from what was promised at the time of purchase. This family carries the most subjective weight and the most argument about what "as promised" meant.
The cardholder states they never authorised the purchase. Wikipedia notes that in card-not-present transactions the merchant is usually responsible for the chargeback and associated fees, and that after chip-card adoption merchants who did not upgrade generally became liable for chargebacks they would not previously have carried.
Network rules are private contracts. Behind them, for United States consumer credit cards, sits Regulation Z. Two of its sections define the shape of every dispute above, and both are worth reading in the original rather than in a summary.
12 CFR 1026.13 defines "billing error". Its list is the source of the clerical and quality families: an extension of credit not made to the consumer or to someone with authority to use the card; a charge for property or services not accepted by the consumer or not delivered as agreed; a failure to credit a payment properly; a computational error; a charge for which the consumer requests documentary evidence.
The same section defines the notice. A billing error notice is a written notice received by the creditor no later than 60 days after the creditor transmitted the first periodic statement reflecting the alleged error, identifying the consumer and the account, and indicating the consumer's belief about the error. That 60-day figure is the one number in the whole process that people most often misremember — it runs from the statement, not from the purchase.
12 CFR 1026.12 covers unauthorised use, which is the fraud family. It caps a cardholder's liability for unauthorised use at the lesser of $50 or the value obtained before the issuer was notified, and only where the card was an accepted card and the issuer had given adequate notice of that maximum liability and of how to report a loss. "Unauthorised use" is defined there as use by someone other than the cardholder who has no actual, implied, or apparent authority, and from which the cardholder receives no benefit.
| Claim family | Document that decides it | Document that looks relevant and is not |
|---|---|---|
| Technical | Authorisation approval code with its date, next to the capture date | Order confirmation email |
| Clerical — duplicate | Both transaction identifiers and both settlement timestamps | Customer service transcript |
| Clerical — refund not credited | Refund reference plus its settlement date from the processor | Internal order status marked "refunded" |
| Quality — not received | Carrier tracking terminating at the cardholder's billing or confirmed shipping address | Dispatch note from the warehouse |
| Quality — not as described | The listing text and images as displayed on the purchase date | The current version of the same listing |
| Fraud — unauthorised | Chip transaction record, or address verification plus prior undisputed history on the same account | Proof the goods were used |
One habit protects every row of that table: keep records that are timestamped by somebody other than yourself. A processor's settlement file, a carrier's scan history, and an archived page snapshot all carry outside dates. An internal database field does not.
Take the code from the acquirer's notification rather than from a blog table, because networks renumber. Visa publishes its Core Rules and Product and Service Rules for public download; Mastercard, American Express, and Discover each publish their own dispute guides. Match your code against the current edition of the right network's document and read the paragraph, not a summary of it.
Then ask three questions in this order. Which family does the code sit in? What is the one document that family turns on? Do you hold that document with an outside timestamp? If the answer to the third is no, the case was lost before the dispute arrived, and the fix belongs in record-keeping rather than in the response letter.
For a cardholder, the mirror question is simpler: does the complaint fit the definition of billing error in 1026.13, or is it a disagreement with a merchant about value? The first has a federal procedure behind it. The second does not, and filing it as one tends to end badly for everyone involved.