July 17 Mass Claude Billing Incident — $604.71 Refund Dispute

Machine-Readable Transaction Track

Open the corrected privacy-safe eight-transaction JSON ledger →

This page uses only track july17_full_day: six automatic rows totaling USD 604.71. The claim period is the entire July 17 merchant date. Anthropic's selected 18:16–18:47 UTC correction window does not limit the claim. The August 1 and August 12 tracks are separate, and the manual USD 100.00 purchase remains excluded.

This Is Its Own Incident

This July 17 mass billing incident is distinct from the separate discounted manual-credit purchase failure. Its dedicated Anthropic-owned public tracker is anthropics/claude-code#81703.

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.

Official Incident Metadata

Anthropic's official machine-readable incident record classifies the impact as major. It records the investigation opening at 18:32:32 UTC, the listed components moving from operational to partial outage, a fix and monitoring update at 18:48:23 UTC with the components moving to degraded performance, and resolution at 19:43:35 UTC with the components returned to operational.

The listed components are Claude.ai, Claude API, Claude Code, and Claude Cowork. That component scope does not reclassify this customer's disputed objects: they remain Claude subscription / Individual-plan extra-usage-credit transactions, not Console or API-workspace invoices.

Evidence boundary: resolved service status does not establish payment reconciliation, an original-method refund, or which private transactions were caused by the incident. Anthropic still must join the incident record to the customer's entitlement, debit, recharge, invoice, payment, and correction ledgers.

Anthropic Documented a Separate July 20 Recurrence

Anthropic's official July 20 incident, Fable 5 requiring usage credits on Max plans, says some Claude Code Max-plan users were incorrectly prompted to use usage credits for Fable 5 even though it was included in their plan. Anthropic advised affected users to restart Claude Code. The incident opened at 2026-07-20 07:35:29 UTC and was resolved at 15:35:33 UTC.

Evidence boundary: this first-party record establishes a distinct later entitlement/credit-gate incident. It does not prove that this account was affected on July 20, that credits were consumed or purchased, that an automatic recharge completed, that the two incidents share a root cause, or that any particular transaction is refundable. It changes neither the six-charge $604.71 demand nor the unquantified boundary around adjacent dates.

Corrected Claim History

The customer did not claim that the billing problem lasted only 30 minutes. The original private report used a broader July 7–18 range because the affected date had not yet been isolated. The current refund request covers all six automatic recharges dated July 17 across the entire day; the separate $100 manual purchase is excluded. It remains possible that the same incident affected earlier dates and July 18, but that extension has not yet been established.

Anthropic's 18:16–18:47 UTC window is Anthropic's own automated incident window, not the customer's asserted scope.

Private Evidence, Public-Safe Totals

6 auto-rechargesAll disputed charges are dated July 17, 2026.

$604.71Full automatic-only refund demand.

$100 excludedSeparate manual purchase retained only in the chronology.

$3.11 creditPartial automated correction for only Anthropic's 30-minute window.

A complete July 7–18 receipt reconstruction also located $1,006.62 in successful charges marked paid July 7–16 and $191.73 marked paid July 18. Those adjacent-period charges are preserved because the incident may potentially extend to earlier dates and July 18. They are not included in the current $604.71 refund demand, and the possible extension is not treated as established without transaction-level evidence tying the charges to the same incorrect-routing mechanism.

The Central Contradiction

Usage credits were billed while included plan capacity remained. After extra usage and auto-reload were disabled, the customer continued the same work using included plan limits. That behavior is inconsistent with a claim that extra usage was triggered only after the included allowance was exhausted.

Anthropic's own usage-credit documentation says paid credits are the continuation mechanism after included plan limits are reached and says the Usage dashboard clearly distinguishes included plan usage from paid credit consumption. The July 17 account therefore requires a transaction-level reconciliation against Anthropic's entitlement, debit, auto-reload, and payment records.

