OpenAI API Usage Tiers and Payments: Rules, Prepaid Credits, Virtual Card Limits

🕐 2026-10-03 ✍️ Moyi Foreign Trade

OpenAI API usage tiers and payment setup guide 2026

The real bottleneck isn't your budget, it's your tier

Developers outside OpenAI's supported regions run into two walls with the API. The first is eligibility: I pulled the official supported countries page on October 4, 2026. The list has 208 entries. Mainland China, Hong Kong, and Macau are all absent; Taiwan, Japan, Singapore, and South Korea are on it. The page carries an explicit warning: accessing or offering access to the services from outside the listed countries may result in your account being blocked or suspended.

The second wall is payment, and that's where this guide spends most of its time. Before we get into mechanics, one thing needs to be said plainly: OpenAI's official help center states that prepaid cards cannot be used to purchase API credits, only standard credit or debit cards, and the issuing bank must be located in a supported region. Whether your virtual card counts as "prepaid" is decided by its BIN category and underlying account structure, not by what the card provider's marketing page calls it.

Usage tiers: spend enough and the ceiling lifts itself

OpenAI graduates organizations through usage tiers automatically as cumulative spend grows. More spend, higher requests-per-minute (RPM) and tokens-per-minute (TPM) limits. Here's the tier table from the official rate limits documentation, fetched live on October 4, 2026:

Tier	Qualification (cumulative spend)	Usage limit
Free	Must be in an allowed geography	$100/month
Tier 1	$5 paid	$100/month
Tier 2	$50 paid	$500/month
Tier 3	$100 paid	$1,000/month
Tier 4	$250 paid	$5,000/month
Tier 5	$1,000 paid	$200,000/month

Details people miss:

Qualification is cumulative, not monthly. Pay $5 in your first month and $45 in the second; hitting $50 total still triggers Tier 2.
There's a waiting period. Community reports consistently confirm tier upgrades also require account or payment tenure (Tier 2, for instance, needs 7+ days since your first successful payment). If the money's spent but the tier hasn't moved, the clock is usually the reason. Your current tier lives under platform.openai.com → Settings → Limits.
The monthly usage limit is a separate ceiling. Tiers set your rate limits; the usage limit caps total monthly burn. Set a project-level budget during testing so a runaway agent doesn't drain your balance overnight.
Watch for ramp-rate throttling. The docs describe a slow_down error (HTTP 429) that fires when traffic ramps up too quickly even if RPM and TPM are within limits. The rule of thumb: past 1 million TPM, raise traffic by no more than 50% every 15 minutes.

Payment setup: how prepaid billing actually works

New API accounts default to prepaid billing: buy credits first, usage draws down the balance. Per the official prepaid billing help article (verified October 4, 2026):

Open Billing overview and click Add payment details.
Choose your initial credit purchase, $5 minimum, with a maximum based on your trust tier.
Confirm the purchase; the balance reflects within a few minutes.
Optionally enable auto-recharge: when the balance drops below a threshold, OpenAI tops it back up to a target amount, capped by a monthly recharge limit (manual purchases don't count against that cap).
When credits run out, API calls return a billing quota error; go back to Billing and use Add to balance.

Two traps deserve their own paragraph. First: credits expire one year after purchase, are non-refundable, and can't be extended. Buying a year's worth of credits for a project that might not survive the quarter is just donating money to OpenAI. Second, the help article describes "delayed billing": cutoff after your balance hits zero isn't instant, and the excess shows up as a negative balance deducted from your next purchase. That means your auto-recharge threshold needs headroom. Setting it at $0 defeats the purpose.

Virtual cards: what the official policy actually says

The official "Why was my credit card declined?" help article (verified October 4, 2026) is unambiguous: prepaid cards cannot purchase API credits; only standard credit or debit cards are supported, and the payment card must be issued by a bank in a supported region.

Where does that leave virtual cards? A virtual card is just a form factor. What matters is whether the BIN is categorized as credit/debit or prepaid, and where the issuing bank sits. Many virtual card platforms, especially USDT-funded ones, run on prepaid BINs; those get rejected at OpenAI's checkout outright. Others issue debit-categorized BINs through US or EU banks, and those frequently work in practice. But "works today" is not "works forever": OpenAI's risk systems re-scan high-risk BIN ranges, and a card that funded your account for months can start declining without warning.

If you're going the virtual card route, self-check in this order:

Check the BIN first. Look up the first 8 digits of the card number to see how the issuer categorizes it; our guide on free BIN lookup tools and their safety limits covers the method. Prepaid category? Stop, get a different card.
Match issuing region to account region. A US account paired with a UK-issued card raises flags more often than a consistent pairing.
Use the billing address the card platform has on file. AVS mismatches are a top decline reason; don't improvise a ZIP code.
Let 3D Secure windows open. The help article specifically notes that ad blockers, pop-up blockers, or VPNs can swallow the 3DS redirect and produce "authentication required" failures. Use an incognito window with blockers off when binding the card.
Keep a backup card on file. Add a second card under Payment methods so auto-recharge has something to fall back on when the primary gets flagged.

For comparing specific providers, our directory entries like Cashi and Hyperbeat Pay list fees, KYC requirements, and card categories. Read the card type and issuing region fields, not the signup fee.

Account risk: the failure mode that costs more than a declined card

The Free tier's qualification reads "user must be in an allowed geography," and the supported countries page warns that out-of-region access can get accounts blocked or suspended. That risk exists independently of your payment method: a perfectly clean card does not fix a region problem. Accounts registered through unconventional means and used from unsupported regions carry standing risk with no appeal guarantee.

The practical play is limiting blast radius:

Issue API keys per project with individual budgets. One key running everything is how small outages become big ones.
Keep the auto-recharge monthly cap low. Manual top-ups are mildly annoying; an uncapped agent loop is expensive.
Don't put production workloads on a single account whose region status is ambiguous.
Set billing email alerts and treat the first negative balance as a signal, not a rounding error.

FAQ

Can I use the OpenAI API from an unsupported country?

Not officially. The supported list (208 countries and territories, verified October 4, 2026) excludes mainland China, Hong Kong, and Macau among others. Out-of-region access risks suspension. Some teams route through entities in supported regions, but that risk is yours to carry.

Are virtual cards officially allowed for API payments?

Officially, only standard credit or debit cards are supported, and prepaid cards are excluded. Debit-categorized virtual BINs from supported-region banks often pass in practice, but that's tolerance, not endorsement; enforcement can tighten at any time.

I paid $5 and my RPM is still tiny. Why?

$5 only gets you Tier 1. Meaningful jumps start at Tier 2 ($50 cumulative). Also check whether you're hitting slow_down throttling, which fires on rapid traffic growth regardless of tier.

Do credits expire?

Yes, one year from purchase, non-refundable and non-transferable. Buy in batches matched to actual usage.

3D Secure keeps failing at checkout. What now?

Incognito window, blockers and VPN off, complete the bank's OTP or app approval without closing the page. If it still fails, switch cards or ask your bank to enable 3DS for international e-commerce.

Can I go beyond Tier 5?

Yes. Tier 5 is the end of automatic advancement. From Settings → Limits, submit a Request increase for the specific model and limit with your use case and expected volume; reviews typically take a few business days.

Risks and limitations

All figures here were verified on October 4, 2026 against OpenAI's official documentation and help center, and are subject to change; the official rate limits page is the source of truth. Virtual card payments sit in a gray zone: BIN policy, issuer risk controls, and account region rules can each shift under you. Nothing here is legal or financial advice.