Chargebacks are the network's veto — cardholders claw back funds through issuer process while merchants scramble evidence. Reason codes, compelling evidence, representment windows, and how dispute outcomes actually get decided: the full mechanics from both sides of the chargeback, hidden below.
— RELATED GUIDES —
Tracking always, packet against the exact code, refunds cheaper than fights — the dispute game rewards preparation at fulfillment and precision at representment. Deadline calendared, evidence structured, ratio watched weekly; networks veto less when merchants answer properly the first time.
THE PROCESS (KID VERSION)
Buyer disputes with their bank → issuer reviews under reason code → provisional reversal debits merchant → merchant can represent with evidence → issuer decides → arbitration if escalated and amounts justify. Timelines: consumer disputes possible up to 120 days from transaction (network rules vary, some claims longer for certain codes); merchant response windows commonly 7–21 days from notification. Miss the window, lose by default.
REASON CODE FAMILIES
REPRESENTMENT (THE FIGHT)
FROM THE HOLDER SIDE (HOW CLAIMS WORK)
DEATH PATTERNS
WORKING SEQUENCE
Answer the code, ship with tracking, refund the small ones — disputes get won at fulfillment time far more often than at representment time. Ratio managed, packets specific, deadlines calendared; the network's veto gets exercised less when the store runs like it expects questions.
Buyer disputes with their bank → issuer reviews under reason code → provisional reversal debits merchant → merchant can represent with evidence → issuer decides → arbitration if escalated and amounts justify. Timelines: consumer disputes possible up to 120 days from transaction (network rules vary, some claims longer for certain codes); merchant response windows commonly 7–21 days from notification. Miss the window, lose by default.
REASON CODE FAMILIES
| Family | Core claim | Winning evidence |
| Fraud (card not present) | "I didn't authorize this" | AVS/CVV match, IP/device history, prior undisputed transactions from same customer, delivery proof |
| Product not received | "never arrived" | tracking + delivery confirmation + address match |
| Not as described / defective | "item differs" | listing screenshots, communication log, return-policy adherence, refund offer proof |
| Duplicate processing | "charged twice" | single authorization records, settlement IDs |
| Credit not processed | "refund promised, never got it" | refund receipt, policy terms, communication showing no refund agreed |
| Subscription/ongoing billing | "canceled but charged" | signed terms, cancellation-policy + usage after cancel date |
REPRESENTMENT (THE FIGHT)
- Compelling evidence standard: respond to the SPECIFIC reason code — generic screenshots lose; structured evidence packets win.
- Delivery proof hierarchy: carrier confirmation with geo timestamp > carrier "left at door" > merchant claim without tracking (worthless).
- Fraud-claim counters: device fingerprint matching PRIOR legitimate sessions from same cardholder is devastating evidence; IP mismatch alone rarely decides.
- Prior-transaction argument: same card + same device + same address buying for months = fraud claim gets skeptical review.
- Chargeback ratios matter more than individual wins: even winning fights costs fees and counts toward monitoring thresholds (network threshold programs track ratios).
- Pre-emptive wins: refunds under dispute cost (say under $40 math) close issues BEFORE they become chargebacks — ratio math beats dispute heroics.
FROM THE HOLDER SIDE (HOW CLAIMS WORK)
- Merchants CAN counter with evidence — frivolous claims get reversed against the holder after review; issuer may close abuse-prone accounts.
- Friendly-fraud reality: claiming non-receipt when delivered gets caught when tracking shows signature; banks compare claim history per holder.
- Timing: claim within windows, keep communication records — disputes escalate faster with documentation.
DEATH PATTERNS
- Late representment: missed response window = automatic loss, no appeal at issuer level.
- Evidence addressing nothing: sending policy pages when reason code says "not received" — answer THE code.
- No tracking on shipments: shipping without carrier confirmation forfeits product-not-received disputes entirely.
- Ignoring retrieval requests: pre-dispute info demands answered wrong or late harden issuer toward chargeback.
- Ratio blindness: winning 60% of fights while accruing 4% dispute rate still gets account terminated — manage the RATE, not just outcomes.
WORKING SEQUENCE
Bash:
prevention: clear descriptions + tracking always + refund small claims + communication logged
-> receipt of dispute: calendar the response deadline immediately
-> evidence: build packet against the EXACT reason code (delivery proof / device history / policy terms)
-> represent: within window, structured, documented, specific
-> post: update fraud filters from loss patterns; refund-drive dispute rate below thresholdsAnswer the code, ship with tracking, refund the small ones — disputes get won at fulfillment time far more often than at representment time. Ratio managed, packets specific, deadlines calendared; the network's veto gets exercised less when the store runs like it expects questions.
— RELATED GUIDES —
- Bank Drop Cashout: ATM, ACH, and BTC Routes
- Stripe Cashout Method: Merchant Account Payouts
- Payment Gateway Cashout: Shopify, Woo, Wix
- CNP Carding: Card-Not-Present Retail Method 2026
- How Platforms Detect Cashout: Fraud Signals 101
Tracking always, packet against the exact code, refunds cheaper than fights — the dispute game rewards preparation at fulfillment and precision at representment. Deadline calendared, evidence structured, ratio watched weekly; networks veto less when merchants answer properly the first time.