Time-stamped first-party record: neutral Wayback captures now preserve Anthropic's paid-plan usage-credit guide, its Fable 5 plan article, and the direct July 17 incident page as captured on August 13 JST. Together, those pages preserve the published control model, the July 17 plan-inclusion context, and Anthropic's own statement that it fixed an erroneous usage-credit requirement. They do not prove this account's historical entitlement, map requests to charges, establish the affected period outside Anthropic's incident record, or decide the refund.

Receipt-Delivery Timeline

All seven first-party receipt bodies say Paid July 17, 2026. Their Gmail delivery timestamps span from July 17 09:59:43 UTC to July 18 04:47:33 UTC—18h 47m 50s.

One excluded $100.00 manual-purchase receipt email arrived before Anthropic's 18:16–18:47 window, one disputed $97.12 automatic-recharge receipt arrived inside it, and five disputed automatic-recharge receipts totaling $507.59 arrived after it. Therefore 83.9% of the current $604.71 dispute appears in receipt emails delivered after the selected window.

Against Anthropic's official major incident record—opened at 18:32:32 UTC and resolved at 19:43:35 UTC—the six disputed automatic-recharge receipt emails span 10h 13m 44s. One $97.12 receipt arrived during the official incident; five totaling $507.59 arrived after Anthropic marked it resolved, continuing through 04:47:33 UTC the following day. The first post-resolution receipt arrived 7m 58.533s after resolution, and the final one arrived 9h 3m 57.533s after it.

Open the public-safe visual timeline →

Email delivery time is not necessarily the internal debit, recharge-trigger, payment, or invoice timestamp. This evidence supports a full transaction audit without claiming that outside-window delivery proves incident causation by itself.

Request-Metadata Window Audit

A privacy-redacted local Claude Code inventory contains 2,177 deduplicated July 17 records spanning 00:00:06–23:46:50 UTC. Using [18:16, 18:47) because Anthropic says included limits worked as intended since 18:47, the records divide into 1,241 before, 29 inside, and 907 after.

That places 2,148 records (98.67%) and 706,168,401 / 722,463,837 recorded counters (97.74%) outside Anthropic's selected interval.

Open the privacy-safe aggregate audit →

This proves day-spanning local request activity, not provider-billed dollars, historical plan entitlement, included-versus-paid routing, credit debits, auto-reload triggers, or request-to-invoice mapping. Only Anthropic's authoritative historical ledgers can decide those questions.

Payment-Processor Trace — Transactions Located, Root Cause Unresolved

All six July 17 automatic-recharge receipts, totaling $604.71, say Payment method Link. A subsequent human Link review under the correct Gmail-authenticated account located all six transactions and supplied their card-network/last-four and timestamp/status mappings privately. The earlier no-match result came from a different Link identity and is superseded.

This proves that the six wallet debits exist and can be traced to the correct account. It does not prove Anthropic's internal subscription entitlement, included-plan-versus-paid-credit routing, paid-credit debit, automatic-recharge trigger, or incident causation. Link stated that the PaymentIntent and charge identifiers remain merchant-side details that Anthropic must retrieve.

Read the corrected privacy-sanitized processor update →

The public update intentionally omits the Link case number, account emails, invoice IDs, card data, and private support transcript.

Latest Stripe/Link Complaint Response

On August 15 JST, authenticated Link Support confirmed that its support case and personal-data investigation remained open. Its initial purchase list did not include any of the six disputed July 17 automatic recharges totaling USD 604.71; it also omitted the two disputed August 1 recharges and instead included Platform payments plus unrelated purchases. A September 3 correction established that the two Platform entries were genuine API credit grants and withdrew the former USD 99.08 claim. The fixed consumer dispute is USD 1,600.38 original, with USD 1,585.12 remaining.

Link then stated that purchase refunds and invoices are best handled by Anthropic, suggested contacting a card-issuing bank if the merchant remains unresponsive, and said its written support case would remain open. One concise same-thread response kept the unanswered Link-controlled July 17 mapping, preservation, merchant-referral, case-status, and next-update questions pending.

