gpt-daichong: a Chinese-language guide to buying ChatGPT Plus and Pro without an overseas card

What gpt-daichong actually is, and who it is written for

The repository name suggests a tool. It is not one. The default branch holds Markdown guides, a Jekyll layout directory, a CITATION.cff, an llms.txt, and three example folders. There is no installer, no service, no CLI. The primary language entry is HTML, which comes from the layout templates rather than from an application.

The subject is payment access. OpenAI bills ChatGPT Plus at 20 USD per month and Pro at 100 or 200 USD per month, and those charges normally require a card that works for the region. The README frames the audience as users in mainland China who have no convenient overseas bank card and want an Alipay or USDT path with Chinese-language order tracking. It also addresses people who already pay but keep hitting usage limits and are deciding between Plus, Pro 5x and Pro 20x.

The guides are all written in Simplified Chinese. An English README.en.md exists at the top level, but the detail lives in the Chinese files: CHATGPT_PLUS_DOMESTIC_RECHARGE.md, GPT_PLUS_PRO_COMPARISON.md, CHATGPT_PAYMENT_ORDER_TROUBLESHOOTING.md and others. If you cannot read Chinese, most of the substance is out of reach.

How the repository is put together and how a purchase is meant to flow

The architecture is a set of Markdown documents plus a Jekyll site configuration, with the README acting as a hub that links to the deeper files. Each guide carries a review date. The README states it was re-checked on 2026-09-16, and the price table is dated 2026-09-01. That dating is the most useful structural feature here: it tells you when a number was true rather than implying it still is.

The purchase flow described in the README has five steps for Plus. Open the Plus page and check the live price, stock and payment methods. Enter a contact method used for order lookup and pay. After automatic delivery, read the card code and the Chinese instructions on the order page. Complete the remaining steps in your own browser. If the page does not redirect back, query the order instead of paying again.

Pro 5x and 20x run differently. The README says those are handled manually per order, typically within about 2 to 5 minutes when nothing goes wrong, and that the service does not ask for your login password, verification code or recovery code. The account-side step is done by the user in their own browser, and the README tells buyers to confirm the final plan state on their own official ChatGPT account page.

One eligibility rule is stated plainly for Pro 20x: the original subscription must not have been opened through the Apple App Store or Google Play, and the account must still be within its term or still show Pro 20x after expiry. First-time 20x purchases, upgrades from another plan, and accounts that no longer display 20x are listed as outside the scope of that renewal service.

No install step: what the subscription reconciliation example contains

There is no install step for the repository itself. The README points at examples/subscription-reconciliation/README.md and describes it as containing constructed data, expected output and a verification script that runs offline. That folder is the only place in this repository where you run something rather than read something.

The honest starting move is to open that example's own README before executing anything, because the top-level README does not name the script or the data file it reads. The example is about reconciling subscription records against expected state, which mirrors the manual check the guides ask buyers to perform: compare what you paid for against what your account shows.

For the guides themselves, there is nothing to install. Open the Markdown file for your case, or read the rendered pages through the Jekyll layout if the site is built. The payment links in the README carry UTM parameters that identify the GitHub guide as the referral source, which is worth noticing: this repository is a funnel for a commercial service, and the tracking is explicit in the URLs.

Where the documentation stops being documentation

The strongest content is the troubleshooting material. CHATGPT_PAYMENT_ORDER_TROUBLESHOOTING.md covers the failure modes that matter: payment succeeded but nothing arrived, order stuck in processing, duplicate payment, refunds and invoices. The README answers four of these directly and gives a sensible first instruction, which is to query the original order rather than pay a second time.

The refund language is careful in a way that is worth reading closely. The README states that a full refund is initiated immediately after customer service confirms the agreed delivery was not completed, and then adds that the time to actually receive the money depends on the original payment channel, bank or on-chain confirmation. That distinction between initiating a refund and the money landing is stated rather than blurred, which is more than many reseller pages do.

