Chargeback reason codes: what the number is actually asking you for

A chargeback reason code is the identifier the issuing bank attaches to a dispute, stating the ground on which the cardholder’s claim is made. Each network maintains its own set, and the code determines everything downstream: what evidence is relevant, how long you have to respond, and whether responding is worth the effort at all.

Merchants who lose disputes they should win almost always make the same mistake — they answer the customer rather than the code. A file explaining that the customer is being unreasonable, submitted against a code that asks for proof of delivery, loses to a file containing a tracking number and nothing else.

The four families of chargeback reason codes

• Fraud: the cardholder says they did not authorise the transaction. Evidence is about identity and prior relationship — address verification results, device and account history, previous undisputed orders from the same customer.
• Authorisation: something was wrong with the authorisation itself — declined, expired, or processed without approval. These are rarely winnable; the error is usually the merchant’s.
• Processing errors: duplicate charge, wrong amount, wrong currency, credit not processed. Evidence is the transaction record and any refund already issued.
• Consumer disputes: goods not received, not as described, cancelled subscription still charged, service not rendered. This family is where good record keeping wins most often.

Read the code before assembling anything

Each code carries a required evidence list published in the network’s rules, and submitting outside it is wasted effort. A goods-not-received code wants delivery confirmation to the cardholder’s address, not a warehouse dispatch record. A not-as-described code wants the product description as it appeared at the time of purchase and any returns policy the customer accepted. A cancelled-subscription code wants the cancellation route, the notices sent and the date the customer actually cancelled, if they did. Matching the file to the code is the whole skill.

Codes are renumbered and reorganised periodically as the networks revise their dispute frameworks. Do not build permanent internal documentation around specific numbers; record the code as received and map it to your own evidence categories, so a renumbering changes a lookup table rather than a process.

Use the codes as a diagnostic

The distribution of codes across your disputes says more about the business than the individual cases do. A cluster of fraud codes suggests a checkout that needs stronger verification. A cluster of goods-not-received suggests a delivery or descriptor problem. Repeated cancelled-subscription codes point at a cancellation flow customers cannot find, which is a product fix rather than a disputes fix — and, in several jurisdictions, a regulatory exposure as well. Tracking the mix monthly turns a cost centre into a signal.

Keeping the mapping

What makes this fast is a small table maintained once: code, network, family, required evidence, deadline, and your win rate against it. Ettex Sheets holds that mapping alongside the dispute log, Ettex Records keeps the evidence per transaction, and the submission it feeds is covered in chargeback representment.

Plainly: this is a spreadsheet and a file, not chargeback software, and the network rulebooks are the authority on codes, evidence requirements and deadlines. They change, and a list copied from anywhere — including here — ages.