On August 18 JST, Stripe Complaints then sent what it labeled a Final Response under the controlling existing Link complaint. It said Stripe could not issue the merchant refund and redirected the consumer to Anthropic or a bank. The response did not address any of the six July 17 invoice/receipt rows, provide a payment/refund/reversal/merchant-action/original-destination disposition or safe processor mapping for a row, or explain the decision basis for a row. It also did not acknowledge the verified USD 15.26 partial original-payment refund on a separate August 1 row within the same existing USD 1,600.38 complaint track. One evidence-backed reconsideration was sent in the same thread that day.

After Anthropic's authenticated billing-bug notice was supplied, Stripe said it had reviewed the follow-up and that its Final Response remained firm while still naming 0 of 8 existing-track transactions and filling 0 of 56 required transaction-response fields. A later authenticated reply in the separate formal-support lane said it was closing that support case to centralize communications in the case-associated thread; that routing step supplied no new complaint reference, refund, reversal, merchant action, safe processor reference, or transaction-level decision. BBB separately confirmed that the existing complaint record was amended again and that Anthropic was sent a reminder to reply.

Calling the response final does not make it transaction-specific or complete. It is not proof that a July 17 payment was refunded, reversed, or disposed of. Verified original-payment refunds for the six July 17 rows remain USD 0.00. A signed chargeback request was sent to the card-issuing bank on August 20, 2026. On August 21, the bank confirmed registration and forwarding to responsible staff. A September 3 clarification corrects the scope to eight consumer charges and USD 1,585.12 remaining; it is prepared as a draft and has not been sent. Formal chargeback acceptance, a merits decision, and Mastercard routing remain unconfirmed. The July 17 demand remains USD 604.71; the separate USD 100.00 manual purchase remains excluded. The August 1 dispute is outside this page's demand, and the former August Platform-grant claim is withdrawn.

Subscription Classification and Evidence Boundary

The six disputed automatic-recharge receipts are Claude Individual-plan extra-usage-credit objects associated with the subscription account. A seventh record is a one-time manual usage-credit purchase and is excluded. These are not Console or API-workspace invoices.

Anthropic's current Consumer Terms say they govern Claude.ai, Claude Pro, and other individual services. They separately say API-key and Console offerings are governed by the Commercial Terms and clarify that this does not include Claude.ai or Claude Pro use. This primary-source product boundary aligns with the Individual-plan labels on the disputed receipts. It does not by itself establish whether any July 17 request was correctly routed, whether the charges were authorized, or whether a refund is due.

Local request metadata can independently establish timestamps, models, and usage counters. It cannot determine whether Anthropic correctly classified a request as included subscription usage or paid Individual-plan extra usage. Only Anthropic's transaction-time subscription-entitlement and paid-credit ledgers can resolve that question. Present-day local authentication state is irrelevant and is not part of this claim. The corrected technical update is preserved in the dedicated Anthropic tracker.

Independent Document-First Coverage

Future Stack Reviews' Tier C analysis separately examines Anthropic's July 17 public record. It distinguishes Anthropic's approximately 30-minute model-selectability statement from the approximately 71-minute status-page incident, explains that returning usage credits is not the same as returning cash, and treats a remediation announcement as different from proof that an account correction completed.

Future Stack Reviews expressly did not reproduce the incident, holds no account record from the incident window, and verified no account-level debit, auto-reload, external payment, credit restoration, matching-credit delivery, cash refund, or card reversal. Its analysis therefore does not verify this account's $604.71 automatic-recharge loss or refund entitlement. It independently supports only the public-record distinctions that make Anthropic's transaction-level full-day ledger and original-payment refund evidence necessary.

Relevant Billing-Provider Relationship — Not Proof of Scope

Metronome's February 2025 company announcement publicly names Anthropic among companies relying on its billing platform. Metronome's August 2025 billing-correction guidance says billing errors require repair across usage, invoices, credit ledgers, reporting, customer dashboards, and threshold logic, with correction records carrying timestamps, transaction IDs, and actor metadata.

