Claude API Payment Failing? Fix Credit Balance & Billing Errors (2026)

When using the Claude API, you may hit “payment won’t go through” or a “credit balance too low” error. The cause is usually one of three: insufficient credit balance, a billing/payment issue, or a rate limit. This guide, based on the official errors documentation as re-checked on September 9, 2026, walks through each error code and how to fix it.

First: API credits and subscriptions are separate

To avoid confusion: the Claude API (for developers) draws from prepaid credits in the Console (platform.claude.com — the old console.anthropic.com redirects there). By contrast, Claude Pro/Max subscriptions are chat-service fees on claude.ai — the two are separate billing. So “I paid for Pro but the API doesn’t work” is expected: the API must be funded separately in the Console.

1. Most common cause — insufficient credit balance

This is the error you’ll hit most often. Officially, it appears as:

• HTTP 400, invalid_request_error
• Message: “Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits.”

How to fix:

1. Sign in to the Console: console.anthropic.com
2. Go to Settings → Plans and Billing
3. Add a payment method and purchase credits
4. To prevent recurrence, enable auto-reload and usage alerts

In short: creating an API key is free, but sending real requests requires a funded Console balance.

2. When the billing info itself is the problem (402)

If the payment itself is blocked when you try to add funds, your payment method may be the issue. Per the official error docs:

• HTTP 402, billing_error — there’s an issue with your billing or payment information

How to fix: in the Console billing settings, check your card details (expiry, limits, international-payment permission) and switch to another card if needed. (If you use Claude Platform on AWS, check payment details in AWS Marketplace instead.)

Note (reported case): some users have reported that prepaid cards did not register well as a payment method. In such cases, a regular credit/debit card tends to be safer. This is an individual report, however, and may not apply to every situation.

If your card keeps getting declined — official checklist

When the card itself is declined, the official support docs recommend checking the following, in order:

1. Supported billing location — confirm your card's billing address and issuing country are on the supported billing locations list, and that the two match each other.
2. Billing address match — the address on your payment method must exactly match what your bank has on file. Even a small typo can trigger a decline.
3. Complete 3DS (3D Secure) verification — finish any one-time-password or bank-app confirmation your issuer requires.
4. Use an accepted payment method — credit and debit cards are the standard options; third-party processors such as PayPal are not accepted. (ACH bank transfer is available for accounts on monthly invoicing.)
5. Sufficient funds — make sure the card can cover the full amount.
6. Retry with another card or later — temporary technical issues sometimes cause declines that resolve on their own.
7. Contact your bank — the issuer often knows the specific decline reason. If your card is domestic-only, also ask whether international payments are enabled.

If none of these resolve it, contact official support. (Source: the official support article Why was my card declined?)

3. Balance is fine but you get “rate limit” (429)

Regardless of payment or balance, sending many requests in a short window hits the rate limit.

• HTTP 429, rate_limit_error — your account has hit a request/token rate limit

Per the official docs, if an organization sees a sharp increase in usage, 429s can also appear due to acceleration limits. The fix is to retry after a short wait (exponential backoff recommended) and check your usage Tier and limits in the Console. Limits ease as your Tier increases.

4. When errors persist despite sufficient balance

Rarely, the Console shows credits but the API keeps returning credit_balance_too_low or similar. This may be an account- or payment-processing-state issue that is hard to resolve yourself.

How to fix: every API response includes a request-id header (e.g., req_018Ee…). Officially, when contacting support about a specific request, include this request-id to speed up diagnosis. Reach out through the official Console support channel with the request-id and details.

Checklist when payment fails (summary)

1. Check the error code first — is it 400 (balance), 402 (billing info), or 429 (limit)?
2. If 400, add credits in Console → Plans and Billing.
3. If 402, check/replace your payment method (card).
4. If 429, retry + check your Tier and limits.
5. If it still fails, contact official support with your request-id.
6. Prevention: enable auto-reload + usage alerts.

The error codes and fixes here are based on the official errors documentation (platform.claude.com/docs), re-checked September 9, 2026. Console layout and detailed policies may change, so verify the latest state in the Console when taking action. Individual reports (e.g., prepaid cards) are based on user reports and are not guaranteed to apply to every case.

Are API credits refundable? — Refund and expiry policy

While troubleshooting payments, you may also wonder about refunds. The official policy is as follows (as of July 2026):

• Credit purchases are non-refundable. The official help article states that all credit purchases are non-refundable.
• Credits expire one year from the purchase date, and the expiration date cannot be extended. Expired credits appear under Invoice history in your Console billing settings.
• Failed API requests are not charged — you are only billed for successful calls and completed tasks.
• The same credit policy applies when you use Claude Code on API credits.

Subscription plans (Pro/Max) follow a separate cancellation and refund policy. For subscription issues, see our billing & subscription troubleshooting guide. Policies can change, so check the official help article before making decisions.

Curious what your usage would cost? Try the API cost calculator — pick a model and token counts for an instant estimate.

Related articles

• Is the Claude API Free? — Credits & Alternatives
• Claude API Key, Pricing & Usage — Full Guide
• Claude API Error Handling & Retry Guide
• Claude API Errors & Rate Limits — 429·529
• Paying for Claude in Korea — Cards, Receipts, VAT