The invoice was correct to the cent. Every API call, every gigabyte and every seat-hour was metered, summed and multiplied by a rate printed on your pricing page. And the customer still looked at a number four times larger than last month's and felt something drop in their stomach. Eleven days later you get the Stripe notification: dispute opened.
You didn't overcharge anyone. But in a usage-based billing chargeback, being arithmetically right is the least of what you have to prove.
The feeling behind the dispute is bill shock
A flat monthly price is a promise: this is what the relationship costs. A metered price is a different kind of promise: this is what the relationship could cost, depending on things you'll mostly forget about. People are not good at holding that second kind in their heads.
Behavioral economists have studied this for a long time. Lambrecht and Skiera's work on internet-access plans found that many consumers pick flat-rate tariffs even when a pay-per-use plan would have cost them less. Part of the reason is that people value predictability and dislike the sensation of a meter running. Prelec and Loewenstein described the related "pain of paying," the discomfort of watching money leave in direct connection with consumption. Flat rates numb that pain. Usage billing switches it back on, then sends the bill weeks after the consumption happened, when the pain has no obvious cause.
So the customer who disputes your overage is usually not lying. They believe, sincerely, that they agreed to a price, and the invoice doesn't feel like that price. The gap between the number they carried in their head and the number on the statement is the entire dispute.
That tells you what the reviewer needs to see. They aren't deciding whether your math is right. They're deciding whether this customer could reasonably have known.
What a reviewer is actually weighing
A dispute over a metered charge usually comes down to three questions, whatever the label on the dispute reason:
- Was the pricing model disclosed before they paid? Did they see "$0.002 per request above 50,000" or just "Pro plan, $49"?
- Is the usage real and attributable to them? Can you show these calls, jobs or minutes came from their account, not a bug or a leaked key?
- Were they warned? Did anything tell them they were approaching or crossing the line before the bill arrived?
The third question is where most merchants lose. You can have airtight answers to the first two and still look careless if the first notice of an overage was the invoice itself. A reviewer reading for reasonable doubt will ask the same thing the customer did: why didn't anyone tell me?
Build the packet around the customer's own timeline
Resist the urge to lead with your rate card. Lead with their behavior. A strong packet for a metered charge tells a short story in order.
The agreement. Show the pricing page or checkout screen as it appeared when they subscribed, with the metered rate visible. If your page has changed since, use an archived capture or your own dated screenshot, and say so honestly. Add the terms they accepted and the timestamp of acceptance. If the overage rate is only in a footnote, say where it is and show it.
The usage record. Export the usage events behind the invoice: dates, quantities, and the account or API key that generated them. A daily rollup is easier to read than a million raw rows. Put the total next to the invoice line so the reviewer can see the arithmetic closes.
The pattern. This is the quietly powerful part. If the customer's usage climbed steadily over weeks, show it. A chart of daily usage that rises on a clear slope reads very differently from a single unexplained spike. Steady growth suggests deliberate use. A spike might suggest a runaway script or a compromised key, in which case you may want to think harder about whether to fight (more on that below).
The warnings. Include every threshold email, in-app banner, dashboard usage meter or webhook notification, with send dates. Show the product screen where they could see current usage. Even a passive usage dashboard counts: it proves the information was available to them at any moment.
The prior invoices. If they've paid earlier metered invoices, including ones with overages, show them. Past payment of a similar charge without complaint is some of the best evidence you have that they understood the model.
The communication. If they wrote in before disputing, or didn't, say which. Support threads where they discuss their usage or ask about limits show awareness. Silence before a dispute matters too, since a customer who understood the charge to be wrong would usually have asked you first.
When the usage isn't really theirs
One caution. If the spike traces back to a leaked API key, a misconfigured loop, or a bot, the customer may be right that they didn't intend the usage, and a reviewer may agree. Your evidence that the calls came from their credentials is strong against "I never used this," but weak against "someone abused my account." Look at the pattern honestly. If it looks like abuse, a goodwill credit or partial refund often costs less than losing, and keeps a customer who would otherwise leave angry.
Fighting is the right call when the usage is steady, plausible, disclosed and warned about. Conceding, at least partly, is the right call when the evidence shows you let a runaway process burn through someone's budget with no alert.
Your next moves
Do these today, before the next metered invoice goes out:
- Capture your pricing page now. Take a full-page, dated screenshot of the page showing your overage rates, and save it with the checkout flow. Repeat it whenever pricing changes.
- Turn on usage alerts at 50%, 80% and 100% of included quota. Send them by email, and log the send dates. These are your best defense and your best prevention.
- Write a one-paragraph plain-language rate summary and put it on the invoice itself, right under the total: what's included, what the overage rate is, and how many units they used.
- Export one sample usage report for a real account and save the template, so you can produce a daily breakdown in minutes when a dispute lands.
- Add a cap or a confirmation step for enterprise-sized spikes. A spend limit the customer sets themselves is evidence they understood the model, and it prevents the shocking invoice in the first place.
What the dispute is really teaching you
Every bill-shock dispute is a small report on a communication gap. The charge may have been right, but nothing in the customer's week made it feel real until the invoice arrived. The merchants who win these cases, and who rarely face them, are the ones who make the meter visible before it matters.
That's the work Argeback is built around. It pulls the dispute from Stripe, assembles the usage records, invoices and customer history into an evidence-backed response, and files it before the 7-day deadline, all from your phone. A metered dispute has many moving parts, and the deadline doesn't wait for you to find them. If you'd like to see how it handles that, you can look at Argeback whenever it's useful.