[Billing][Bug] Two Individual-plan auto-recharges completed (USD 99.08); Auto-reload off at post-charge capture

Preflight checklist

• [x] I searched the tracker. Prior reports include the closed/locked disabled-Auto-reload report #14857, the closed extra-usage re-enable report #25647, the open consumer auto-recharge-loop thread #68773, and the closed API/prepaid-credit reports #29108 and #53292. The latter two concern credit drain after an API-key/session event, not completed Claude Individual automatic purchase objects. I found no active dedicated issue for this new two-transaction sequence.
• [x] This is one bug: automatic Claude Individual credit purchases completed after the customer had disabled Auto-reload.
• [x] This is separate from my July 17 entitlement-routing issue #81703 and August 1 post-reset issue #83062.
• [x] I am using Claude Code 2.1.228.

What's wrong?

Two completed Anthropic merchant invoice/receipt pairs document automatic Claude Individual credit purchases of:

• USD 49.88 — receipt email delivered 2026-08-12 05:13:57 JST;
• USD 49.20 — receipt email delivered 2026-08-12 05:56:55 JST; and
• USD 99.08 total.

Both merchant-document pairs describe the line item as Auto-recharge credits. These are Claude Individual subscription-account extra-usage purchases, not manual top-ups and not Console/API-workspace invoices.

I had disabled Auto-reload before both transactions. A signed-in Claude Billing screenshot captured at 2026-08-12 06:20 JST, about 24 minutes after the second receipt email arrived, shows the Auto-reload row with a Turn on button. That proves the customer-facing control was off when captured.

Evidence boundary: the post-charge screenshot does not independently prove the earlier disable timestamp or the setting state at each internal recharge trigger. Anthropic controls the historical setting-change, configuration-version, queue, threshold-evaluation, authorization, capture, retry, and refund logs required to establish that sequence.

Customer-visible processor correlation

Read-only customer-visible Stripe hosted-invoice records independently map each merchant-document pair to a distinct successful payment chain:

| Amount | Payment object created (JST) | Invoice-payment state |
| --- | --- | --- |
| USD 49.88 | 2026-08-12 05:12:29 | Paid at 05:12:32 |
| USD 49.20 | 2026-08-12 05:55:28 | Paid at 05:55:30 |

Both chains use the same card-type Stripe payment-method object. The private Stripe invoice, PaymentIntent, invoice-payment, and payment-method identifiers are withheld publicly but have been supplied in the existing Anthropic, Link, and Stripe complaint threads.

Evidence boundary: these records prove two successful paid processor chains and provide transaction-level correlation. They do not prove the Auto-reload setting at either trigger, explain why Anthropic created the purchases, or establish whether the charges were correct. Anthropic controls the historical configuration, queue, threshold, trigger, and merchant-side refund records.

Authenticated pre-charge email record

An authenticated Claude email delivered on 2026-07-27 16:00:22 UTC (2026-07-28 01:00:22 JST) has the exact Subject header “We turned off auto-reload on your Claude Code account.” The first-party sender domain passed DKIM, SPF, and DMARC.

The body does not repeat or confirm that setting-change statement. Instead, it describes the July 17 billing correction and USD 3.11 account credit. The Subject header is therefore first-party, pre-charge evidence consistent with the reported setting state, but the subject/body mismatch prevents treating the message as conclusive proof of the disable action or persistence through the August 12 triggers.

A Gmail search covering July 26 through August 12 found no later Anthropic email stating that Claude Auto-reload had been enabled. Absence of such an email is not proof that no re-enable event occurred, because Anthropic's notification behavior is not established. Anthropic should reconcile this message with its authoritative setting-change and billing-worker logs.

Anthropic's documented control model

Anthropic's current paid-plan usage-credit guide describes these as usage credits for paid Claude plans, says Auto-reload can be enabled to make an automatic purchase when the balance falls below a customer-set threshold, and lists Auto-reload settings as a spending control. The guide also says usage credits apply to Claude Code.

The same guide separately says that disabling usage credits restricts the account to included-plan usage, that included limits continue to reset every five hours, and that paid credits do not change that reset timing. It also says the dashboard distinguishes included-plan use from paid-credit use and that a notification and confirmation precede the switch to paid credits.

Auto-reload and usage-credit access are distinct controls in Anthropic's own model: Auto-reload governs automatic funding of the credit balance, while usage-credit access governs whether an available paid balance may be consumed. This report alleges that Auto-reload was off; it does not allege that the separate usage-credit-access control was off.

That first-party guide establishes the intended customer control model; it does not establish this account's historical toggle state or disclose what happens to already queued work after the control is turned off. Those facts still require Anthropic's timestamped configuration and trigger records.

After the second charge, I blocked the funding card to prevent further automatic withdrawals. This was a protective action, not an allegation of stolen credentials and not a chargeback.

