A woman buys a $29 notebook at 11:40 at night. The page thanks her, and a bright offer appears: Add the matching pen set for just $12. One click. Her thumb is already moving toward the next thing. She taps, the screen flickers, and she closes the tab.

Three days later her statement shows two charges. She remembers buying one thing. In her mind the second charge is not an upsell she accepted. It is money that left her account without her permission.

So she disputes it. And here is the uncomfortable part: she may be telling the truth about her memory.

Why a real customer can forget a real purchase

Behavioral science has a name for part of this: inattentional blindness. People fail to notice things that are in plain view when their attention is on something else. After a purchase, attention is already spent. The decision feels finished, and the offer lands in a mind that has moved on.

Add the default effect and habituation. We tap "confirm" and "continue" dozens of times a day. Buttons that look like the previous step get pressed without being read. A fast, frictionless tap leaves a faint memory trace, because the whole design goal was to make it feel like nothing.

This is the trap of the one-click upsell. The very smoothness that lifts your conversion rate also weakens the customer's recollection that they agreed. When the dispute arrives, you are fighting a memory that was never properly formed.

The customer isn't necessarily lying, and you aren't necessarily at fault. But the bank will ask one question: can the merchant show this cardholder knowingly authorized this specific charge?

What the reviewer is actually weighing

For a second charge, the reviewer typically sees something that looks like a duplicate or an unrecognized transaction. Two charges, minutes apart, same card. The customer says they bought once.

Your job is to turn a vague pattern into a clear sequence of consented steps. The question isn't "did we charge them?" You clearly did. It is "was the second charge a separate, disclosed, accepted offer?"

Three things make that case:

  1. The offer was visible and priced. The reviewer needs to see the exact amount, the product name, and the words that told the customer this was an additional purchase.
  2. The customer took a deliberate action. A button labeled with the price and the action ("Yes, add the pen set for $12") reads very differently from a vague "Continue."
  3. The charge matches what was shown. The amount, currency, and product on the statement line up with the offer, with no surprises.

If the page said "Complete your order" and the button secretly added a charge, you have a consent problem no evidence can fix. If the page said what it was and the customer pressed the button, you have a case.

Why your own page design decides the dispute

This is one of the few chargeback types where the outcome is largely decided before the sale. Consider the difference between two upsell screens.

The first says: "Wait! Your order isn't complete. Click to finish." The button reads "Complete Order." A reviewer will read that as ambiguous at best, and as deceptive at worst.

The second says: "Add the matching pen set for $12.00 (charged to the card ending 4242). " There are two clear buttons: "Yes, add for $12.00" and "No thanks." Both are the same size, and declining is as easy as accepting.

The second page is better ethics and better evidence at once. In the US, the principle that online sellers need clear disclosure and the customer's express informed consent before charging a saved payment method is well established in consumer-protection law for negative-option offers. Even outside those rules, card networks and issuers care about the same thing: evidence of informed agreement.

A design that makes the customer's consent obvious to a stranger reading a screenshot is a design that wins disputes.

Build the proof around the click

You can't reconstruct what the customer was thinking, but you can document what the system recorded. Gather these:

  • A screenshot of the upsell screen as it appeared, with the price, product, and both buttons visible. Capture the version live at the time of the sale. If you've redesigned since, say so and show the dated version.
  • The server-side event log showing the accept click, with a timestamp, tied to the same session and customer as the original order.
  • The order confirmation email, which should list both items and both amounts. This matters because it gave the customer a second chance to notice the charge before disputing.
  • The charge details showing the second payment was created from the same session, with the same card, shortly after the first.
  • Any fulfillment proof for the add-on: shipping, download, or access records.

Then tell the story in order. Keep it plain: the customer placed an order at 11:40 p.m., was shown a separately priced offer, chose to accept it at 11:41, and received a confirmation listing both items. Link each sentence to an attachment.

A tidy chronology beats volume here. A reviewer who can follow the sequence in thirty seconds is more likely to side with you than one who has to dig through twelve loosely related files.

Be honest about when to concede

Some upsell disputes aren't worth fighting. If your accept button was vague, if the offer was pre-checked, if you can't produce a log of the click, or if the add-on was never delivered, the evidence won't carry you. Fighting a dispute you can't support costs time, and a weak submission doesn't teach you anything the loss wouldn't.

Use those losses as a design review instead. A pattern of second-charge disputes is a signal that your upsell is too slippery, and that the problem is upstream of any rebuttal.

Your next moves

  • Open your own checkout in a private window and buy something. Walk through the upsell as a tired stranger would. If you can't tell it's an additional charge at a glance, neither can a bank reviewer.
  • Put the price on the accept button. Change "Add to order" to "Yes, add for $12.00," and make the decline option just as visible.
  • Log the accept event. Confirm your system stores a timestamp, session ID, and customer ID for the upsell click, separate from the original purchase.
  • Capture and date your upsell screen. Take a screenshot today, save it with the date, and repeat it whenever the page changes. Disputes arrive weeks later, and you will want the version that was live.
  • Check your confirmation email. Make sure it itemizes the add-on and its price on its own line, not folded into a single total.

The tie-in

The hard part of an upsell dispute isn't the argument, it's assembling the sequence before a seven-day clock runs out: the screenshot, the click log, the email, the charge, laid out so a reviewer can follow them. Argeback pulls your disputes in, drafts the evidence-backed response, and files it on time from your phone, so a tired Tuesday doesn't turn into a forfeited $12 win. If you'd like that handled, you can take a look at Argeback.