Skip to content

[BUG] [BUG] Billing: extra usage charged during acknowledged July 17 config error — compensation issued as unusable credit, refund to payment method requested (EU) #81869

Description

@Pinkashtray0

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Anthropic has acknowledged in writing that a configuration error on July 17, 2026
caused Claude usage to be billed to usage credits instead of counting against
included plan usage. My account was affected. The compensation offered is a
credit I structurally cannot use, so the incorrect charge remains uncorrected in
economic terms.

Per the notification email I received from Anthropic:

  • Incident window: July 17, 2026, 18:16–18:47 UTC (~30 minutes)
  • Cause: a configuration error routing usage to usage credits instead of the
    plan's included weekly usage
  • Acknowledged as resolved as of 18:47 UTC on July 17
  • Compensation: EUR 3.91, stated to be twice the amount incorrectly billed,
    which implies the erroneous charge was approximately EUR 1.96

Why the compensation does not resolve the issue:

  • The correction credit is only consumed when usage exceeds included plan limits.
  • I have held approximately USD 100 in extra usage balance, purchased with real
    money, for about a year. I have not consumed a single cent of it. I do not
    exceed my plan limits in normal use.
  • Therefore the EUR 3.91 credit will, with high probability, expire unused on
    July 21, 2027.

The practical result: real money was taken due to an error Anthropic has
admitted, and the remedy is a voucher against a service I demonstrably do not
consume. That is not restitution. A remedy that only materialises if the
customer spends more money is not a remedy.

Related prior reports of extra usage being charged while plan capacity remained:
#32544, #29579, #27603, #45497.

What Should Happen?

  1. Refund the incorrectly charged amount (~EUR 1.96) to the original payment
    method, promptly, rather than as account credit.

  2. Do not condition the remedy on any future purchase or on any future
    consumption of extra usage. Whatever is acceptable practice in other
    jurisdictions, in the EU an amount charged in error is owed back in the form
    in which it was taken. I am an EU consumer and this is not negotiable from my
    side.

  3. Confirm the expiry date of my existing purchased extra usage balance
    (~USD 100, entirely unused). If those funds are subject to a 12-month expiry,
    state the exact date and whether an extension is possible. If purchased
    credits are allowed to lapse unused while the account remains active and in
    good standing, that is a separate and considerably larger problem than the one
    in this report.

  4. Route this to a human reviewer. Multiple prior reports ([BUG] Bug: Extra Usage charged despite available plan capacity + false rate limit errors in Claude Code #32544, [BUG] #45497)
    document the support chatbot acknowledging billing errors in writing with no
    human follow-up.

Error Messages/Logs

Subject: Claude — July 2026 billing correction

A billing error briefly affected how some Claude usage was billed on July 17.
It's been resolved, and a credit has already been added to your account.

What happened
On July 17, 2026, between 18:16 and 18:47 UTC (about 30 minutes), a
configuration error caused some Claude usage to be billed to usage credits
instead of counting against your plan's included weekly usage. If you were using
Claude during that time, you may have seen a notice that Claude was temporarily
available with usage credits only. The issue has been resolved, and included
usage limits have worked as intended since 18:47 UTC on July 17.

What's been done
A credit of EUR 3.91 has been added to your account. It appears as "Claude Extra
Usage Credit — July 2026 Billing Correction", is available to use now, and
doesn't expire until July 21, 2027. Where your account was affected during the
incident window, this credit is set at twice the amount that was billed
incorrectly. The credit applies automatically before any usage credits are
charged, and will appear on your July billing statement on or around
August 1, 2026.

Steps to Reproduce

  1. Hold an active paid Claude plan with included weekly usage remaining.
  2. Hold a separately purchased extra usage balance (~USD 100 in my case).
  3. Use Claude on July 17, 2026 between 18:16 and 18:47 UTC.
  4. Usage is billed against usage credits instead of the plan's included weekly
    allocation, despite plan capacity being available.
  5. Anthropic issues a correction as account credit (EUR 3.91) rather than a
    refund to the payment method.
  6. The credit is unusable for any customer who does not exceed plan limits, and
    expires July 21, 2027.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

N/A

Claude Code Version

N/A - billing issue not CLI

Platform

Other

Operating System

Other

Terminal/Shell

Other

Additional Information

Filing here because Anthropic routes claude.ai billing issues to this repo
(see #45662, #45497, #23674). Anthropic's consumer support is handled primarily
by a chatbot with no documented escalation path to a human agent, and prior
reports show billing errors acknowledged in writing with no human follow-up.

Account details:

  • Plan: <<Pro / Max 5x / Max 20x>>
  • Account region: EU
  • Compensation credit reference: "Claude Extra Usage Credit — July 2026 Billing Correction"

This is a small amount. I am raising it because the principle — an admitted
billing error remedied only in a currency the affected customer cannot spend —
scales badly, and because the same pattern recurs across multiple open issues on
this tracker.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions