A chargeback notice gives you a clock and a claim. Your first job is to understand what the customer says happened. Then gather the few records that answer that claim. A pile of unrelated screenshots rarely makes the case clearer.
These seven AI prompts help online merchants organize a response file. They do not decide whether a dispute is valid or promise a win. The exact evidence, form fields, and submission deadline depend on the reason, payment processor, and card network.

The Online Merchant Chargeback Response Prompts book offers more prompts for preparing a dispute file. Start with the notice and your payment processor’s current instructions.
Start with the notice and the actual deadline
Save the dispute notice, reason or category, transaction details, response deadline, and evidence instructions. Use the date shown inside your processor account for this dispute. Stripe says its response windows are usually 7 to 21 days depending on the card network. That is a Stripe example, not a deadline for every merchant or provider.
Visa’s current Core Rules and Product and Service Rules describe dispute response requirements by condition. The details can change, so check the current rule set and your processor’s case screen before you prepare the submission.
Seven prompts for a focused response
| Prompt task | What the tool should return | Check before using it |
|---|---|---|
| 1. Explain the claim | A short plain-language summary of what the customer says happened | Read the notice and attached claim documents yourself |
| 2. Index the evidence | Filename, date, source, transaction link, and what it shows | Confirm each file belongs to this transaction |
| 3. Build a timeline | Order date, fulfillment, messages, delivery, refund, or cancellation events | Check dates and time zones against source records |
| 4. Match evidence to claim | Claim point, supporting record, gap, and question to resolve | Use the current processor evidence categories |
| 5. Draft a factual narrative | A short sequence of facts with source references | Remove any claim not proved by a source |
| 6. Find missing facts | Unresolved questions and records to locate | Do not let AI fill gaps with assumptions |
| 7. Review for privacy and clarity | Potentially sensitive details, irrelevant pages, and unclear labels | Follow processor file limits and privacy rules |
Use one prompt at a time. Keep the notice and original records open while reviewing the output. A tool can sort a timeline faster than a person, but it cannot see whether the merchant has confused two similar orders.
Prompt 1: restate the claim
“Read this de-identified dispute notice. Summarize the customer’s claim in two sentences. Quote the stated reason or category exactly and list any requested evidence fields. Do not decide whether the claim is true or suggest a legal conclusion. Cite the notice page or field for each item.”
Start here because the reason code or category points to the specific question you need to answer. Stripe’s dispute response guidance recommends reviewing the dispute category and complaint details before choosing evidence. That is Stripe’s process. Check the help materials for your own provider.
Prompt 2: build an evidence index
“Create an evidence index from these transaction records with filename, date, source system, transaction or order reference, and what the document directly shows. Flag duplicate, unreadable, or unrelated records. Do not infer delivery, authorization, customer identity, or agreement from a partial record.”
Possible records depend on the claim. A delivery dispute may point you toward order fulfillment and carrier records. A cancellation dispute may involve cancellation logs and customer messages. A “not as described” claim may call for the product page or agreed specifications. Use the fields and evidence categories in your actual case form.
Prompt 3: make a short event timeline
“Arrange these dated records in chronological order. Show the date, event, source, and any difference in time zone or timestamp format. Mark dates that conflict. Do not add events that are not in the records.”
A simple timeline helps a reviewer see the order without paging through every attachment. Keep it short and point to the source file. Do not claim the customer received, used, or accepted an item unless the record supports that statement.
Prompt 4: connect each claim point to evidence
“For each specific point in the dispute notice, list the record that directly supports or contradicts it, what that record proves, what it does not prove, and any missing source. If no record addresses a point, say ‘no supporting record found.’”
This can reveal a gap before you submit. A tracking page might show delivery status, but not what was in the parcel. A customer message might show a discussion, but not that a refund was processed. State only what the file demonstrates.
Prompt 5: draft a factual response
“Draft a brief response using only the verified facts in this evidence table. Address each point in the dispute claim once. Add a source reference after every factual statement. Keep the tone neutral. Do not accuse the customer of fraud, invent policy terms, promise an outcome, or quote a rule unless it appears in the attached current processor instructions.”
Read the draft aloud and compare each sentence to its source. Remove filler and emotional language. If a paragraph adds no fact or answer, it probably does not belong.
Prompt 6: find unresolved questions
“Review the draft and evidence index for claims without a source, inconsistent transaction identifiers, dates that do not match, and questions the current case instructions ask but the file does not answer. Return only a checklist. Do not make up missing facts.”
Send the checklist to the right owner. That might be fulfillment, support, billing, or the person who managed the order. Keep a note of what was verified before the submission.
Prompt 7: check the file before sending
“Review this response packet against the current processor instructions. Flag missing required fields, unsupported statements, duplicate pages, unreadable files, exposed sensitive data, and any file that does not appear to relate to this transaction. Do not submit the response. Return a list for human review.”
Do your own final pass. Check the deadline, evidence limit, file type, file size, redaction rules, and transaction ID in the processor’s form. Stripe says merchants have one opportunity to submit a response through its Dashboard, and that the response and files cannot be edited or supplemented afterward. That is specific to Stripe’s process; your provider may work differently.
Keep sensitive data out of the prompt
Do not paste a full card number, security code, password, government ID, or private customer details into an unapproved AI tool. Use a transaction reference or a redacted copy if your company policy allows it. Keep originals in your controlled system.
The seven prompts are most useful for sorting, not deciding. AI can expose a missing file or awkward sentence. It cannot tell you whether a bank or network will accept the evidence. The final response should follow the provider’s form and current network rules.
Where to continue
For common response gaps, read the chargeback mistakes guide. Use the order-to-response workflow to set owners and stages, then review questions merchants should ask before replying. The evidence and timeline templates will help keep the records consistent. The Online Merchant Chargeback Response Prompts book has additional prompt patterns to adapt after checking your case instructions.
Frequently asked questions
What is the deadline to respond to a chargeback?
Use the deadline shown by your payment processor for the specific dispute. Stripe says its usual response windows range from 7 to 21 days, depending on the network.
What evidence should I submit for a chargeback?
Choose evidence that answers the specific claim and follows your processor’s current instructions. Records may include order, delivery, service, communication, refund, or policy evidence depending on the dispute.
Can AI write a chargeback response?
AI can organize records and draft a factual summary, but a merchant must verify every statement against the source documents and provider instructions.
Should I submit every document I have?
No. Follow the current evidence fields and file limits in your provider’s response form. Submit relevant, legible records that address the claim.
Does strong evidence guarantee that I will win a chargeback?
No. The issuer or card network decides the dispute under its rules. A clear file supports review but does not guarantee an outcome.