[Billing][Bug] $995.67 in two Individual-plan auto-recharges after included limits reset

[COOLak]

Preflight checklist

• I searched existing issues before filing this report.
• This reports one separately quantified August 1 billing incident.
• Private invoice, receipt, card, account, and support identifiers are omitted from the public report.

What's wrong?

My Claude Individual subscription's included usage limits had reset, but Claude Code continued drawing from usage credits. Two high-value automatic recharges then completed through Link:

Receipt email delivered (JST)	Amount	Merchant description
2026-08-01 07:50:52	USD 496.75	Auto recharge extra usage, Individual plan
2026-08-01 12:25:00	USD 498.92	Auto recharge extra usage, Individual plan

The separately quantified total is USD 995.67. These were automatic recharges, not manual top-ups. The merchant PDFs label both payments “Paid July 31, 2026,” while the receipt emails arrived on August 1 in Japan; Anthropic and its processor should supply the exact transaction timestamps and timezone.

After the second recharge, usage credits continued to drain. I disabled usage credits to stop further losses.

Anthropic's own help-center article says that usage credits let paid subscribers continue after reaching included plan limits, that included session limits reset every five hours, and that usage credits do not affect reset timing:

https://support.claude.com/en/articles/12429409-manage-usage-credits-for-paid-claude-plans

The same guide says the Usage dashboard distinguishes included-plan use from paid-credit consumption, that the user receives a notification and confirmation before switching to paid credits, and that disabling usage credits leaves only included-plan access.

That published behavior is inconsistent with the customer-observed sequence here: the included limits had reset, yet Claude Code continued consuming usage credits and triggered two automatic purchases.

These are Anthropic's current published control and accounting rules, not independent proof of the precise August 1 reset time, the warnings displayed to this account, or the server-side routing decision. Those historical facts remain inside Anthropic's timestamped entitlement, notification, routing, debit, and recharge records.

Issuer-verified USD 15.26 partial refund; USD 980.41 remains

On August 17, Anthropic generated records stating that USD 15.26 was sent
to the original payment route for the automatic charge originally totaling
USD 498.92. Anthropic's refund memo identifies an automatic extra-usage
reload charged during a hosted-Claude service issue spanning July 24 through
August 12, 2026. The card issuer's own history now shows a distinct USD 15.26
incoming Anthropic posting that maps to that charge. The partial refund is
therefore counted once, leaving USD 483.66 on that row and USD 980.41
across this August 1 incident.

Authenticated Anthropic email admits the billing mechanism

On August 19 JST, an authenticated first-party Claude billing-correction
email supplied the causal explanation absent from the public status archive.
Anthropic says that from July 24 through August 11, some cloud-hosted Claude
Code and Cowork sessions repeatedly restarted while waiting on an unanswered
permission prompt; each restart caused a model call and billed usage the
customer did not initiate. Anthropic says it fixed the bug on August 12.

The email says this account had USD 15.26 in affected usage-credit charges
and describes USD 30.52 in total remediation: an original-charge refund
plus an additional USD 15.26 account usage credit. The original-charge
refund is now issuer verified and reduces the disputed balance once. The
separate account usage credit is not money returned to the original payment
method and does not reduce the card claim.

The email does not map its calculation to both August 1 invoices, explain why
one charge received no documented refund and the other only USD 15.26, or
provide a transaction-by-transaction disposition of the remaining USD 980.41. Its
subject's “No Action Required” label cannot settle that unresolved ledger. The
stated July 24–August 11 window does not cover the July 17 incident and does not
establish that the separate August 12 disabled-Auto-reload charges arose from
this bug.

Public status archive does not identify that refund event

Anthropic's official incident feed contains no public incident that spans the
full memo window or names billing, payments, usage credits, Auto-reload,
recharges, invoices, refunds, subscriptions, entitlements, or charges. That
does not rule out an undisclosed internal or account-level issue. It means the
public archive does not identify the event named in the memo or explain the
refund calculation.

Exactly USD 15.26 is issuer verified as returned to the original payment
route. The August 1 incident therefore has USD 980.41 unresolved, and the
existing automatic-only track has USD 1,585.12 unresolved. Private refund,
credit-note, payment, and support identifiers remain omitted here. The public
reconciliation is available at
https://coolak.github.io/anthropic-claude-billing-incident/august-1-evidence-chain.html.

Evidence boundary

The original invoice and receipt PDFs independently prove the two successful automatic Individual-plan recharges and their amounts. They do not by themselves prove the precise limit-reset time or the server-side entitlement/routing decision. Anthropic must reconcile those elements from its own plan-entitlement, limit-bucket, request-routing, usage-credit ledger, auto-recharge-trigger, invoice, and payment records.

