[BUG] Claude Code login fails due to phantom unpaid invoice
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?
NOTE: I have attempted to use the AI support bot while logged in to my claude.ai account to resolve this issue several times, but it keeps giving me nonsense advice that ignores facts I have clearly articulated for it. I am filing this bug here because I don't see any other recourse.
This morning I opened up my work laptop and found my claude code sessions from last week still active. I picked up where I left off on a bug fix task on Friday and claude code was slopping along merrily for several minutes.
After several minutes of slopping to itself, it suddenly told me that I wasn't authorized and that I needed to run /login. I did this, pasted the auth URL it gave me into a browser, then clicked "Authorize" at which point I see the following in the web browser:
<img width="337" height="297" alt="Image" src="https://github.com/user-attachments/assets/36965767-be0c-4b13-8e79-efe06b651c36" />
However, when I navigate to Settings > Billing I can clearly see that all of my invoices are paid. The most recent dated Feb 26 which covers the period between Feb 26, 2026 and Mar 26, 2026, is paid. I can see the corresponding credit card transaction in my bank account dated Feb 28. Today is March 10, 2026 and I have been using my account since Feb 26 with no problem.
There is no invoice to pay. All of my invoices have been paid. There is no other recourse for me than to post here hoping it gets through the inevitable LLM filter that Anthropic is slopping at users like me.
What Should Happen?
I have already paid my Feb 26 - Mar 26 invoice. I should be able to log in. I can't.
Error Messages/Logs
Steps to Reproduce
Pay your invoice on time, use claude code for a couple weeks, then be unlucky enough to get caught up in a failed synchronization between Anthropic's billing and authz backends.
Claude Model
Not sure / Multiple models
Is this a regression?
I don't know
Last Working Version
2.1.59
Claude Code Version
2.1.71
Platform
Anthropic API
Operating System
Other Linux
Terminal/Shell
Other
Additional Information
_No response_
11 Comments
This is not invalid.
@dicksontsai @blois @bogini @ThariqS @antrewmorrison @shawnm-anthropic
I realize this isn't a claude code issue of the type this repo might be concerned with, but all my invoices are paid and the claude authz flow is refusing to log me in, in spite of all my invoices being paid. The status page doesn't indicate anything is wrong at the moment. The support agent on the website keeps giving me irrelevant/nonsense advice then closing the chat.
I realize it's probably not very good form to ping a bunch of contributors to this repo, but I am concerned that the
invalidlabel on this issue means that this issue will otherwise get lost amongst all the slop issues showing up here. My apologies in advance if this is annoying.Just to confirm that I have exactly the same problem as @waynr
The same for me.
Wow. This one is very bad. Make some noise on linkedin/reddit/social media, hopefully it gets some traction. So insane how impossible it is to get in contact with a person for stuff like this.
I get the exact same issue despite having paid all invoices
Quick update for subscribers to this issue -- I tried downgrading from the
Max20x plan down toMax5x plan. Doing this seems to have reset whatever state was breaking the authz backend (maybe it forced a synchronization from the billing to the authz API?). My login still works after cancelling that downgrade.I still think this implies something needs to be fixed on the backend so I'll leave the issue open, but I'm unsubscribing from it for now. Back to slopping code!
I have the same issue. And you know they are not going to credit us for time we cant use the product.
Same for me, all invoices paid on time, Max plan.
Fix: downgrade to Pro, then immediately cancel the downgrade.
Another workaround for Pro, I cancelled and then resubscribed and now it works.
We're looking into this and will update when we have more information. So sorry about this and thanks so much for reporting.