The evidence package

When you generate an evidence package, Rebuttal builds a response matched to the dispute's reason code — a "product not received" case leads with delivery proof; a "fraudulent" case leads with payment verification and customer history. Every section carries a provenance line showing exactly when that evidence was captured.

What's inside, and why banks care:

• Payment verification — AVS and CVV results from the moment of payment. Shows the card's billing address and security code checked out.
• Customer and session — the checkout IP, device, and email, plus how many prior undisputed orders this customer has with you. A repeat customer disputing a familiar charge is the classic "friendly fraud" pattern, and this is the rebuttal to it.
• Order and fulfillment — line items, totals including shipping, and carrier tracking with delivery status, timestamped as it updated.
• As listed at time of purchase — the product title, description, price, and images exactly as the customer saw them on the day of the sale. If the listing changed later, this proves what was promised.
• Store policies in effect at time of purchase — your refund policy and terms of service as they stood that day. (Rebuttal words this carefully: it proves what was in effect, not what the customer clicked — that's the honest claim a bank can rely on.)