Privacy-sanitized public incident brief

Anthropic returned USD 15.26 of USD 1,600.38. The remaining USD 1,585.12 covers eight Claude Individual extra-usage charges.

Corrected September 3, 2026: authenticated Claude Platform billing and API usage records established that the former USD 99.08 claim involved genuine Platform/API credit grants. That claim is withdrawn and Platform charges are excluded.

July 17 scope note: The disputed amount remains $604.71. The affected period may potentially extend to earlier dates and July 18, but that has not yet been established; adjacent-date charges remain outside the current total unless Anthropic's transaction-level records connect them to the same incident.

Updated: 2026-09-03
Status: registered by bank; pending review
Scope: Claude Individual-plan extra usage — not API workspace billing

Reporter-ready automatic-charge reconciliation

The corrected active dispute covers the July 17 and August 1 Claude Individual extra-usage incidents only. Eight charges total USD 1,600.38; USD 15.26 was returned; USD 1,585.12 remains. Platform/API grants and manual purchases are excluded.

Disputed periodAutomatic rechargesVerified amountReturned to original payment methodsScope boundary
July 176USD 604.71USD 0.00Entire-day claim; separate USD 100 manual purchase excluded
August 12USD 995.67USD 15.26Partial refund on one USD 498.92 charge; USD 980.41 remains
Existing automatic-only track8USD 1,600.38USD 15.26USD 1,585.12 remains; manual top-ups excluded
Claude Platform/API grants3ExcludedN/AUSD 49.88, USD 49.20, and USD 45.28 are genuine Platform/API funding

Issuer-dispute submission status: on August 20, 2026, a signed chargeback request was sent to the card-issuing bank. On August 21, the bank confirmed registration and forwarding to responsible staff. A September 3 clarification corrects the scope to eight charges and USD 1,585.12 remaining; it is prepared only as a draft and has not been sent. Formal acceptance, a merits decision, and Mastercard routing remain unconfirmed.

Verified partial refund: Anthropic returned USD 15.26 on one August 1 automatic charge originally totaling USD 498.92. The same charge still has USD 483.66 unresolved. The other seven active disputed charges remain entirely unresolved.

Authenticated Anthropic billing-bug admission: A first-party Claude email delivered August 19 JST 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 identifies USD 15.26 in affected usage-credit charges and describes USD 30.52 in total remediation: the original-charge refund plus an additional USD 15.26 account usage credit. Only the original-route USD 15.26 counts as a verified payment refund. The account credit is not money returned to the payment method. Anthropic still has not mapped the calculation to both August 1 invoices or disposed of the remaining USD 980.41. The stated window does not cover July 17. The former August Platform-grant claim was withdrawn on September 3.

Latest processor-complaint response: on August 18, Stripe Complaints labelled its response under the controlling Link case final while giving no transaction-specific disposition for any of the eight charges in the USD 1,600.38 track and not addressing the documented USD 15.26 partial refund. After Anthropic's authenticated billing-bug notice was supplied, Stripe said it had reviewed the follow-up and that its Final Response remained firm. The response still named 0 of 8 transactions and filled 0 of 56 requested 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. Read the privacy-sanitized status.

Anthropic also added a USD 3.11 expiring account credit for its own 30-minute July 17 interval. That credit is not money returned to an original payment method and is not included in the verified USD 15.26 refund total.

September 3 correction: the earlier USD 99.08 FTC and Japanese filings were based on the same mistaken product classification and are being corrected. No refund is sought for the three confirmed Platform/API grants.

Evidence boundary: original WUIURKUV merchant records establish the eight active Individual extra-usage purchase objects and amounts. Authenticated Claude Platform billing and API usage records control the exclusion of the XEEZTIBR Platform grants.

Open the Platform-charge correction → · Open corrected issue #85937 → · Open the August 1 evidence chain → · Open the July 17 reporter brief →

Corrected Claude Individual extra-usage dispute: USD 1,600.38 original, USD 15.26 returned, and USD 1,585.12 remaining.

Download machine-readable eight-transaction JSON · Download corrected share-card PNG · Accessible SVG

Correction: August Platform charges withdrawn

Authenticated Claude Platform billing history and API usage records established that the USD 49.88 and USD 49.20 entries were genuine Platform/API credit grants. The USD 99.08 refund demand is withdrawn.

A later USD 45.28 Platform credit grant is also genuine API funding and was never added to the dispute. The earlier consumer-facing screenshot came from a different credit surface and did not establish the Platform billing classification.

Read the full correction → · Read corrected issue #85937 →

New Separate Case: August 1 Post-Reset Auto-Recharges

Two successful automatic extra-usage recharges totaling USD 995.67 were documented after the customer observed that the Claude Individual subscription's included limits had reset. Anthropic has now returned only USD 15.26; USD 980.41 remains unresolved on this incident.

Open the dedicated Anthropic tracker →

Inspect the August 1 evidence chain and proof boundary →

Open the standalone August 1 X evidence post →

Open the standalone August 1 LinkedIn evidence post →

Customer-observed August 1 sequence: limits reset, credits kept draining, and two automatic Claude Individual-plan recharges totaled USD 995.67; merchant transactions proven and Anthropic ledger join missing.

Privacy-redacted raster excerpts from two original Anthropic invoices showing automatic Individual-plan extra-usage line items of USD 496.75 and USD 498.92, with no invoice, receipt, payment, account, contact, or address identifiers visible.

The raster excerpts expose only the invoice line-item and total regions, so there is no hidden PDF text or reversible overlay. They strengthen public verification of the two automatic-recharge objects and amounts, but do not prove the reset timestamp or server-side routing decision.

The original merchant documents identify the transactions as Auto recharge extra usage, Individual plan, show Link as the payment method, and establish amounts of USD 496.75 and USD 498.92. They are automatic recharges, not manual top-ups. Their private invoice, receipt, card, account, and support identifiers are intentionally omitted here.

All four originals have now been delivered privately through the controlling correct-account Link support case and through Anthropic's written support route. That establishes evidence availability, not acknowledgment, fault admission, refund approval, or settlement. Private case and message identifiers remain withheld.

Formal processor-complaint status: a complaint was sent through Stripe's published route with all sixteen originals covering the eight quantified consumer transactions across July 17 and August 1. Stripe acknowledged receipt one minute later. That proves intake only—not an investigation result, refund approval, reversal, settlement, or final decision. The corrected original dispute is USD 1,600.38; manual purchases and Platform/API grants are excluded. The issuer request was registered and forwarded to responsible staff; a September 3 clarification correcting it to eight charges and USD 1,585.12 remaining is prepared as a draft and has not been sent. Formal acceptance, a merits decision, and Mastercard routing remain unconfirmed.

