A customer disputes a payment for an order you shipped three weeks ago. You have a tracking number, but is that enough to win the chargeback? Not necessarily. A strong chargeback response connects the customer’s claim to clear, relevant evidence—and submits it in the format and timeframe your payment provider requires.
For an ecommerce store, the goal is not to send every record you have. It is to show, as plainly as possible, what happened: what the customer ordered, what they agreed to, how you fulfilled the order, and how you handled any complaint. Here’s how to build a payment dispute response that gives the reviewer the information they need without burying the important details.
Start with the dispute reason, not your order history
Before gathering documents, open the dispute notice in your payment dashboard. Note the reason code or stated claim, response deadline, disputed amount, and submission requirements. Requirements vary by payment provider, card network, and dispute type, so your provider’s instructions should take priority over any general checklist.
The reason for the dispute determines what you need to prove. If the customer says an item never arrived, a screenshot of your product description will do little on its own. If they say the product was not as described, delivery confirmation does not address the main complaint.
| Customer’s claim | Evidence to prioritize |
|---|---|
| Unauthorized or fraudulent transaction | Checkout and payment records, available authentication results, relevant customer account activity, and any applicable prior transaction history |
| Item not received | Order details, shipping address, carrier tracking, delivery confirmation, and relevant customer communications |
| Item not as described or defective | The product page as shown at purchase, order details, fulfillment records, and your response to the customer’s complaint |
| Refund not received | Your refund policy, the customer’s request, your reply, and records showing whether and when a refund was issued |
| Subscription or recurring charge disputed | Enrollment terms, the customer’s acceptance, billing notices where applicable, cancellation records, and evidence of service delivery |
These are starting points, not guarantees. For example, a “delivered” tracking status can help with an item-not-received claim, but it may not resolve a dispute if the package went to the wrong address.
Build a clear timeline for each disputed order
A reviewer should be able to understand your case quickly. Create a short timeline that matches the documents you submit:
- Purchase: When was the order placed, what was purchased, and what shipping or billing details did the customer provide?
- Payment: What transaction records and authentication information are available?
- Fulfillment: When did you ship or provide access, and to which address or account?
- Delivery or use: What records show receipt of the goods or access to the service?
- Customer contact: Did the customer report a problem, and how did you respond?
- Resolution: Was a replacement, return, cancellation, or refund offered or completed?
Use dates consistently and identify any differences that might otherwise look suspicious. For instance, if a customer purchased on Monday but the carrier first scanned the package on Wednesday, explain the processing time rather than leaving the gap unexplained.
A brief response summary can introduce the evidence: “The customer ordered a blue jacket on 4 May. We shipped it to the address entered at checkout on 6 May. Carrier tracking shows delivery to that address on 9 May. The attached order record, shipping label, and carrier record support this timeline.” Only include statements your records substantiate.
Gather evidence that answers the specific claim
Order and checkout records
Save the order confirmation, item names and variants, price, taxes, shipping charges, order date, and the address supplied at checkout. If the dispute concerns product expectations, preserve the product description, size information, images, and applicable terms as they appeared when the customer bought the item. A current product page may have changed since the purchase.
For policies such as returns or subscriptions, evidence that the policy existed is helpful; evidence that it was presented to the customer at the relevant point in checkout is stronger. Avoid claiming the customer agreed to terms unless you have a record supporting that claim.
Shipping and delivery records
For physical products, collect the shipping label, carrier name, tracking number, scan history, and proof of delivery if available. Check that the destination in those records is consistent with the address on the order. For high-value shipments, a signature or other delivery detail may provide useful context when available.
Be precise about what each record proves. A label shows that a shipment was prepared. A carrier acceptance scan shows that the carrier received it. A delivery scan shows the carrier marked it delivered. Those are different events, and none should be described as more conclusive than it is.
Digital delivery and service records
If you sell downloads, memberships, or other digital products, shipping records will not apply. Instead, gather records showing when access was granted, when a download link was sent, or whether the customer used the account or service. Explain what each record represents, especially if you use internal event names that a reviewer may not recognize.
For recurring charges, include the subscription terms presented at signup, the billing schedule, relevant notices, usage records where appropriate, and any cancellation request or confirmation. The strongest response addresses the exact billing period under dispute rather than the subscription in general.
Customer communications and refunds
Include relevant emails, support tickets, chat transcripts, return requests, and your replies. Preserve timestamps and enough context to make the exchange understandable. If you offered a remedy, show what you offered and whether the customer accepted it.
If you already issued a refund, provide the refund date, amount, and transaction reference available in your payment system. Check your provider’s guidance before issuing a new refund after a dispute has opened; refunding separately while a chargeback is in progress can create an avoidable duplicate-credit problem.
Make your chargeback response easy to review
Even useful evidence loses impact when it is disorganized. Put the most directly relevant document first, use readable screenshots, and label files descriptively—for example, “Order-4821-carrier-delivery” rather than “Screenshot-7.” If your provider allows a written explanation, use it to point to the evidence, not to repeat every detail in the attachments.
Keep the tone factual. Avoid accusing the customer of fraud, speculating about their motives, or relying on statements such as “we always deliver orders.” Your store’s usual practices do not prove what happened with this order.
Before submitting, check:
- Does each attachment relate to the stated dispute reason?
- Do the order, payment, shipping, and refund records refer to the same transaction?
- Are dates, addresses, and amounts consistent—or explained where they differ?
- Are screenshots complete and legible?
- Have you removed unrelated customer information and followed your provider’s rules for sensitive data?
- Have you submitted before the deadline shown in your dashboard?
Store an internal copy of the response and the supporting records. That makes follow-up easier and helps you identify recurring issues, such as unclear delivery estimates or product descriptions that repeatedly lead to complaints.
Know when responding may not be the best choice
Not every chargeback is worth contesting. If your records show that you sent the wrong item, missed a promised refund, or cannot substantiate fulfillment, an evidence packet is unlikely to fix the underlying problem. Review the facts, the disputed amount, and any fees or operational costs before deciding what to do.
Likewise, do not miss a short deadline while trying to assemble a perfect file. Dispute processes have strict time limits, and late evidence may not be considered. If you are unsure which documents to provide or whether a refund is still possible, consult your payment provider’s guidance for that case.
Prepare for the next dispute before it happens
The easiest chargeback response to build is one whose evidence is already organized. For each order, keep accessible records of the checkout details, terms presented, payment and authentication information supplied by your provider, fulfillment events, and customer support history. Set a routine for checking dispute notifications so deadlines do not depend on someone spotting an email.
Then use disputes as feedback. Repeated “item not received” claims may point to delivery communication problems; “not as described” claims may reveal a gap between your product page and the item customers receive. Better records help you respond, but clearer expectations and faster support may prevent some disputes from arising at all.
Your next step: create a simple evidence checklist for your store’s most common dispute reasons. The next time a chargeback arrives, you can focus on the claim and submit a concise, supported response rather than searching through disconnected systems at the last minute.
Frequently asked questions
What is the most important evidence for an ecommerce chargeback?
It depends on the dispute reason. For an item-not-received claim, carrier records and the order’s shipping address are often central. For a not-as-described claim, the product information shown at purchase and your communications about the complaint are more relevant. Start with the claim, then choose evidence that directly addresses it.
Does proof of delivery guarantee I will win a chargeback?
No. Proof of delivery can be valuable, but the outcome depends on the claim, the quality of the evidence, and the applicable payment provider and card network rules. Confirm that the delivery record corresponds to the disputed order and the address provided at checkout.
Can I submit customer emails or chat messages as evidence?
Usually, relevant customer communications can help explain what happened, subject to your provider’s submission requirements. Include enough context and timestamps to make the exchange clear, and avoid sharing unrelated personal information.
How long do I have to respond to a chargeback?
Response deadlines vary by provider and dispute. Check the deadline displayed for the specific case in your payment dashboard, and allow time to gather, review, and upload evidence before it expires.