The number on the statement is $127.40. The number in her head is $99. She does not remember the shipping line, the sales tax, or the gift-wrap box she ticked at eleven at night with the dog asleep on her feet. What she remembers is the big green price on the product page, and the feeling, right now, that someone moved it after she stopped watching. She is not angry about twenty-eight dollars. She is angry about being handled. So she opens her banking app, taps the charge, and chooses the option that says she was billed a different amount than she agreed to. And that, to the people who will decide the case, is a remarkably specific accusation.

The dispute that admits almost everything

Most chargebacks are vague. Fraudulent. Not received. Unrecognized. The incorrect-amount dispute is different because it concedes nearly the whole story: yes, I bought from this merchant; yes, I authorized a charge; no, I don't want the order unwound. The only thing in question is whether the figure you took matches the figure the customer said yes to.

Under Visa's rules this lands as reason code 12.5, Incorrect Amount, in the processing-errors family. Mastercard folds it into 4834, Point-of-Interaction Error. American Express calls it P05, Incorrect Charge Amount. Stripe's dashboard may label it more loosely, but the question the issuing bank's reviewer is asking is narrow: can the merchant show the cardholder agreed to this exact total before the money moved?

That narrowness is good news and bad news. Good, because you don't have to prove the product was wonderful or that the customer loved it. Bad, because "they agreed" is a claim about one moment in time, and most merchants never captured that moment in a form a stranger can read.

Why the smaller number is the one that sticks

The customer is rarely lying. She is remembering, and memory for prices is not a recording. It is a reconstruction built around whatever number arrived first.

Psychologists call that first number an anchor. In the classic experiments by Amos Tversky and Daniel Kahneman, people's estimates drifted toward an arbitrary number they had just seen, even when they knew it was arbitrary. A product page does something stronger than that. It presents its number in the largest type on the screen, repeats it in the cart, and lets everything that follows arrive in smaller grey text. The anchor is not incidental. It is the design.

There is a more specific finding that should make every merchant with a shipping line uncomfortable. Research on what marketers call partitioned pricing, led by Vicki Morwitz and colleagues in the late 1990s, found that when a base price and surcharges are shown separately, people tend to recall a lower total than when they are shown a single all-in figure. The surcharges do not disappear from the page. They disappear from the memory. Your customer saw the tax. She also, in a meaningful sense, did not.

Then time does the rest. The purchase happened at the moment of wanting. The statement arrives weeks later as a single bare line: a billing descriptor and a total, with no line items to explain the gap. Faced with a number that doesn't match the one she remembers, the mind doesn't conclude "I forgot the shipping." It concludes "they changed it." The second story has a villain, and stories with villains are easier to believe.

A few situations make this worse. Tips are the obvious one: the customer sees a pending authorization for the meal and then a larger posted amount with the gratuity folded in, and the difference looks like an unauthorized bump. Post-sale adjustments do the same thing, whether it's a backorder upgrade, an extra night, or a weight-based shipping correction. And cross-border sales add a wrinkle that isn't even yours: a price shown in euros, settled in dollars, with a conversion fee the customer's own bank added. Visa has a separate code for currency mismatches, 12.3, but customers don't file by code. They file by feeling.

What the reviewer is actually looking for

The person deciding your dispute is not reading for narrative. They are scanning for one artifact: evidence that the customer saw this total, in this currency, and consented to it before the charge was made. Everything else in your submission is supporting cast.

The strongest form of that artifact is a line-item record that sums, to the cent, to the disputed amount, timestamped before the payment. Your order confirmation email is usually the best candidate, if it actually itemizes. A screenshot of the checkout review step, with the exact total sitting above the pay button, is the next best. For tips, it's the signed receipt or the digital tip-selection record. For adjustments, it's the message or screen where the customer approved the new figure, not the one where you announced it.

Notice what this list excludes. A screenshot of the product page showing the headline price loses the dispute, because it proves the customer's anchor rather than your total. A terms-of-service clause that says taxes and shipping "may apply" is not consent to any particular number. And a partial refund of the difference, offered once the dispute is open, is usually impossible in Stripe and never closes the case on its own. The reviewer wants the moment of agreement, not your remorse about it.

One more detail that quietly decides these: the amount on the customer's statement must match the amount in your evidence. If you captured the order in two pieces, or adjusted after authorization without a record of consent to the final figure, the numbers won't reconcile, and the reviewer will side with the side whose number is simplest.

Your next moves

  • Put the full total above the pay button, and put it on the button too. A button that reads "Pay $127.40" is consent in the plainest form a reviewer can see. Stripe Checkout does this by default; custom forms often don't. Open yours right now and look.
  • Make your confirmation email a true receipt. Every line item, the tax, the shipping, and a total that equals the Stripe charge exactly, sent within a minute of payment. This email is your primary exhibit in every incorrect-amount dispute you will ever face.
  • Capture consent for any amount that changes after the first screen. Tips, upgrades, corrected shipping, extended stays: record the customer choosing the new total, not just receiving notice of it. A tip-selection screen or a reply saying "yes, go ahead" is enough. Silence is not.
  • If you sell across borders, label the currency on every price and add one sentence at checkout noting the customer's bank may apply a conversion fee. Better still, price in the customer's currency so the statement matches what they saw.
  • Audit your last five orders today. Compare the confirmation email total to the Stripe charge, cent for cent. If any pair disagrees, find out why before a customer finds out for you.

The seven days after the number arrives

The hard part of an incorrect-amount dispute is not the argument. It is finding the one timestamped record that shows the agreed total, assembling it in the shape a reviewer expects, and filing it before the window closes, usually while you're busy running the business that generated the order in the first place. Argeback was built for exactly that stretch. It pulls your Stripe disputes in as they arrive, drafts a response around the evidence that actually answers the reason code, and lets you review and submit it from your phone before the deadline passes. If you'd rather spend those seven days selling than searching, you can see how it works at argeback.lumenlabs.works.