[BUG] [BILLING] Unauthorized Gift Max 5X x3 — support unresponsive
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?
Three unauthorized “Gift Max 5X x3” purchases totaling approximately $300 were made from my Claude account on April 23, 2026, without my permission. After I froze my payment card, additional purchase attempts continued. I reported the issue multiple times through live chat and email, submitted screenshots and receipts, and only received automated responses without any meaningful support or resolution.
What Should Happen?
Anthropic should urgently investigate the unauthorized transactions, secure my account from further unauthorized access or purchases, provide a response from a real support representative, and refund the fraudulent charges.
Error Messages/Logs
Steps to Reproduce
- Unauthorized access was somehow obtained to my Claude account.
- Three unauthorized “Gift Max 5X x3” purchases were made on April 23, 2026.
- After freezing the linked payment card, additional purchase attempts still occurred.
- Multiple reports were submitted through support chat and email (Conversation IDs: 215474139181398 and 215474267449859).
- Only automated acknowledgements were received, with no human follow-up or resolution.
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.146
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
I have already contacted support multiple times through email and live chat regarding this issue and provided screenshots, receipts, and all requested details. However, I still have not received any meaningful response from your team and only received automated acknowledgements.
Conversation IDs:
- 215474139181398
- 215474267449859
This matter involves unauthorized transactions and account security concerns. Please look into this issue urgently, escalate it to a real support representative, and provide an update as soon as possible.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