Official written 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:49 JST, the dedicated Anthropic Gmail thread for this standalone incident contained five customer-sent messages and no Anthropic reply: one initial blank transmission followed by four substantive written messages carrying the complete evidence notice, the authenticated pre-charge email supplement, the standalone FTC intake update, and the private processor-correlation supplement. No named human billing owner, separate later-incident case reference, 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. A disabled Auto-reload setting must prevent creation or execution of every new automatic purchase.
2. Disabling Auto-reload must atomically cancel or invalidate queued recharge work that has not yet been authorized and captured.
3. The setting UI and the billing worker must use the same authoritative, versioned configuration state.
4. Anthropic should preserve and reconcile the setting-change, configuration, recharge-trigger, queue, threshold, debit, authorization, capture, retry, invoice, and refund records for both transactions.
5. Anthropic should refund USD 49.88 and USD 49.20, totaling USD 99.08, to the original payment method.
6. Anthropic should state the exact timestamp/source of the last disable action and the internal trigger time and configuration version used for each automatic purchase.

Observed sequence

1. Auto-reload was disabled in the Claude Billing settings.
2. Two automatic credit purchases nevertheless completed and generated original merchant invoices and receipts.
3. Twenty-four minutes after the second receipt email, the signed-in Billing page displayed Auto-reload as off via the Turn on button.
4. The funding card was blocked to stop further automatic withdrawals.

This is account-ledger and server-side billing-worker behavior. I cannot reproduce Anthropic's internal trigger decision locally; the exact transition requires Anthropic's historical configuration and payment records.

Issue #68773 is a broader open thread about a consumer auto-recharge loop and support escalation. This report is narrower: the disabled-control invariant, two exact completed purchase objects, and the historical configuration/trigger records needed to reconcile them. The closest closed reports explicitly direct users to open a new issue if the problem remains relevant.

Later public corroboration (separate account, unverified)

A current r/claude report concerning August 9-10 transactions alleges that Extra Usage re-enabled itself twice and that a customer-set spend cap reverted to USD 20,000 after the reporter turned Extra Usage off and reset the cap. The thread includes several other unexpected re-enablement or charge allegations, while other commenters raise account or session compromise as an alternative explanation.

The post shows a list of paid transactions but does not supply original merchant or processor records, historical configuration logs, or Anthropic trigger records. It is a separate user anecdote, not proof of this account state, a common cause, aggregate loss, or refund entitlement. It reinforces the request for immutable, timestamped configuration, session, trigger, and purchase logs.

Fresh separate Usage Credits-off report

A fresh separate r/claude report says Usage Credits were off and alleges that 17 individual charges nevertheless appeared, typically in the EUR 40–50 range. The post reproduces text attributed to Fin saying that a pre-request limit check followed by final token accounting might explain minor overage, but not that repeated-charge pattern, and that a human account-level billing investigation was needed. The same post also reproduces an earlier no-compensation statement.

This is the reporter's public account, not an authenticated support transcript, original merchant record, processor record, or proof that any refund was refused by a human reviewer. Usage Credits and Auto-reload are different controls in Anthropic's documented model. The report does not establish which control state existed at any trigger, prove this account's historical Auto-reload state, show a shared root cause, verify the reported charge count or amounts, establish aggregate loss, or create refund entitlement here. It is relevant only as a fresh public example in which Fin's reported response itself distinguishes minor overage from a repeated-charge sequence and calls for the same human transaction-level investigation requested here.

Environment

• Claude Code: 2.1.228
• Plan/billing platform: Claude Individual subscription and its extra-usage-credit system
• Billing classification: subscription account, not Console/API workspace
• OS: macOS 26.6.1
• Date observed: August 12, 2026 JST

Public-safe evidence

Privacy-sanitized transaction summary, disabled-state screenshot, and proof boundary:

https://coolak.github.io/anthropic-claude-billing-incident/august-12-disabled-auto-reload.html

The public image contains no name, email, address, invoice number, receipt number, card digits, account identifier, or support identifier. The original screenshot, both invoices, and both receipts have been delivered privately to Anthropic and through formal processor/regulator routes.

Independent editorial citation

Future Stack Reviews added a dated August 12 update to its document-first July
17 report that cites this issue by number and title and records the two reported
amounts:

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

The publication expressly says that it did not reproduce or verify this event,
holds no record of the account, and takes no position on whether the charges
were correct. It also preserves the same proof boundary stated here: the
post-charge screenshot does not establish the setting state at either internal
purchase trigger, and Anthropic controls the historical records needed to
settle that point.

This is independent editorial citation of a visible public report. It is not
an Anthropic response, account-level verification, fault finding, refund
approval, or evidence that the report represents more than one account.

Written escalation status

As of August 12, 2026 JST:

