[BUG] July 17 mass billing incident: usage credits charged despite plan allowance; $604.71 automatic recharges disputed

Preflight checklist

• [x] I searched the existing tracker and found mechanism-related reports, but no dedicated issue for Anthropic's acknowledged July 17 incident and the unreconciled full-day charges.
• [x] This is one bug: subscription usage was routed to paid usage credits while included plan allowance remained.
• [x] I am using the latest installed Claude Code version available to me (2.1.210).

What's wrong?

Cached-preview correction (August 12, 2026): Some external search previews still display an obsolete $704.71 figure and describe a refund request covering all seven July 17 invoices. The current quantified demand is $604.71 for six automatic recharges. The separate $100 manual purchase is excluded. This live issue is the current source of truth.

On July 17, 2026, Claude Code charged paid usage credits while my included subscription allowance was still usable. The current quantified refund demand covers six automatic extra-usage recharges dated July 17 totaling $604.71.

A separate same-day $100.00 manual usage-credit purchase is excluded from the quantified refund demand. It remains visible in the receipt chronology only so the full-day ledger can be reconstructed accurately.

Anthropic has now acknowledged a July 17 configuration error. Its status page says users were erroneously required to use usage credits for an included model across Claude.ai, Claude Code, and other surfaces:

• Incident: https://status.anthropic.com/incidents/g613ntyj2pwf
• 18:48 UTC update: Anthropic said it fixed the “erroneous requirement for usage credits”
• 19:43 UTC update: Anthropic said the model was available again “without usage credits, as expected”

Official incident-record precision

Anthropic's machine-readable incident record classifies the impact as
major and records this UTC progression:

• 18:32:32 — investigation opened and the listed components moved from

operational to partial outage;

• 18:36:40 — Anthropic described Fable 5 selection failures across Claude.ai,

Claude Code, and other surfaces;

• 18:48:23 — a fix was applied and the components moved to degraded

performance during monitoring; and

• 19:43:35 — the incident was marked resolved and the components returned to

operational.

The listed components are Claude.ai, Claude API, Claude Code, and Claude Cowork.
The API component's presence in that status record does not reclassify these
disputed transactions: they are Claude subscription / Individual-plan
extra-usage-credit objects, not Console or API-workspace invoices.

The incident's resolved service status is not proof of payment reconciliation,
an original-method refund, or which private transactions were caused by the
incident. Anthropic still must map the status incident to the complete
entitlement, usage-credit debit, automatic-recharge, payment, and correction
ledger.

Separate official July 20 recurrence

Anthropic separately documented a later incident, Fable 5 requiring usage
credits on Max plans:

https://status.claude.com/incidents/tnypgb2jbqnq

Its public update 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, and
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.

This first-party record establishes a distinct later entitlement/credit-gate
incident. It does not prove that my account was affected on July 20, that
credits were consumed or purchased, that an automatic recharge completed, that
the July 17 and July 20 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.

Receipt sequence versus the official incident window

Live Gmail delivery timestamps and the six original receipt PDFs establish a
separate, bounded chronology. Every disputed receipt says Auto recharge extra
usage, Individual plan and Paid July 17, 2026. The six automatic-recharge
receipt emails span 10h 13m 44s, from 18:33:49 UTC to 04:47:33 UTC the
following day.

Against Anthropic's official major-incident window (18:32:32–19:43:35 UTC):

• one automatic-recharge receipt for $97.12 arrived during the incident;
• five automatic-recharge receipts totaling $507.59 arrived after Anthropic

marked it resolved;

• the first post-resolution receipt arrived 7m 58.533s after resolution; and
• the final receipt arrived 9h 3m 57.533s after resolution.

The separate $100 manual purchase arrived before the official incident and
remains excluded from the refund demand. Public-safe timeline:
https://coolak.github.io/anthropic-claude-billing-incident/july-17-receipt-timeline.html

Receipt-email delivery time is not necessarily the internal usage event,
paid-credit debit, automatic-recharge trigger, payment authorization, or
invoice-creation timestamp. This chronology does not independently prove
transaction-level causation; it shows why service resolution and a correction
limited to one short interval cannot reconcile the complete six-charge ledger.

Anthropic also emailed me that it identified incorrect usage-credit billing from 18:16–18:47 UTC and added a $3.11 account credit. That 30-minute window is Anthropic's scope, not my claim.

My original support report used July 7–18 while I was still isolating the affected date. The current evidence-backed refund minimum covers the six automatic recharges dated July 17 across the entire day. The same reconstruction located $1,006.62 in successful July 7–16 charges and $191.73 in successful July 18 charges. The affected period may potentially extend to those earlier dates and July 18, but that has not yet been established. Those adjacent-period charges remain under investigation and are not included in the current $604.71 demand without transaction-level evidence tying them to the same incorrect-routing mechanism.

The decisive behavioral evidence is this: after I disabled extra usage and auto-reload, Claude Code continued working against my included plan allowance. If that allowance had actually been exhausted, turning off paid extra usage should have stopped the work. It did not.

Anthropic's documented paid-plan baseline

