[BUG] Paid Claude accounts are being suspended after subscription/payment with no clear reason, no refund path, and no support response

Preflight Checklist

• [x] I have searched existing issues and found related reports, but this case needs a separate issue because the impact is business-critical and the support/refund path remains unresolved.
• [x] This is a single issue: paid account access is suspended after subscription/payment despite no known abuse or policy violation.
• [x] I am using Claude/Claude Code as a legitimate paid customer for business and development work.

What's Wrong?

Paid Claude accounts and business projects are being blocked without a clear explanation, without evidence of abuse, and without a working support or refund path.

In our case, the purchased subscription was not used for abuse, harmful activity, or policy-violating behavior. Access was simply blocked, and the business impact is severe: multiple projects are unavailable, paid capacity cannot be used, and company budget has been lost without a clear remediation process.

This is not only a technical access problem. It raises serious user-rights and consumer-protection concerns because customers are paying for access, losing that access without a meaningful explanation, and receiving no practical way to resolve the situation or recover unused funds.

Business Impact

• Paid subscription access is unavailable.
• Company projects depending on Claude/Claude Code are blocked.
• Budget has been spent without usable service or a clear refund process.
• No detailed explanation has been provided for the suspension/block.
• Support/appeal channels have not produced a meaningful response.
• The lack of transparency makes it impossible to know what should be corrected or avoided.

What Should Happen?

Anthropic should provide a clear and accountable process for paid customers whose accounts are suspended or blocked:

1. A specific reason for the block or suspension, unless legally impossible.
2. A way to confirm whether this was a false positive in billing, fraud detection, abuse detection, or account-risk systems.
3. A human support escalation path for paid business-impacting cases.
4. Restoration of access when no abuse or policy violation occurred.
5. Refund or credit for unused paid subscription time when access is blocked.
6. Clear public guidance on where customers should write to challenge an incorrect suspension and request corrective action.

Questions for Anthropic

• Why are paid accounts being blocked immediately after subscription/payment or during normal Claude Code usage?
• Is this related to billing/fraud detection, payment method changes, account-risk automation, or policy enforcement?
• What is Anthropic's position when a paid customer is blocked without explanation and cannot use purchased service?
• Where should companies write to request formal review, restoration of access, refund/credit, or other corrective measures?
• Will Anthropic provide a transparent escalation path for business-critical paid account suspensions?

Steps to Reproduce

This appears to be account-side and cannot be reproduced deterministically by the user, but the observed pattern is:

1. Purchase or maintain a paid Claude/Claude Code subscription.
2. Use Claude/Claude Code for legitimate business/development work.
3. Account or organization becomes blocked/suspended.
4. Customer cannot use the paid service.
5. Customer receives no detailed explanation and no effective refund/support resolution.

Expected Behavior

A paid account should remain usable unless there is a clear, justified, and communicated policy or billing reason to block it. If Anthropic blocks access, the customer should receive a clear appeal path, human review, and refund/credit for unused paid time if access is not restored.

Actual Behavior

The account is blocked without a clear reason. Paid service becomes unusable. Projects and business workflows are interrupted. Support/appeal channels do not provide timely or actionable resolution.

Error Messages/Logs

No useful technical log is available from the customer side. The observable result is that the paid account/organization is blocked or suspended and Claude/Claude Code cannot be used.

Claude Model

Multiple / not model-specific

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Latest available version at the time of use

Platform

Claude Code / Claude paid subscription

Operating System

Not OS-specific

Terminal/Shell

Not shell-specific

Additional Information

Related reports in this repository suggest this may affect multiple paid users, especially around subscription changes, payment events, or normal Claude Code usage.

Please treat this as a business-critical paid-account access issue, not only as an individual support complaint. The current behavior creates a loss of paid service, business disruption, and serious trust concerns for companies relying on Anthropic products.