Build the dispute evidence file while fulfilling the order

A dispute response is constrained by the reason presented, the network and acquirer process, and the records the merchant can produce. A large bundle of screenshots is not automatically persuasive. Build a compact evidence file around the transaction before a notice arrives, then select only material that answers the actual dispute.

Visa’s merchant guidelines give condition-specific examples such as authorization evidence, delivery records, cancellation disclosures, and documentation of a credit or reversal. Mastercard’s overview explains that disputes move through defined categories and a process between issuers and acquirers, while warning that its summary does not replace current rules or manuals (Visa; Mastercard). These are network-specific references. The merchant should follow the deadline, reason, and evidence instructions supplied by its own acquirer or processor.

Give the transaction one record spine

At order creation, assign an internal order ID and preserve the processor transaction reference. Link later authorization, capture, refund, shipment, subscription, and dispute references without replacing the originals. Store timestamps with time zone, currency, amount, acceptance channel, descriptor, customer-facing item description, and the policy version shown at checkout.

The record should distinguish an approved authorization from capture and fulfillment. If the business uses delayed capture, log who or what triggered capture and which fulfillment milestone supported it. The authorization, capture, void, and refund guide maps those states; refund versus dispute explains why a merchant credit and an issuer dispute are separate processes.

Preserve evidence by fulfillment type

For shipped goods, retain the order confirmation, exact ship-to details as permitted by policy, carrier, tracking identifier, shipment date, delivery status, and exception history. A delivery scan alone may not answer identity or product-description allegations, so preserve item and customer-communication records too.

For pickup, retain the pickup method, date, location, order identifier, and the business’s ordinary verification record. Do not start collecting excessive identity data solely “for chargebacks.” For services, record the scope accepted, appointment or access dates, work product, completion acknowledgement, and any attempt to resolve a complaint. For digital goods, preserve entitlement creation, material access or download events, device or session signals already lawfully collected, and support history. Explain what each log proves; do not imply that an IP address proves a person’s identity.

For subscriptions, keep the consent record, terms delivered at enrollment, price and frequency, notices of changes, invoices, cancellation route, cancellation request, and service-end date. A clean cancellation log often matters as much as the initial sale.

Keep policy evidence reproducible

Save the actual version of the return, cancellation, delivery, and trial terms presented for the transaction. A link to today’s policy does not prove what a buyer saw months earlier. Record the display location and acceptance event without inventing consent. If checkout did not require an affirmative action, say so.

Customer communications should be chronological, complete, and minimally redacted for relevance. Include the merchant’s attempts to solve the stated problem, not a character argument about the customer. If a refund or credit already occurred, provide its amount, date, and processor reference so the reviewer can distinguish a pending credit from no credit.

Respond to the reason, then stop

When a notice arrives, record its received time and deadline. Identify the reason and amount, check for an existing refund, and decide whether to accept or contest. Build a one-page chronology: order, authorization, fulfillment, customer contact, cancellation, and credit. Attach the smallest set of readable records that supports that chronology. Label mismatched names, split shipments, partial refunds, or changed order values rather than hoping the reviewer will infer them.

Run a monthly quality review: missing policy versions, unlinked shipment IDs, captures before the business’s fulfillment trigger, and refunds without original transaction references. The best dispute file is a by-product of disciplined fulfillment. It is not a retroactive story.

Sources

• Visa, Dispute Management Guidelines for Visa Merchants — network-specific
• Mastercard, Chargebacks Made Simple Guide — network-specific