Stripe's Link terms generally place merchant product or service refunds with the merchant. The complaint targets Link's handling, evidence preservation, merchant referral, and written transaction disposition; it does not allege that Stripe caused Anthropic's entitlement or routing behavior. For Japan residents, Link's published contracting-entity page identifies Stripe Technology Company, Limited.

Anthropic's usage-credit documentation says credits apply after included plan limits are reached, that included session limits reset every five hours, and that usage credits do not affect reset timing. The payment documents prove the recharges; the precise reset time and server-side routing decision remain account-level claims requiring Anthropic's entitlement, limit-bucket, request-routing, usage-credit-ledger, auto-recharge-trigger, invoice, and payment records.

Two same-day Anthropic tracker reports, #83036 and #83037, separately describe usage-credit or credit-block behavior despite visible plan allowance. A third report, #83093, alleges that an Apple-billed Max 20x subscription was marked canceled in Anthropic's OAuth profile immediately before credits_required errors. These are independently inspectable public reports, not proof of this customer's payment path, the reporters' underlying account status, or a shared root cause.

This August 1 total is separately quantified and does not replace or alter the July 17 disputed amount.

New Standalone Case: July 17 Mass Billing Incident

This is distinct from the discounted manual-credit purchase failure. Anthropic's official status incident acknowledged an erroneous usage-credit requirement across Claude surfaces. Anthropic later added a $3.11 account credit for 18:16–18:47 UTC, but the customer never claimed the problem lasted only 30 minutes. Six automatic-recharge invoices dated July 17 total $604.71; a separate $100 manual purchase is excluded. Disabling extra usage and auto-reload allowed continued work on included plan limits.

Time-stamped first-party record: neutral Wayback captures preserve Anthropic's paid-plan usage-credit guide, Fable 5 plan article, and direct July 17 incident page as captured on August 13 JST. They preserve Anthropic's published control and plan-inclusion context plus its own erroneous-requirement statement; they do not prove this account's request-to-charge mapping or refund entitlement.

Open the dedicated Anthropic tracker →

Read the July 17 incident brief →

Inspect the public-safe July 17 receipt timeline →

Inspect the 2,177-record request-window audit →

Inspect the public report matrix →

Inspect the Anthropic-owned GitHub issue cluster →

Customer evidence summary showing $604.71 in six disputed July 17 automatic recharges versus a $3.11 account credit; manual purchase excluded.

A July 7–18 receipt reconstruction also 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 outside the current $604.71 demand unless transaction-level evidence connects them to the same incident.

All seven receipt bodies say Paid July 17, but the $100 manual purchase is excluded from the $604.71 automatic-recharge refund demand. Their Gmail delivery timestamps span 18h 47m 50s. One manual-purchase receipt arrived before Anthropic's 18:16–18:47 UTC correction window, one automatic-recharge receipt during it, and five automatic-recharge receipts after it. Email delivery time is not the internal debit timestamp; the timeline demonstrates why Anthropic must produce the complete transaction ledger rather than limiting reconciliation to one interval.

A separately verified, privacy-redacted local request-metadata inventory contains 2,177 deduplicated July 17 records: 1,241 before Anthropic's interval, 29 inside it, and 907 after it. That puts 2,148 records (98.67%) and 97.74% of the four recorded usage counters outside the selected interval. This proves day-spanning local activity, not provider-billed dollars or request-to-charge causation. Read the audit and its limitations →

Six July 17 automatic-recharge receipts totaling $604.71 say Payment method Link. A later human review under the correct Gmail-authenticated Link account located all six transactions and supplied their card-network/last-four and timestamp/status mappings privately. This proves traceability of the wallet debits, not Anthropic's entitlement/routing decision, recharge trigger, incident causation, or refund entitlement. Link stated that the PaymentIntent and charge identifiers remain merchant-side details for Anthropic to retrieve. Read the corrected privacy-sanitized processor update →

Anthropic's public documentation says usage credits apply after included limits and that transitions to API credit usage require consent. Portkey's public logging documentation covers requests, models, tokens, costs, and raw request/response records. The documented boundary supports a narrow inference: external telemetry can evidence consumption, but only Anthropic's internal entitlement and billing-routing ledger can decide whether included usage was incorrectly charged to paid credits. Read the sourced technical update →

Future Stack Reviews' independent Tier C, document-first analysis separately examines the July 17 public record. It distinguishes Anthropic's roughly 30-minute selectability statement from the roughly 71-minute status incident, returning usage credits from returning cash, and a remediation announcement from proof of completed correction. The outlet did not reproduce the incident, holds no account record from the incident window, and could not verify an account-level debit or refund entitlement. It therefore does not verify this customer's $604.71 ledger or refund claim; it independently sharpens the public-record questions that Anthropic's full-day internal records must resolve.

Official support route versus observed state: Anthropic's current support guide says paid Pro and Max subscribers have Fin plus Product Support assistance, that matters requiring additional investigation are passed onward, and that a person responds by email. It also says Anthropic offers no phone or live-chat support. As of 2026-08-13 00:20 JST, the controlling July formal-dispute Gmail thread contained 11 customer-sent messages and no Anthropic reply, with no named human billing owner, transaction-by-transaction disposition, or original-payment refund present. This is observed mailbox state, not proof of Anthropic's internal review state or a specific response deadline.

Metronome's February 2025 company announcement publicly names Anthropic among companies relying on its billing platform. Its August 2025 correction guidance describes full-state repair across usage, invoices, credit ledgers, reporting, dashboards, and threshold logic, with timestamped audit records. This does not prove that Metronome handles Claude consumer usage credits or caused this incident; it establishes a directly relevant public correction standard and an existing Anthropic relationship. Read the caveated provider-relationship update →

Download share-card PNG · Accessible SVG

Contemporaneous public reports include a nine-issue Anthropic-owned tracker burst in 67 minutes, unexpected Anthropic card notifications, usage credits reaching 105%, claimed $50 and $100 usage-credit limits being consumed, separate reports of $200 and $287 consumed or lost, a 75% session / 11% weekly / credits-off case with about $8 reportedly spent, and a Max 20x case that reportedly burned credits at only 8% five-hour / 3% weekly usage. The $200 poster separately said the credits had not returned after model access returned and alleged that Fin misrouted the debit-card credit complaint to Apple/iOS. These third-party reports corroborate the mass scope but are not proof of this customer's private ledger and must not be added into an aggregate loss total.

A separate Anthropic-owned tracker report filed August 11 and closed August 14 without planned action, labeled invalid because its reporter identifies a Claude.ai consumer-subscription issue rather than a Claude Code runtime bug, alleges a successful subscription charge while the account still showed Free, two unresolved duplicate subscription charges, and repeated Fin handoffs without restoration or refund. The automated tracker closure is a product-scope disposition, not a billing resolution. This is a separate customer's allegation and a different subscription-entitlement synchronization mechanism. It does not verify this account's automatic charges, a shared root cause, aggregate loss, or refund entitlement; private identifiers from the source report are intentionally omitted.

