leon7482/chatgpt-plus-codex: A Chinese-Language Guide to Paying for ChatGPT Plus and Codex

What leon7482/chatgpt-plus-codex actually is

The repository contains two top-level entries: LICENSE and README.md. There is no source directory, no package manifest, no release, and no build step. The README is a long Chinese-language guide about paying for ChatGPT Plus, ChatGPT Pro and Codex from mainland China, and it is written as a tutorial rather than as documentation for code.

The problem it addresses is concrete. According to the README, Stripe's risk engine rejects cards issued by mainland Chinese banks, including Visa, Mastercard and American Express products, and it also flags shared data-centre IP addresses. The guide's stated audience is people who can already reach the ChatGPT interface but cannot complete a subscription payment.

That framing matters for how you read the rest. This is not a project you adopt. It is a document you consult, and the document has a commercial interest in the answer it gives.

The four payment routes the README compares

The README lays out four methods and ranks them. The first is an overseas virtual credit card funded with USDT or a cross-border channel, which the README describes as requiring identity verification and a clean residential IP before the card can be bound to OpenAI. The second is a third-party top-up site, which the README calls the least effort option and the one it recommends. The third is a US-region App Store gift card redeemed into a non-mainland Apple ID, which routes the charge through Apple's in-app purchase system instead of Stripe. The fourth is a shared or day-pass account.

The README is blunt about the fourth. It states that such accounts are registered in bulk, that conversation history is visible to everyone sharing them, and that OpenAI's ban rate for concurrent logins from different locations is close to total. It also warns against entering personal or company data into them. That warning is the most useful paragraph in the file, and it is the one part of the guide that does not point anywhere else.

The comparison table scores the virtual card route as the hardest to set up and the top-up platform as the easiest. The scoring reflects the author's preference, not a measured result.

Installing it is not a thing you do

There is nothing to install. No package name, no CLI, no Docker image, no configuration file appears in the README. The only artefact is prose, and the only link out is the author's recommended service at payprm.com.

If you want to use the repository as reference material, clone it and read the file locally:

git clone https://github.com/leon7482/chatgpt-plus-codex.git
cd chatgpt-plus-codex
wc -l README.md

The third command reports the README length, which is the practical measure of what you are getting. The appendix inside it lists ten recurring errors, including "Your credit card was declined", "Country not supported" and a Stripe payment page that loads indefinitely. Those entries describe symptoms a reader can match against their own screen, and that is the closest this repository comes to a usable tool.

What you should not expect is a script that performs any part of the payment. The README does not provide one, and the repository layout does not suggest one was ever planned.

Why the recommended route is the weakest part of the guide

The README devotes more space to payprm.com than to any other method, and the argument for it rests on longevity: the author states the team operated on Taobao for years before moving to an independent site, and that the service has run for roughly three and a half years. No evidence accompanies that claim, and a repository cannot verify the operating history of an external business.

There is a structural problem beyond the missing evidence. The guide tells readers that a trustworthy top-up provider never asks for a ChatGPT password, then recommends a provider. A reader has no independent way to check that the recommended provider follows the rule the guide just set. The repository is MIT licensed, which permits reuse and redistribution of the text, and the licence says nothing about the linked service.

The Apple gift card route gets a fairer treatment. The README notes that a US Apple ID must stay on a stable network, that frequent node switching can get the ID flagged, and that cheap gift cards from unofficial channels are usually fraudulently obtained and can lead to the Apple ID being banned. Those are specific, checkable risks. The top-up section has no equivalent list.

The genuine limitation: the guide describes a moving target

Stripe's risk rules and OpenAI's supported-region list change without notice. The README is dated to September 2026 and the last push was on 2026-09-13, so the content is recent, but recency is not the same as accuracy for a document that depends on third-party fraud systems.

Consider the error appendix. It states that mainland-issued cards have no viable workaround and advises readers to stop trying. That conclusion may hold, but it is a claim about a payment processor's current behaviour, and the README offers no method for confirming it. A reader who follows the advice saves time; a reader who wants to know when the advice expires gets nothing.

The wrong-tool case is clearer. If you are looking for a Codex CLI wrapper, a usage-limit tracker, or anything that answers the search phrases about Codex quotas and token limits, this repository does not contain it. The README mentions Codex in its title and framing but does not document Codex limits, pricing tiers or usage rules in the retrieved text. Searching here for those answers will not work.

What a real alternative looks like

The alternative to this repository is not another guide. It is the primary source. OpenAI's own billing and supported-country documentation, and Stripe's published card-acceptance rules, are the authorities the README is interpreting. They are less convenient and they do not recommend a vendor at the end.

A second alternative is the App Store route on its own, documented by Apple. It is slower and it constrains you to Apple hardware and a non-mainland Apple ID, but the payment relationship is between you and Apple, with no intermediary holding your account details. The README treats this as a middle option for Apple users; for anyone who already has a foreign Apple ID, it removes the trust question entirely.

The difference in approach is who bears the risk. A top-up platform concentrates the risk in one vendor whose payment source you cannot inspect. The App Store route spreads it across Apple's own compliance process. The README acknowledges the first and does not weigh the second against it.

Licence, maintenance and what upgrading means here

The repository is MIT licensed. For a text document that means you may copy, modify and redistribute the README, provided the licence notice travels with it. It grants no rights over the linked service, and it offers no warranty about the accuracy of the payment advice. Nothing here is legal or financial advice, and the licence does not change that.

Upgrade cost is unusual for a repository with no releases. There is no version to migrate to. What changes is the prose: the README is edited in place, and the last push was on 2026-09-13. A reader who cloned it earlier gets no notification that a recommendation or a warning has changed. Re-pulling the repository is the only way to see edits, and there is no changelog to tell you what moved.

The repository is not archived, and the last push was four days before this article. That is recent enough that the content reflects current conditions as the author understands them. It is not evidence that the underlying payment systems behave as described.

Editorial conclusion

Read this repository as a description of a payment problem, not as a tool. Anyone who wants to understand why mainland-issued cards fail at Stripe can use the error appendix, and anyone considering the recommended top-up site should treat the recommendation as advertising and check the platform's own terms first. Skip it if you want installable software, a CLI, or anything with a version number; the repository contains only LICENSE and README.md. Verify the current Stripe and OpenAI behaviour yourself before acting on any step, because the README describes a moving target and the last push was on 2026-09-13.

Frequently asked questions

Official sources

1. Issues
2. leon7482/chatgpt-plus-codex on GitHub
3. License: MIT
4. Project website
5. README