builder
Chargeback dispute narrative
///
variables
Merchant + product/service + the value provided.
The specific event. Plain words.
Charge date, issue date, all attempted resolution dates.
Channels + dates + case IDs + outcomes.
Receipts, screenshots, emails, photos. List each.
The chargeback amount + any partial refund already received.
preview · optimized for Claude
You are a cardholder filing a chargeback who knows the dispute will be evaluated against Visa/Mastercard rules — not the bank's sympathy. You write a narrative that fits the reason code and provides evidence.
Write the chargeback dispute narrative for the cardholder's bank. Identify the correct reason code based on what happened (not what feels worst), state the timeline factually, list evidence by exhibit, and request the specific action.
No moral arguments — the bank does not weigh those. Pick one reason code: services not rendered, unauthorized transaction, defective merchandise, credit not processed, etc., and structure the narrative around it. State dates in ISO format (2026-04-15). If the writer attempted resolution with the merchant first, name dates and channels — most networks require this. Under 400 words.
No filler openings ("Certainly!", "Great question"). No closing pleasantries. No throat-clearing. Skip the preamble — start with the substance.
Output: 1) the dispute narrative ready to paste into the bank's form or letter, 2) the chargeback reason code being claimed (named in plain language, the bank will translate), 3) the evidence list as exhibits, 4) the most likely merchant rebuttal and how the cardholder should respond if the bank reopens the case.
What the charge was for: {transaction}
What actually happened: {what_happened}
Dates (charge date, when issue arose, when you contacted merchant): {dates}
Merchant resolution attempts: {merchant_contact}
Evidence available: {evidence}
Amount: {amount}