A second Anthropic-owned tracker report filed August 12 and closed August 15 without planned action, labeled invalid because its reporter identifies a Claude.ai account and billing problem rather than a Claude Code runtime bug, alleges that an active paid Pro account remained inaccessible for 28 days after an incomplete Team-upgrade flow, that at least one subscription invoice was issued during the lockout, and that more than 30 messages across five support threads produced no human response. The automated tracker closure is a product-scope disposition, not a billing resolution, refund, or account-level answer. This is another customer's allegation about a separate account-state and support-routing mechanism. It does not verify this account's automatic charges, Anthropic's internal handling of either account, a shared root cause, aggregate loss, or refund entitlement; private identifiers from the source report are intentionally omitted.

A separate Anthropic-owned tracker report closed without planned action alleges three consumer Max auto-recharge purchases totaling USD 2,196.17 and a further USD 1,865.81 in attempted charges blocked after card suspension. The reporter describes a chat-only account with Claude Code absent and no API keys, says Fin refused a human transfer and declined a refund without investigating the alleged cause, and reports Extra Usage and Auto-reload as off at the time of the post. That displayed control state is post-event and does not prove the historical setting or trigger state. No original merchant, processor, account, or support record is authenticated here. The automated closure and later lock are product-scope administration, not a billing resolution. This is a different account, date, and product surface; its claimed amounts are excluded from this customer's demands and arithmetic exposure, and it does not establish a shared root cause, aggregate loss, or refund entitlement. Private identifiers from the source report are intentionally omitted.

A fresh open Anthropic-owned tracker report filed August 13, currently labeled bug, has repro, platform:macos, area:cost, and area:agent-view, alleges that background Fable sessions on two Max accounts were gated to usage credits while interactive Fable sessions on the same accounts still used subscription allowance and the visible Fable weekly meter showed headroom. A recurrence comment reports the same background-session gate on version 2.1.232 while the account's Fable weekly meter showed 72% used and an interactive Fable session continued on subscription. These are the reporter's observations, not authenticated entitlement or billing records. The report describes a path-specific credit gate and does not document a completed charge. It is a separate reporter's allegation, not proof of this account's July 17 routing, automatic charges, a shared root cause, aggregate loss, or refund entitlement.

A newer open Anthropic-owned tracker report filed August 16, currently labeled bug, has repro, area:cost, and area:core, reports two separate byte-identical Claude Code session-start sidecar requests about 13 milliseconds apart. The reporter says a one-machine, one-day proxy capture found 75 duplicate pairs across 45 captures, 62 requests joined to completed usage records, and 24 duplicate streaks in which both members were billed. Those are the reporter's measurements, not an invoice audit: the issue gives no transaction amount, original-payment record, automatic-recharge record, or proof of this account's request-to-charge path. It is useful only as a distinct duplicate-request and usage-accounting allegation, not proof of a shared cause or refund entitlement here.

A separate open Anthropic-owned tracker report filed August 17, currently labeled bug, has repro, platform:macos, area:cost, and area:auth, reports Max-plan weekly and Fable meters depleting roughly 1.7–5 times faster after the August 17 reset despite a below-median workload. The reporter also found a plan-tier claim mismatch, but expressly states that correcting it did not fix the meter and does not establish causation. Two other GitHub participants then reported similarly abrupt or unexplained Fable usage. None of those posts documents a completed payment or automatic recharge, and none verifies this account, a common mechanism, aggregate loss, or refund entitlement.

A different GitHub participant later reported EUR 2,932.51 in charges from July 23–24 and no promised human support reply. That claim is unverified, is excluded from this customer's $604.71 July 17 ledger, and may be a distinct incident; it is preserved only as separately labeled later-date pattern context. Read the public report →

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 every demand here, and does not verify a shared root cause, aggregate loss, or refund entitlement. Read the public comment and source screenshots →

A separate open, bug-labeled Anthropic tracker issue 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 does not state the charge dates. It is unverified, excluded from this customer's $604.71 ledger, and does not establish the same date, mechanism, or root cause. Read issue #81941 →

X thread · Official-account escalation · Evidence card · Policy/source update · r/ClaudeCode · r/Anthropic · LinkedIn · Facebook

Separate archived issue: discounted manual-credit purchase failure

Scope wall: the material below preserves an older manual prepaid-credit checkout dispute. It is not evidence for, part of, or included in the July 17, August 1, or August 12 automatic-charge demands. The automatic-charge hub above and its three dedicated incident records are the current sources of truth for those disputes.

Open the separate archived reporter brief · Open its billing-owner action packet · Open its reconciliation matrix

Archived manual-purchase incident: what happened

A high-usage Claude customer cannot reliably complete manual prepaid usage-credit purchases through Anthropic's billing flow. The manual purchase path has failed or lost the advertised discounted bulk-credit checkout state. At the same time, automatic usage-credit top-ups from the same saved billing setup continue charging successfully.

Fails Manual prepaid credit purchase Manual prepaid usage-credit purchases fail or lose discounted checkout state on Anthropic's side.
Succeeds Automatic top-up charging Automatic usage-credit top-ups from the same saved billing setup continue charging successfully.
Unresolved Human billing ownership Support now points toward specialized billing-team review, but no named human Billing Platform owner or fix has been confirmed.

Latest Support Posture

After earlier generic card-decline guidance, a support-route readback at 2026-07-27 03:16 JST found one official support thread closed after generic card-decline bot guidance and a later thread where Fin acknowledged a billing-system technical contradiction, offered human connection, then created a new pending support conversation. No human Billing Platform / payment-operations owner, written explanation, credit reconciliation, refund, equivalent adjustment, or restored manual purchase path has been confirmed. The automated failed-payment sender route also bounced as address-not-found when used as an inbound escalation route.

Latest Public Route Refresh

