Somewhere in a customer's inbox there is an invoice with three lines on it. One says "Unused time on Basic." One says "Remaining time on Pro." One is a total that matches neither plan's price. The customer upgraded on purpose, maybe even happily, and now they're staring at a number they can't explain. They don't think "I should email support." They think "something's wrong," and the fastest way to make something wrong go away is the button in their banking app.
That is how a proration chargeback is born. It is rarely a story about fraud or a bad product. It's a story about arithmetic that was correct and still felt like a trick.
Why a correct charge can feel like an overcharge
Proration is fair in principle. When someone changes plans mid-cycle, you credit the time they didn't use on the old plan and charge for the time they'll use on the new one. Stripe's billing system does exactly this and shows each piece as its own line item on the invoice.
The trouble is what that does to a human brain. People anchor on the sticker price. If the Pro plan is advertised at one number and the card statement shows a different one, the gap registers as an error, even when the gap is the exact result of the math. Behavioral science has a name for the general pattern: anchoring. The first number we see sets the reference point, and everything afterward gets judged against it, not against what the situation actually calls for.
A second effect makes it worse. People are poor at reasoning about partial periods. "Eleven days of a thirty-day month at a different rate, minus a credit for nineteen days at the old rate" is not a calculation anyone does in their head at a kitchen table. So they don't check it. They distrust it.
And if the customer upgraded days or weeks ago, the memory of the decision has faded while the confusing statement line is fresh. The dispute is filed against the line, not against the choice they made.
What the reviewer is actually asking
The person or system reading your response is not auditing your pricing. They are asking a narrower question: did the cardholder authorize this charge, and is the amount the one they agreed to?
That second half is where proration disputes live. The cardholder will say, in effect, "I was charged an amount I did not agree to." Your job is not to argue that the math is right. It's to show two things:
- The customer knowingly chose to change plans.
- The amount followed mechanically from that choice, and they could see how.
Notice what this does to your evidence. A screenshot of your pricing page is not the centerpiece. The centerpiece is the sequence: the action the customer took, what they were shown at that moment, and the invoice that resulted.
The evidence that tells the story
Think of it as three exhibits, ordered the way a reader would need them.
Exhibit one: the decision. Whatever record shows the customer initiated the change. That might be an event log entry showing the plan change from their account, a timestamp, the logged-in user, and the session details. If they upgraded through a confirmation screen, capture it. If they emailed asking to upgrade, that email is gold, because it is the customer's own words requesting the change.
Exhibit two: what they were shown. If your upgrade flow displays a prorated amount before confirming, a screenshot of that screen is the strongest single piece you can submit. It shows disclosure at the moment of consent. If your flow doesn't display it, say so plainly and lean on exhibit three. Don't pretend a preview existed.
Exhibit three: the invoice, annotated. Submit the actual Stripe invoice with its line items, then add a short plain-language walkthrough beside it. Not a wall of text. A few lines that a tired reviewer can follow:
- The old plan's price and the date of the change.
- The credit for the unused portion of the old plan.
- The charge for the remaining portion of the new plan.
- The resulting total, and how it equals the sum of those.
Use a worked example if it helps, with round, clearly illustrative numbers. If the old plan was $30 a month, the new one is $60, and the change happened exactly halfway through the cycle, the credit is $15 and the charge is $30, so the net amount due is $15. A reviewer who can verify your arithmetic in ten seconds trusts the rest of your packet more. Just make sure your example uses your real figures from the real invoice when you submit, not a generic one.
The follow-through that quietly strengthens your case
Two supporting items are easy to overlook.
First, any email Stripe or your own system sent after the upgrade. A receipt or confirmation that went to the customer's address shows they had the breakdown in hand. It doesn't prove they read it, but it shows you weren't hiding anything.
Second, evidence of continued use of the upgraded plan. If they used features exclusive to the higher tier after the change, that's behavioral confirmation that they got what they paid for, and it's hard to square with "I never wanted this." Usage logs, feature access records, or activity timestamps all work. Keep it to the relevant window, not a data dump.
A caution, though. More is not better here. A reviewer skimming a packet needs the decision, the disclosure, and the math, in that order. Everything else is clutter that can bury the thing that wins.
When the customer has a point
Sometimes the dispute is partly your fault, and it's worth honestly checking before you fight. Look for these:
- The upgrade flow showed a price that didn't match what was charged, such as a monthly figure with no note that the first charge would be adjusted.
- A plan was changed twice in a short window, producing stacked prorations that really are confusing.
- The customer was moved to a new plan by you, such as in a migration, without a clear message.
If any of those is true, the strongest move may be a refund of the confusing portion and a fix to the flow. Declining to fight a dispute you'd likely lose isn't failure. It's triage, and it means the effort you save goes to the disputes you can win.
Your next moves
- Pull one recent upgrade invoice today and read it as if you were a customer. Could you explain every line to a friend in under a minute? If not, that's your future dispute.
- Check your upgrade confirmation screen. Does it show the prorated amount due before the customer clicks? If not, add a single sentence such as "You'll be charged the difference for the rest of this billing period today."
- Write a three-line invoice walkthrough template in your notes app: old plan and change date, credit, new charge, total. Keep it ready so you can paste real numbers into it in two minutes.
- Turn on or verify the customer receipt emails in your Stripe settings, so every plan change leaves a message in the customer's inbox.
- Save a screenshot of your upgrade flow with today's date in the filename, so you can prove what customers saw if you change the design later.
Where the deadline matters most
Proration disputes tend to feel small, a difference of a few dozen dollars, which is exactly why they get ignored until the response window is nearly gone. The evidence for these cases is also unusually perishable: the screen design you shipped last month may have changed, and the logs that show the customer's action may roll off. The best time to assemble this packet is the day the dispute arrives, while the memory of how your own flow works is still fresh.
This is the kind of case Argeback was built around. It pulls the dispute in from Stripe, drafts a response from the invoice and account records, and lets you review and file from your phone before the seven-day deadline, so a dispute about forty dollars of prorated math doesn't quietly default to a loss. If that sounds useful, you can see how it works at https://argeback.lumenlabs.works, and if not, the checklist above works fine on its own.