All four original payment PDFs have been supplied privately through both relevant authenticated written channels: the existing correct-account Link processor case and Anthropic’s written support route. This establishes evidence availability, not acknowledgment, fault admission, refund approval, or settlement. I am not publishing receipt numbers, invoice numbers, payment-card details, account identifiers, or support-case content here.

Official support route and 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 formal-dispute Gmail thread that preserves this August 1 incident as a separate automatic-only demand contained 11 customer-sent messages and no Anthropic reply. Its newest controlling message at that checkpoint demanded the full USD 995.67 original-payment refund for these two automatic recharges and excluded manual purchases. No named human billing owner, transaction-by-transaction disposition, or original-payment refund was present in that thread at that time. Anthropic later issued the separate USD 15.26 refund now verified by the card issuer and described above. This is an observed historical mailbox state, not proof of Anthropic’s internal review state.

Expected behavior

After included plan limits reset, eligible Claude Code usage should draw from the included subscription allowance. It should not continue draining usage credits or trigger automatic recharges unless Anthropic can show that a separate documented limit remained exhausted and that the affected requests were properly routed to paid credits.

Actual behavior

According to the account-visible sequence, the included limits reset, but usage credits continued to be consumed. This triggered two automatic Individual-plan recharges totaling USD 995.67. Credit depletion continued until usage credits were disabled.

Requested resolution

1. Return the remaining USD 980.41 to the original payment method or methods.
2. Preserve and reconcile the relevant plan-entitlement, limit-reset, request-routing, usage-credit-debit, auto-recharge-trigger, invoice, and payment records.
3. Identify the exact included limit or model-specific gate Anthropic believes was exhausted for each paid-credit debit after the observed reset.
4. Add a billing guard that prevents automatic recharges while the entitlement and limit state disagree or immediately after an included-limit reset.
5. Route this to a human Billing Platform / payment-operations owner and provide a substantive response.

Scope and related reports

This is a separate August 1 incident. It does not alter the quantified July 17 dispute in #81703.

Related reports provide pattern context but do not prove that they share the same root cause:

• [Bug] Fable 5 incorrectly requires usage credits despite active Max plan with available allowance #83037 — same-day report that Fable 5 required usage credits despite an active Max plan and available allowance.
• Session silently falls back from Fable 5 to Sonnet 5 mid-conversation; manual switch back blocked by out-of-credits message despite ~12% weekly limit used #83036 — same-day report of an out-of-credits block despite roughly 12% weekly usage.
• [BUG] Max 20x silently downgraded to Pro mid-cycle — subscription_status "canceled" while Apple confirms subscription active #83093 — same-day report that an Apple-billed Max 20x subscription was marked canceled in Anthropic's OAuth profile immediately before credits_required errors; this is pattern context, not proof of this account or a shared root cause.
• [BUG] Bug: Extra Usage charged despite available plan capacity + false rate limit errors in Claude Code #32544 — extra usage consumed while the dashboard showed substantial plan capacity.
• [Billing][Bug] Auto-recharge loop charged consumer plan 29x ($661) in error; Fin support admits malfunction but cannot escalate to a human #68773 — repeated consumer Individual-plan auto-recharges and an inaccessible human-refund route.
• [BUG] Hung Cowork scheduled task silently consumed full Max 20x Fable allowance + $1,031.92 in 48h with no alert or spend cap #85912 — independently reports eleven automatic recharges totaling USD 1,031.92 on August 1–2 from a separate Max/Cowork account, with no interactive Fable use alleged during those two days, no spend alert, and no human support response for nine days. It uses a different product surface and advances a different causal theory; it is pattern context, not proof of this account or a shared root cause.
• Later r/Anthropic report — alleges more than USD 480 in phantom usage and says Anthropic Support attributed multiple August 1 usage-credit top-ups within 31 minutes to an internal backend loop, with some transactions voided and others paid. The claimed support finding is not independently authenticated and is not an Anthropic admission concerning this account.
• Later r/ClaudeAI report — alleges Max 20x usage rose from 11% to 47% and then 100% in about 31 minutes while idle, followed by a Max invoice and an extra-usage auto-recharge invoice, with no human support response. It is an unverified third-party claim and does not prove this account's reset or payment chain.
• Fresh r/ClaudeCode spending-control report — alleges a USD 40 monthly overage cap was exceeded in two consecutive months; after a weekly limit was reached, three purchase-notification emails arrived within seconds and the purchased credits were already exhausted; a claimed human-support escalation then remained unanswered for about a month. No original transaction, setting, usage, or support records are authenticated here, so this is pattern context only—not proof of this account, a shared root cause, aggregate loss, or refund entitlement.
• [Bug] Claude Fable 5 model incorrectly draws from usage credits on Max 20x plan, on Claude code #83242 and [Bug] Fable model usage credit requirement on Max plan #84694 — later August 2 and August 7 reports that Claude Code told Max users Fable required usage credits. [Bug] Claude Fable 5 model incorrectly draws from usage credits on Max 20x plan, on Claude code #83242 says reauthentication cleared the gate. Neither report proves a paid-credit debit, automatic recharge, payment, this account's reset chain, or a shared root cause.
• [BUG] 5-hour quota consumption jumped ~15-20x starting 2026-08-08, persists (previously intermittent + self-resolving); multi-instance Claude Code usage #86033 and [BUG] Issue: Session (5hr) usage limit exhausted within minutes on a lightweight document-edit task #85992 — later August 12 reports, respectively, that a paid-plan five-hour quota began consuming about 15–20× faster than the reporter's prior baseline and that a five-hour session exhausted within 3–10 minutes of a confirmed full reset during lightweight work, reproduced twice. Neither report alleges an automatic purchase or payment, proves this account's August 1 reset/charge chain, or establishes a shared root cause.
• [BUG] July 17 mass billing incident: usage credits charged despite plan allowance; $604.71 automatic recharges disputed #81703 — the separate July 17 acknowledged usage-credit incident and unresolved refund record.

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 either disputed August 1 automatic recharge—USD 496.75 or USD 498.92—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 August 1 mapping, preservation, merchant-referral, case-status, and next-update questions pending.