Between 2026-07-26 22:37 and 2026-07-27 16:31 JST, existing Anthropic-owned GitHub comments were refreshed or extended in place with the 2026-07-26 22:26 JST support posture, later verified independent guide corroboration, including a newly verified Claude Code pricing-guide caveat, a fresh paid-account usage-meter/support-routing report, a session-limit / zero-token usage-meter mismatch report, a silent cross-account billing/auth route, a central billing-pattern anchor tying the guide corroboration to the #81116/#72552 route evidence, additional public Reddit payment-initiation / credit-ledger, invoice-lock, support-loop, gift-entitlement, and hidden billing-route reports, plus public upgrade-payment, paid-invoice/past-due, failed-payment-notification, refund-credit-state, large-billing-error, refund-window, known-billing-system-error/manual-intervention, mid-cycle-downgrade/double-charge, unauthorized-plan-mutation, gift-cancellation/redemption-failure, unauthorized-gift-charge/support-loss, support-loop reports, a new public X reply on a high-visibility official Claude launch thread, a directly relevant Facebook Claude Community billing/support-thread comment, newly added public subscription/extra-usage billing-mode reports, fresh Anthropic-owned cost-control comments covering visible-ledger/overage enforcement mismatch, wrong monthly-spend remediation, paid-work loss after spend-limit interruption, orphaned background-agent work after ambiguous limiter failures, recursive agent cost-burn guardrails, a fresh paid-tier allocation / weekly-limit reconciliation route, phantom-usage / idle quota-drain / usage-leak cost-control routes, a billing-source / scheduled API-key owner-route comment, a mid-session usage-credit gate owner-route comment, a false monthly-spend-limit owner-route comment, a billing-identity / limit-attribution owner-route comment, a usage-state / per-model weekly-limit owner-route comment, a usage-credit limit-enforcement / premature-completion owner-route comment, a session-wide premium-model billing-scope owner-route comment, a skill-loading / usage-window burn owner-route comment, an excessive Max-plan quota-burn owner-route comment, a usage-meter / limit-enforcement mismatch owner-route comment, a reset-window usage-limit mismatch owner-route comment, a no-use usage-window drain owner-route comment, a zero-meter weekly-limit lockout owner-route comment, a rapid weekly-limit spike owner-route comment, a zero-session-meter forced-credit-workaround owner-route comment, a bad-args 1000-agent fanout / cost-control owner-route comment, a cache-read metering / usage-meter owner-route comment, a cloud-review confirmation / cost-estimate owner-route comment, a workflow retry / duplicate usage owner-route comment, a subagent 1M-context / extra-usage entitlement owner-route comment, a task-scoped model-leakage / credit-exhaustion owner-route comment, a Max/Fable usage-credit gate owner-route comment, a Fable session-meter / usage-credit overflow owner-route comment, a Fable usage attribution / burn-rate owner-route comment, a Max entitlement / rate-limit owner-route comment, an org-seat entitlement / credit-prompt owner-route comment, and a central billing-pattern impact update for exact-match #80055 direct-credit-purchase failure, and the direct #80055 exact-match comment refreshed in place. These are public route/context records, not proof of private account state.

  • Central billing-pattern thread updated in place at 16:26 JST with today's #80055 public impact update, where the reporter says failed direct Anthropic credit purchasing forced a third-party workaround and capability loss, while retaining the request for a human Billing Platform / payment-operations reconciliation across checkout/payment confirmation, purchase commit, manual purchase versus auto-reload divergence, discount/prepaid-credit eligibility, credit-ledger posting, and support-case routing: anthropics/claude-code#55982 comment / #80055 impact update
  • Central billing-pattern thread updated in place at 15:47 JST with the latest #76427 Fable session-meter / usage-credit overflow and #67506 Fable usage attribution / burn-rate route evidence, while retaining the request for a human Billing Platform / payment-operations reconciliation across checkout/payment confirmation, purchase commit, discount eligibility, account controls, usage-ledger provisioning, and credit/cap restoration: anthropics/claude-code#55982 comment
  • Central billing-pattern thread updated again at 01:56 JST with the newly published public disappeared-credits and billing-transparency corroboration links, while retaining verified CrazyRouter/OpenClaw independent-guide corroboration plus #81116 session-limit / zero-token usage-meter and #72552 silent cross-account billing route evidence: anthropics/claude-code#55982 comment
  • Public X reply posted at 04:23 JST under the official Claude launch thread, tagging Anthropic with the sanitized manual-prepay-fails / auto-topups-work / no-billing-owner pattern and linking the public evidence hub: x.com/Coolak777/status/2081460261844828301
  • Facebook Claude Community billing/support-thread comment posted at 04:50 JST on a directly relevant public community thread, linking the sanitized hub and summarizing the manual prepaid-credit failure / auto-topups-work / no-billing-owner pattern: facebook.com/groups/claudecommunity/posts/1062395349634463/
  • Public Anthropic-owned subscription/extra-usage billing-mode reports added at 05:05 JST, covering claims that Max/Pro subscription usage or available plan quota can still drain Extra Usage or purchased credits despite subscription login or low plan usage: anthropics/claude-code#68501 and anthropics/claude-code#64613
  • Public Anthropic-owned cost-control route comments added at 05:26-05:38 JST, covering visible spend-ledger / overage enforcement disagreement, wrong monthly-spend-limit remediation for a different limiter, quota-consuming workflow interruption with no durable deliverable, ambiguous limiter errors that can leave background-agent work non-recoverable, and recursive agent fan-out without default spend guardrails: #39678 comment, #75730 comment, #79958 comment, #74006 comment, and #72732 comment
  • Public Anthropic-owned paid-tier allocation route comment added at 05:48 JST, covering a Max 5x to Max 20x upgrade allegedly not reflected in weekly limits and asking for Billing Platform / entitlement reconciliation: #79773 comment
  • Public Anthropic-owned phantom-usage / idle quota-drain / usage-leak route comments added at 11:57-12:06 JST, covering reports that paid Max usage can climb while idle or without visible activity logs, and asking for Billing Platform / cost-control / usage-accounting / agent-runtime owner reconciliation across server-side session lifecycle, quota debits, auto-reload triggers, phantom or orphaned work, and credit/cap restoration policy: #80199 comment and #80705 comment
  • Public Anthropic-owned billing-source / scheduled API-key route comment added at 12:17 JST, covering a Max subscriber silently routed from subscription billing to API billing for interactive and scheduled sessions, and asking for Billing Platform / entitlement / cost-control owner reconciliation across credential precedence, session billing source, scheduled execution, credit-ledger debits, subscription entitlement, and support routing: #78491 comment
  • Public Anthropic-owned mid-session usage-credit gate route comment added at 12:26 JST, covering Fable 5 becoming unusable mid-session with a usage-credit-required gate despite expected remaining access, and asking for Billing Platform / entitlement / usage-credit ledger owner reconciliation across model-access gates, subscription allowance, credit-ledger balance, manual purchase commit state, auto-reload state, session/runtime billing source, and support routing: #78614 comment
  • Public Anthropic-owned false monthly-spend-limit route comment added at 12:31 JST, covering a newly purchased subscription account blocked almost immediately by a monthly-spend-limit message after low reported usage, and asking for Billing Platform / entitlement / spend-limit owner reconciliation across subscription activation, spend-limit initialization, usage counters, credit-ledger balance, manual purchase commit state, auto-reload state, session/runtime billing source, and support routing: #79630 comment
  • Public Anthropic-owned billing-identity / limit-attribution route comment added at 12:36 JST, covering requests to show effective account/org/billing source and attribute limit messages to the right identity, and asking for Billing Platform / identity / entitlement / support-tooling owner reconciliation across credential precedence, account/org binding, session billing source, limit-message attribution, support-visible plan state, credit-ledger balance, manual purchase commit state, and auto-reload state: #77993 comment
  • Public Anthropic-owned usage-state / per-model weekly-limit route comment added at 12:45 JST, covering a dropped server-provided Fable weekly-scoped limit, contradictory local account flags, and another Claude surface showing the same limit correctly; asks for Billing Platform / usage-ledger / entitlement / Claude Code cost-surface owner reconciliation across server payloads, local cache, subscription flags, per-model limit buckets, reset windows, and support-visible state: #78507 comment
  • Public Anthropic-owned usage-credit limit-enforcement / premature-completion route comment added at 12:51 JST, covering a security scan reportedly exceeding configured usage-credit limits and reporting completion before usable work was finished; asks for Billing Platform / cost-control / usage-accounting / agent-runtime owner reconciliation across limit enforcement, workflow completion status, retry semantics, and credit/cap restoration policy: #80983 comment
  • Public Anthropic-owned session-wide premium-model billing-scope route comment added at 13:01 JST, covering Fable model selection reportedly applying to an entire session and billing routine turns at the premium rate without a clear confirmation boundary; asks for Billing Platform / cost-control / usage-accounting / Claude Code model-routing owner reconciliation across session-wide model changes, per-task routing, premium-rate confirmation UX, usage-ledger debits, and credit-review policy: #79478 comment
  • Public Anthropic-owned skill-loading / usage-window burn route comment added at 13:05 JST, covering a simple usage-limit/pricing question reportedly loading a very large bundled skill body and consuming disproportionate plan-window usage; asks for Billing Platform / cost-control / usage-accounting / Claude Code skill-loading owner reconciliation across skill trigger policy, deferred-loading behavior, usage-window accounting, and credit/usage-review policy: #79457 comment
  • Public Anthropic-owned excessive Max-plan quota-burn route comment added at 13:09 JST, covering Fable/Opus sessions reportedly consuming Max-plan quota much faster than the visible workload would suggest; asks for Billing Platform / cost-control / usage-accounting / Claude Code model-runtime owner reconciliation across model selection, session lifecycle, tool/subagent activity, cache behavior, quota debits, visible usage meters, and credit/usage-review policy: #78702 comment
  • Public Anthropic-owned usage-meter / limit-enforcement mismatch route comment added at 13:19 JST, covering a Max 5x report where Claude Code blocked input with Usage limit reached after roughly 35% weekly usage while Claude.ai web still worked on the same account; asks for Billing Platform / usage-ledger / entitlement / Claude Code limit-enforcement owner reconciliation across visible usage meters, enforcement gates, account/session billing source, credit-ledger state, and support-visible billing state: #78617 comment
  • Public Anthropic-owned reset-window usage-limit mismatch route comment added at 13:28 JST, covering a report where Claude Code said the user had hit a usage limit immediately after a session reset while the web surface showed a different state; asks for Billing Platform / usage-ledger / entitlement / Claude Code limit-enforcement owner reconciliation across reset-window state, web-vs-CLI usage state, local cache, enforcement gates, billing identity, credit-ledger state, and support-visible billing state: #78402 comment
  • Public Anthropic-owned no-use usage-window drain route comment added at 13:32 JST, covering a report where the 5-hour Claude Code usage window was reportedly consumed despite no same-day Claude Code use; asks for Billing Platform / usage-accounting / Claude Code runtime owner reconciliation across visible usage meters, server-side session lifecycle, account/session billing source, quota debits, credit-ledger state, enforcement gates, and support-visible billing state: #78087 comment
  • Public Anthropic-owned zero-meter weekly-limit lockout route comment added at 13:43 JST, covering a Max 20x report where Claude Code/Cowork enforced a weekly-limit block while visible weekly meters showed 0% and claude.ai web still worked on the same account; asks for Billing Platform / usage-ledger / entitlement / Claude Code limit-enforcement owner reconciliation across visible usage meters, hidden Claude Code-scoped limit buckets, reset-window state, account/session billing source, subscription entitlement, credit-ledger state, and support-visible billing state: #78982 comment
  • Public Anthropic-owned rapid weekly-limit spike route comment added at 13:53 JST, covering a report where weekly usage reportedly jumped from 98% to 100% faster than user activity would explain; asks for Billing Platform / usage-ledger / entitlement / Claude Code limit-enforcement owner reconciliation across visible weekly meters, hidden Claude Code-scoped counters, reset-window state, account/session billing identity, credit-ledger state, and support-visible state: #81245 comment
  • Public Anthropic-owned zero-session-meter / forced-credit-workaround route comment added at 14:04 JST, covering a Max 20x report where Claude Code enforced a usage-limit block while visible 5-hour session usage showed 0%, and the reporter said they had to purchase additional usage credits to work around the block; asks for Billing Platform / usage-ledger / entitlement / Claude Code limit-enforcement owner reconciliation across visible session meters, enforcement gates, subscription entitlement, account/session billing source, usage-credit ledger state, and refund/credit-restoration policy: #78352 comment
  • Public Anthropic-owned bad-args agent-fanout / cost-control route comment added at 14:16 JST, covering a report where a malformed workflow input triggered 1000 agent calls, burned 13M tokens, and hid an 800/1000 failure ratio behind a completion-shaped summary; asks for Billing Platform / cost-control / agent-runtime owner reconciliation across bad-args validation, agent fanout limits, non-retryable session-limit handling, token/credit debits, workflow completion semantics, and credit/cap restoration policy: #81351 comment
  • Public Anthropic-owned cache-read metering / usage-meter route comment added at 14:25 JST, covering a Max 20x report where transcript-level accounting after deduplication did not explain a 53% weekly quota drain unless cache-read or equivalent cached-context tokens were metered at a higher-than-expected weight; asks for Billing Platform / usage-ledger / cost-control owner reconciliation across per-request token categories, Max weekly and 5-hour limit weights, visible meters, hidden buckets, usage-credit debits, support-visible state, and credit/cap restoration policy: #81234 comment
  • Public Anthropic-owned cloud-review confirmation / cost-estimate route comment added at 14:41 JST, covering a report where a billed Claude Code cloud review launched from the CLI without the documented confirmation dialog, review scope, remaining free-run state, or estimated cost; asks for Billing Platform / cost-control / Claude Code cloud-review owner reconciliation across documented confirmation requirements, alias-specific CLI behavior, scope/cost estimate display, usage-credit debit timing, final charge attribution, support-visible state, and refund/credit-restoration policy: #77222 comment
  • Public Anthropic-owned workflow retry / duplicate usage route comment added at 14:51 JST, covering a report where a session-limit error was treated as retryable and subagents restarted cold from blank context, repeating completed work with no additional usable output; asks for Billing Platform / usage-accounting / cost-control / agent-runtime reconciliation across retry classification, duplicate-attempt attribution, repeated prompt/file-read/cache/tool tokens, artifact reuse, workflow preflight agent/model/cost confirmation, and refund/credit-restoration policy: #80253 comment
  • Public Anthropic-owned subagent 1M-context / extra-usage entitlement route comment added at 15:02 JST, covering a Max 20x report where Sonnet subagents, skills, and background agents appear to inherit a parent 1M-context request path and hit extra-usage / usage-credit gates even when the intended child work was standard 200K Sonnet; asks for Billing Platform / entitlement / cost-control / agent-runtime reconciliation across child context derivation, request-tier inheritance, failed admission-gate ledger treatment, extra-usage preflight, support-visible resolved model/context state, and credit/cap restoration policy: #68727 comment
  • Public Anthropic-owned task-scoped model-leakage / credit-exhaustion route comment added at 15:10 JST, covering a report where a Fable model request intended for one task allegedly became session-wide, drained usage credits, and hit an out-of-credits gate during compaction; asks for Billing Platform / cost-control / usage-accounting / model-routing reconciliation across per-task intent, persisted session model state, premium-rate confirmation, inherited turns/tools/subagents, ledger attribution, support-visible charge attribution, and credit/cap restoration policy: #79477 comment
  • Public Anthropic-owned Max/Fable usage-credit gate route comment added at 15:18 JST, covering a report where a paid Max account could not switch to Fable because Claude Code treated it as requiring usage credits; asks for Billing Platform / entitlement / model-routing reconciliation across Max-plan Fable entitlement state, client-side cached model access, standard included allowance vs extra-usage vs usage-credit-only path, account/org/billing identity, support-visible entitlement state, and credit/cap restoration policy: #80706 comment
  • Public Anthropic-owned Fable session-meter / usage-credit overflow route comment added at 15:30 JST, covering a report where Fable's dedicated 5-hour bar disappeared after reset while weekly Fable usage continued and overflow had already been billed to usage credits; asks for Billing Platform / usage-ledger / entitlement / Claude Code usage-UI reconciliation across Fable session-bucket lifecycle, generic session-bucket attribution, weekly Fable accounting, overflow debit trigger, hidden/stale meter state, support-visible ledger state, and credit/cap restoration policy: #76427 comment
  • Public Anthropic-owned Fable usage attribution / burn-rate route comment added at 15:47 JST, covering a long-running report where Fable-specific usage, delegated model work, background/session state, and usage-credit burn did not reconcile cleanly from user-visible counters; asks for Billing Platform / usage-ledger / entitlement / Claude Code runtime reconciliation across per-model attribution, background-agent lifecycle, Fable sub-cap accounting, usage-credit debit triggers, spend-limit gates, support-visible ledger state, and refund/credit-restoration policy: #67506 comment
  • Public Anthropic-owned Max entitlement / rate-limit route comment added at 15:52 JST, covering a long-running report where Claude Max subscription state and low visible usage still produced API rate-limit errors, with thread context discussing extra-usage/API-credit workarounds; asks for Billing Platform / entitlement / usage-ledger / rate-limit reconciliation across subscription recognition, server-side limiter state, visible usage counters, extra-usage/API-credit debit triggers, VS Code/CLI credential scope, account/org billing identity, support-visible state, and refund/credit-restoration policy: #29579 comment
  • Public Anthropic-owned org-seat entitlement / credit-prompt route comment added at 16:13 JST, covering a Team seat report where synced local entitlement state says hasAvailableSubscription: false and routes Claude Code toward credits / pay-as-you-go despite subscription entitlement; asks for Billing Platform / entitlement / auth-state reconciliation across org-seat vs personal subscription semantics, subscriptionType, model-access cache, CLI-vs-desktop entitlement divergence, credit-prompt gating, credential precedence, support-visible billing identity, ledger attribution, and refund/credit-restoration policy: #79671 comment
  • Independent Claude Code pricing-guide caveat verified at 04:10 JST: Dmytro Klymentiev's public guide now includes a billing-reliability caveat checked July 26, links Anthropic-owned tracker issues #73450, #56895, and #55982, says this is not a general outage, and advises users not to leave usage-credit top-ups until they are already blocked: klymentiev.com/blog/claude-code-pricing
  • Public Reddit billing/support-loop corroboration added at 02:13 JST, covering repeated emailed receipts absent from the Anthropic billing page, paid Max invoice state reverting to Free access, double-charged subscriptions with AI-support/refund friction, and unauthorized-upgrade/refund/account-disable claims; private identifiers from those threads are intentionally omitted here: random/repeated charge report, paid-Max downgraded-to-Free report, double-charged subscription report, and refund/account-disable support-loop report
  • Public Reddit usage-credit controls corroboration added at 02:26 JST, covering claims that promotional or free usage-credit claiming can interact with paid usage billing, spend-limit defaults, and unclear balance semantics; this is billing-control-surface context, not proof of this customer's private state: usage-credit controls warning
  • Public Reddit payment-initiation / credit-ledger corroboration added at 02:40 JST, covering API-credit purchase verification pages showing USD 0, top-up attempts charging $0 while balance remains zero, card declines where the bank reportedly saw no Anthropic attempts, paid extra-usage purchases not unlocking usage, usage-credit balances zeroing while $0 spent, and promotional credits disappearing after auto-billing hiccups; these are public pattern reports only: API-credit top-up $0 report, API-credit verification USD 0 report, card-decline / no-bank-attempt report, paid-extra-usage-not-unlocking report, usage-credit zeroed report, and promotional-credit disappearance report
  • Public Reddit billing-route / support-loop corroboration added at 02:54 JST, covering locked-credit/open-invoice payment failure with CVC-recollection checkout errors and Fin auto-closures, multi-card and wallet payment failures where an alternate higher-tier path reportedly succeeded, card/payment setup failures where banks reportedly saw no issue, gift subscriptions reverting to Free, extra-usage runtime errors despite visible usage/credit state, and hidden extra-usage billing-route reports; these are public pattern reports only: locked-credit invoice / CVC checkout report, multi-card wallet payment-failure workaround report, banks-see-no-issue payment setup report, gift subscription reverts-to-Free report, extra-usage runtime error despite visible state report, and hidden extra-usage billing-route report
  • Public Reddit and GitHub billing-state corroboration added at 03:10 JST, covering repeated upgrade payment failures after recurring-payment setup approval, Pro subscription payment-failure loops with trapped account credit and Fin handoff cycling, failed-payment email floods after a paid subscription and no reported API use, paid-invoice/past-due access mismatches despite paid invoices or additional Console credit, unexpected annual-plan charge/support-bot lockout reports, and official refund-link / redeemed-credit state transitions where credit or subscription payment allegedly did not reflect; these are public pattern reports only and private identifiers from source material are intentionally omitted here: upgrade payment failure after setup approval report, Pro payment loop / trapped credit report, failed-payment notification flood report, paid-invoice / past-due mismatch report, unexpected annual-plan charge support-loop report, and refund-link / credit-state transition report
  • Public Reddit large-billing-error / refund-routing corroboration added at 03:26 JST, covering a reported Anthropic-acknowledged large billing-system error with repeated bank charge attempts and automated escalation routing, plus a refund-window support-bot report that was later escalated to a person and refunded; these are public pattern reports only and private identifiers from source material are intentionally omitted here: large billing-system error / escalation-routing report and refund-window support-bot escalation report
  • Public GitHub known-billing-system-error / manual-intervention corroboration added at 03:36 JST, covering a public Anthropic-owned issue that reports support-bot acknowledgement of a known July 2026 billing-system error affecting multiple customers and a human-support statement that missing credits required investigation/manual intervention; this is public pattern evidence only and private identifiers from source material are intentionally omitted here: #77097 known billing-system error / manual-intervention issue
  • Public GitHub mid-cycle downgrade / unauthorized plan-mutation corroboration added at 03:44 JST, covering public Anthropic-owned issues that report paid accounts being downgraded or plan state mutating without intended user action, double-charge/refund friction, generated Gift Max invoices, and support-routing gaps; this is public pattern evidence only and private identifiers from source material are intentionally omitted here: #64557 mid-cycle downgrade / double-charge issue and #51168 unauthorized plan-mutation issue
  • Public GitHub free-plan downgrade / gift-cancellation / unauthorized gift-charge corroboration added at 03:49 JST, covering public Anthropic-owned issues that report paid Max accounts reverting to Free, gift subscriptions auto-canceling with broken redemption/credit links, unauthorized gift-subscription charges, disappeared support conversations, and extended support silence; this is public pattern evidence only and private identifiers from source material are intentionally omitted here: #41581 paid Max downgrade thread, #44163 gift cancellation / redemption failure issue, and #62461 unauthorized gift-charge / support-loss issue
  • Central billing-pattern thread updated in place at 04:10 JST with the verified Dmytro pricing-guide caveat plus the same #41581 / #44163 / #62461 paid-plan, gift-entitlement, and support-loss corroboration, while noting that public status still showed All Systems Operational at 03:59 JST and repeating the request for a human Billing Platform / payment-operations owner: anthropics/claude-code#55982 comment
  • Prepaid commit / zero-bank-auth thread refreshed at 22:37 JST: anthropics/claude-code#73450 comment
  • Banks-see-zero-attempts / support-routing thread refreshed at 22:40 JST: anthropics/claude-code#54055 comment
  • Fin auto-closes / organization-credit thread refreshed at 22:42 JST: anthropics/claude-code#80178 comment
  • Card-auth-succeeds / Anthropic-purchase-fails thread refreshed in place at 16:31 JST with today's #80055 public impact update and central anchor link: anthropics/claude-code#80055 comment / #80055 impact update / central anchor
  • Console Buy Credits path disabled / inconsistent billing-state thread refreshed at 22:51 JST: anthropics/claude-code#62644 comment
  • Payment-fails-across-cards / support-unresponsive thread refreshed at 22:57 JST: anthropics/claude-code#56281 comment
  • Balance-label / credit-ledger reconciliation thread added at 23:09 JST: anthropics/claude-code#67083 comment
  • Paid-plan usage-meter / reset-boundary / support-routing report linked at 23:36 JST: anthropics/claude-code#81366 comment
  • Session-limit / zero-token usage-meter mismatch linked at 00:44 JST: anthropics/claude-code#81116 comment
  • Silent cross-account billing / credential-resolution route linked at 00:57 JST: anthropics/claude-code#72552 comment

