The single biggest blocker to calling the OpenAI API from China, or from anywhere OpenAI's billing doesn't play nice, is not having a card it will accept. Signup requires an international card, and most domestic cards simply get rejected. This post lays out three real paths around that wall, with the actual cost and risk of each.
Option 1: get a card OpenAI accepts (official signup)
The most "proper" route is to get your hands on a card OpenAI's billing will accept, then register, add it, and top up directly.
- A real international bank card: most reliable if you have one, but most people don't;
- A virtual card: several services issue these, but OpenAI's fraud checks are strict — plenty of virtual cards get rejected outright or stop working later, so success is far from guaranteed.
Upside: lowest possible price (official rate), most stable and compliant.Cost: high barrier to entry, can take a while to sort out, and the account still carries some fraud-review risk. Best for teams with the means and a real need for stability and compliance.
Option 2: use an API relay (least hassle)
A relay takes payment through whatever local method it supports and hands you an OpenAI-compatible endpoint you can reach directly, no VPN required. Skip the international card and the network workarounds entirely — swap in a new base_url and key and you're calling GPT.
- Upside: lowest barrier to entry, running in minutes, and one key often reaches several model providers at once;
- Cost: you pay a billing multiplier on top of official pricing, you're dependent on the relay's upstream being stable, and there's some risk the provider disappears with your balance.
This is the practical default for most individual developers without an international card. The trick is picking a decent provider and keeping deposits small and spread out — see How to Choose an AI API Relay and Are API Relays Legal and Safe.
Option 3: have someone top up an official account for you (not really recommended)
Someone with a working card tops up an official account on your behalf, and you pay them back in your local currency. Essentially: borrowing someone else's card to go through the official channel.
- Upside: it's the official channel, so pricing is close to list price;
- Cost: you either hand over account control to a third party or send money up front and hope — trust cost is high, and if the account gets flagged for unusual billing activity, that's your loss to eat.
Unless the other person is someone you genuinely trust, the risk-to-reward ratio here is poor, and it's generally not something we'd recommend.
How the three compare
| Option | Barrier | Price | Best for |
|---|---|---|---|
| Official signup | High (needs a working card) | Lowest | Anyone with international payment access who values compliance |
| API relay | Lowest | Multiplier on top | Individuals / small teams who want it done fast |
| Third-party top-up | Medium | Near list price | Only with someone you truly trust |
Bottom line
Without a working card, a relay is the realistic answer for most people — pay however you already can, connect directly, and be up and running in minutes. The trade-off is accepting a billing multiplier and some counterparty risk, which small, spread-out deposits keep manageable. If you do have international payment access and stability matters most, official signup is worth the extra setup. To compare a handful of GPT relays quickly, use the HowToken directory and filter by payment method and minimum top-up.