On August 18, after the USD 15.26 merchant refund evidence was supplied, Stripe Complaints sent a response labelled final under the controlling Link case. It said that Stripe could not initiate a merchant refund and redirected the matter to Anthropic or a bank. The response did not acknowledge the documented USD 15.26 merchant refund action, identify what merchant instruction produced it, explain whether the USD 15.26 merchant action settled at the issuer, or provide a payment/refund/reversal disposition for either August 1 transaction. It also supplied no transaction-level answer for the six July 17 charges in the separate earlier component of the same fixed USD 1,600.38 complaint track.

Calling that answer final did not make it transaction-specific. A same-day reconsideration request listed all eight existing-track charges and required, for each one, current payment, refund, reversal, merchant-action, original-destination, safe-reference, and decision-basis fields. It also required confirmation that the separate Link/Stripe personal-data investigation remains open. This was an in-place response in the existing case, not a new complaint.

Stripe reaffirmed finality after the merchant-admission supplement

At 06:08 JST on August 19, in a reply received after the authenticated merchant-admission supplement, Stripe Complaints said it had reviewed the follow-up response and that its August 18 Final Response was firm. It said it would not engage further without additional information and again directed purchase and refund issues to Anthropic.

The reaffirmation still named neither August 1 transaction and none of the six July 17 transactions in the same existing complaint track. It did not acknowledge the USD 15.26 refund action that is now issuer verified, identify any merchant instruction, provide a current payment/refund/reversal position, supply a safe processor reference, or give a written decision basis for any of the eight rows. It confirmed no additional refund or reversal.

This is evidence of the complaint-handling state, not proof of liability or of what undisclosed processor records may contain. But calling the response firm and closing further same-fact engagement does not convert aggregate merchant routing into eight transaction-specific dispositions. No repetitive same-fact reply was sent. After the issuer-verified USD 15.26 partial refund, the August 1 balance is USD 980.41, the existing automatic-only track has USD 1,585.12 remaining, and the separate August 12 USD 99.08 incident remains outside this complaint response.

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. The August 1 incident has USD 980.41 unresolved; the complete existing automatic-only track has USD 1,585.12 unresolved. The separate August 12 USD 99.08 incident remains outside this issue's demand.

Environment

• Product/billing route: Claude Individual subscription with extra-usage credits
• Surface: Claude Code
• Payment method shown on the merchant documents: Link
• Region/timezone: Japan (JST)
• Claude Code version/model: not asserted in this public billing report because the current evidence set is transaction- and entitlement-focused

Machine-readable automatic-charge ledger

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

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

For this August 1 issue, use only track august1_post_reset: two automatic
rows totaling USD 995.67. The July 17 and August 12 tracks are not part of
this issue's demand. Manual purchases remain excluded. The reset sequence is a
customer observation; the payment records do not independently establish the
exact reset time or Anthropic's server-side entitlement and routing decision.

August 19 processor centralization update

After the post-admission firm response described above, 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 step
did not supply a new complaint reference, refund, reversal, merchant action,
safe processor reference, or transaction-level decision.