Historical Same-Method Account Lockout Evidence

A closed public Anthropic-owned issue from 2026-05-24 reports the same payment method being accepted on one Anthropic account while rejected on another, followed by Fin handoff to human support and no visible resolution before stale closure. This is public historical pattern context for account-level billing, risk, and support-routing divergence, not proof of private account state.

Same-Card Manual Payment / Paid-Entitlement Evidence

Additional open Anthropic-owned issues show the same failure family from two angles: card acceptance differs by billing path, and paid billing records can fail to map to usable Claude access. These links are public pattern context only, with private identifiers intentionally omitted.

  • Same card reportedly used for the regular monthly bill, but a manual payment attempt was declined and later led to an account-access disabled state: anthropics/claude-code#72178
  • Paid Max invoice/account-dashboard mismatch where support reportedly acknowledged backend synchronization without a public resolution timeline: anthropics/claude-code#71821
  • Paid Max invoice followed by a Free-plan state and support ticket submission, with private invoice details omitted here: anthropics/claude-code#68257

Post-Payment Access-Disabled Evidence

An open Anthropic-owned issue with cost, auth, and oncall labels reports payment/subscription activity followed by disabled Claude access, refund/support friction, and a long public thread of similar user reports. This is public pattern context only; this hub does not copy user emails, account identifiers, screenshots, appeal details, or invoice/payment identifiers from the thread.

  • Payment or renewal followed by disabled Claude/organization access and unresolved support-routing reports: anthropics/claude-code#5088
  • Paid Max account routed into account-creation/onboarding access failure after payment, while support reportedly auto-closed; author later reported an account-creation workaround, so this is historical account-state/support-routing evidence only and private receipt/email/account details are not copied here: anthropics/claude-code#51294

