Anthropic Billing Guide 2026: Add Credits, Read Usage, Fix a Declined Card, and Control Claude API Costs

Short answer: Anthropic bills the Claude API on prepaid credits. You add money in the Console under Settings → Billing, usage is deducted per token as you call the models, and you can turn on auto-reload so a balance never hits zero mid-deploy. Rate limits grow with your cumulative purchases (usage tiers). Claude Pro and Max subscriptions are billed separately inside the claude.ai app and are not API credit. If your card is being declined, jump to the fix list; if you cannot pay Anthropic at all from your country, a gateway such as Crazyrouter lets you use the same Claude models with Alipay, WeChat Pay, or a local card.

For anyone searching claude billing, first identify which account produced the charge. A Claude.ai Pro or Max fee pays for the consumer app and subscription-based Claude Code access. Anthropic Console credit pays for API requests from software, scripts, or Claude Code configured with an API key. A Crazyrouter balance is a third, independent account for requests sent through its endpoint. Money, invoices, limits, and payment methods do not move between these systems. Check the hostname in your receipt and the base URL in your application before adding funds, because paying the wrong account will not restore a stopped API request.

Before changing a card or buying more credit in October 2026, collect three pieces of evidence: the merchant name on the receipt, the organization or workspace shown in the billing console, and the API host recorded by the application. Those details resolve most claude billing problems faster than retrying payment. A subscription receipt should be investigated in the Claude.ai account that owns the plan. A direct API charge belongs to the Anthropic Console organization that issued the key. Traffic sent to https://api.crazyrouter.com/v1 is charged to the corresponding Crazyrouter account instead. If a team has several workspaces, also verify that the key belongs to the workspace you funded. Adding credit to a different organization leaves the original service unable to run even though the payment itself succeeded.

Last updated: October 8, 2026.

Claude billing: subscriptions, API credit, and gateway charges#

Claude billing is not one shared wallet. For an app subscription, manage the plan and payment method in Claude.ai. For direct developer usage, open the Anthropic Console organization that owns the API key and review its Billing, Usage, and Limits pages. For a request routed through Crazyrouter, review that gateway account instead. You can verify the route in code: api.anthropic.com uses direct Anthropic billing, while https://api.crazyrouter.com/v1 uses the Crazyrouter balance. This check also explains why a valid subscription can coexist with an API error that says the credit balance is too low.

First, which "Anthropic billing" do you mean?#

Most confusion starts here. There are three separate billing systems and they do not share balances:

Buying Max does not give you API credit, and API credit does not unlock the app. If you are on a subscription and want the plan comparison instead, read the Claude Max plan guide. The rest of this article is about the API.

How Claude API billing works#

1. You buy credits in advance. The minimum first purchase is small (single-digit dollars). Credits are tied to your organization, not to an individual API key.
2. Every request deducts tokens × price. Input tokens, output tokens, cache writes and cache reads each have their own rate per model. As of 2026-10, the documented list rates in our pricing reference are Claude Opus 4.6 at $5 per million input tokens and$25 per million output tokens, Claude Sonnet 4.6 at $3 /$15, and Claude Haiku 4.5 at $1 /$5. Confirm the current model row before budgeting. Cached reads and batch jobs can use different rates where supported.
3. Your usage tier rises with cumulative spend. Each tier raises the requests-per-minute, tokens-per-minute, and monthly spend ceilings. The current thresholds are on the Console's Limits page; if you need Tier 4-level limits on day one, contact sales rather than trying to buy your way up.
4. Credits expire. Anthropic's terms give prepaid credits a validity period (twelve months at the time of writing), so do not pre-buy a year of usage you might not consume.
5. Invoicing is available for larger accounts. Monthly invoicing with net terms is a sales conversation, not a self-serve toggle.

Setting up billing step by step#

1. Sign in at console.anthropic.com and open Settings → Billing.
2. Click Add payment method and enter a card that supports international online payments. Make sure the billing address matches the card exactly.
3. Fill in Business details and tax ID if you need compliant invoices; this can be edited later but existing invoices are not regenerated.
4. Buy credits. Start small; you can top up any time.
5. Turn on Auto-reload and set a threshold (for example, reload $50 when the balance falls below$10). This is the single most useful switch on the page: production outages caused by an exhausted balance are common and entirely avoidable.
6. Create workspaces for each product or environment and set a spend limit on each. Workspace limits are the only hard cost cap Anthropic offers.
7. Issue one API key per service and environment, never one shared key. Usage reports are per key, so this is what lets you attribute spend later.

Reading your usage and cost#

The Console has two views that answer different questions:

• Usage shows tokens by model, by API key, and by workspace over a chosen period. Use it to find which feature is generating spend and whether cache reads are actually happening.
• Cost turns the same data into dollars and is what finance will reconcile against invoices and receipts, which live under Billing → Invoice history.

