The Full Story Behind Cursor's $1,799 Overbilling: A Waived Charge That Came Back

A Promised Waiver That Wasn't

A Cursor Ultra user recently published a detailed account on Reddit describing a billing dispute. At the center of it all: a $1,799 overage charge that Cursor officially promised to waive — in writing, on an invoice — only to re-bill the exact same usage the moment the user adjusted their spending limit.

The user was on the Cursor Ultra plan with on-demand billing enabled and a $1,000 hard limit set. Midway through the billing cycle, their usage suddenly showed roughly $2,799 — far exceeding the cap they had configured.

What made the situation notable is that Cursor's own invoice explicitly acknowledged the issue. The refund description on that invoice read:

"Refund because the last hard limit in the month was $1000.00, but the total cost was $2799.15 (likely because of processing delays — the hard limit enforcement is not instant!). We will eat this cost for you, to ensure that your hard limit is upheld."

In plain terms: Cursor admitted the overage happened due to processing delays, and promised to absorb the extra cost to honor the user's hard limit.

The Hidden Asterisk on "We'll Eat This Cost"

The matter could have ended there. The user accepted the explanation, paid the remaining $445 shown on the invoice — bringing their total on-demand payments to exactly $1,000 — and kept all receipts.

But because the hard limit had been reached, the user could no longer access the models. So they raised the limit from $1,000 to $3,000 to continue working. That's when everything went wrong. Within minutes of changing that setting, Cursor generated a new invoice for $1,799.16 and attempted to charge their card.

The user then compared the two invoices line by line and reached a damning conclusion:

• Same models
• Same number of calls
• Same token counts, down to the individual request
• Same event IDs

In other words, this wasn't new usage — it was the previously waived usage being re-billed, minus the $1,000 already paid. As the user pointedly noted: for Cursor's explanation to hold, they would have had to generate $1,799.16 in brand-new usage in roughly one minute, with token counts matching the waived charges down to the last digit. That's simply impossible.

The Gap Between Promise and Reality

The user summed up the experience with a sharp observation: "We will eat this cost for you" apparently came with an invisible asterisk — unless you touch the spending limit slider again within the same billing cycle, at which point the waiver is quietly reversed.

That condition appears nowhere on the invoice, and nowhere in the Terms of Service. The user confirmed they checked.

A Support Experience That Went Nowhere

The user's interactions with Cursor support were equally frustrating. According to their account, the support responses were consistently off-target:

• Support repeatedly pushed back on a claim the user never made — that the new invoice was "double-charging" the $445 they had already paid. The user never said that.
• When the user explicitly clarified they were not requesting a refund, but rather refusing to pay an outstanding invoice for usage that had already been formally waived in writing, support kept citing refund policy in response.

The final answer from support: the charge stands; contact the legal department if you disagree.

The user has since filed a formal dispute and frozen the card charge at the bank level, and says they will continue to post updates.

Practical Warnings for On-Demand Users

Beyond the dispute itself, this incident exposes a technical detail in Cursor's billing system that every user should be aware of. The user noted they found at least one other post describing the exact same situation — overage waived, then re-billed upon raising the limit — suggesting this is likely not an isolated case.

Based on their experience, the user offered several highly actionable recommendations:

Hard Limits Are Not Enforced in Real Time

If you're using on-demand billing with a hard limit set, understand that the limit does not take effect instantly — Cursor's own invoice language confirms this ("the hard limit enforcement is not instant"). This means actual charges can exceed your configured cap due to processing delays.

Save Your Invoices and Raw Usage Data

The user stressed the importance of downloading your invoices and raw usage events from the dashboard. It was this line-by-line comparison that allowed them to prove the two invoices reflected identical usage. In any billing dispute, that raw data is your only reliable evidence.

Don't Adjust Your Spending Limit After Receiving an Overage Credit

This is the most critical lesson from the incident: if you've received an overage credit, do not touch your spending limit settings within the same billing cycle without first getting written confirmation that the credit remains valid — because based on this experience, adjusting the limit may silently void it.

Final Thoughts

This dispute is still ongoing, and the outcome remains to be seen. But the issues it surfaces go beyond one user's account: when a billing system's "promises" lack clear contractual backing, and when automated billing can execute delayed or unexpected reversals, users' right to informed consent and basic trust is undermined.

For developers who rely on AI coding tools for intensive, high-volume work, this is a timely reminder: enjoy the flexibility of pay-as-you-go billing — but keep your receipts, understand the edges of the billing rules, and maintain a healthy skepticism toward any assurance that isn't backed by explicit, written terms.