Anthropic's current paid-plan usage-credit guide describes usage credits as the continuation mechanism after a paid subscriber reaches included plan limits and says the system applies to Claude Code. It says included session limits continue to reset every five hours, paid credits do not alter that reset timing, the Usage dashboard distinguishes included-plan use from paid-credit use, and the user receives a notification and confirmation before switching to paid credits. The guide also says disabling usage credits leaves only included-plan access.

That current guide establishes Anthropic's published control and accounting model; it does not by itself prove this account's historical settings, per-request routing, or recharge triggers on July 17. The full-day claim therefore still requires Anthropic's timestamped entitlement, usage-credit debit, and automatic-purchase records. The guide makes those records more—not less—important because the observed continued included-plan access after paid usage was disabled must be reconciled against the published separation between the two usage buckets.

The $3.11 expiring account credit is therefore only a partial automated correction. It does not reconcile the other July 17 credit debits or the six automatic recharges.

Official written support route versus observed response 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 a person 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 prove 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 carries the definitive automatic-only correction: $604.71 demanded for the six July 17 automatic recharges, the separate $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.

What should happen?

1. Included plan allowance must be consumed according to the plan before Claude Code routes eligible usage to paid usage credits.
2. Auto-reload must not trigger from usage that should have remained inside included allowance.
3. Anthropic should assign a human Billing Platform/payment-operations owner to audit the full July 17 ledger, not only the company-selected 30-minute window.
4. Anthropic should refund the six July 17 automatic recharges—$604.71 total—to the original payment method. The separate $100 manual purchase is excluded.
5. If Anthropic disputes any invoice, it should identify that invoice and provide timestamped entitlement, routing, usage-credit debit, and auto-reload evidence.
6. Anthropic should disclose the incident scope and confirm that all affected accounts—not only those who noticed—were reconciled.

Steps that exposed the bug

1. Use Claude Code with an active subscription plan and extra usage/auto-reload enabled.
2. Continue normal Claude Code work on July 17.
3. Observe usage credits being depleted and automatic recharges repeatedly invoiced.
4. Disable extra usage and auto-reload.
5. Observe Claude Code continue working against included plan allowance.
6. Compare the July 17 invoices with Anthropic's later incident acknowledgment and $3.11 correction.

This is account-ledger behavior, so Anthropic will need internal telemetry to reproduce the exact routing decision.

Latest Stripe/Link complaint response

On August 15 JST, authenticated Link Support confirmed that its written 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 automatic recharges in the separate August 1 incident and instead included the separate August 12 payments plus unrelated purchases. One written scope correction preserved the fixed USD 1,600.38 earlier-track demand, the separate USD 99.08 later incident, and the manual-purchase exclusions.

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 now issuer-verified USD 15.26 partial original-payment refund on a separate August 1 row within the same existing USD 1,600.38 original complaint track. One evidence-backed reconsideration was sent in the same thread that day. 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 covering all ten documented automatic charges was sent to the card-issuing bank on August 20, 2026. On August 21, the bank confirmed that the letter was registered and forwarded to the responsible staff. Formal chargeback acceptance, a merits decision, and any Mastercard routing remain unconfirmed and pending bank review. This issue's demand remains USD 604.71 for the six automatic recharges; the separate USD 100.00 manual purchase remains excluded. The later August 1 and August 12 transactions remain outside this issue's demand.

Environment

• Claude Code: 2.1.210
• Plan/billing platform: Claude Individual subscription and its extra-usage-credit system; not Console or API-workspace billing
• OS: macOS 26.5.2
• Model: multiple models / incident involved an included model
• Regression: yes; paid-credit routing was not the expected plan behavior

Evidence and privacy

Public incident brief:

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

Supporting public-safe records:

• Receipt chronology: https://coolak.github.io/anthropic-claude-billing-incident/july-17-receipt-timeline.html
• Request-window audit: https://coolak.github.io/anthropic-claude-billing-incident/july-17-request-window-audit.html
• Contemporaneous-report matrix: https://coolak.github.io/anthropic-claude-billing-incident/july-17-mass-report-matrix.html
• Anthropic-owned issue cluster: https://coolak.github.io/anthropic-claude-billing-incident/july-17-github-issue-cluster.html
• Affected-user ledger checklist: https://coolak.github.io/anthropic-claude-billing-incident/july-17-ledger-checklist.html
• Reporter verification brief: https://coolak.github.io/anthropic-claude-billing-incident/july-17-reporter-brief.html
• Public-safe regulator attachment: https://coolak.github.io/anthropic-claude-billing-incident/july-17-regulator-attachment.pdf

I have provided the existing private Anthropic support conversation and formal dispute thread with the six automatic-recharge invoice identifiers and exact amounts, the excluded manual-purchase record, the adjacent-period audit perimeter, and the full $604.71 refund demand. I can provide the underlying invoices and account details to Anthropic staff through that private channel.

I am intentionally not publishing invoice identifiers, payment details, the private support ID, screenshots containing account data, or private conversation text.

Independent document-first coverage

