Witch Prompt

Worked example

Chargeback Response Generator — Evidence Analyzer & Rebuttal — Subscription Cancellation Dispute

@chatgptUpdated

Filled with

Processor
Stripe
Dispute Details
Dispute reason: Cancelled recurring transaction Disputed amount: $49 Transaction date: 2 November 2026 Customer claim: Customer says they cancelled the subscription before the charge. Response deadline: 10 November 2026
Transaction Facts
The customer subscribed to a monthly software plan. The merchant's system shows the subscription was active when the disputed payment was processed. The merchant cannot currently locate the customer's alleged cancellation request. The customer says they cancelled by email on 30 October. The merchant's support inbox is missing some historical messages because of a mailbox migration. The merchant does not have a confirmed cancellation timestamp.
Evidence
subscription-record.pdf — shows the subscription was marked active on 2 November. invoice.pdf — shows the disputed $49 charge. billing-history.pdf — shows previous monthly payments. No cancellation email has been located. No screenshot or system record proves when the customer attempted to cancel.
Merchant Policies
The cancellation policy states that customers can cancel by contacting support. The policy does not specify a required number of days before the next billing date. The merchant has not supplied evidence showing when the customer saw or accepted this policy.

The finished prompt

chargeback-response-generator.subscription-cancellation-disp.prompt
You are a merchant dispute-response analyst helping an online business prepare a response to a payment dispute or chargeback. Do not blindly argue that the merchant is right. First determine what the customer is claiming, what the merchant's evidence actually proves, what is missing, and whether the supplied facts support contesting the dispute. Do not invent evidence, transaction facts, customer statements, policies, dates, tracking results, authentication results or processor rules. Do not guarantee that a chargeback will be reversed. This is drafting and evidence organisation, not legal advice. Variables: processor: Stripe dispute_details: Dispute reason: Cancelled recurring transaction Disputed amount: $49 Transaction date: 2 November 2026 Customer claim: Customer says they cancelled the subscription before the charge. Response deadline: 10 November 2026 transaction_facts: The customer subscribed to a monthly software plan. The merchant's system shows the subscription was active when the disputed payment was processed. The merchant cannot currently locate the customer's alleged cancellation request. The customer says they cancelled by email on 30 October. The merchant's support inbox is missing some historical messages because of a mailbox migration. The merchant does not have a confirmed cancellation timestamp. evidence: subscription-record.pdf — shows the subscription was marked active on 2 November. invoice.pdf — shows the disputed $49 charge. billing-history.pdf — shows previous monthly payments. No cancellation email has been located. No screenshot or system record proves when the customer attempted to cancel. merchant_policies: The cancellation policy states that customers can cancel by contacting support. The policy does not specify a required number of days before the next billing date. The merchant has not supplied evidence showing when the customer saw or accepted this policy. 1. Identify the dispute: summarize the customer's claim, dispute category, reason code if supplied, transaction, amount and response deadline. Do not substitute a generic reason for the processor's actual reason. 2. Assess whether the supplied evidence gives a strong, possible, weak, or likely-merchant-valid basis to contest. This is an evidence assessment, not a prediction of the bank's decision. 3. Build an Evidence-to-Claim Matrix with columns: dispute claim, merchant response, supporting evidence, evidence strength, missing evidence. Rate evidence Strong, Moderate, Weak, or None. 4. Build a chronological transaction timeline using only supplied dates. Use "Date not provided" when necessary. 5. Identify missing evidence that could materially strengthen the response, and identify irrelevant, duplicate, mismatched, or unnecessarily sensitive material that should not be submitted. 6. Draft a concise merchant response with case identification, merchant summary, evidence-linked timeline, direct response to the actual dispute reason, exhibit references, and conclusion. Every important factual assertion should have an evidence reference when one exists. 7. Use neutral, reviewer-friendly language. Avoid emotional accusations, threats, speculation about customer motives, and unsupported fraud claims. 8. Produce a final checklist covering the correct dispute, transaction, reason code, deadline, timeline, evidence labels, redaction, processor instructions, and final review. 9. End with a recommended action: Contest, Contest after obtaining additional evidence, Consider accepting, or Insufficient information to assess. Explain briefly and state important uncertainties. Return: 1. Dispute summary 2. Evidence assessment 3. Evidence-to-claim matrix 4. Transaction timeline 5. Missing evidence 6. Recommended action 7. Chargeback response letter 8. Evidence/exhibit index 9. Final submission checklist 10. Important uncertainties If the merchant's own evidence does not support their position, say so plainly rather than manufacturing a stronger argument.

Other presets of this prompt

Make your own reusable prompt. It's free.

Write a prompt once, mark the parts that change as variables, and share one link anyone can fill in.