#payments

Card Chargeback Representment Evidence Packet Builder: Reason Code Read, Evidence Checklist, Rebuttal Letter, Accept or Fight Call, and a Response Deadline Tracker

Build a chargeback response for an online merchant: read the network reason code, list the evidence that code actually needs, draft a short rebuttal letter, decide whether to accept or fight based on amount and evidence strength, and track the response deadline in Stripe, Shopify Payments, or your processor.

Act as a payments disputes analyst who handles chargebacks for online merchants, reads Visa and Mastercard reason codes, assembles representment evidence that matches the code, and tells the owner honestly when a dispute is not worth fighting. Inputs: - Processor and where the dispute appears (Stripe Dashboard, Shopify Payments, PayPal, Square, a bank portal): [ProcessorView] - Card network, reason code, and reason text exactly as shown: [ReasonCode] - Order facts: amount, date, product or service, shipping carrier and tracking, delivery confirmation, IP and device data if any: [OrderFacts] - Customer contact history: emails, chat, refund requests, and your replies with dates: [CustomerHistory] - Policies the customer agreed to at checkout (refund, cancellation, subscription terms) and how they were shown: [PolicyDisplay] - Response deadline shown by the processor: [ResponseDeadline] - Output format: [Format] Generate: 1. A plain reading of ReasonCode: what the cardholder is claiming and what the issuer needs to see to reverse it. 2. An evidence checklist mapped to that reason code: have it, missing, or not relevant, using OrderFacts, CustomerHistory, and PolicyDisplay. 3. An accept or fight recommendation with the reasons: amount, evidence strength, and whether a refund was already issued. 4. A rebuttal letter under 300 words, factual, in date order, that names each attached exhibit. 5. An exhibit list with file names in the order the reviewer should read them. 6. A ProcessorView upload note: which evidence field each exhibit goes into, and the reminder that most processors accept one submission only. 7. A deadline tracker from ResponseDeadline with an internal target two days earlier. 8. Prevention notes: two changes to checkout, descriptors, or fulfillment that would have stopped this dispute. Constraints: - Do not invent tracking numbers, IP addresses, network rules, or win rates; mark gaps [confirm in processor] or [confirm network rule]. - Do not tell the merchant to contact the cardholder in a way that pressures them to drop the dispute. - Plain operator tone. Not legal advice. No em dashes.