Somewhere right now, a person is staring at a charge on their statement and sincerely believing they never agreed to it. They aren't lying. They are remembering, and memory is a much less reliable witness than most of us assume.

That is the quiet problem under a lot of disputes. The customer's account of what the checkout page said and your account of it are both sincere, and only one of them is backed by a document. If you can't produce that document, the reviewer is left weighing one confident memory against your say-so.

Memory is a reconstruction, not a recording

Psychologists have argued for a century that remembering is an act of rebuilding. Frederic Bartlett's work in the 1930s showed that people retelling a story gradually reshape it toward what makes sense to them. Elizabeth Loftus's later research on the misinformation effect showed that details introduced after an event can slip into the memory of the event itself.

Apply that to a purchase. A customer clicks "Pay" at 11 p.m., half-reading. Three weeks later they see an unfamiliar line on a statement. The brain fills the gap with what feels plausible: I would never have signed up for something recurring. There was no mention of a fee. I didn't see any terms.

Source monitoring is a related idea, from Marcia Johnson's research. We are often better at remembering that we know something than at remembering where we learned it. A customer may truly recall "nobody told me it renews" when the renewal notice was right above the button.

This is why "our terms were on the site" persuades no one. The reviewer needs to see what the customer's eyes were looking at when they committed.

The trap: your checkout page is a moving target

Here is what makes this hard. You are probably improving your checkout all the time. You tweak the button copy, move the cancellation language, add a line about renewals, or swap a plan name.

That is good product work and terrible evidence hygiene. When a dispute arrives, you open your live checkout page, and it no longer matches the page the customer saw. A screenshot taken today proves what your page says today. A careful reviewer, or simply a skeptical one, may discount it.

The disputes that reach you are also old by definition. Customers can dispute charges weeks or months after the fact, so the page in question may be several versions behind.

A checkout screenshot only works as evidence if it is tied to a specific moment.

What a convincing checkout exhibit contains

Think of it as answering four questions a reviewer will silently ask.

1. Is this really the page they saw? Show the URL, the date, and ideally the plan or product they purchased. A capture with a visible address bar and timestamp is far stronger than a cropped image floating without context.

2. Was the key term visible without effort? If the dispute is about recurring billing, a trial that converts, or a nonrefundable fee, the relevant language must be legible in the capture. Highlight it with a simple box or arrow and leave the rest of the page intact so nobody thinks you cropped out something inconvenient.

3. Did the customer have to act to proceed? A checkbox the customer ticked, or a button labeled with the commitment ("Start subscription, $29/month after trial"), is more persuasive than text sitting passively in a footer. Show the interaction, not just the words.

4. Can you connect this page to this customer? This is where most exhibits fall short. A generic screenshot proves your page existed. A record showing that this customer, with this email, at this timestamp, completed the flow ties the page to the person. Pair the screenshot with your order record, confirmation email, or Stripe payment details, so the story is one coherent chain.

Stripe's dispute evidence form has places for this kind of material, including text fields where you can describe how a policy was disclosed to the customer. Use them to explain the screenshot in two or three plain sentences, such as: "This is the checkout page as shown on the date of purchase. The renewal terms appear directly above the Pay button." The reviewer shouldn't have to infer what you want them to notice.

Version history: the habit that makes this possible

You can't screenshot the past. You can only keep the past as it happens. A few approaches work, in rising order of effort.

  • Capture on change. Whenever you edit checkout copy, terms, or pricing language, take a dated full-page screenshot before and after. It takes two minutes and builds a library.
  • Keep a change log. One line per edit: date, what changed, why. If a dispute lands, you can say with confidence which version applied on the purchase date.
  • Store the terms the customer accepted. If your system records which version of the terms or policy was accepted at checkout, that record is worth more than any screenshot.
  • Use your own version control. If your checkout lives in a code repository, your commit history is already a dated record of what shipped. Note the relevant commit or deploy date in your evidence.

None of this requires special software. It requires deciding that checkout copy is a document worth preserving.

What this evidence can't do

A screenshot is persuasive, not magic. If the terms were buried in grey text under a wall of other content, a reviewer may decide a reasonable customer wouldn't have noticed them. If your page was different on the purchase date than what you show, the exhibit can backfire. And if the underlying dispute is about something else, like a product that never arrived or a duplicate charge, a pristine checkout page doesn't address it.

It also won't help with an honest mistake on your side. If your page was genuinely unclear, the useful move is to fix the page, not to argue the old one was fine.

Be accurate about what the exhibit shows. Overclaiming costs you credibility on everything else in the file.

Your next moves

  • Capture your checkout today. Take full-page screenshots of every step of your purchase flow, from product page through confirmation, with the URL and date visible. Save them in a folder named with the date.
  • Mark the commitment language. For each step, note where the price, renewal terms, trial length, and refund or cancellation language appear. If any are hard to find, treat that as a bug and fix it.
  • Start a one-line change log. Open a note or spreadsheet. Every time you edit checkout copy or terms, add the date and what changed. Backfill what you remember now.
  • Check what your system records at purchase. Confirm that you store the timestamp, email, plan, and (if possible) the version of terms accepted for each order. If something is missing, add it going forward.
  • Pull one open dispute and test the chain. Take a recent dispute and see whether you can connect the matching checkout version to that specific customer's order in under ten minutes. Wherever you get stuck is your gap.

Where Argeback fits

The hardest part of a dispute is rarely the argument. It's assembling the right pieces, in the right order, before a seven-day clock runs out, often while you're away from your desk. Argeback pulls your dispute in, drafts an evidence-backed response from your records, and files it from your phone, so the exhibits you've kept are ready to be used. If you'd like to see how that works, you can look at Argeback whenever it's useful.