For anything more granular — per-user, per-request, per-tenant — you need to log the usage object returned in every API response yourself, or route through a gateway that keeps per-request logs for you.

Your card was declined: what to try, in order#

"Your card was declined" is the most common Anthropic billing search, and the cause is almost never Anthropic itself:

1. Try a second card from a different bank. Many declines are the issuing bank blocking an unfamiliar overseas merchant. A quick call to the bank to whitelist the charge often fixes it.
2. Check the card type. Prepaid, gift, and many virtual cards are rejected. Debit cards without international online payment enabled fail too.
3. Match the billing address exactly, including postcode format, to what the bank has on file.
4. Complete 3-D Secure. If the bank's verification popup is blocked by an extension or a corporate browser policy, the charge fails silently.
5. Check whether your country is supported. Anthropic sells API access only in a published list of countries and regions. If yours is not on it — mainland China is the largest example — no card will work, and using a VPN to fake location violates the terms and risks the account.
6. If none of that helps, use a reseller or gateway. Crazyrouter resells the same Claude models (Opus 5.5, Opus 5, Sonnet 5, Fable 5.1) with an OpenAI-compatible API, accepts Alipay, WeChat Pay, and cards from regions Anthropic does not serve, and needs no Anthropic account. Prices are per token with no subscription; see Claude Opus 5 and Claude Sonnet 5.

Direct Anthropic billing vs a gateway#

Direct billing is the right default when Claude is your only model and you are in a supported country. A gateway earns its place when you need several model families behind one key, need a payment method Anthropic does not take, or want per-key budgets and logs without building them.

from openai import OpenAI

client = OpenAI(api_key="your-crazyrouter-api-key", base_url="https://api.crazyrouter.com/v1")

response = client.chat.completions.create(
    model="claude-sonnet-5",
    messages=[{"role": "user", "content": "Summarize this support ticket in two lines: ..."}],
    max_tokens=300,
)
print(response.choices[0].message.content, response.usage)

Six habits that keep the Claude bill predictable#

1. Set max_tokens on every call. Uncapped output is the fastest way to a surprise.
2. Use prompt caching for anything repeated — system prompts, tool schemas, long documents. Cache reads cost a tenth of fresh input.
3. Route by difficulty. Sonnet 5 handles most classification, extraction, and drafting; keep Opus 5.5 or Fable 5.1 for the steps that measurably need them.
4. Send offline work to the Batch API for a 50% discount.
5. Alert on retry rate, not just spend. A misbehaving client that retries 429s in a tight loop can burn a day's budget in an hour.
6. Review the Usage page weekly by API key. Keys nobody recognises are either leaked or forgotten; both should be revoked.

FAQ#

What does claude billing include?#

Claude billing can refer to a Claude.ai subscription or direct Anthropic API usage, but those products have separate balances. Check the receipt and the API base URL to identify which account is charging you before changing a plan or payment method.

Where is the Anthropic billing page?#

For the API: console.anthropic.com → Settings → Billing. For Claude Pro/Max: claude.ai → Settings → Billing.

Does Anthropic bill monthly in arrears?#

Not by default. Self-serve API accounts are prepaid; monthly invoicing is available for larger customers through sales.

Why does my API say "credit balance is too low" when I just paid for Claude Pro?#

Because Pro/Max subscriptions and API credits are separate systems. Add credits in the Console.

Can I set a hard monthly cap?#

Yes, per workspace, under Workspace settings → Limits. Organization-wide monthly caps are set by your usage tier.

Does Anthropic accept PayPal, Alipay, or WeChat Pay?#

The Console takes cards. For Alipay or WeChat Pay, use a gateway such as Crazyrouter.

Do unused credits expire?#

Yes — check the current validity period in Anthropic's terms before buying a large block.

How do I get invoices with my company's tax ID?#

Fill in business details and tax ID under Billing before purchasing; invoices are then available under Invoice history.

Summary#

Anthropic API billing is simple once you separate it from the app subscriptions: prepaid credits, auto-reload on, one key per service, workspace limits as the hard cap, and caching plus Batch for the discounts. If a declined card or an unsupported country is what brought you here, the fastest path to working Claude access today is Crazyrouter — the same models, per-token pricing, and payment methods that work where you are.

→ Claude models and prices on Crazyrouter · Create a free account

Related guides#

• Claude Max plan: tiers, limits, and when the API is cheaper
• Claude API card declined: fixes and workarounds
• Claude Code with Crazyrouter: base URL, auth, models
• OpenRouter alternatives compared

Related on crazyrouter.com#

• Claude Sonnet 4.6 price comparison (list vs Azure / Bedrock / Vertex vs Crazyrouter)
• All Anthropic models with live prices