Across the eight-row existing complaint matrix, Stripe's firm response still
named 0 of 8 transactions and filled 0 of 56 required row fields. The
closure is procedural routing only; it does not close or resolve the underlying
refund demand, and no duplicate reply was sent.

No additional original-payment refund beyond the issuer-verified USD 15.26
has been verified. The August 1 incident has USD 980.41 unresolved; the
complete existing July 17-plus-August 1 track has USD 1,585.12 unresolved.
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/august-1-evidence-chain.html

[COOLak]

Evidence-chain update: originals delivered privately to Link and Anthropic

All four original merchant PDFs for the two disputed transactions have now been
delivered through both relevant authenticated written channels:

• the controlling correct-account Link support case; and
• Anthropic's written support route, copied to its notices address.

The originals establish two successful Auto recharge extra usage, Individual plan transactions of USD 496.75 and USD 498.92, totaling USD
995.67. They identify Link as the payment method. They are automatic
recharges, not manual top-ups.

The customer-observed sequence remains: included limits reset before the first
recharge, Claude Code continued consuming usage credits, two automatic
recharges completed, and credit depletion continued until usage credits were
disabled after the second charge.

Evidence boundary: the payment records prove the transactions and amounts;
they do not independently prove the exact reset timestamp or Anthropic's
server-side entitlement and routing decision. Anthropic controls the missing
subscription-entitlement, limit-bucket, reset, model/feature-gate,
request-routing, usage-credit-debit, auto-recharge-trigger, invoice,
authorization, correction, and refund records.

Privacy-sanitized evidence chain and proof matrix:

https://coolak.github.io/anthropic-claude-billing-incident/august-1-evidence-chain.html

No private invoice, receipt, card, account, support-case, or email identifier is
published there. Dual delivery establishes evidence availability, not
acknowledgment, fault admission, refund approval, or settlement.

Independent-verification gap

Anthropic's help article says customers should see a notification when the
included session limit is reached, that the Usage dashboard clearly
distinguishes included-plan usage from paid-credit consumption, that limits
reset every five hours, and that usage credits do not change reset timing.

The public record does not yet expose a stable event-level key joining the
applicable subscription entitlement and reset bucket to a Claude Code request,
paid-credit debit, auto-recharge trigger, invoice, payment, and any correction.
The updated proof matrix therefore distinguishes:

• the two payment objects and amounts, which the originals prove;
• the reset-to-credit-drain sequence, which remains an account observation;
  and
• the missing full-chain join, which only Anthropic can supply.

Anthropic should provide a safe reconciliation key or signed mapping that an
independent reviewer can verify without exposing card or account identifiers.

The requested remedy is unchanged: refund the full USD 995.67 to the
original payment method or methods, assign a human Billing Platform /
payment-operations owner, provide a transaction-level written reconciliation,
and prevent automatic recharges while entitlement and included-limit state
disagree. No original-payment refund or human Anthropic billing decision has
been confirmed.

Public redacted transaction evidence

A privacy-redacted raster sheet now exposes only the line-item and total regions
of the two original Anthropic invoices:

https://coolak.github.io/anthropic-claude-billing-incident/august-1-redacted-payment-excerpts.png

The visible invoice text identifies both objects as Auto recharge extra usage, Individual plan and shows USD 496.75 and USD 498.92, totaling USD
995.67. The raster contains no invoice, receipt, payment, account, contact, or
address identifiers, and it has no hidden PDF text or reversible overlay.

This materially strengthens public verification of the two automatic-recharge
objects and amounts. It still does not prove the reset timestamp,
request-routing decision, paid-credit debit cause, fault, or refund entitlement;
those remain within Anthropic's entitlement and billing records. The requested
original-payment refund and full-chain reconciliation are unchanged.

Private local activity timestamp bridge

A privacy-redacted scan of the local Claude Code record for August 1 JST adds
a time-correlation layer without publishing prompts, responses, raw IDs,
credentials, account data, or filesystem paths:

• 2,545 JSONL files / 1,059,231 lines scanned;
• 6,482 raw response-usage records;
• 2,860 deduplicated records after removing 3,622 duplicate copies; and
• 0 parse errors.

The nearest deduplicated response-usage records bracket the first receipt-email
delivery by 17.757 seconds before and 7.494 seconds after, and the second by
9.731 seconds before and 6.312 seconds after. This establishes
contemporaneous Claude Code activity across both receipt deliveries.

