National merchant dispute guidance
What Is a Chargeback Reason Code?
A chargeback reason code is the card network's structured label for the condition behind a payment dispute. It tells the merchant and its acquirer why the issuer initiated the chargeback and points to the rules, deadlines, and evidence that apply to that case.
Plain-language definition
The code identifies the dispute condition
A reason code does not prove that a cardholder's claim is correct, and it is not a complete case summary. It classifies the issue under a network rule so the parties can follow the appropriate dispute path. The notice may also include a condition name, transaction data, narrative, deadline, requested documents, and case status.
Common groupings
What a reason code may describe
Fraud or authorization
The cardholder may say the transaction was not authorized, or the case may concern authorization data, authentication, or a liability rule. The required response depends on the payment channel and case details.
Processing error
The dispute may involve a duplicate transaction, incorrect amount or currency, late presentment, or another processing condition. Transaction and settlement records help identify what occurred.
Consumer dispute
The claim may concern goods or services not received, not as described, canceled, returned, or otherwise disputed. Fulfillment, cancellation, refund, and customer-communication records may be relevant.
Credit or refund issue
The cardholder may claim an expected credit did not post. A merchant should compare the refund date, amount, account, reference, and status before responding.
Case review
Read beyond the code itself
Confirm the network and workflow
Identify the card network, dispute stage, case identifier, processor or acquirer instructions, and the exact reason or condition shown. Similar business complaints can be classified differently.
Match the original transaction
Verify the amount, date, currency, payment channel, transaction identifier, order number, and customer or fulfillment record. Investigate mismatches before submitting anything.
Read the rule-specific deadline
Use the deadline and time zone displayed for the case. Internal targets should leave time for review and submission before the provider cutoff.
Answer the stated condition
Organize a concise response around the disputed point. A large packet of unrelated material can obscure the records that directly address the reason code.
Follow the provider's evidence prompts
Evidence varies by condition and transaction. Use the portal instructions and current network rules, preserve original records, and avoid altering or manufacturing documentation.
Save submission and outcome records
Keep the case ID, response timestamp, documents submitted, confirmation, later status, and accounting treatment so the dispute can be reconciled.
Practical example
The same sale can require different evidence
If a notice says merchandise was not received, delivery and customer-use records may address the stated issue. If the notice instead says the transaction was unauthorized, delivery alone may not answer the applicable fraud or authorization condition. The reason code helps focus the response, but the merchant still needs the full case details and provider instructions.
Team workflow
Turn reason codes into consistent operations
Assign ownership
Define who receives notices, gathers records, approves responses, submits cases, and monitors results.
Use condition-based checklists
Build internal checklists around the provider's current categories without treating them as a substitute for the live case instructions.
Track root causes
Group outcomes by issue type, sales channel, fulfillment method, product, and operational cause. Do not compare raw codes across networks without mapping their meanings carefully.
Protect sensitive data
Submit dispute records only through approved channels. Do not place cardholder data, passwords, bank credentials, or secret keys in general contact forms.
Related resources
Continue your dispute research
Common questions
Chargeback reason code FAQ
Are reason codes the same across card networks?
No. Networks use their own terminology, numbering, conditions, and processes. Provider interfaces may also display a mapped label alongside the network code.
Does a reason code determine the outcome?
No. It identifies the dispute condition. The outcome depends on the applicable rules, transaction facts, submitted records, timing, and decisions made within the dispute process.
Can a merchant choose a different reason code?
The issuer initiates the dispute under an applicable condition. A merchant should respond through its processor or acquirer workflow and flag an apparent mismatch using the options the live case permits.
Where should a merchant find current requirements?
Start with the processor or acquirer case notice and portal, then consult current official network rules or support channels when more detail is needed.
Last editorial review: August 11, 2026. Sources reviewed: current Mastercard merchant chargeback guidance and Visa chargeback guidance. Network rules and provider workflows can change.
Next step
Build a reason-specific review process
Document who owns each case, where current instructions are found, and how evidence, deadlines, submissions, and outcomes are recorded.
To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.
CONTACT US