[BUG] illing bug: Max 5x upgrade does not trigger payment attempt while Max 20x works on same card

Resolved 💬 3 comments Opened May 13, 2026 by edsilva-collab Closed May 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?

Bug description

Upgrading from Pro to Max 5x produces no payment attempt (no charge, no error,
no feedback). Upgrading to Max 20x on the same account, same card, same
session works normally.

## Reproduction

  1. Logged into Pro account
  2. Navigate to https://claude.ai/settings/billing
  3. Click "Upgrade to Max 5x"
  4. Complete checkout — no charge attempt registered on card statement
  5. Repeat with "Upgrade to Max 20x" — works immediately

## Expected
Both tiers should trigger payment attempts equally.

## Environment

  • Browser: [Chrome/Safari/etc + versão]
  • OS: [seu OS]
  • Region: Brazil
  • Account tier: Pro

## Already tried

  • Incognito mode
  • Different browser
  • Different network
  • Support ticket #[número do ticket da Etapa 4]

## Impact
Cannot upgrade to the tier I actually want; forced to either pay 4x more (20x)
or stay on Pro.

What Should Happen?

I'm experiencing a reproducible billing bug when trying to upgrade my plan:

  • Current plan: Pro
  • Account email: edwaneder@gmail.com
  • Attempted upgrade: Pro → Max 5x → FAILS (no charge attempt appears in my

card statement, no error shown)

  • Tested alternative: Pro → Max 20x → WORKS (charge attempt appears normally

on the same card)

Since the SAME payment method works for the 20x tier but produces zero charge
attempt for the 5x tier, this rules out a card/bank issue and points to a bug
in the Max 5x checkout flow or a flag on my account.

Troubleshooting already performed on my end:

  • Tried incognito window
  • Tried different browser
  • Disabled extensions
  • Tried different network

I have already contacted support previously without resolution. Please
escalate this to the billing engineering team and check:

  1. Server-side logs for my account's Max 5x upgrade attempts (timestamps

available on request)

  1. Whether there is an account-level flag blocking the 5x tier
  2. Payment gateway routing differences between the 5x and 20x SKUs

I'd like to subscribe to Max 5x specifically — the 20x tier exceeds my needs.

Thank you,

Error Messages/Logs

Pagamento falhou. Por favor, tente novamente mais tarde. Se o problema persistir, entre em contato com o suporte em https://support.anthropic.com/

Steps to Reproduce

I'm experiencing a reproducible billing bug when trying to upgrade my plan:

  • Current plan: Pro
  • Account email: edwaneder@gmail.com
  • Attempted upgrade: Pro → Max 5x → FAILS (no charge attempt appears in my

card statement, no error shown)

  • Tested alternative: Pro → Max 20x → WORKS (charge attempt appears normally

on the same card)

Since the SAME payment method works for the 20x tier but produces zero charge
attempt for the 5x tier, this rules out a card/bank issue and points to a bug
in the Max 5x checkout flow or a flag on my account.

Troubleshooting already performed on my end:

  • Tried incognito window
  • Tried different browser
  • Disabled extensions
  • Tried different network

I have already contacted support previously without resolution. Please
escalate this to the billing engineering team and check:

  1. Server-side logs for my account's Max 5x upgrade attempts (timestamps

available on request)

  1. Whether there is an account-level flag blocking the 5x tier
  2. Payment gateway routing differences between the 5x and 20x SKUs

I'd like to subscribe to Max 5x specifically — the 20x tier exceeds my needs.

Thank you,

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

max

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

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