Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Team Org Account rejected -> resulting in account banned for suspicious signals. [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#53096•Fetched 2026-04-25 06:12:27
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
vheunvheun
Participants
vheunvheun
Timeline (top)
labeled ×1

Error Message

I registered using my company email (I am the CEO) and selected a team account. I entered all required information, but received the error message: “Could not create subscription.” Double check your team onboarding mechanism. Something is not working right. Improve your error messages. There was just a generic message without any way for me to understand what could be the root cause.

Error Messages/Logs

Root Cause

Double check your team onboarding mechanism. Something is not working right. Improve your error messages. There was just a generic message without any way for me to understand what could be the root cause.

RAW_BUFFERClick to expand / collapse

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?

After using Claude via my personal email, we decided to register our business for a team account.

I registered using my company email (I am the CEO) and selected a team account. I entered all required information, but received the error message: “Could not create subscription.”

After several attempts, I tried registering a personal account using my work email to see if that would work. It did. The help desk then asked me to contact Sales. I contacted Sales, and they replied that I should contact the help desk. I responded that there might be a bug in the system.

A few hours later, my newly registered and paid Pro account was banned for “suspicious activity,” even though I had not used it at all.

  1. There appears to be a bug in your order form.
  2. There appears to be a bug in your suspicious activity detection system.

I represent a standard US-based tech company and am simply trying to register for your service on behalf of my company.

What Should Happen?

Double check your team onboarding mechanism. Something is not working right. Improve your error messages. There was just a generic message without any way for me to understand what could be the root cause.

Don't ban people that point out to your sales team that there is a software bug!

Error Messages/Logs

Steps to Reproduce

Register a new user with a .space top level domain email. Click on team registration. Type in all your data and click on continue. Again. There was no feedback that could allow me to tell you anything else.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

N/A

Claude Code Version

N/A

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue may be resolved by improving the team onboarding mechanism and enhancing error messages to provide more specific feedback.

Guidance

  • Verify the team registration process with a different email domain to isolate if the issue is specific to the .space top level domain.
  • Test the registration process with varying input data to identify potential patterns or triggers for the "Could not create subscription" error.
  • Review the suspicious activity detection system to prevent false positives, especially for newly registered accounts that have not been used.
  • Consider adding more detailed error messages or a contact method for users to report issues during the registration process.

Example

No code snippet is provided as the issue is more related to the registration process and error handling.

Notes

The issue may be specific to the Anthropic API and macOS platform, but more testing is needed to confirm. The lack of error logs or detailed messages makes it challenging to pinpoint the exact cause.

Recommendation

Apply workaround: The user should try registering with a different email domain or contact the help desk directly to report the issue and request assistance, as the current error messages do not provide enough information to resolve the issue independently.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#configuration error#environment variable#network issue#logging issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Team Org Account rejected -> resulting in account banned for suspicious signals. [1 participants]