💼 Business
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.
0Reviews
Prompt
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.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Generated Output
This image was generated using the prompt above.
Examples
Example Input
ProcessorView: Stripe Dashboard, Payments > Disputes ReasonCode: Visa 13.1 Merchandise/Services Not Received OrderFacts: order 48213, $186.40, 2026-09-02, two linen duvet covers; shipped UPS Ground 2026-09-03; UPS shows delivered 2026-09-08 to front door, no signature; shipping address matches billing ZIP CustomerHistory: 2026-09-12 customer emailed saying the box never came; we replied same day asking them to check with neighbors and offered to open a UPS claim; no reply; dispute filed 2026-09-20 PolicyDisplay: checkout page shows a checkbox for the shipping policy that says lost package claims must be reported within 14 days of delivery ResponseDeadline: Stripe shows evidence due by 2026-10-11 Format: reason read, checklist, recommendation, rebuttal letter, exhibits, upload note, tracker, prevention
Example Output
1) REASON CODE READ Visa 13.1 says the cardholder did not receive the goods. To reverse it, the issuer needs proof the order was shipped to the cardholder's address and delivered, plus anything showing you tried to help. 2) EVIDENCE CHECKLIST - Proof of shipment with tracking: HAVE (UPS Ground, shipped 2026-09-03) - Proof of delivery to the billing or agreed address: HAVE (UPS delivered 2026-09-08, front door). Signature: MISSING - Address match: HAVE (shipping address matches billing ZIP) - Customer communication: HAVE (2026-09-12 email and same day reply with claim offer) - Shipping and lost package policy shown at checkout: HAVE (checkbox screenshot needed) - Prior undisputed orders from this customer: NOT RELEVANT for 13.1 3) RECOMMENDATION: FIGHT The amount is meaningful, delivery is confirmed by the carrier to a matching address, and you responded quickly with an offer to file a carrier claim. The weak spot is no signature. No refund was issued, so there is nothing to double count. 4) REBUTTAL LETTER Re: Dispute on order 48213, $186.40, Visa 13.1 The cardholder ordered two linen duvet covers on 2026-09-02. We shipped the order by UPS Ground on 2026-09-03 to the address entered at checkout, which matches the billing ZIP code (Exhibit A, order record). UPS tracking shows the package was delivered to the front door on 2026-09-08 (Exhibit B, tracking history). On 2026-09-12 the cardholder emailed us that the box had not arrived. We replied the same day, asked them to check with neighbors, and offered to open a UPS claim for them (Exhibit C, email thread). We did not receive a reply. The dispute was filed on 2026-09-20. At checkout the cardholder accepted our shipping policy, which explains how lost package claims are handled (Exhibit D, checkout screenshot and policy text). The goods were shipped and delivered to the cardholder's address, and we offered help when contacted. We ask that the dispute be resolved in our favor. 5) EXHIBITS A_order_48213_record.pdf B_ups_tracking_delivered_2026-09-08.pdf C_customer_email_thread_2026-09-12.pdf D_checkout_policy_checkbox_and_text.png 6) STRIPE UPLOAD NOTE - Shipping documentation: Exhibit B, add tracking number and carrier fields [confirm in processor] - Customer communication: Exhibit C - Refund or shipping policy: Exhibit D - Receipt: Exhibit A - Additional information: paste the rebuttal letter Submit once. Stripe does not let you add evidence after you submit [confirm in processor]. 7) DEADLINE TRACKER | Item | Date | | Processor deadline | 2026-10-11 | | Internal target | 2026-10-09 | | Expected issuer decision | [confirm in processor] | 8) PREVENTION - Require signature confirmation on orders over a set amount you choose. - Send a delivered email with a photo link when the carrier offers delivery photos, and remind customers of the claim window.