[BUG] Max 5x plan incorrectly downgraded to Free after Max 20x refund (Fable 5 government removal, June 13 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?
What's Wrong?
Two compounding billing failures:
- Accepting a Max 20x refund downgraded my account to Free instead of reverting to Max 5x.
- Following support's resubscribe instructions charged me again ($106.60) — the system did NOT recognize my still-active Max 5x entitlement.
Charge & Refund Sequence
| Date | Event | Amount |
|------|-------|--------|
| June 4, 2026 | Pro plan renewal | $21.32 |
| June 4, 2026 | Mid-cycle upgrade to Max 5x | $85.30 |
| June 11, 2026 | Mid-cycle upgrade to Max 20x | $129.82 |
| June 13, 2026 | Refund of Max 20x premium after Fable 5 removal | -$129.82 |
| June 13, 2026 | Resubscribe to Max 5x (per Fin support instructions) | $106.60 |
What Should Happen?
Expected Behavior
After the $129.82 refund (which only covers the Max 20x premium), account reverts to Max 5x. The $85.30 and $21.32 paid June 4 covers Max 5x through ~July 4, 2026 and is unaffected by the refund. No resubscribe or additional charge should have been necessary.
Actual Behavior
- Refund downgraded account to Free (no notification).
- Support (Fin) instructed me to resubscribe, stating the system "should recognize your existing entitlement."
- The resubscribe flow did NOT recognize the entitlement and charged $106.60 in full.
- I am now paying for Max 5x twice for the same period ([$21.32 + $85.30] + $106.60).
Error Messages/Logs
Steps to Reproduce
Subscribe to Max 5x, then subscribe to Max 20x, then unsubscribe from Max 20x.
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.177 (Claude Code)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
Additional Context
- Billing cycle anchor: 4th of each month
- Max 20x upgrade was made solely for Fable 5 access to use its full potential
- Fable 5 removed June 13 due to a government-issued directive; refund accepted via offered flow
- Fin chat: requested human escalation, Fin stopped responding before completing handoff
- Follow-up email sent to support@anthropic.com; replied requesting the human escalation Fin offered
Related Issues
Same entitlement mismatch pattern as: #47286, #48399, #49744, #54560, #61339
9 Comments
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Hit this too. Here's how the agent responded when I attempted to settle:
Same underlying entitlement rollback issue here. Adding my data point in the format that seems useful for billing/support triage.
Timeline and billing state
| Date | Event | Amount / status |
|---|---|---|
| Jun 11, 2026 | Paid for 5x Max tier | $100 charged. Billing UI currently labels this invoice as "Partially Refunded", but I did not receive any actual refund from this $100 payment. |
| Jun 12, 2026 | Upgraded from 5x Max to 20x Max specifically for Claude Fable 5 access | Additional $102.04 charged |
| After Claude Fable 5 became unavailable | Requested refund for the 20x Max upgrade | Only the $102.04 upgrade charge was refunded |
| Current state | Account plan shown in Claude billing settings | Free plan |
Expected behavior
Refunding only the 20x upgrade charge should roll the account back to the already-paid 5x Max tier for the remaining billing period. The original $100 5x Max payment was not refunded and should still represent an active entitlement.
Actual behavior
The account was downgraded all the way to Free even though only the $102.04 20x upgrade charge was refunded. The original $100 5x Max payment was not returned, and access was not restored to 5x Max.
What I am requesting
This appears to be the same pattern as the issue described here: the refund should cancel only the 20x upgrade delta, not remove the underlying paid 5x Max entitlement.
Same defect, same week: Max 5x renewed June 10 ($108.88) → upgraded to 20x June 11 ($112.62 prorated, with a $96.56 unused-5x credit applied) → accepted the Fable refund → entire subscription cancelled to Free instead of reverting to 5x → support instructed resubscribe → charged $108.88 again June 13. The $96.56 trade-in credit was never returned as money or service. Support acknowledged the figure in writing, then declined as "final decision." The July 1 restoration included no remediation for accounts hit by this flow.
+1, same defect here — accepted a Max 20x refund and my account was wiped straight to Free instead of reverting to Max 5x, no resubscribe option available, and I've been stuck in the support bot loop with no real fix for over a day now despite this clearly being a known, repeating pattern across this whole thread. Would really appreciate someone from Anthropic actually addressing the root cause here instead of one-off manual patches per user.
Hi, I bought my 5x max plan today and upgraded to max 20x when I ran out of hourly usage, at that point my fable 5 weekly usage was a little over 20% and my all models weekly usage was a little over the 13% mark, after I upgraded to the 20x plan my weekly fable usage is at 100% and my weekly all models usage is at around 55%, this can't be correct, can I get some help with this
@MichaelDustin Did they ever get this resolved? I'm in the same situation—support hasn't replied since last week. Tried getting a refund to save $100, but instead I've lost days of time and I'm still $100 out of pocket.
In my case, there has been no resolution one month in at this point. Anthropic's human representative told me it was their supervisor's final decision not to issue me a refund (or billing credit, as I had suggested) - and that any further replies I make regarding this topic would go unmonitored.
In most consumer situations this would be grounds for a credit card chargeback, but I am reluctant to do this and risk being locked out of my ongoing work by the same disfunctional policy loop that spawned this discrepancy in the first place.
This is super disappointing to read. This isn't how a company that wants to keep its customers should operate. Really hoping this gets real attention.