Why It Matters

Anthropic sells usage credits to customers who may depend on Claude for ongoing work. The issue is not merely that a card declined. The reported contradiction is that recurring automatic charging works while manual prepaid purchasing does not, and support has not resolved the account state or restored the discounted purchase path.

Short public summary

Anthropic / Claude manual prepaid usage-credit purchases fail or lose discounted checkout state, while automatic top-ups from the same saved billing setup continue charging successfully, and support has not produced a human billing owner or explanation.

Evidence Available Publicly

GitHub evidence hub Privacy-sanitized public brief and HTML incident page. GitHub evidence repository Indexable public archive with the current sanitized summary. Reporter brief One-page public brief with questions for Anthropic and resolution criteria. Billing owner action packet Concrete inspection checklist for Anthropic Billing Platform / payment operations. Billing reconciliation matrix Symptom-to-system matrix for payment, entitlement, credit-ledger, and support-routing review. GitHub billing-pattern issue Existing Anthropic repo issue comment updated with the evidence hub. GitHub banks-see-zero-attempts issue Related Anthropic repo comment on multiple-card payment failures and dead support routing. GitHub cloud-review consent issue Related Anthropic repo comment on billed cloud review launch without documented confirmation or cost estimate. GitHub workflow retry issue Related Anthropic repo comment on duplicate paid usage after session-limit retry behavior. GitHub subagent context issue Related Anthropic repo comment on 1M-context inheritance pushing standard subagents into extra-usage gates. GitHub model-scope billing issue Related Anthropic repo comment on task-scoped model selection becoming session-wide credit burn. GitHub Max/Fable gate issue Related Anthropic repo comment on Max-plan Fable selection being blocked behind usage credits. GitHub Fable meter issue Related Anthropic repo comment on hidden Fable session-meter state and usage-credit overflow. GitHub Fable attribution issue Related Anthropic repo comment on Fable usage attribution, background/session state, and burn-rate reconciliation. GitHub Max rate-limit issue Related Anthropic repo comment on Max entitlement, visible usage counters, and extra-usage/API-credit reconciliation. GitHub org-seat entitlement issue Related Anthropic repo comment on Team/org subscription entitlement, local account flags, model-access cache, and credit/pay-as-you-go prompt gating. Reddit evidence thread Public summary and updates in r/Anthropic. X thread Public escalation thread tagging relevant Anthropic accounts. X reply on official Claude thread High-visibility public reply linking the sanitized evidence hub. Facebook Claude Community thread Relevant public community thread where the sanitized evidence hub was linked. LinkedIn post Professional-network post summarizing the billing contradiction.

