A Claude Max subscriber says they woke up to 17 separate charges in one day, despite having usage credits explicitly turned off. It's not the first time Anthropic's billing has produced a documented incident like this — and a separate, unrelated fraud case just made UK national news the same week.
A widely upvoted r/claude thread describes a user finding roughly a dozen-and-a-half authorized charges in the €40-50 range on their card, all dated the same day, despite — they say — having usage credits disabled and a spending cap set well below that total. Anthropic's support chat (an AI agent, not a human) reportedly told them it couldn't identify the root cause and that "we're unable to issue compensation for degraded service or technical/billing errors of this nature." Multiple replies in the same thread described a similar pattern hitting their own accounts within roughly the same 12-24 hour window.
This isn't the first billing complaint of its kind. This post lays out what's actually been confirmed — a prior acknowledged billing bug, and a separate, unrelated fraud case reported by The Guardian — against what's still just user reporting, and what's worth checking on your own account regardless of which explanation applies.
TL;DR
| Question | What's known |
|---|---|
| What's newly being reported? | Users describe usage credits switching to "on"/unlimited unexpectedly, followed by a burst of separate ~€40-50 charges |
| Confirmed cause for this specific wave? | No — not publicly, by Anthropic or independently, as of this writing |
| Has something like this happened before? | Yes — Anthropic acknowledged a July 17, 2026 config error that misrouted usage billing for roughly 30 minutes |
| Is this the same as the Metro Bank fraud story? | No — that's stolen-card fraud buying Claude credits, a different mechanism, reported separately by The Guardian |
| What did Anthropic support reportedly say? | An AI agent said it couldn't identify the cause and that billing-error compensation isn't issued |
| Most-recommended fix path | Bank chargeback, not waiting on support — several users report this working |
The confirmed prior incident: July 17, 2026
Before this week's reports, Anthropic had already acknowledged one specific billing bug. According to a bug-tracker thread on the anthropics/claude-code GitHub repository, Anthropic confirmed a configuration error on July 17, 2026, lasting roughly 18:16-18:47 UTC, that caused usage to be routed to billed usage credits instead of counting against a plan's included weekly usage. Users reported unexpected charge notifications during that window, with usage credits shown reaching over 100% and individual overages around $50 — figures broadly consistent with the shape of what's being described in this week's newer reports, even though the two incidents aren't confirmed to share a cause.
The compensation detail matters here: reported resolution for the July 17 incident was account credit, not a refund to the original payment method — credit described as unusable by anyone who doesn't separately exceed their plan limits, with an expiration date over a year out. That's the same category of complaint running through this week's thread: users aren't just asking for the charges to be explained, they're specifically frustrated that the offered remedy (when offered at all) doesn't put money back on the card that was charged.
A separate story: stolen cards buying Claude credits
The same week this Reddit thread went viral, The Guardian reported on an unrelated but adjacent problem: a Metro Bank customer, Zoli Rutter, lost £14,244 after fraudsters used stolen card details to buy Claude platform credits through what Anthropic described to the Guardian as a coordinated fraud operation. The first flagged transaction was £90.90 on June 19; when Metro Bank texted Rutter to confirm it, he said no — but the bank blocked only that single transaction rather than freezing the card, and further charges between £90 and £200 kept clearing for another full day before the card was finally frozen. Anthropic told the Guardian it found no evidence the stolen card details originated from its own systems, banned the account responsible for the purchases, and refunded Rutter directly. The Guardian also noted an earlier, similar case from May involving a US Claude user whose payment details were used to buy gift cards.
This is worth separating clearly from the Reddit thread's pattern. The Rutter case is fraudsters using someone else's stolen card to buy Claude credits for themselves — a payment-fraud problem that could target any subscription checkout, not specific to a bug in the victim's own Claude account settings. The newer Reddit reports describe something structurally different: charges apparently hitting the reporting user's own account, with their own usage-credit toggle apparently changing state. Both are real, documented problems with money moving unexpectedly around Claude billing — but they're very likely not the same mechanism, and conflating them would overstate what either report actually shows.
What's still genuinely unconfirmed
Whether this week's wave of reports traces back to the same root cause as July 17, is a new and separate bug, or reflects individual account/API-key compromise on some or all of the affected accounts, isn't publicly established. The Reddit thread itself splits on this exact question: the original poster leaned toward compromise after the fact (rotating passwords, freezing their card, taking their PC offline), while other commenters described far smaller charges ($3-4) with the same symptom — usage credits appearing re-enabled despite being explicitly turned off — and no evidence of compromise on their end. One reply specifically flagged that claiming a promotional credit ("free Fable credit") had turned their usage credits on as a side effect, which, if accurate and widespread, would point toward an unintended settings interaction rather than any external actor.
Do these explanations actually contradict each other? Not necessarily. It's entirely possible some of the reported accounts were genuinely compromised while others hit an unrelated settings issue that happens to produce a similar-looking symptom — a dozen-plus charges on one account and a $3 charge on another aren't obviously the same event just because both involve a mis-set usage-credits toggle.
What's worth checking on your own account
Regardless of which explanation applies to any specific case:
- Usage credits setting — confirm it currently matches what you last configured, not what you assume it still is.
- Active API keys — revoke anything you don't immediately recognize; a leaked key can bypass subscription-level usage limits.
- Recent account activity — session/login history, if your account provides it, for anything unfamiliar.
- Recent promotional credit claims — per the report above, claiming certain promotions has been described as an unexpected trigger for re-enabling usage credits.
- Payment method exposure — whether your card on file has a hard spending cap you control, independent of what any single service's settings claim to enforce.
None of these take more than a few minutes, and doing them costs nothing regardless of whether anything is actually wrong on your specific account.
What people are asking
Does the confirmed July 17 incident mean Anthropic has a systemic billing reliability problem? One acknowledged 30-minute config error, a GitHub-tracker thread of individual billing disputes, and a separate card-fraud case reported by the Guardian are three data points, not a comprehensive audit — they establish that billing incidents have happened and have been publicly documented at least twice this year, without establishing how common they are relative to Anthropic's total user base.
If Anthropic says it can't identify a specific charge's root cause, does that mean it's being evasive? Not necessarily — "a first-line AI support agent doesn't have visibility into why this specific charge occurred" is a different claim than "no one at the company can determine this." Several threads describe the standard path from there as escalation to a human agent with deeper account access, which takes longer but is a different investigative depth than the chat response quoted.
Is a chargeback the right move if this happens to me? Multiple commenters describe successful chargebacks after documenting a support interaction where compensation was explicitly declined — a decision between you and your bank, but documenting the support conversation before disputing appears to be the commonly recommended first step across these reports.
The takeaway
Two things are independently confirmed here, and one is still just user reporting: Anthropic has acknowledged at least one prior billing configuration error (July 17) that misrouted usage charges, and a separate, unrelated card-fraud pattern targeting Claude credit purchases made UK national news the same week this new thread went viral. What's not yet confirmed is whether this week's specific wave of reports shares a cause with either of those, or is its own distinct issue. Until Anthropic addresses it directly, the useful move isn't picking a side — it's checking your own usage credits setting and active API keys today, and documenting anything unusual before you need to dispute it.
Related on explainx.ai:
- How to Use Claude Cowork Safely: Official Security Guide
- Claude in Chrome: Features, Access & Safety
- Claude Programmatic Usage Credits, Explained
- How to Use Claude Connectors and MCP Servers
Primary sources: Reddit — r/claude billing thread · GitHub — anthropics/claude-code billing incident thread · The Guardian — Metro Bank customer fights for refund after AI fraud
This post summarizes user reports and press coverage as of August 5, 2026. Anthropic has not published a statement confirming a cause for the newer wave of reports; if you're experiencing unexpected charges, contact Anthropic support directly and consider your bank's dispute process for your specific situation.