[BUG] Critical: Unauthorized Charges After Downgrade + Repeated Billing Attempts

Resolved 💬 2 comments Opened Apr 13, 2026 by rajajmal Closed Apr 16, 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 am experiencing a critical billing issue where my card was charged and repeatedly targeted for payment attempts despite a confirmed subscription downgrade.

After downgrading from Max to Pro (effective April 13, 2026), the system still attempted multiple charges, including amounts that do not match any plan.

One incorrect charge of $100 was successfully deducted, and additional attempts (including $200) were made multiple times.

This behavior continued even after contacting support, with no human response received.

What Should Happen?

After a confirmed downgrade, no further billing attempts should occur beyond the valid billing cycle.

Charges should:

  • Match the correct subscription plan
  • Not retry aggressively after failures
  • Stop immediately if a downgrade is scheduled

Users should also receive timely human support for billing issues.

Error Messages/Logs

No application error logs.

Evidence available:
- Bank SMS notifications showing 6 charge attempts
- Invoice and billing history
- Downgrade confirmation email
- Support conversation logs

Can provide screenshots if needed.

Steps to Reproduce

  1. Subscribe to Max plan
  2. Request downgrade to Pro plan before billing cycle ends
  3. Wait for scheduled downgrade confirmation
  4. Observe billing behavior before renewal date

Result:
System attempts multiple charges (including incorrect amounts) despite downgrade confirmation.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.38

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