How to Use the Chargeback Evidence Packet Prompt to Answer the Reason Code You Actually Got

A chargeback lands, the deadline clock starts, and the instinct is to upload everything you have and hope. Issuers do not read it that way. They look for evidence that answers the specific reason code the cardholder used. The Card Chargeback Representment Evidence Packet Builder: Reason Code Read, Evidence Checklist, Rebuttal Letter, Accept or Fight Call, and a Response Deadline Tracker prompt reads the code, checks your evidence against it, and drafts a short, factual response packet.

What the prompt produces

1. A plain reading of the reason code: what the cardholder claims and what the issuer needs to see.
2. An evidence checklist marked have, missing, or not relevant.
3. An accept or fight recommendation with honest reasons.
4. A rebuttal letter under 300 words in date order, naming each exhibit.
5. An exhibit list with file names in reading order.
6. An upload note for your processor's evidence fields.
7. A deadline tracker with an internal target two days before the processor's date.
8. Prevention notes with two changes that would have stopped this dispute.

How to fill the inputs

ProcessorView tells the prompt where you will submit: Stripe, Shopify Payments, PayPal, Square, or a bank portal. Each one lays out evidence fields a little differently.

ReasonCode should be copied exactly, including the network and number. A "not received" code and a "fraud" code need very different evidence, and the prompt builds the checklist around the one you paste.

OrderFacts covers the amount, dates, product, carrier, tracking, delivery confirmation, and any IP or device data you have. Leave out anything you cannot document.

CustomerHistory is often the strongest piece. Paste the emails or chat logs with dates, including any time you offered help or a refund.

PolicyDisplay describes how the customer saw your refund, shipping, or subscription terms at checkout. A screenshot of a checkbox or a link near the pay button is more useful than a policy page nobody had to see.

ResponseDeadline is the date your processor shows. The tracker sets your internal target earlier so you are not uploading at midnight.

Reading the example output

The example is a home goods store facing a Visa 13.1 merchandise not received dispute on two duvet covers.

• The checklist shows carrier tracking with a delivered scan to a matching address, plus a same day reply to the customer, and flags the missing signature as the weak point.
• The recommendation is to fight, with the reasons spelled out, and notes that no refund was issued so nothing would be double counted.
• The rebuttal letter is short, in date order, and points to exhibits A through D.
• The upload note reminds you that most processors accept one submission, so check everything before you click submit.
• The prevention notes suggest signature confirmation above an amount you choose and a delivered email that reminds customers of the claim window.

Tips for better results

• Name exhibit files clearly. A reviewer skimming twenty disputes will thank you.
• Keep the rebuttal factual. Emotional language and blame do not help.
• If you already refunded the customer, say so and include proof. Fighting a refunded dispute wastes your time.
• Save the packet as a template for the same reason code. Many stores see the same few codes again and again.

Mistakes to avoid

• Do not invent tracking numbers, IP addresses, or network rules. The prompt marks gaps for you to confirm.
• Do not contact the cardholder in a way that pressures them to drop the dispute.
• Do not upload evidence that does not relate to the reason code. It dilutes the strong pieces.
• Do not wait for the last day. Processor portals can be slow, and some evidence takes time to export.

Who it is for

Shopify and Stripe store owners, ecommerce operations leads, bookkeepers who handle disputes for clients, and small SaaS teams dealing with subscription chargebacks. It is operations help, not legal advice.

Deciding when to accept

Not every dispute is worth fighting. Small amounts with weak evidence can cost more in staff time than they return. The prompt weighs amount, evidence strength, and whether a refund already happened, then gives you a clear call. Accepting a dispute you would lose keeps your focus on the ones you can win and on the prevention steps that cut future disputes.

Related PromptDig links

Open the Card Chargeback Representment Evidence Packet Builder: Reason Code Read, Evidence Checklist, Rebuttal Letter, Accept or Fight Call, and a Response Deadline Tracker prompt with your next dispute. For more business operations prompts, Browse more prompts. If you have a dispute workflow that saves your team hours, Share a prompt.