This does not establish that Metronome handles Claude consumer usage credits, processed the six disputed automatic-recharge receipts, or caused the July 17 incident. It establishes a public provider relationship and a directly relevant correction standard: a small account credit is not evidence that the complete connected billing state was repaired. The caveated record is preserved in Anthropic's dedicated tracker.

Independent BBB Mechanism Report

Anthropic's current BBB complaints page contains a separate June 29, 2026 Billing Issues complaint alleging that usage credits were deducted while included plan allowance remained and that a configured $50 spending limit was exceeded to $66.

This is a third party's public allegation. BBB does not verify complaint accuracy, and the report does not prove this customer's $604.71 amount or establish the same root cause. It does independently describe the same observable included-limit-to-paid-credit mechanism. The caveated source record is preserved in Anthropic's dedicated tracker.

Related Anthropic Consumer Litigation — Separate Allegations

Two pending federal consumer cases provide broader context, but neither establishes the facts, amount, cause, or legal status of this July 17 dispute:

Kahn v. Anthropic PBC, No. 3:26-cv-05763 (N.D. Cal.), filed June 14, 2026. Plaintiff's counsel describes the complaint as alleging that Anthropic misled consumers about the usage and value of its Max 5x and Max 20x plans.
Pascual v. Anthropic, PBC, No. 3:26-cv-07699 (N.D. Cal.), filed July 24, 2026. The public docket identifies a contract complaint; Bloomberg Law reports that it alleges retained subscription fees after service reductions and defects.

These are allegations in pending cases, not findings of fact or liability. Neither case proves that this customer's July 17 usage was misrouted, proves the $604.71 ledger, expands the refund demand, or establishes that the customer is a member of any proposed class. The July 17 matter remains a separate operational billing claim: usage credits allegedly consumed while included plan capacity remained, followed by six automatic recharges totaling $604.71, an excluded $100 manual purchase, and only a $3.11 account credit.

Why the $3.11 Credit Is Not Settlement

The credit addresses only Anthropic's automated 30-minute window. It does not reconcile the six disputed July 17 automatic-recharge invoices, establish correct routing during the rest of the day, or refund the claimed charges to the original payment method.

Requested Remedy

Assign a human Billing Platform / payment-operations owner.
Audit the full July 17 ledger, not only 18:16–18:47 UTC.
Reconcile plan entitlement, session/model routing, usage-credit debits, auto-reload triggers, and invoice creation transaction by transaction.
Refund every July 17 charge caused by routing usage to credits while included plan capacity remained.
Return the refund to the original payment method, or identify each disputed invoice with timestamped usage and entitlement evidence.

Official Written Support Route and Observed State

Anthropic's current How to get support guide says paid Pro and Max subscribers have access to Fin plus further assistance from the Product Support team. It says matters requiring additional investigation or Product Support input are passed onward by Fin and that someone responds by email. The same guide says Anthropic does not offer phone or live-chat support and routes Product Support through the support messenger.

Anthropic's separate paid-plan refund guide directs a signed-in customer to the messenger's Claude Refund Request flow. Those official pages establish the published written route; they do not establish that a human has reviewed this account or create a specific response deadline.

As of 2026-08-13 00:20 JST, the controlling July formal-dispute Gmail thread contained 11 customer-sent messages and no Anthropic reply. Its newest message is the definitive automatic-only correction: $604.71 demanded for the six July 17 automatic recharges, the $100 manual purchase excluded, and adjacent dates unquantified. No named human billing owner, transaction-by-transaction disposition, or original-payment refund was present in that thread. This is an observed mailbox state, not proof of Anthropic's internal review state.

Standalone Public Discussion

Contemporaneous July 17 Mass Reports

Public discussions posted during the incident show that the paid-credit impact was not isolated to one account:

Open the structured public report matrix →

