Payment Dispute Evidence Pack

A customer disputes a card payment through the bank, and the merchant may have a chance to respond with records showing what was ordered, charged and delivered. An evidence pack organises those records around the actual dispute reason.

Read the reason code and deadline first, because a claim of non-receipt needs different evidence from a claim of an unauthorised transaction and rules vary by network and payment provider. Identify the exact transaction by matching amount, date, payment reference, invoice and customer order, since similar orders or duplicate names can lead to a convincing-looking but irrelevant file.

Create a chronology showing when the customer ordered, accepted terms, paid, received goods or service and raised a complaint, with consistent dates. Stripe's dispute guidance recommends chronological organisation, grouping by evidence type and brief explanations of what each item shows, while the bank, not the merchant's payment provider, decides the final result.

Match the evidence to the claim. For physical delivery, include order confirmation, tracking and delivery records, remembering that a carrier status may not establish the identity of the person who received a parcel; for digital services, use access logs, usage dates and service records, explaining how each log ties to the disputed account without unsupported claims about the person behind an IP address.

For a cancellation dispute, show the cancellation policy and when the customer saw it along with the request and effective date, because a policy posted later cannot prove earlier notice, and for a pricing dispute show the displayed amount, invoice, discounts and any later adjustment, since a screenshot from today's website may not reflect the price at the purchase date. Check refunds and credits, and if money was already returned or a credit issued include the accurate status and date rather than implying a pending refund has settled.

Use customer correspondence selectively, preserving surrounding context and redacting unrelated private data, and avoid misleading certainty because a successful login does not prove who held the device and a shipment record does not always prove a parcel contained the promised goods. Check policy relevance too, since a generic no-refunds term may not settle statutory consumer rights for a faulty item, and keep irrelevant sensitive material such as payment credentials, unrelated customer conversations and internal notes about other accounts out of the pack.

Confirm the response window, because network deadlines can be short and provider-specific and an excellent pack submitted after the cutoff may not be reviewed. Separate preparation from submission, since a draft is not a representation to the bank until an authorised person reviews and submits it and the sign-off is recorded.

Consider whether to contest at all, because if records show the customer was charged wrongly a fair correction may be better than a weak challenge, given fees, effort and customer treatment. Use a cover summary that states the dispute claim and the strongest relevant facts in a few lines, with references to attached pages and no emotional language about the customer.

An illustrative completeness rate is disputes with the required evidence categories assembled before the internal review cutoff divided by all disputes selected for response, so eight of ten equals 80%, and it does not measure the chance of winning. Track outcomes separately, since a bank may accept or reject evidence for reasons outside the merchant's control, and preserve an audit trail of the submitted version, timestamp and provider response under the company's retention rules, because an evidence pack should be honest, relevant and easy to follow so an independent reviewer can understand the transaction without being offered a certainty the records cannot support.