[BUG] Unable to complete claude team bill payment

[fl-udit]

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?

During the Claude Team subscription checkout, my browser session closed/timed out mid-payment. After the interrupted session, the account is now stuck in a broken state — the billing page shows no active subscription, but I am unable to attempt a new payment either.

Error message: No Stripe subscription found

What Should Happen?

• If a payment session is interrupted, the account should reset cleanly
• User should be able to re-attempt the subscription checkout without errors
• Alternatively, the UI should clearly indicate a pending/failed payment and offer a retry option

Error Messages/Logs

No Stripe subscription found

Steps to Reproduce

1. Navigate to claude.ai → Settings → Billing
2. Error: No Stripe subscription found — cannot proceed

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

latest

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

org id - 1e57b6e3-b62b-454d-b947-146aa71c8823

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] No stripe subscription found error , Payment invoice is showing access till 17th april 2026 #38127
2. [BUG] Gifted subscription expired, stuck state blocks new subscription purchase #43338
3. [Billing Bug] account_session_invalid on billing page – subscription paused 3 weeks #45086

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

Closing for now — this doesn't appear to be about Claude Code. Please open a new issue if this is still relevant.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.