Billing UX: purchased usage credits unusable behind monthly spend limit; misleading error; cancel/refund offered without explaining consequences

What happened

Mid-session (Claude Code CLI, Pro plan) my prompts started being rejected with:

You've hit your monthly spend limit · raise it at claude.ai/settings/usage /usage-credits to adjust your monthly spend limit.

I purchased additional usage credits (A$5.25 showing as available), reasonably assuming — as in virtually every prepaid system — that purchased credits become spendable immediately. My messages kept being rejected with the same error, so I purchased a further A$10, which was also blocked (balance showed A$15.25, still unusable). At no point did anything indicate the purchases had succeeded but a separate control (the monthly spend limit) was still blocking usage.

Notably, the settings page where credits are bought says: "Buy usage credits so your team can keep using Claude if they hit a limit." That is precisely what did not happen — I hit a limit, bought credits twice, and could not keep using Claude.

During this, the billing flow offered to cancel my account and issue a refund — a frightening option to surface to a user mid-payment-problem, with no indication of what cancellation would do to my account information, history, or settings. This all happened in the middle of active work: it looked like I had paid twice for something that didn't work, and the system's suggested way out was account cancellation.

(I also submitted this via /bug, which itself gave no visible confirmation that anything was sent — filing here so there is a trackable record.)

Problems

1. Terminology: "usage credits" (balance) and "monthly spend limit" (cap) are independent controls, but nothing in the purchase flow or the error explains that buying credits does not raise the limit. This defies the near-universal convention that buying credit makes it available — and contradicts the purchase page's own copy quoted above.
2. Error message: the spend-limit error doesn't acknowledge the existing credit balance, so a user who just paid twice reads it as "your payments didn't work".
3. Cancel/refund placement: offering account cancellation during a payment-confusion moment, without explaining its consequences for account data, escalates anxiety instead of resolving the problem.
4. /bug gives no visible confirmation that a report was submitted.

Suggested fixes

• Error should state both values: "You have $X.XX in credits, but your monthly spend limit of $Y is blocking usage — raise the limit at claude.ai/settings/usage or run /usage-credits."
• The purchase flow should warn when the spend limit will still block new credits, and offer to raise it in the same step.
• Any cancel/refund option must state plainly what happens to the account, its data, and remaining balance — and shouldn't be a prominent path out of a spend-limit block.
• /bug should print a confirmation (and ideally a reference ID).

Environment: Claude Code CLI on Linux (Ubuntu 24.04), Pro plan (monthly), currency AUD.