Nine tightly clustered issues in Anthropic's own Claude Code tracker were opened between 18:17 and 19:24 UTC. Public reports include roughly 12%, 24% session / 28% weekly, 45%, and 50% included-usage positions, plus macOS/Linux/Windows and Claude Code/Claude.ai impact.
High-engagement r/ClaudeCode incident thread with contemporaneous reports of unexpected Anthropic card notifications, usage credits reaching 105%, $50 in overages, a claimed $100 monthly usage-credit limit being consumed, and a second user who said the same happened with a $50 limit.
Separate r/ClaudeCode incident thread with multiple reports that an included model suddenly required usage credits, including one user who said roughly half of the included usage remained.
r/claude incident discussion with reports that paid-credit charging started during the outage and one commenter who said $287 was consumed before they noticed.
Large r/ClaudeCode incident thread with one public claim that $500 of usage credit was consumed when the service switched to credits, another report that the user's full Extra Usage budget was consumed without notice, and a separate report of a $6.32 charge despite plan capacity reportedly remaining.
Contemporaneous r/claudexplorers report saying the interface switched to “Now using credits” and charged $6.32 while plan capacity remained; a second user reported spending several dollars in Claude Code without a warning that usage was switching to credits.
Large r/claude discussion with multiple reports of the “Usage credits are required” message appearing mid-session, including users who said they had 30% or substantial weekly plan capacity remaining.
r/Anthropic incident thread with reports from Max 20x and Max 5x users that usage credits were suddenly required, including one commenter who said only about 6% of included usage had been consumed.
r/ClaudeAI incident discussion showing 75% session usage, 11% weekly usage, and usage credits off in the original post; commenters said credits were nevertheless consumed during the outage, including one claim of about $8 spent after enabling credits to finish a task.
Separate Max 20x report saying the app burned usage credits while the account showed only 8% five-hour usage and 3% weekly usage.
Separate r/Anthropic report in which the poster claimed $200 in credits disappeared without warning, later said the credits had not returned after model access returned, and reported that Fin redirected the debit-card credit complaint to Apple/iOS. This unverified third-party claim is not included in this customer's $604.71 total.

These are third-party public reports, not proof of this customer's private ledger. They corroborate Anthropic's own statement that the incident affected users across Claude surfaces and justify a full-day, account-by-account reconciliation.

Related Later/Unknown-Date Reports — Separate and Unverified

On July 28, a different GitHub participant reported being charged EUR 2,932.51 from July 23 until a credit-card limit was reached on July 24 and said a promised human support reply never arrived.

This is an unverified third-party claim from July 23–24, not a July 17 source. It is not included in this customer's $604.71 ledger, does not prove the same mechanism or root cause, and may represent a distinct later incident. It is preserved as related pattern context because it independently alleges large automated billing and failed human escalation later in the same month.

Read the participant's public comment →

Another public comment on the same Anthropic-owned issue reports three completed July 23 Individual-plan automatic recharges of USD 236.00, USD 205.93, and USD 207.23—USD 649.16 total—and generic support replies. The attached screenshots visibly show those three paid totals and the Auto recharge extra usage, Individual plan item. The reporter's no-interaction statement is an allegation; the single visible chat-list screenshot is not an exhaustive account-activity audit.

The comment text says two failed USD 199.48 attempts, while the two attached failure screenshots show USD 199.48 and USD 125.49. That discrepancy remains unresolved. This is a separate account and later date, is excluded from this customer's USD 604.71 ledger and every other demand here, and does not prove a shared root cause, aggregate loss, or refund entitlement.

Read the public comment and source screenshots →

Anthropic tracker issue #81941 separately alleges 35 unexpected usage-credit charges totaling EUR 1,809.55, including repeated overnight charges about 4–6 minutes apart while Claude reportedly also displayed weekly-limit blocks. The issue is open and bug-labeled but does not state the charge dates. It is an unverified self-report, is not included in this customer's $604.71 ledger, and does not prove the same date, mechanism, or root cause.

Corroborating Mechanism Reports

These reports corroborate the mechanism but do not replace the dedicated July 17 incident.

Privacy Boundary

Exact invoice numbers, payment details, support identifiers, private screenshots, and private conversation text remain in Anthropic's support channel. They are intentionally not published here.