The weakness is evidence. The section on user feedback is compiled by AIXiamo itself from authorized communications, anonymized, and reports repeat corporate purchasing and personal referrals. That is the reseller describing its own customers. Nothing in the repository is an independent test, and no delivery rate, dispute rate or refund rate is published. The claim of "4.2万+ users" is presented as something AIXiamo's own site displays, not as a verified figure. If you need third-party validation before spending money, this repository does not provide it, and the README does not pretend otherwise.

Price comparison, with the caveats the README attaches

The README publishes a dated comparison of named resellers as of 2026-09-01: GetPlus around 148 CNY, AIXiamo at 153.8 CNY, PayAI.Plus at 179 CNY and PayForChat at 199 CNY. It states that AIXiamo is 5.8 CNY above the lowest sample and does not claim to be the cheapest on the market. That restraint is unusual for this kind of page and makes the table easier to trust as a snapshot.

The plan table gives AIXiamo prices of 153.8 CNY for Plus, 719 CNY for Pro 5x and 1269 CNY for Pro 20x, against official tiers of 20, 100 and 200 USD per month. The README explicitly says these are a snapshot from the review date, not permanent prices, and that live price, stock, payment method and processing time can change.

Payment rails listed are Alipay, USDT-BEP20 on BSC and USDT-TRC20 on TRON. WeChat Pay is not a self-service option; the README says to contact customer service for manual assistance before paying. It also warns that BSC and TRON must not be mixed up when sending USDT, which is the kind of mistake that loses funds permanently.

For anyone already holding a working overseas card, the README's own table points at OpenAI's official subscription as the first option. The third-party path is framed as a fallback for people who lack that card, not as an upgrade.

The alternative that does not involve a reseller

The README lays out four paths side by side: OpenAI's own subscription, Apple or App Store billing, a domestic third-party recharge, and shared or rented accounts. The differences are concrete rather than rhetorical.

Buying directly from OpenAI keeps the billing relationship and the account with one party, and the official help pages the README links to cover payment methods and plan usage. The cost is that you need a card and billing details that the region accepts, which is exactly the constraint this repository exists to work around.

Apple or App Store billing suits people who already have a working Apple account in a supported region and understand that store's renewal behavior. The trade-off is that the plan is tied to that store account, and the README's Pro 20x eligibility rule shows why that matters: subscriptions opened through the App Store or Google Play are excluded from the renewal service it describes.

The fourth path, shared or rented accounts, is the one the README advises against for private chats, work material or long-term use, citing control, privacy, multi-user conflicts and interruption risk. That is a fair summary of why account sharing fails, and it is the clearest recommendation in the document.

Licence, maintenance and what a reader is actually adopting

The licence field reads NOASSERTION, so GitHub could not classify the LICENSE file automatically. There is a LICENSE at the top level and a CITATION.cff, but the repository does not state terms in plain language. If you intend to reuse the text or the examples in your own project, read the LICENSE file itself rather than assuming an open licence applies. Nothing here is legal advice.

The repository is not archived, and the last push was on 2026-09-17. The guides carry explicit review dates, with the README stating a 2026-09-16 re-check and the price comparison dated 2026-09-01. That pattern implies the maintenance cost is ongoing editorial work: prices, payment methods and OpenAI plan rules change, and every guide that quotes a number has to be revisited or it ages into misinformation.

That is the real cost of adopting this repository as a reference. You are not taking on a dependency you must patch. You are taking on a document whose accuracy has a shelf life measured in weeks, and whose most load-bearing numbers come from a vendor that is also the subject of the guide.

Editorial conclusion

Read this repository as a dated price and process record, not as a tool. It is useful if you are in mainland China without an overseas card and want to see one reseller's published prices, payment rails and order-query steps before you pay. It is not for you if you already have a working overseas card, or if you need the repository to prove anything about delivery reliability: the only evidence offered is authorized anonymous user feedback and the reseller's own pages. Verify three things yourself before paying: the live price on the checkout page, whether the flow asks for your ChatGPT password or verification code (the README states it does not), and whether your account shows the expected plan afterwards on OpenAI's own subscription page. The SQL example under examples/subscription-reconciliation is the one piece you can run offline, and it is the only part of this repository that behaves like code.

Frequently asked questions

Official sources

1. Issues
2. momochoog/gpt-daichong on GitHub
3. Project website
4. README