The Receipt Evidence
09:59:43
04:47:33
Public-Safe Timeline
| Receipt-email delivery (UTC) | Amount | Type | Relation to 18:16–18:47 |
|---|---|---|---|
| July 17 09:59:43 | $100.00 | One-time credit purchase | Before |
| July 17 18:33:49 | $97.12 | Automatic extra-usage recharge | Inside |
| July 17 19:51:34 | $108.46 | Automatic extra-usage recharge | After |
| July 17 21:08:28 | $95.21 | Automatic extra-usage recharge | After |
| July 17 21:48:33 | $101.05 | Automatic extra-usage recharge | After |
| July 17 22:50:04 | $97.51 | Automatic extra-usage recharge | After |
| July 18 04:47:33 | $105.36 | Automatic recharge; body says Paid July 17 | After |
| Total | $704.71 | Six automatic recharges + one purchase | $607.59 outside |
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
- The usage event or events that triggered each paid-credit debit.
- Included-plan entitlement immediately before each debit.
- The exact paid-credit debit and automatic-recharge trigger timestamps.
- Payment authorization, invoice creation, and receipt delivery timestamps.
- 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.