Account reactivated without instruction after cancellation, then charged twice; further charge attempts continuing

Status Closed — not planned
Maintainer reply None cached
Activity 1 comment · opened Sep 8, 2026 · closed Sep 11, 2026

Preflight Checklist

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

What's Wrong?

I cancelled a Max 20x subscription. The billing page correctly showed it as cancelled with an end date, and automatic credit top-up was switched off.

During the run-out period before that end date, the subscription status flipped from cancelled back to active on its own. Each time it flipped, a usage credit charge followed. This happened more than once.

On 4 September 2026 that produced two charges of GBP 630 within minutes of each other. On 8 September a further attempt to charge GBP 2,400 to the same card failed, described in the notification email as a repeat attempt.

I never resubscribed, never re-enabled top-up, and never bought credits.

Four separate support conversations over four days. Every one ended with the bot saying it had passed the case to a human. No human has ever replied.

The billing page offers no way to remove a stored card, only to replace it, so there is no way to stop further attempts from the account side.

What Should Happen?

A cancelled subscription with automatic top-up disabled should not reactivate itself, and no charge should be raised against the stored card. A stored card should be removable from the billing page.

Error Messages/Logs

Steps to Reproduce

  1. Subscribe to Max 20x.
  2. Cancel it. The billing page shows the cancellation and an end date in the future.
  3. Confirm automatic credit top-up is switched off.
  4. During the run-out period before the end date, the status changes from cancelled back to active without any action from me.
  5. A usage credit charge follows the status change.
  6. Steps 4 and 5 repeat.

I cannot reproduce this on demand; it happens with no action from me. On 4 September 2026 it produced two charges of GBP 630 minutes apart, and on 8 September a GBP 2,400 attempt that the bank declined.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.46388.4

Platform

Other

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

This may be related to the 17 July 2026 usage-credit routing incident, but the unrequested reactivation appears to be a separate problem. UK business account, Max plan, card payment.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