Public Documentation-Caveat Updates

To reduce misdiagnosis by users following third-party Anthropic API setup guides, privacy-sanitized documentation-caveat issues were filed where project docs tell users to purchase Anthropic credits or troubleshoot low-credit API errors. These links are route/context records, not proof of private account state.

Independent Buyer-Guidance Updates

Independent Claude/Anthropic guide sites have started adding public buyer-guidance caveats that separate manual credit purchases from automatic reloads. These public caveats were directly fetched and verified on 2026-07-26, with CrazyRouter reverified live and Dmytro Klymentiev's Claude Code pricing caveat verified live on 2026-07-27. They are public buyer-guidance context, not proof of private account state.

  • CrazyRouter Anthropic payment/billing guide, verified again at 2026-07-27 00:38 JST, includes a dedicated manual-prepaid-credit failure while auto-reload still works troubleshooting section and tells readers to check bank authorization attempts, document exact checkout evidence, and ask Anthropic support for billing/payment-operations escalation: crazyrouter.com/en/blog/anthropic-claude-api-payment-billing-guide-2026
  • Dmytro Klymentiev's Claude Code pricing guide, verified at 2026-07-27 04:10 JST, includes a billing-reliability caveat checked July 26 that links Anthropic-owned billing tracker issues and warns users not to leave usage-credit top-ups until already blocked: klymentiev.com/blog/claude-code-pricing
  • OpenClaw Launch guide warning readers to verify Anthropic one-time credit purchases and auto-reload separately before depending on direct Anthropic Console billing, verified at 2026-07-26 21:14 JST: openclawlaunch.com/guides/openclaw-anthropic
  • OpenClaw Launch managed-agents guide warning that Claude Console billing relies on prepaid credits and separate one-time purchase / automatic reload paths, verified at 2026-07-26 21:14 JST: openclawlaunch.com/guides/claude-managed-agents

