A chargeback response is strongest when it is timely, organized, and tied to the specific dispute reason. This checklist helps online businesses assemble an evidence pack covering the order, payment, delivery, account activity, refund handling, and customer communications without assuming that any single record proves liability.
Overview
A chargeback or payment dispute occurs when a cardholder or payment customer challenges a transaction through a bank, card issuer, payment provider, or another payment channel. The business may then be invited to respond, sometimes through a process called representment. The exact terminology, evidence format, deadlines, and permitted documents depend on the payment method, processor, network, reason code, and applicable rules.
Start by treating each dispute as a time-sensitive evidence review rather than a general customer-service complaint. Read the dispute notice first and identify:
- the stated reason or reason code;
- the response deadline and submission channel;
- the transaction amount, currency, date, and order number;
- the remedy requested, such as a reversal, refund, or explanation; and
- any file-format, character-limit, or document requirements in the processor portal.
Do not submit every record you have without explanation. A concise evidence pack should show what happened, when it happened, which terms applied, and how each document addresses the stated dispute. Keep the original records unchanged and create a separate response summary for submission.
If a dispute involves suspected account takeover, a data incident, repeated fraud, or a material financial loss, preserve evidence and consider obtaining qualified legal or specialist advice. This guide is a practical workflow, not a determination of liability or a substitute for the rules governing your payment arrangement.
Checklist by scenario
Every dispute: build the basic transaction file
Begin with a one-page transaction summary. Include the order identifier, customer identifier used in your system, product or service purchased, transaction date, amount, currency, payment method, and fulfillment status. Then gather:
- the checkout or order confirmation;
- the invoice or receipt;
- the product, service, subscription, or digital-access description shown at purchase;
- the terms, cancellation rules, refund policy, and delivery terms presented to the customer;
- the payment authorization or processor transaction reference, where available; and
- a chronological account of relevant customer contact.
Record the source and date of each item. If a policy has changed since the order, identify the version that applied when the customer purchased. Avoid presenting a current policy as though it governed an earlier transaction.
Unauthorized transaction or fraud allegation
Evidence may be relevant when it connects the transaction to the customer account or the normal purchasing pattern, but avoid treating technical signals as conclusive on their own. Depending on the transaction and the rules of the payment provider, consider including:
- login, account-creation, password-reset, or multifactor-authentication events;
- device, browser, IP, or location indicators, with appropriate privacy controls;
- records showing that the customer accessed a digital product or account after purchase;
- prior undisputed transactions or customer interactions that are genuinely comparable; and
- shipping, billing, and account details, handled consistently with applicable privacy obligations.
Explain what each signal demonstrates and what it does not demonstrate. For example, a matching IP address may support an account-activity timeline, but it may not establish who physically used a device. Do not include unnecessary personal data or sensitive authentication information.
Merchandise not received
For physical goods, collect the order confirmation, dispatch record, carrier tracking, delivery scan, delivery address, and any delivery exception or investigation record. If the customer reported a problem, include the complaint, your response, and any replacement or refund offer.
Where tracking shows delivery but the customer disputes receipt, describe the record precisely rather than asserting that delivery automatically resolves the dispute. Consider whether the delivery address was supplied by the customer, whether the carrier record is complete, and whether local rules, processor requirements, or the order terms affect the response.
Services, subscriptions, or digital goods
Show the purchase and the promised performance. Useful records can include:
- the service scope, subscription period, or delivery schedule;
- the customer’s acceptance of relevant terms;
- appointment, project, milestone, or completion records;
- login, download, streaming, activation, or usage events;
- messages showing delivery, access, or customer approval; and
- cancellation, renewal, pause, and refund records.
For recurring payments, identify the initial authorization and each later billing event. Do not rely solely on the fact that a subscription was technically active. Show how cancellation requests were received and processed, including the effective date and any communication sent to the customer.
Product not as described or defective goods
Compare the customer’s allegation with the description that was visible at purchase. Preserve the relevant product page, specifications, images, configuration selected, invoice, and support exchange. If the product was returned or inspected, retain the return tracking, inspection notes, photographs, replacement record, and refund decision.
Address the allegation directly. A general statement that the item was shipped is not a complete response to a quality or description complaint.
Refund, cancellation, or credit dispute
Gather the refund policy in force at the time, the customer’s request, your decision, and the processor record showing whether a refund or credit was issued. If a partial refund was made, state the amount, date, transaction reference, and reason. If the customer accepted store credit or another resolution, include the relevant communication, while recognizing that acceptance may not settle every dispute under every payment process.
Customer-service resolution or duplicate dispute
For a customer who says the matter was already resolved, provide the ticket timeline, agreed outcome, refund or replacement record, and delivery of that outcome. For a possible duplicate charge, compare the dates, amounts, authorization references, order numbers, and goods or services supplied. Similar amounts alone do not establish duplication; show why the transactions were separate or why one was reversed.
What to double-check
Use this evidence-pack template before submitting:
- Dispute identification: reason, code, transaction, deadline, and required response channel.
- Position: accept the dispute, contest it, or explain why only part of the claim is supported by the records.
- Timeline: purchase, authorization, fulfillment, access or delivery, complaint, refund, and response dates.
- Evidence index: numbered documents with a short explanation of what each proves or supports.
- Policy match: the version of the terms, refund policy, or cancellation rule that applied at purchase.
- Privacy review: remove irrelevant personal data, passwords, full payment credentials, and internal notes that do not help answer the dispute.
- Submission check: confirm file type, size, page limits, text limits, and successful upload or receipt.
Compare the reason code with the evidence rather than using a one-size-fits-all response. A general comparison looks like this:
| Dispute theme | Evidence to prioritize | Question to answer |
|---|---|---|
| Unauthorized transaction | Account activity, authorization records, access events | What transaction and account activity are linked, and what limits apply to that evidence? |
| Not received | Dispatch, tracking, delivery, and address records | What was promised, where was it sent, and what does the carrier record actually show? |
| Not as described | Listing, specifications, correspondence, return or inspection records | How does the delivered item or service compare with the purchase description? |
| Refund or cancellation | Policy, request, cancellation log, refund transaction | What did the customer request, when was it processed, and what amount was returned? |
| Duplicate or processing error | Transaction references, dates, amounts, invoices | Are the charges duplicates, or do they represent separate goods or services? |
Before final submission, have someone unfamiliar with the case read the response. They should be able to identify the disputed transaction, follow the timeline, and understand why each attachment matters.
Common mistakes
- Missing the deadline: Processor deadlines can be short and may differ by dispute type. Route every notice to an accountable owner immediately.
- Submitting a generic narrative: A long account of the business is less useful than a short explanation tied to the specific allegation.
- Ignoring the customer’s version: Address the actual complaint, including defects, cancellation requests, delivery exceptions, or promised features.
- Using the wrong policy: Current website terms may not match the terms shown when the transaction occurred.
- Overstating technical evidence: Device, IP, and login data can be supportive without proving identity or consent.
- Including excessive personal data: Share only what is relevant and permitted through the submission channel.
- Failing to preserve originals: Exported screenshots can lose context. Retain source records, timestamps, and system references.
- Refunding without documenting the outcome: A refund, replacement, or credit should have a transaction reference and a clear customer-facing record.
For related operational controls, review the Small Business Compliance Calendar and the Data Breach Response Legal Checklist where a payment dispute reveals a wider security or record-keeping issue.
When to revisit
Review this chargeback evidence checklist before seasonal sales periods, when you change processors or payment methods, and whenever your checkout, subscription, refund, fulfillment, or customer-service workflow changes. Processor portals, reason-code descriptions, submission windows, and evidence requirements can change, so confirm the current instructions at the time of each dispute rather than relying on an old internal guide.
At least periodically, analyze closed disputes by reason, product, channel, and outcome. Look for preventable patterns such as unclear renewal notices, inconsistent delivery records, delayed refunds, incomplete cancellation handling, or product descriptions that create avoidable confusion. Update your evidence map and assign owners for the records you may need later.
For practical use, keep a dispute folder with a standard transaction summary, timeline, evidence index, policy archive, and submission confirmation. When a new notice arrives, identify the deadline, preserve the relevant records, match the reason to the correct scenario above, and submit only a clear, supported response. That repeatable process improves consistency without promising that any evidence pack will determine the outcome.