National merchant dispute guidance
What Evidence Should a Merchant Submit for a Chargeback?
Submit evidence that directly answers the dispute reason and documents what happened from authorization through fulfillment, customer communication, and any refund. The strongest response is a short, chronological case file built for the specific transaction—not a large collection of unrelated records.
Start with the claim
Match every document to the dispute reason
Open the processor or acquirer case before gathering files. Record the reason category, network reason code when shown, disputed amount, transaction date, response deadline, and the cardholder's stated claim. Evidence for an unrecognized transaction differs from evidence for merchandise not received, a canceled recurring service, duplicate processing, or a credit that was not posted.
Core record set
Build a transaction timeline
Order and payment record
Include the order number, transaction identifier, date, amount, item or service description, customer details relevant to the case, and the receipt or invoice. Use the processor's record for authorization results already captured with the payment.
Customer authorization
For an authorization claim, relevant records can include a signed receipt or agreement, checkout acceptance, account login history, IP or device data, 3-D Secure results, and address or security-code results when the provider makes them available.
Fulfillment or service proof
For physical goods, use carrier, tracking, ship date, full delivery address, and delivery confirmation. For services or digital goods, use appointment records, access logs, download history, usage records, or a signed completion document.
Communication and policy
Provide concise customer messages relevant to the complaint plus the refund, cancellation, return, or service terms the customer saw and accepted. Highlight the applicable passage instead of submitting an entire policy without context.
Reason-specific evidence
Use the claim to narrow the packet
Product or service not received
Connect the transaction to delivery or performance. Include tracking with the complete delivery destination, proof of pickup, signed acceptance, appointment attendance, project milestones, or system logs showing access. Explain any difference between the buyer's name and recipient's name.
Product unacceptable or not as described
Show the original listing, product description, service scope, condition disclosures, customer communications, return instructions, and any attempt to resolve the complaint. If the merchant accepted a return, include whether and when it arrived.
Credit not processed
Provide the original transaction, refund date and amount, processor-generated refund identifier, processing log, and settlement or merchant statement entry. The records should show whether the credit was full or partial and tie it to the disputed purchase.
Duplicate or recurring transaction
For duplicate claims, distinguish the separate purchases with order details, timestamps, items, and receipts. For recurring claims, include the subscription terms, the customer's consent, renewal notices where applicable, usage after renewal, cancellation history, and the date access ended.
Packet quality
Make the evidence easy to evaluate
Lead with a short explanation
State what the customer claimed, why the merchant believes the claim is incorrect, and which attached records support that conclusion. Keep the explanation factual and tied to the case.
Put events in order
Arrange the purchase, authorization, fulfillment, customer contact, cancellation, return, and refund events chronologically. Label each document with its date and purpose.
Keep files self-contained
Issuers may not open external links or request more information. Put the relevant tracking details, screenshots, messages, and logs inside the submitted packet, within the provider's file and page limits.
Review before submitting
Some provider workflows allow only one final evidence submission. Confirm that every file is readable, belongs to the correct transaction, fits an accepted evidence type, and contains no unrelated sensitive data.
What to leave out
Avoid evidence that distracts from the case
Do not submit a generic statement that the merchant always delivers orders, an entire policy without proof the customer saw it, unrelated customer histories, unreadable screenshots, links that require the issuer to visit another site, or personal opinions about the cardholder. Do not alter records or create documents after the fact. A response should explain the existing business record, not manufacture a new one.
Decision check
Challenge only when the record supports it
Review whether the merchant can directly disprove the claim before submitting. If the cardholder's claim is valid or the merchant lacks relevant records, the processor may offer an option to accept the dispute. If the merchant challenges it, the issuing bank—not Payments Max or the payment processor—decides the outcome under the applicable network process.
Related resources
Continue your chargeback research
Common questions
Chargeback evidence FAQ
Should every dispute receive the same documents?
No. Start with the case reason and provider checklist. Shipping evidence may help a delivery claim but does not by itself answer whether a cardholder authorized the payment.
Are customer emails useful evidence?
They can be when they show recognition of the purchase, acceptance of delivery, use of a service, a cancellation request, or an attempt to resolve the specific complaint. Include only the relevant exchange.
Can a merchant send a tracking link?
Include the carrier, tracking number, delivery address, and delivery status inside the evidence packet. Provider guidance warns that reviewers may not follow external links.
Does submitting evidence guarantee a win?
No. Relevant, readable records help the issuer evaluate the case, but the issuing bank decides the outcome under the applicable rules and facts.
Last editorial review: August 11, 2026. Sources reviewed: current Stripe dispute-response guidance, Visa merchant resources, and Mastercard's May 19, 2026 merchant chargeback guide. Provider and network procedures can change.
Next step
Assemble the case before the deadline
Payments Max can help merchants organize payment records and provider questions. Submit the final evidence through the processor or acquirer's approved dispute workflow.
To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.
CONTACT US