• Anthropic received a complete written merchant notice with the signed-in disabled-state capture and both original invoice/receipt pairs.
• Stripe accepted the standalone formal complaint. Anthropic, Link, and Stripe then received the exact private processor mappings in their existing complaint threads, with requests for transaction-by-transaction disposition and refund to the original payment method.
• The existing Link human complaint channel received one routing supplement requesting a distinct reference for this later incident while preserving the earlier dispute unchanged.
• The California Department of Financial Protection and Innovation received one later-conduct evidence supplement.
• One standalone FTC ReportFraud filing for this USD 99.08 incident was accepted and entered Consumer Sentinel. The report number is withheld from this public issue.
• One application covering only this separate USD 99.08 event was sent through Japan's official Specified Commercial Transactions Act Article 60 procedure. This is filing status only, not an agency finding or refund decision.

No original-payment refund, transaction-by-transaction reconciliation, or separate later-incident case reference has been verified. These are verified submission/intake facts, not an agency finding, processor conclusion, investigation confirmation, individual-refund decision, or proof of the historical setting state.

Latest authenticated Link support movement

On August 15 JST, authenticated Link Support confirmed that its written support case and personal-data investigation remained open and that both disputed August 12 payments were visible to its team. Its initial purchase list also included unrelated purchases and omitted the eight automatic transactions in the separate earlier dispute track; one written scope correction preserved the two-track boundary.

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 that its written support case would remain open. One concise same-thread response kept the unanswered Link-controlled case-status, mapping, preservation, merchant-referral, and next-update questions pending.

This is procedural routing only. It is not a refund, reversal, transaction-by-transaction disposition, final complaint response, or proof of the historical Auto-reload state. The two references in Link's subject both pre-date this August 12 incident and do not establish a distinct later-incident reference. 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. Verified original-payment refunds on this standalone August 12 track remain USD 0.00.

August 18 refund-document boundary — different track, no August 12 settlement

On August 18, Anthropic documented a USD 15.26 original-route refund action
against a different automatic transaction in the separate August 1 incident.
It does not map to either the USD 49.88 or USD 49.20 payment in this
issue. No private transaction identifier is needed in this public boundary.

Anthropic's refund memo describes a hosted-Claude billing-impact window ending
August 11. The card issuer now verifies that separate USD 15.26 original-payment
refund on the August 1 row. It does not establish the historical Auto-reload
state or the disposition of either August 12 recharge here.

Issuer-settled refunds for this standalone incident remain USD 0.00, and its
unresolved amount remains USD 99.08. The standalone Stripe complaint remains
acknowledged but has no verified final response, transaction-by-transaction
disposition, refund, or reversal. The separate issuer-verified August 1 refund
does not reduce this issue's demand; it reduces only the earlier track once,
from USD 1,600.38 original to USD 1,585.12 remaining.

Separate dispute boundary

This later disabled-Auto-reload incident is a separate USD 99.08 demand. It does not alter the earlier automatic-only track in #81703 and #83062: USD 1,600.38 original, USD 15.26 returned, and USD 1,585.12 remaining. Manual prepaid purchases remain excluded. The figures must not be merged or substituted.

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 the August 12 disabled-Auto-reload issue, use only track
august12_post_charge_capture: two automatic rows totaling USD 99.08. The
July 17 and August 1 tracks are not part of this issue's demand. Manual
purchases remain excluded. The post-charge capture does not independently
establish the Auto-reload setting at either internal recharge-trigger time.

August 19 fix-versus-trigger proof gap and merchant demand

Anthropic's authenticated billing-correction notice says that a different bug
affected some cloud-hosted Claude Code and Cowork sessions from July 24 through
August 11 and was fixed on August 12. The notice names neither automatic
payment in this issue and supplies neither the exact fix-deployment time nor
either internal recharge-trigger time.

The notice therefore does not establish whether either trigger preceded or
followed the claimed fix, does not establish the Auto-reload setting at either
trigger, and does not establish the cause, refund, or reversal status of the
USD 49.88 and USD 49.20 payments.

One reply in the existing merchant-support thread requested return of both
amounts to the original payment method and asked Anthropic for the exact fix
deployment time, both recharge-trigger times, each trigger's before-or-after
relationship to the fix, the relevant setting-state records, and a row-level
disposition for both payments. That records the requested remedy and missing
evidence; it is not a merchant response or proof of a refund.

No original-payment refund or reversal has been verified for either row. The
post-charge screenshot still proves only that Auto-reload was off when captured
after the charges, not the earlier disable time or the setting at either
internal trigger. This standalone demand remains exactly USD 99.08 and
remains separate from the earlier July 17-plus-August 1 track.

Privacy-safe current record:
https://coolak.github.io/anthropic-claude-billing-incident/august-12-disabled-auto-reload.html