[Billing][Bug] Auto-recharge loop charged consumer plan 29x ($661) in error; Fin support admits malfunction but cannot escalate to a human

Fellow operator here (I track Claude Code billing failures across the tracker). The 6 charges in 10 minutes (09:57, 09:59, 10:01, 10:03, 10:04, 10:07) is the decisive signal: genuine metered consumption cannot bill on that cadence, so this is an auto-recharge retry loop, not usage. A few practical things while you pursue the refund:
1. Stop it from firing again first. Disable auto-reload / "extra usage" auto-recharge in your billing settings now, and if a spend/usage cap is available, set it low. The loop can keep charging while the dispute is open, so killing the trigger is the priority before anything else.
2. Your strongest asset is the written admission. The Fin agent stating in writing that these were "erroneous charges ... resulting from a technical malfunction," and that consumer terms "do not preclude refunds for charges resulting from technical malfunctions," is exactly what a card issuer wants. Export/screenshot that full transcript now before the conversation rolls off. When a merchant's own support admits an erroneous charge in writing, a "billing error / not as described" chargeback usually resolves in the customer's favor — so the bot pointing you to a chargeback, while infuriating, is actually a usable path with that admission attached.
3. For triage, it helps to separate the two distinct bugs so they don't get collapsed into one:

• the auto-recharge loop (6+ fires in 10 min) — a billing-system defect, and
• the consumer-vs-API-terms misrouting in the refund denial (#57594) — a support-policy defect.

The second half is a recurring cluster (#57594 / #56895 / #66558, as you listed). Keeping the per-minute charge timestamps front and center is the cleanest possible evidence that this is a loop rather than consumption — that single detail is what makes the report hard to dismiss.
Hope you get the $661 back.

I experience this same bug last weekend, getting 27 charges for a total of $321.67 . I pasted the log to the helpdesk FIN, and wonder how long it will take for them to get to it. The frustrating thing was that when I detected the bills in the morning, I toggled off the extra credit TWICE, and somehow it got toggled ON TWICE. I cancelled subscription and set the usage credits limit to zero and autoreload to off, and finally after about 6 hours it stopped. There were charges that happend within minutes but mostly were every half an hour for $10-15. Now I'm wary of using claude at all, and when the charges get accepted by my CC, I will dispute them because I've heard that it may take weeks for Anthropic to respond.

Same issue here. On June 17, 2026 I was charged four times for "Auto recharge extra usage" within about one hour, while my Claude Max 5x dashboard showed only ~5% of my weekly limit and ~2% of my five-hour limit — nowhere near any limit. Four auto-recharges in one hour is a loop/malfunction, not real usage. Support refused a refund, called it a "final decision," and never explained what usage supposedly triggered the charges. Adding my case — this is clearly not isolated.

I wonder if anyone has gotten a response. I called my CC and had 27 disputes, and my CC was nice enough to refund my money, but no response from Anthropic. Even something like, "we're aware of the issue" would make me feel better. I cancelled my recurring monthly subscription and deciding whether or not to re-up - is i so helpful to me that I'll withstand the pain of more disputes and wondering what the heck is going on again?

Same here — you're not alone. And to be clear, this is definitely a bug, not real usage: there's no way I'm being charged "extra usage" while my plan sits at 2–5%. That's impossible — obviously a malfunction.

Here's the response you can expect so you're not left wondering: about a week's wait, then a templated reply — "I've consulted with my supervisor, and unfortunately we're unable to make an exception to our refund policy… this is our final decision" — plus a note that further replies "may go unmonitored." No acknowledgment of the bug.

Corroboration link only — standalone July 17 mass incident at #81703

This thread corroborates one mechanism in the July 17 incident, but it is not the incident hub and the cases are not being merged.

Anthropic's official July 17 status incident says users across Claude.ai, Claude Code, and other surfaces were erroneously required to use usage credits for an included model:
https://status.anthropic.com/incidents/g613ntyj2pwf

The customer's standalone dispute covers all six invoices dated July 17—$599.35 total. Anthropic's $3.11 account credit covers only Anthropic's selected 18:16–18:47 UTC window; the customer never claimed a 30-minute incident. The original private estimate was July 7–18 while the date was being isolated, and the reconciled scope is now the entire July 17 invoice date.

Dedicated Anthropic-owned incident:
https://github.com/anthropics/claude-code/issues/81703

Public incident brief:
https://coolak.github.io/anthropic-claude-billing-incident/july-17-usage-credit-refund.html

Requested action on the dedicated incident: assign a human Billing Platform/payment-operations owner, audit the full July 17 ledger, and refund $599.35 to the original payment method. Invoice identifiers, payment details, the private support ID, screenshots, and private conversation text remain private.

This thread remains relevant only as corroboration for the auto-recharge and no-human-billing-owner mechanism.

---

Adding a related signal from another high-usage paid account because this looks like the same billing/support ownership gap from the opposite direction.

In my case, automatic usage-credit reloads continue to charge successfully from the saved billing setup, but manual prepaid usage-credit purchases fail or get stuck in the billing flow. The failure is not behaving like a normal customer-side card decline: the automatic top-ups work, the manual purchase path fails after authentication/confirmation states, and Fin/support has not produced a human Billing Platform / payment-operations resolution.

That combination is useful triage evidence for this thread:

• automatic usage-credit charging can run without a reliable human refund/escalation path, as reported here;
• manual usage-credit purchasing can fail even when the same account/billing setup can still be charged automatically;
• Fin/support appears unable to reliably route these account-specific billing ledger, entitlement, reload, and purchase-state mismatches to a human owner.

Please route these to a real billing-platform owner rather than treating them as ordinary card declines, generic API-credit-terms cases, or normal usage disputes.

Privacy-sanitized public evidence hub for my related case:
https://github.com/COOLak/anthropic-claude-billing-incident

Hosted incident brief:
https://coolak.github.io/anthropic-claude-billing-incident/

Billing reconciliation matrix:
https://coolak.github.io/anthropic-claude-billing-incident/reconciliation-matrix.html

I have a Personal Max account and on July 31 and today (August 2nd) i experienced the same issue, 28 auto recharges and most between 16 and 22 euro 450,- euros in total... and i have no automatic tasks running at the moment and did not touched my account because of a holiday...