Future Stack Reviews published a Tier C, document-first analysis of Anthropic's July 17 record:

https://future-stack-reviews.com/claude-fable-5-usage-credit-error-july-17/

The publication independently confirms the bounded public-record points: Anthropic described the July 17 usage-credit requirement as erroneous; the 30-minute selectability statement and the approximately 71-minute status-page incident measure different intervals; returning credits is not the same as returning cash; and a remediation announcement is not proof that any account was fully corrected.

Future Stack Reviews expressly did not reproduce the incident, holds no account record from the incident window, and verified no account-level debit, external payment, credit restoration, matching-credit delivery, cash refund, or card reversal. This coverage therefore does not verify this account's USD 604.71 automatic-recharge loss or refund entitlement. It is independent support for the public-record distinction that makes Anthropic's transaction-level full-day ledger and original-payment refund evidence necessary.

Contemporaneous July 17 reports

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

• Unexpected Anthropic card notifications and claimed $50/$100 usage-credit impacts: https://www.reddit.com/r/ClaudeCode/comments/1uz7oae/its_happened/
• Included models suddenly requiring usage credits while plan capacity reportedly remained: https://www.reddit.com/r/ClaudeCode/comments/1uz7rzw/usage_credits_are_required_for_this_model/
• Paid-credit charging during the outage and a separate claimed $287 impact: https://www.reddit.com/r/claude/comments/1uz7sk7/apparently_17_19_according_to_anthropic/
• Separate claimed $500/full-budget/$6.32 impacts: https://www.reddit.com/r/ClaudeCode/comments/1uz7pmj/fable_gone/
• A plan-capacity/no-warning $6.32 report: https://www.reddit.com/r/claudexplorers/comments/1uz88co/suddenly_lost_access_to_fable_on_subscription_i/
• Max-plan headroom reports during the same incident: https://www.reddit.com/r/Anthropic/comments/1uz7rsk/fable_5_issue/

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

Standalone discussion and evidence-update routes already in use:

• X evidence thread: https://x.com/Coolak777/status/2081778624722829642
• r/ClaudeCode: https://www.reddit.com/r/ClaudeCode/comments/1v85cuh/july_17_mass_billing_incident_anthropic/
• r/Anthropic: https://www.reddit.com/r/Anthropic/comments/1v85sj5/was_your_full_july_17_usagecredit_ledger/

Related mechanism reports

These reports corroborate the same class of routing/accounting failure but do not replace this July 17 incident report:

• #80750 — usage credits consumed while plan allowance remains
• #68773 — repeated auto-recharge billing and failed human escalation
• #32544 — Extra Usage charged despite visible plan headroom

This issue should remain the dedicated public record for the July 17 mass billing incident and its unreconciled full-day charges.

Machine-readable automatic-charge ledger

A privacy-safe JSON ledger lists all ten documented automatic purchases across
the three separately scoped incident records in two dispute tracks:

https://coolak.github.io/anthropic-claude-billing-incident/automatic-charge-summary.json

For this July 17 issue, use only track july17_full_day: six automatic rows
totaling USD 604.71. The August 1 and August 12 tracks are not part of this
issue's demand. The separate USD 100.00 manual purchase is excluded.
Receipt-email delivery timestamps are not internal debit, recharge-trigger,
payment-creation, or invoice-creation times.

August 19 processor response after Anthropic's billing admission

Anthropic's authenticated billing-correction notice says that, from July 24
through August 11, a bug caused some cloud-hosted Claude Code and Cowork
sessions to restart while waiting on an unanswered permission prompt; each
restart made a model call and billed usage the customer did not initiate.
Anthropic says it fixed that bug on August 12 and attributes USD 15.26 in this
account's usage-credit charges to it.

That stated window begins after July 17. The notice therefore does not identify,
explain, or dispose of any of the six July 17 automatic recharges in this issue.
It is first-party evidence of a separate billing bug and stated remediation in
the later August 1 record, not proof of the cause or refund status of the July
17 rows.

After the authenticated notice was supplied to Stripe/Link, Stripe said it had
reviewed the follow-up and that its Final Response remained firm. A structured
response-completeness audit found that the response still named 0 of 8
existing-track transactions and filled 0 of 56 required row fields: current
payment, refund or reversal, merchant action, original destination, safe
processor reference, and decision basis for each transaction.

A later authenticated reply in a 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. No duplicate reply was sent.

Verified original-payment refunds for the six July 17 rows remain USD 0.00,
and this issue's demand remains USD 604.71. Across the separate existing
July 17-plus-August 1 complaint track, the card issuer verifies one USD 15.26
original-payment refund on an August 1 row, leaving USD 1,585.12 unresolved
on that track. The separate August 12 USD 99.08 incident remains outside
this issue's demand. The signed ten-operation chargeback request was registered
by the bank on August 21 and forwarded to the responsible staff. Formal
chargeback acceptance, a merits decision, and any Mastercard routing remain
unconfirmed and pending bank review.

Privacy-safe current record:
https://coolak.github.io/anthropic-claude-billing-incident/