Nobody remembers signing up for the price you are charging them now. They remember the price they signed up at. Every renewal since the change, their card has quietly paid a number that stopped matching the one in their head, and the first time they look closely, the gap does not read as a bill. It reads as being taken advantage of. That is the raw material of a subscription price increase chargeback: not greed, and usually not dishonesty, but the particular sting of learning that something you trusted changed while you weren't looking.

The merchant, meanwhile, feels something equally real. You raised prices because costs rose, because the product got better, because the old number was never sustainable. You sent an email. You did the responsible thing, and the reward is a dispute, a fee, and a stranger at a bank deciding whether your business was honest. Both sides feel wronged. Only one of them has the evidence to settle it, and it is you, if you kept it.

This is not an 'incorrect amount' dispute

It helps to be precise about what the customer is claiming. They are not saying you made a math error or charged a figure different from the receipt. They are saying the price they agreed to was the old one, and the new one was never part of the deal. Depending on the bank, that lands in Stripe as an unrecognized charge, a cancelled subscription, or a general complaint. The reason code almost never says 'price increase' anywhere.

That framing changes what you have to prove. A dispute over a wrong amount is won by showing the receipt matches the charge. A dispute over a changed amount is won by showing three things: that the original agreement allowed the price to change, that the customer was told before the first charge at the new rate, and that they had a real way to leave before it hit. Miss any of the three and a reasonable reviewer can side with the cardholder without being wrong.

Why a fair price change still feels like a betrayal

In 1986, Daniel Kahneman, Jack Knetsch, and Richard Thaler published a study on what people consider fair in pricing, and one scenario from it became famous. A hardware store raises the price of snow shovels the morning after a blizzard. A large majority of respondents called that unfair, even though it is textbook supply and demand. The researchers named the rule underneath the reaction 'dual entitlement': customers believe they are entitled to their reference price, and firms are entitled to their reference profit. An increase that protects a firm's margin against rising costs is judged acceptable. An increase that simply takes more from a customer who is already committed is judged as a violation.

Your customer has a reference price, and it is the number on the day they entered their card. Prospect theory supplies the second half of the mechanism: outcomes are evaluated against a reference point, and losses relative to that point hurt more than equivalent gains feel good. A ten dollar increase is not experienced as paying forty instead of thirty. It is experienced as losing ten dollars a month, and losses demand an explanation.

This is why the notice email most merchants send fails even when it is sent. 'We're updating our pricing' explains nothing. It announces a loss and offers no entitlement story. A notice that says what changed, why it changed, when it takes effect, and how to leave does something different. It gives the customer a reason to file the increase under 'fair' instead of under 'taken.' Customers who have filed it under 'fair' do not call their bank.

What the reviewer is actually deciding

The person reading your response works for the issuing bank, has minutes, and is not deciding whether your price is reasonable. They are deciding whether the cardholder could reasonably have known this charge was coming at this amount. Every exhibit should answer that one question.

The card networks' recurring-billing rules give you the frame. Merchants running subscriptions are expected to disclose the terms clearly at enrollment and to notify cardholders in advance when the amount or timing of a recurring charge changes. A notice that goes out the same day as the charge is not advance notice. A notice buried in a changelog nobody is emailed is not notice at all. What the reviewer wants is a timestamped message, sent to the address on the account, before the first charge at the new rate, stating the new amount.

Then they want the paper trail that connects the dots. The signup record showing the original price and the terms the customer accepted, including the clause that says prices can change with notice. The invoice history, so the old price, the notice date, and the first new-price invoice appear in sequence. The cancellation path, ideally a screenshot of the self-serve cancel page plus the absence of any cancellation request between the notice and the charge. Login or usage records after the notice, if you have them, because a customer who kept using the service after being told the price carried on with the agreement.

Keep it short. Four or five exhibits, each labeled with a date and one sentence on what it proves, beat a forty-page export. Reviewers decide fast, and a packet that makes the decision easy is a packet that wins.

The notice that wins the dispute before it exists

Here is the uncomfortable part. Most price increase chargebacks are not lost on evidence day. They are lost on notice day, months earlier, when the email went out with a vague subject line and the new price in the fourth paragraph.

Write the notice as if it will be Exhibit A, because it will. Put the new amount and the effective date in the subject line, so that even a customer who never opens it has been told. State the old price and the new price side by side. Give the actual reason in one honest sentence. Name the date of the first charge at the new rate. Include a cancel link that works without three login screens. Send it at least thirty days out, then send a shorter reminder about a week before the first new-rate charge. Stripe fires an upcoming-invoice event ahead of each renewal; most merchants have never connected it to anything, and it is exactly the hook a reminder should hang on.

One more rule protects you more than any email: never change the price inside a term the customer already paid for. Increases take effect at the next renewal, after the notice, never before. A reviewer who sees an increase applied mid-term does not need to read the rest.

Your next moves

  • Pull every subscription price change you made in the last twelve months from Stripe, and for each one find the notice email you sent. If you cannot find it, you do not have it, and the next dispute will prove that. Draft the missing notice today for your next scheduled increase.
  • Rewrite your price-change email template so the subject line carries the new amount and effective date, the body shows old and new prices side by side, gives one sentence of reason, names the date of the first charge at the new rate, and ends with a one-click cancel link. Archive the sent copy with its headers.
  • Set up a reminder seven days before the first new-rate charge, either by wiring Stripe's upcoming-invoice event to an email or by putting the date in your calendar and sending it by hand.
  • Check your terms of service for a clause stating that prices may change with advance notice by email, and confirm your checkout actually required the customer to accept those terms rather than linking to them in a footer.
  • Build a one-page price-change packet template: signup screenshot with the original price, the notice email, the invoice history, and the cancel page. When the dispute arrives, you assemble instead of excavate.

Where Argeback fits

Everything above works whether or not you ever use a tool, and the notice email is something no software can write in your voice for you. What a tool can do is make sure the packet gets built and filed before the clock runs out, on the week you are busiest, from wherever you happen to be. Argeback pulls your Stripe disputes in, drafts the response around the evidence that answers the reviewer's one question, and files it from your phone before the seven-day deadline. If you have ever lost a dispute you had the evidence to win because you got to it on day eight, that is the gap it was built to close. See how it works at https://argeback.lumenlabs.works.