Hidden Billing-Mode / Support-Routing Evidence

Additional public Anthropic-owned issues show that Claude account state, support-visible plan state, credential precedence, and model entitlement can diverge in ways that route paid users to usage credits or metered API billing. These links are pattern context, not proof of this customer's private account state.

Anthropic-Owned Related-Case Comments

Privacy-sanitized related-case comments were posted on open Anthropic-owned billing and usage-credit issues where the failure shape overlaps with manual credit purchasing, credit-ledger reconciliation, or support-routing failures. These links are public route/context records, not proof of private account state.

Unauthorized Upgrade / Refund Support-Routing Evidence

A newly refreshed public Anthropic-owned thread reports unauthorized Pro-to-Max upgrades, entitlement loss or account deletion during cancellation/refund flows, Fin acknowledgments that manual review is needed, and no reliable human escalation for some affected users. Latest public thread activity also describes a July 21 same-date cluster, phantom usage, and an automated refund path that may expose only residual cash rather than prepaid annual-plan credit. This is public pattern context, not proof of this customer's private account state.

Paid Invoice / Entitlement Sync Evidence

Additional open Anthropic-owned threads report paid invoices, active store subscriptions, or successful Max payments not mapping to usable Claude access. Public reports include account states stuck on Free or past_due, Claude Code subscription access blocked, and cancellation or support paths failing to reconcile backend state. This is pattern context for invoice/subscription/entitlement propagation, not proof of this customer's private records.

Related Public Reports

These public links do not prove this customer's private account state by themselves. They do show that Claude credit purchasing, credit posting, credit balance recognition, billing support, and support-response failures have appeared in other public user reports and Anthropic-adjacent venues.

Escalation Timeline

Claude Support / Fin and Anthropic support were contacted with privacy-sanitized billing-platform escalation requests. Earlier generic card-decline guidance was rebutted as non-resolution. The latest support posture points toward specialized billing-team review, and a direct human connection has been requested.
The attempted failed-payments email route bounced as no-such-user, so it should not be reused unless Anthropic verifies a correct address.
FTC ReportFraud, San Francisco DA consumer mediation, and San Francisco City Attorney business-practices routes were advanced. SF DA consumer mediation auto-replied that the mailbox is not checked daily.
Privacy-sanitized updates were posted on Reddit, X, and LinkedIn, focused on the manual-prepay-fails / auto-topup-works contradiction.
Distinct privacy-sanitized tips were sent to TechCrunch, The Verge, The Information, GeekWire, NBC News, and The Washington Post. The Information acknowledged receipt/review.

What Would Count As A Real Fix

  • A working manual prepaid usage-credit purchase path at the advertised discounted terms.
  • An equivalent credit or discount adjustment applied by Anthropic.
  • A written Billing Platform / payment-operations explanation of why manual prepay failed while auto-topups worked.
  • Assurance that the failed or stuck manual purchase state did not consume discount eligibility, create hidden payment debt, or penalize the account.
Privacy boundary

This public page omits card endings, bank names, payment processor IDs, invoice or receipt identifiers, raw logs, screenshots, payment URLs, one-time codes, private support-thread bodies, addresses, identity documents, document numbers, and FTC report number.

Automatic top-ups continuing to charge is not a fix. It is evidence that the billing platform can charge the account while the manual prepaid-credit path remains broken.