A chargeback file does not need another complicated system. It needs a few sheets that answer simple questions: what is the case, what does the claim say, which record supports each fact, and who checked the final response?
These five worksheets are internal aids for online merchants. They are not payment network forms and do not replace the current instructions in your processor’s case screen. Evidence fields and file limits can vary by reason, provider, network, and dispute stage.

For prompt ideas, see the Online Merchant Chargeback Response Prompts book. The chargeback prep article explains how to use AI for bounded file checks.
Before using the worksheets
- Start with the provider’s current case notice and deadline.
- Use a transaction reference or approved internal ID in working copies.
- Keep source files unchanged and store them in your controlled system.
- Follow your company’s rules for customer information and access.
- Retire any field that does not fit the provider’s case form.
The examples below are fictional. Replace them with the actual case data and verify every entry.
Template 1: dispute intake card
Open one intake record for each case. Copy the provider’s terms and dates rather than rephrasing a deadline from memory.
| Field | Entry | Source |
|---|---|---|
| Provider dispute ID | Enter case reference | Processor case screen |
| Transaction and order | Enter exact reference, amount, currency | Payment and store records |
| Reason or category | Copy exact display | Processor notice |
| Response deadline | Copy date, time, and time zone | Case screen |
| Case owner | Name one responsible person | Internal assignment |
| Open requests | Record each missing file and owner | Team follow-up |
Keep a copy of the notice with the intake card. If the screen updates the deadline or request, save the updated information and note when it changed.
Template 2: claim-to-evidence map
Use this sheet to connect each point in the claim to a source record. It helps you see if a document answers the question or simply sits in the folder.
| Claim point | Evidence file | What it shows | What it does not show | Status or question |
|---|---|---|---|---|
| Example: order shipped | Carrier event for order A-107 | Carrier scan on stated date | Package contents | Match tracking ID to order |
| Example: refund issued | Processor refund record | Amount and processing date | Customer’s bank posting date | Check whether refund matches claim |
These examples are made up. Use the actual claim and records. If a file does not support a point, leave the cell open and find the proper source or say that you do not have one.
Template 3: event timeline
A short timeline can make the case easier to review. Use the same time zone or show the original time zone for each event.
| Date and time | Event | Source file | Transaction reference | Review note |
|---|---|---|---|---|
| Example: 10:14 UTC | Payment recorded | Processor transaction report | Exact transaction ID | Verify local time conversion |
| Example: 15:40 local | Carrier acceptance scan | Carrier tracking export | Exact tracking ID | Check this is the right parcel |
Keep the source timestamp and do not silently convert it. A timeline is a reading aid, not a new source record.
Template 4: factual response builder
Before drafting, write down the facts you can verify. Use this sequence:
- Claim: Copy the customer’s stated issue or summarize it accurately.
- Merchant response: State the specific point you are answering.
- Supporting record: Name the file and relevant page or event.
- Limit: Note what the record does not establish.
- Reviewer: Record who checked the statement.
Fictional example: “The order was handed to the carrier on May 4. The carrier record for tracking reference 00-EX-14 shows an acceptance scan that afternoon. This file shows carrier acceptance. It does not show who signed at the destination.”
Do not submit that example. Use actual records and the response fields in the provider’s form. If a sentence has no source, remove it or mark it for verification.
Template 5: submission review and outcome log
Use a final checklist before sending and a separate section for tracking the result.
- Correct case and transaction IDs.
- Deadline and time zone checked in the provider account.
- Every factual statement tied to a source.
- Evidence matches the stated claim and provider form.
- Files are legible, within limits, and named clearly.
- Unrelated pages and sensitive details removed under policy.
- Second reviewer has checked the final packet.
- Submission receipt saved with exact files sent.
| Submitted | Provider receipt | Decision received | Result | Process follow-up |
|---|---|---|---|---|
| Enter exact date and time | Save confirmation ID | Enter when available | Copy provider status | Record one change for next case |
Stripe says its Dashboard response cannot be edited or supplemented after submission. Other providers and case stages may differ. Check the case instructions before sending and save the submission receipt.
AI prompt for a final worksheet review
If company policy permits, ask an approved AI tool to flag omissions in a redacted copy:
“Review these chargeback worksheets for missing source references, mismatched transaction IDs, inconsistent dates, unsupported response statements, and duplicate or unrelated files. Return a table with worksheet, row, issue, and a question for the case owner. Do not invent evidence, infer customer intent, decide whether the dispute is valid, or submit anything. Mark uncertain fields ‘verify.’”
Check every flag against the original. Never put full card details or sensitive customer information into an unapproved tool. Keep AI output separate from your final submission until a person has reviewed it.
Keep templates current
Review the worksheets when your payment provider changes its evidence form, field names, accepted file types, or submission process. The current Visa rules specify different response requirements by dispute condition. Use the rules that apply to your card network and case. Stripe’s guidance is useful for Stripe users, not every processor.
For context, read the prompt guide, the seven mistakes to catch, the eight-step workflow, and the merchant Q&A. The Online Merchant Chargeback Response Prompts book contains additional prompt ideas to adapt after a human checks the source records.
Frequently asked questions
Are these official chargeback response forms?
No. They are internal worksheets. Use the fields, file limits, and submission rules in your provider’s current case form.
What should a chargeback evidence index include?
Useful fields include filename, date, source system, transaction reference, what the record shows, and whether it directly addresses the claim. Follow the current case requirements.
Can I use a template for every chargeback reason?
You can reuse the organization, but evidence needs differ by claim, provider, and network. Adapt each case to its current instructions.
Can AI complete chargeback templates automatically?
It can index redacted files or flag gaps, but a merchant must verify every fact and should not let AI invent evidence or decide a case.
Should I store customer data in a shared chargeback worksheet?
Limit access and store only what is necessary under company policy. Do not include full payment credentials or sensitive details in unapproved systems.