Paying for API credits when your card does not work
API credit is a separate product with its own billing rules, and it is not what a subscription reseller sells. Here is what each one needs and where people get stuck.
Two products get confused constantly: a subscription, which is one account using a chat interface or a coding tool, and API credit, which is prepaid balance billed per token for software you run yourself. They are sold separately, they fail differently, and one of them is not available through resale.
What API credit actually requires
- A funded organisation. Billing is attached to an organisation, not to a personal login, which is why the API and the chat app can have separate payment methods.
- A card that survives the check. Prepaid top-ups are small and frequent, so a card that fails one authorisation fails repeatedly. This is the single most common block for buyers outside the countries where the vendor's card processing is straightforward.
- Per-token billing. There is no month to buy. Spend stops when the balance does, which is a different failure mode from a subscription ceiling.
Nothing in a subscription purchase touches API balance, and nothing in an API top-up changes your chat limits. If you need the maximum from Claude Code, that is a subscription question. If you are calling the model from your own backend, that is an API question and it needs its own funding route.
Where the two routes differ in practice
A subscription is a fixed month with a quota, activated on the account you already own. Its cost is known in advance and its ceiling is the limit you live with. API credit is metered: cost follows usage, which makes it better for automation and worse for budgeting. Teams routinely need both — seats for people, credit for the pipeline — and they buy them from different places.
This catalog sells the subscription side only: Claude Pro at 105 CNY a month, Max 5x at 499, Max 20x at 1047, ChatGPT Plus at 95, with the Pro tiers at 375, 850 and 2500. There is no API credit here, and anyone offering discounted API balance through a resale channel is selling something else — usually a shared key, which is the fastest way to have an organisation suspended.
What to do when the card is the blocker
- Decide which product you actually need: a seat with a quota, or metered credit. They are not interchangeable.
- If it is a seat, pay for it through a route that does not require a local card, and keep the account.
- If it is credit, the funding has to reach the vendor's own billing — there is no resale shortcut, and the shortcuts that exist risk the organisation rather than the card.
The comparison of the two products in cost terms is in API against subscription. For the seat side, the price list shows every tier next to its official equivalent, and judging a reseller covers what to check before paying anyone.
Common questions
Can I buy API credit here?
No. This catalog sells subscriptions only. API balance has to be funded through the vendor.
Does a subscription include API access?
No. They are billed separately and a subscription does not add credit to your organisation.
Is a shared API key a workaround?
It is the fastest route to a suspended organisation. Keys are tied to billing and abuse detection runs on them.
Guides
All guides →Claude Max 5x vs 20x: which tier you actually need
The difference is not quality — it is how many times you can hit the wall before lunch. A practical way to size your plan.
How to pay for Claude from mainland China (2026)
Four routes, ranked by how often they actually work — and the two that quietly cost you the account.