Chargeback reason codes explained (and the evidence each needs)
5 min read · Updated June 2026
Every chargeback comes with a reason code — a short identifier the card network uses to say why the charge was disputed. The reason code tells you exactly what you need to prove.
Codes differ by network and change over time, so always check the specific code in your processor's dashboard. Here are the broad categories and what each generally calls for.
Fraud
The cardholder says they didn't authorize the charge. Evidence that helps: address/security-code verification, device or login activity, prior orders from the same customer, and signed delivery.
Consumer disputes (product/service)
The customer received something but says it didn't arrive, wasn't as described, was a duplicate, or a credit wasn't processed. Evidence: tracking and delivery proof, the product page, photos, your policies, and refund records.
Processing errors
Something went wrong with the transaction itself — wrong amount, duplicate processing, or currency issues. Evidence: the transaction records and receipts showing what was actually charged.
Authorization
The charge was processed without proper authorization. Evidence: the authorization records from your processor.
Frequently asked questions
- Where do I find my chargeback reason code?
- It's shown on the dispute in your processor's dashboard (Stripe, Shopify, PayPal, Square, etc.), usually alongside the deadline.
- Do reason codes really matter for my response?
- Yes — the code tells you what the bank wants proven. Submitting tracking for a 'not as described' dispute, for example, misses the point.
Related guides
SellerProof is a document-organization and dispute-preparation tool. It is not a law firm, payment processor, bank, or card network, and does not provide legal advice or guarantee dispute outcomes.