Detailed Analysis
A Reddit user on r/Anthropic has surfaced a troubling billing incident in which their American Express card was charged 171 separate times over roughly a week, totaling $1,796.70, despite the user being subscribed to Anthropic's Claude Max plan and having already paid in full through July 15. The charges appeared in recurring increments of $5.30, $10.60, and $15.90, suggesting some kind of malfunctioning micro-billing loop rather than a single erroneous large charge. Critically, the user reports checking their usage against both weekly and daily limits and finding themselves nowhere close to the caps that would ordinarily trigger overage billing, indicating the charges were not tied to legitimate usage-based billing but rather a backend system error. Anthropic's own support channel reportedly acknowledged "an issue with their billing system" when the first small charges appeared, yet no proactive fix, refund, or customer notification followed before the charges multiplied into the hundreds.
The more damaging part of this story, from a customer trust standpoint, is not just the billing glitch itself but Anthropic's support response. The user describes being routed through Fin, Anthropic's AI-powered customer support agent, both in the in-app chat and via email, and encountering what they call an "IN-FIN-NITE loop" — repeated deflections to contact the card issuer or bank, suggestions to use a different payment method, and hollow offers to escalate to a human agent that never materialized. Conversations were reportedly closed by the bot with a canned "I hope we have resolved your issue" message despite no resolution occurring. This pattern reflects a broader and increasingly common complaint across AI companies deploying LLM-based support agents: such systems can be effective at handling routine queries but tend to fail badly at edge cases involving financial harm, fraud, or billing disputes, where users need accountability and human judgment rather than scripted deflection loops.
This incident matters beyond one user's frustration because it touches on a structural risk in how AI companies are scaling subscription and usage-based billing systems. Anthropic's Max and Pro plans involve metered usage components layered on top of flat subscription fees, and any bug in the metering or charge-triggering logic can, as this case illustrates, generate runaway duplicate transactions before a human notices. The absence of automated safeguards — such as charge-velocity limits, fraud-detection triggers, or automatic holds when a card is charged dozens of times in rapid succession — is notable for a company operating at Anthropic's scale and valuation. It also raises questions about PCI compliance and payment-processor oversight, since most payment processors (Stripe, which Anthropic is known to use, included) typically have their own fraud-prevention systems designed to catch this kind of repeated-charge pattern, suggesting either a bypass of those safeguards or a deeper integration failure.
More broadly, this episode is emblematic of a growing tension in the AI industry between the push to automate customer support with LLM agents — reducing headcount and cost — and the reality that billing disputes, fraud claims, and financial harm require escalation paths that AI agents are not yet trusted or equipped to resolve. Anthropic has positioned itself as a safety-focused AI lab, but stories like this one, which the original poster explicitly frames as "Anthropic's betrayal," feed into a narrative among power users and enthusiast communities that AI companies' internal operations (billing, support, trust and safety) lag well behind their frontier model capabilities. As more users adopt higher-tier subscription plans like Max, which carry meaningful monthly costs and usage-based components, incidents like this — if not addressed with transparent refund processes, system audits, and improved escalation to human support — risk becoming a recurring reputational liability, especially as they circulate on public forums like Reddit where user trust is shaped as much by support experiences as by model quality.
Read original article →