Public-safe account evidence

Seven “Paid July 17” receipts. An 18h 47m 50s delivery span.

Anthropic corrected only 18:16–18:47 UTC. Seven receipt emails total $704.71 in the gross chronology, but the current $604.71 demand covers only six automatic recharges and excludes the $100 manual purchase.

Scope note: This is a Claude subscription / Individual-plan extra-usage-credit dispute, not Console or API-workspace billing. 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-08-12 JST
Refund status: unresolved
Private identifiers removed

The Receipt Evidence

7 receiptsEvery body says Paid July 17, 2026.
$604.71Six disputed automatic recharges; manual purchase excluded.
18h 47m 50sFirst-to-last mailbox delivery span.
83.9%$507.59 delivered after the official 19:43:35 resolution.
Anthropic 18:16–18:47 UTC
Jul 17
09:59:43
Jul 18
04:47:33
Receipt email outside Anthropic's window Receipt email inside Anthropic's window

Compared With Anthropic's Official Major-Incident Record

Anthropic's machine-readable status record classifies the July 17 incident as major, opening at 18:32:32 UTC and resolving at 19:43:35 UTC. The six disputed automatic-recharge receipt emails span 10h 13m 44s, from 18:33:49 UTC to 04:47:33 UTC the following day.

  • One automatic-recharge receipt email for $97.12 arrived during the official incident window.
  • Five automatic-recharge receipt emails totaling $507.59 arrived after Anthropic marked the incident resolved.
  • The first post-resolution receipt arrived 7m 58.533s after resolution; the final one arrived 9h 3m 57.533s after it.
  • The excluded $100.00 manual purchase arrived before the official incident and remains outside the refund demand.

Evidence boundary: receipt-email delivery time is not necessarily Anthropic's internal usage event, paid-credit debit, recharge trigger, authorization, or invoice-creation time. This comparison does not independently prove transaction-level causation; it shows why service resolution and a short automated correction do not reconcile the six-charge ledger.

Public-Safe Timeline

Receipt-email delivery (UTC) Amount Type Relation to 18:16–18:47
July 17 09:59:43$100.00One-time credit purchaseBefore
July 17 18:33:49$97.12Automatic extra-usage rechargeInside
July 17 19:51:34$108.46Automatic extra-usage rechargeAfter
July 17 21:08:28$95.21Automatic extra-usage rechargeAfter
July 17 21:48:33$101.05Automatic extra-usage rechargeAfter
July 17 22:50:04$97.51Automatic extra-usage rechargeAfter
July 18 04:47:33$105.36Automatic recharge; body says Paid July 17After
Gross chronology$704.71Six automatic recharges + one manual purchase$607.59 outside
Current refund demand$604.71Six automatic recharges; manual purchase excluded$507.59 after

Source: seven first-party Anthropic/Stripe receipt-email bodies and Gmail delivery timestamps. Receipt, invoice, payment-method, account, and support identifiers are intentionally omitted.

Critical Evidence Boundary

An email delivery timestamp is not necessarily the internal usage-credit debit, auto-recharge trigger, payment authorization, or invoice-creation timestamp. This page does not claim that an outside-window email proves incident causation by itself.

It does show why a correction limited to one 31-minute interval cannot reconcile the account's complete July 17 receipt set. Anthropic must produce its internal transaction timestamps and entitlement-routing ledger.

What Anthropic Must Reconcile

  1. The usage event or events that triggered each paid-credit debit.
  2. Included-plan entitlement immediately before each debit.
  3. The exact paid-credit debit and automatic-recharge trigger timestamps.
  4. Payment authorization, invoice creation, and receipt delivery timestamps.
  5. Whether each charge has been refunded to the original payment method.

Related Public Evidence

Public Discussion

The two Reddit links are existing incident posts edited in place to add this receipt timeline. No duplicate Reddit post or correction comment was created for this update.

Privacy Boundary

This timeline intentionally excludes receipt numbers, invoice numbers, payment-method details, account identifiers, download links, and private support text. Those records remain available only through a private verification channel.