Evidence boundary: receipt-email delivery is not the exact payment,
credit-debit, or auto-recharge-trigger timestamp. The local schema exposes
response usage counters but no field for included-plan headroom or reset
bucket, paid-credit classification, usage-credit balance transition,
auto-recharge trigger, invoice/payment join, or provider-billed dollars. The
local record therefore does not prove that the bracketed responses caused the
transactions or independently prove the reported reset state.

This narrows the missing join rather than filling it: Anthropic should map the
bounded local activity to its subscription-entitlement, limit-reset,
request-routing, paid-credit-debit, recharge, invoice, payment, correction, and
refund records using a privacy-safe reconciliation key.

Formal Stripe/Link complaint status

A formal written complaint has now been sent through Stripe's published
complaint route with all sixteen original invoice and receipt PDFs covering the
eight automatic Claude Individual-plan extra-usage transactions currently
quantified across July 17 and August 1.

Stripe Support acknowledged receipt one minute after submission and said it
would be in touch. That acknowledgment proves complaint intake only. It is
not an investigation result, fault finding, refund approval, reversal,
settlement, or final complaint decision. No substantive Stripe/Link decision or
refund has been confirmed.

The combined automatic-only refund demand is USD 1,600.38: USD 604.71
for July 17 plus USD 995.67 for August 1. The separate July 17 manual
purchase is excluded, potentially related adjacent-date transactions remain
unquantified, and no bank or card chargeback has been filed.

Stripe's Link terms generally place responsibility for product or service
refunds with the merchant. The formal complaint therefore asks Link/Stripe to
preserve the transaction mappings, refer the evidence to Anthropic where
appropriate, and provide a written transaction-by-transaction disposition. It
does not allege that Stripe caused Anthropic's entitlement or routing behavior.

Public evidence and proof boundary:

https://coolak.github.io/anthropic-claude-billing-incident/august-1-evidence-chain.html

Stripe's published Japan complaint route:

https://stripe.com/en-jp/complaints

Independent near-date public signal

A separate r/Anthropic post published July 30 reports an Opus 4.6 Claude Code
session at approximately 25% of its session limit and 44% of its weekly
limit while a small prompt allegedly consumed USD 4.60 in paid usage
credits. The poster says the transition occurred without the usual
limit-reached notification and that Claude Code would not continue when usage
credits were disabled. The poster repeatedly states that the session was Opus
4.6 rather than Fable:

https://www.reddit.com/r/Anthropic/comments/1vaywsv/why_is_claude_using_usage_credits_when_i_havent/

This is an unverified third-party public report. It does not prove this
account's reset timestamp, payments, or root cause. Its limited relevance is
that it independently alleges the same observable class of
included-limit-versus-paid-credit mismatch on the day immediately preceding
the disputed August 1 recharges and on a non-Fable model.

Anthropic's official status page currently says No incidents reported for
August 1. That is an official-record gap, not proof that no account-level
billing or entitlement defect occurred. The page does not provide this
account's entitlement, routing, debit, or payment ledger:

https://status.claude.com/

Additional near-date public pattern signals

Three more separate July 24-30 public reports describe nearby observable
patterns that are relevant to the requested entitlement-and-billing audit:

• A July 27 Max-plan user reported usage increasing again after a session reset
  while the account was allegedly idle, enabled auto-reload charges of
  approximately USD 60 every few hours, and an automated support response
  that initially declined a refund request:
  https://www.reddit.com/r/Claude_reports/comments/1v81ons/rclaudeai_has_anyone_noticed_claude_max_usage/
• A July 30 commenter reported Max usage decreasing without active use and
  allegedly exhausting the full Max allowance in about half an hour, while
  the support bot suggested purchasing usage credits and required extended
  interaction before routing a bug report:
  https://www.reddit.com/r/ClaudeAI/comments/1v86ls8/comment/p03r5rt/
• A July 24 commenter on Anthropic's promotional-credit rollout said accepting
  the credit appeared to enable paid-credit spending, exceed subscription
  limits, and consume roughly half the promotional balance without warning:
  https://www.reddit.com/r/Anthropic/comments/1v1pid7/comment/oypda3o/

These are unverified third-party public reports, not proof of this account,
a common root cause, or aggregate loss. Their limited relevance is that they
independently allege post-reset or idle usage growth, rapid paid-plan depletion,
automatic reloads, and paid-credit behavior without the expected warning or
support remedy during the week surrounding the disputed August 1 transactions.

The proof matrix and source boundaries are consolidated here:

https://coolak.github.io/anthropic-claude-billing-incident/august-1-evidence-chain.html

The requested remedy and evidence boundary are unchanged: refund USD 995.67
for the separate August 1 incident, preserve the server-side entitlement and
billing records, and provide the safe event-level mapping needed to determine
whether these reports are related.