Adding related public context because this is another usage-credit control / billing-ledger reconciliation problem: account controls appear to say one thing, while runtime behavior and credit consumption can move through another path.
My current case is a different surface, but it points at the same ownership gap:
manual Claude usage-credit prepaid / discounted purchase attempts fail or fail to commit cleanly;
automatic usage-credit top-ups on the same paid Claude billing account continue charging successfully;
user-visible billing/payment state and usable credit / account-control state diverge;
automated support routing has not produced a human Billing Platform / payment-operations owner who can reconcile checkout, payment confirmation, account controls, runtime billing mode, spend limits, and credit-ledger provisioning end-to-end.
I am intentionally not posting card digits, bank names, payment IDs, invoice IDs, support IDs, screenshots, raw network logs, private support-thread text, or other private account data here. The useful ask is for Anthropic Billing Platform / payment operations to inspect usage-credit enablement state, account controls, spend limits, runtime billing-mode selection, purchase/commit state, and credit-ledger provisioning together instead of treating these as isolated user-side or generic card/browser issues.
zac343· 2 months ago
The missing evidence here is a local run timeline for the narrow July 15 incident window. A useful reconstruction would:
group Claude Code assistant fragments by request ID so retries are not double-counted;
mark the first model change after the update/commit action, including any actual Fable records versus the intended Opus model;
separate main-session usage from sidechain/background work;
list cache read/write, input/output, failure state, and elapsed time for each abnormal request; and
compare those local timestamps with the usage-credit dashboard and invoice timestamps.
That can show whether a runaway request, hidden fallback, or background branch preceded the charge. It cannot prove that Anthropic re-enabled Usage Credits or reconcile the internal billing ledger; that part still requires Anthropic's billing telemetry.
The analysis is free. A private support-ready evidence pack is optional and costs 1 native USDC on Base Mainnet. No account credentials or raw logs are requested.
Related Claude Code issues
Matched on shared title terms, labels, topic and reported release — ranked so issues with
real discussion come first.
3 Comments
Seconding this. Noticed this too
Adding related public context because this is another usage-credit control / billing-ledger reconciliation problem: account controls appear to say one thing, while runtime behavior and credit consumption can move through another path.
My current case is a different surface, but it points at the same ownership gap:
Public, privacy-sanitized evidence hub:
https://coolak.github.io/anthropic-claude-billing-incident/
Billing reconciliation matrix / owner map:
https://coolak.github.io/anthropic-claude-billing-incident/reconciliation-matrix.html
I am intentionally not posting card digits, bank names, payment IDs, invoice IDs, support IDs, screenshots, raw network logs, private support-thread text, or other private account data here. The useful ask is for Anthropic Billing Platform / payment operations to inspect usage-credit enablement state, account controls, spend limits, runtime billing-mode selection, purchase/commit state, and credit-ledger provisioning together instead of treating these as isolated user-side or generic card/browser issues.
The missing evidence here is a local run timeline for the narrow July 15 incident window. A useful reconstruction would:
That can show whether a runaway request, hidden fallback, or background branch preceded the charge. It cannot prove that Anthropic re-enabled Usage Credits or reconcile the internal billing ledger; that part still requires Anthropic's billing telemetry.
I maintain a browser-local Claude Code audit that performs that request/model/sidechain reconstruction from a selected
.claude/projectsfolder without uploading prompts or logs: https://mailcheck.agentcartai.com/tools/agent-cost-auditor/?platform=claude-code&utm_source=github&utm_medium=issue_comment&utm_campaign=claude_code_runaway_billing_78772The analysis is free. A private support-ready evidence pack is optional and costs 1 native USDC on Base Mainnet. No account credentials or raw logs are requested.