Affected-user evidence checklist

Check your entire July 17 usage-credit ledger.

Count every invoice, auto-reload, manual purchase, correction, and included-plan entitlement state. Share aggregate impact—not private identifiers.

Updated: 2026-07-28 02:32 JST
Privacy-safe workflow
Full day, not only 30 minutes

Why Check the Entire Day?

Anthropic's official incident record says users across Claude.ai, Claude Code, and other surfaces were erroneously required to use usage credits for an included model.

At least one affected account later received a correction limited to 18:16-18:47 UTC, but its seven invoices dated July 17 total $704.71. The customer never claimed that the problem lasted only 30 minutes. A full-day review is necessary before treating a narrow automated credit as complete reconciliation.

Private Worksheet

Complete this locally. Do not post the private identifiers.

FieldYour value
Number of invoices dated July 17
Number of automatic recharges
Total automatic-recharge amount
Number of manual usage-credit purchases
Total manual-purchase amount
Total billed on July 17
Automated correction/account credit received
Remaining amount requiring reconciliation
Did included-plan usage continue after extra usage was disabled?
Human billing owner assigned?

remaining amount = July 17 total billed - refund to payment method - account credit you accept as correction

Keep cash refunds and account credits separate. Record the expiration date of any account credit.

Evidence Collection

  1. Save every invoice or receipt dated July 17.
  2. Save the matching card-statement entries.
  3. Save Anthropic's incident-correction email and note its selected time window.
  4. Export or capture plan-usage indicators and reset times if available.
  5. Record when extra usage and auto-reload were disabled.
  6. Record whether Claude Code continued working under included plan limits afterward.
  7. Preserve the complete support conversation and its conversation ID privately.
  8. Record each support message's date, read state, responder type, and promised action.

Transaction-Level Questions for Anthropic

For every July 17 debit, ask Anthropic to identify:

  1. the exact timestamp;
  2. the model and surface involved;
  3. the applicable included-plan entitlement and remaining allowance;
  4. the event that routed usage to paid credits;
  5. the resulting usage-credit debit;
  6. the auto-reload threshold and trigger event;
  7. the invoice or receipt created; and
  8. the correction, refund, or reason Anthropic claims the charge was valid.

Distinguish These Outcomes

  • Refund to original payment method: money returned through the original payment rail.
  • Account credit: a balance usable only with Anthropic, potentially expiring.
  • Ledger correction: reversal or adjustment of an incorrect usage-credit debit.
  • Explanation only: not a financial correction.
  • Narrow incident-window credit: may leave the rest of July 17 unreconciled.

Public-Safe Reporting

Helpful aggregate facts:

  • invoice count and total billed;
  • number and total of auto-reloads;
  • amount and form of any correction;
  • whether included-plan work continued after extra usage was disabled; and
  • whether a human billing owner completed a full-day audit.

Do not publish: invoice numbers, support IDs, account email, card or bank details, private screenshots, one-time codes, payment links, or complete private support transcripts.

Add Your Aggregate Result

State only the aggregate facts needed to establish impact. Provide supporting records privately to Anthropic, a regulator, a card issuer, legal counsel, or a reporter.

Related Resources

Privacy Boundary

This checklist is an evidence-preservation and reconciliation guide, not legal advice. Keep private identifiers out of public posts and review any regulator or payment-dispute filing personally before submission.