How to Subscribe to ChatGPT Plus — the Complete Guide to Sign-Up, Card Payment and Cancellation

If your local cards are declined, subscribing to ChatGPT takes three things: an OpenAI account at least a week old with a normal usage history, a stable US IP that does not jump around, and a virtual credit card on a US BIN whose BIN range itself supports AI subscription scenarios (together with a US billing address). With all three in place you click Upgrade to Plus in a browser, it takes effect within seconds, and a charge of roughly $20 lands on the card. This ChatGPT subscription guide follows that single thread from start to finish. The point is not which button to click, it is what payment risk control is looking at behind each step — which is the real reason the same card and the same money get one person through on the first try and another declined five times in a row.

1. The Flow in One Line (for People With 30 Seconds)

Conclusion first. The whole subscription chain is only five steps, and steps 1 and 2 need to be prepared days in advance — only the last three are things you actually do at the keyboard:

1. Age the account: register an OpenAI account, let it sit for at least a week, and chat on the free tier a few times during that week.
2. Settle the environment: lock onto one dedicated US IP 24-48 hours before you attach the card, and do not switch countries or regions in that window.
3. Prepare the card: first check on the card-issuing page that the BIN range description says AI subscription scenarios are supported, then issue a US BIN virtual card. Starting at the minimum issuance limit shown on that page is enough (currently 30 USD, whatever the page shows is authoritative), and write down the US billing address that comes with it.
4. Attach the card and pay: go to Upgrade in a desktop browser (not the mobile app), fill in the card plus the billing address, and submit.
5. Stop on failure: do not hammer the button after a decline. Fix the cause, wait at least an hour, and never make a third consecutive attempt.

2. What ChatGPT Costs — the Official List Price Is Not the Amount You Get Charged

The official list price is $20/month, but in the clearing records the charge that actually reaches the card takes three shapes. This is not an exchange-rate effect. It is decided by two things: whether the state of the billing address levies sales tax, and whether the account has an unpaid balance:

Source of these amount shapes: a transaction-by-transaction review of OPENAI subscription merchant family authorizations in our own ledger, data through 2026-07-17. Shapes and distributions differ by merchant family, so do not apply this set to another. ChatGPT Pro at $200/month is separate — for that tier, plan on funding the card to ≥$210.

One more number often mistaken for a fourth shape: $19.99. It is not a charge shape in our ledger — it is the price Google Play shows for the Android in-app purchase, which runs on Google’s billing rail with Google, not OpenAI, as the acquirer. Section 3 explains why we do not recommend that path.

So do not set the limit right at $20. For the $20 tier, keep ≥$26 on the card — that number exists to cover the $24–25 arrears shape peculiar to ChatGPT, and the tax-inclusive ~$21 shape is covered along the way. In practice you do not have to do this math yourself: the minimum issuance limit on the card-issuing page (currently 30 USD, whatever the page shows is authoritative) already covers every shape above, so just issue at that. One more reminder: the card-attach step is a $0 verification authorization and moves no real money, so do not expect a “charge a dollar and see” test to tell you whether the card works.

For how to choose between the Plus / Pro / Business / API tiers and what a year really adds up to, see what a ChatGPT subscription actually costs.

3. ChatGPT Payment Methods: Three Paths, Separable on the Statement, Different Risk Controls

The same card going in through different entry points faces completely different risk control. We can separate them because every entry in the clearing records carries a merchant descriptor, and the three paths use different ones:

Two more descriptors you will see on statements: the $0 verification authorization from attaching a card shows as a bare OPENAI (not a charge); buying credit inside ChatGPT shows as OPENAI* CHATGPT CREDIT. Reconcile by these shapes and nothing gets mixed up.

How to use this distinction

• The web subscription has the highest bar of the three, and it is still the one you should take. A subscription is a recurring charge, and the acquirer scrutinizes it noticeably harder than a one-off top up. Given a correctly chosen BIN range (one that supports AI subscription scenarios), the bulk of failures on this path come from an account / IP / address that do not line up, or from not funding enough — exactly what sections 4, 5 and 6 solve.
• If you only want the GPT models, you do not necessarily need Plus. The API is one-off prepaid, from $5, and our month-by-month review of API-side authorizations shows that roughly nine out of ten failures are insufficient balance — in other words, “the card is no good” barely exists on the API side, only “not funded enough”. For writing a bit of text or running a few scripts, $5 of API credit is often cheaper and smoother than a $20 Plus subscription.
• We do not recommend the Android in-app path — not because it is expensive, but because it complicates the problem. The risk-control chain goes from one party (OpenAI) to two (OpenAI plus Google), so when something fails you cannot tell who declined it, and cancellation happens in Google Play rather than in ChatGPT’s settings. iOS in-app purchases run through Apple, adding the same extra layer.

4. Step 1: the Account — Why Its Age Decides Whether the Card Attaches

The account needs to be more than a week old, with a normal usage history across that week. An account younger than that — especially one registered behind a VPN and taken straight to checkout — will most likely fail outright; and even if it slips through, it tends to trigger KYC identity verification later, at which point no card swap will fix it.

What “normal usage” means concretely

• Log in a handful of times spread across the week and have a few normal conversations on the free tier — do not register and leave it cold, and do not blast hundreds of turns in a single day.
• Stay on the same IP and the same browser as much as you can — environmental consistency is itself a positive signal.
• Do not churn your password, email or region settings during that week.

About the trial entry point: do not use it for a first subscription

If OpenAI shows you a “free Plus trial” entry point, think before you click. A trial still requires a card, but the authorization amount is zero or near zero, and acquirers apply inherently stricter fraud screening to these zero-value sign-up flows — it is simply not the same review as an ordinary monthly purchase. If you want reliability, take the ordinary purchase path; getting through on the first attempt is worth far more than the month you would save.

Two common traps during sign-up

• Phone verification: the phone check at sign-up and the payment risk control that follows are two separate systems — do not conflate them. Which numbers to use, and why SMS-receiving services are a bad idea, is covered in the truth about ChatGPT phone verification.
• Account region: after you log in, go to Settings → Account and confirm the country reads United States. The region has to stay consistent with the IP and billing address that follow; do not run a US account on an IP that lives in another country all year — that kind of inconsistency is one of the more frequent reasons accounts get banned, covered in the real reasons Claude / ChatGPT accounts get banned.

5. Step 2: Three-Way Alignment of IP and Billing Address (Start 24-48 Hours Before You Attach the Card)

The rule is simple: the card’s country = the country of your IP at payment time = the country of the billing address. All three must match. Ideally the IP’s state and the billing address’s state match too. But timing matters more than filling the fields in correctly — and that is what nearly every other guide leaves out.

IP: no jumping around in the 24-48 hours before you attach the card

Payment risk control looks at more than where you are right now; it also looks at where you have recently been. If your IP bounces between countries and regions in the day or two before you attach the card, the account reads as high risk. So:

• Lock the node in advance: pick one US node and stay on it for the 24-48 hours before you attach the card, not Los Angeles today and Frankfurt tomorrow; if you have already jumped, wait 24 hours before attaching, because forcing it only burns attempts for nothing (see section 9).
• IP type: what matters is that it is dedicated, not datacenter versus residential. Many people assume a residential IP is mandatory — in practice the gap between datacenter and residential IPs is smaller than imagined, and what is truly fatal is sharing. Public shared nodes and IPs used by many people are quite likely blacklisted already, and no amount of cleanliness elsewhere helps. Given that it is dedicated, a residential IP does beat a datacenter one, but that is a bonus, not the pass mark.
• Self-check: before paying, open ipinfo.io and confirm the country reads US and the city is a real city rather than an obvious datacenter location.

★ The billing address: it is a set of details to copy into the checkout page, and what matters is that it shares a country with your IP

People immediately get stuck on “is this the card’s real registered address” and “can I pick a better one” — the wrong direction from the start. The billing address on the card detail page has one clear purpose: for you to copy into the merchant’s checkout page. When you fill it in, only one thing really matters: it has to be in the same country as your IP at payment time, and ideally the same state. A country mismatch — a US address paid from an IP somewhere else — is the classic failure shape at this stage; whether anyone actually lives at that street number is not what this step is about.

Why the same Plus subscription charges $20.00 for some people and just over $21 for others

Because sales tax on a subscription is computed from where the billing address is, and combined state-plus-local rates across the US differ quite a bit. That is where the $20.00 and ~$21 shapes in the section 2 table come from — a dollar or two of difference between people is normal. Nobody is being overcharged, and it is not an exchange-rate effect.

Knowing this is useful for exactly one thing: fund a little above the tax-inclusive amount instead of budgeting exactly $20 (the ≥$26 from section 2 already accounts for it). ⛔ Do not go fiddling with the billing address over a dollar or two — what you would save is nothing next to the cost of a cooldown after a failed payment. Besides, whether you may change it and whether changing it causes trouble comes back to the same line: it depends on the BIN range, and the card detail page is authoritative.

6. Step 3: Can You Pay ChatGPT With a Chinese Credit Card? — Getting a Card That Can Actually Pay OpenAI

To answer that frequent question first: RMB credit cards issued in mainland China do not work, and the China-issued “dual-currency” or “overseas spending” cards that carry an international network logo almost never get through in practice either. The reason is not whether the card can transact cross-border; it is that OpenAI’s acquirer looks at the issuing country of the card BIN — if that country is China, the three-way alignment from section 5 collapses on the spot.

So what you need is a virtual credit card on a US BIN. Five things to check when picking one, the first being the gate and the other four the details:

The first row is rigid: if the issuer policy for a BIN range explicitly does not support AI subscriptions, move to a range that does instead of burning time on that card. The fourth row is the one most often misread: the limit you set when issuing the card is one total pool, not a monthly allowance. If you plan to keep Plus long term, plan by total spend — a year is $240 and up, so do not size the card to the first month’s $20. A fuller list of decline reasons is in the top 10 reasons a virtual card gets declined.

7. Step 4: How to Fund for ChatGPT — Money Into the Account First, Then Into the Card

Strictly speaking ChatGPT has no “top up” at all; it charges a card monthly once attached. So “topping up for ChatGPT” really means two stages: first move money into your account balance, then top up the card from that balance, and finally let the card absorb OpenAI’s charge. The two pockets are separate — money in the account with an empty card still means the charge cannot go through.

Stage one: money into the account (two routes)

1. Route A · Step 1: copy your dedicated top-up address

   The top-up page has a receiving address that belongs only to you (TRC20 or ERC20), permanently valid and reusable. Use the copy button, do not transcribe it by hand — one wrong character in an on-chain transfer and the funds are unrecoverable.

2. Route A · Step 2: withdraw from the exchange, on exactly the right chain

   Paste the address into the withdrawal page, make sure the network matches exactly the chain shown on our page, enter the amount, confirm. Assets sent on the wrong network cannot be recovered; this is the most expensive beginner mistake there is.

3. Route A · Step 3: wait a few minutes for it to be credited automatically

   Once confirmed on chain the system credits it automatically, usually within a few minutes, with no screenshot to submit and no manual review. Once the amount reaches the minimum top-up, the fee is a flat 0.5% with no tiers (amounts below the minimum follow the rule in the note below; the rate shown on the top-up page is authoritative).

Route B: paying through the checkout

If you would rather not handle an on-chain transfer yourself, you can place an order and pay through the checkout. One pattern is worth remembering: when the amount paid matches the order amount exactly, it is likewise credited automatically within minutes; when the amounts do not match (say the payer’s side deducted a fee so a few cents less arrived), it goes to manual review and takes longer, so make the amount exact to the cent. Every top up has an order number in your top-up history and in the confirmation email; if nothing has been credited after 30 minutes, bring that number or the transaction hash to live support — far faster than describing how much you sent.

Stage two: topping up the card from your account balance

Once the money is in the account there is one more step, or the card stays empty. The rule for topping up a card: whatever you enter is what lands on the card, the card top-up service fee is deducted separately from your account balance rather than from the card, and the transfer is real time and effective immediately. The rate is a tier based on calendar-month cumulative card top-up volume: from 2%, dropping to 0.5% at high volume; when your month-to-date total reaches a new tier, the difference already collected at the higher rate that month is automatically returned to your account balance, and the count restarts on the 1st. It is not “per BIN range” — for the exact tiers, and which one you are in this month, go by what the Top up card dialog and the pricing page show.

For how the whole cross-border money path works, see cross-border payments 101.

8. Step 5: the Full Web Flow for Subscribing to ChatGPT Plus

With the first four steps prepared, this one takes three minutes. Do it in a desktop browser (reasons in section 3).

1. Step 1: confirm the environment, and check the card status while you are at it

   Use the node you have been on for the past 24-48 hours; do not swap to a “better” one at the last minute. Open ipinfo.io and confirm country = US. Then glance at your card list to see whether the card status reads Active — a card that is inactive or frozen gets declined outright. On a BIN range that supports AI subscription scenarios, this category accounts for nearly three in ten of the failed authorizations in our transaction-by-transaction attribution of the OPENAI subscription merchant family (our own ledger, data through 2026-07-17), and one glance avoids it.

2. Step 2: log in to ChatGPT and open the upgrade page

   Click your avatar at the bottom left → Upgrade plan → choose Plus, and the page hands off to the acquirer’s hosted payment page. If you cannot even get through this step, or it just keeps spinning, do not blame the card yet — that is a network environment problem.

3. Step 3: enter the card number / expiry / CVC — all via the copy buttons

   Do not transcribe by hand. The card-attach step runs a $0 authorization only, and our ledger shows no failure records for it, on the condition that these four fields are copied correctly — mistyping them is the one class of failure that cannot even clear the $0 verification. It does not appear in the charge-failure breakdown in section 9, because it is stopped earlier, at the card verification stage, before the $0 authorization ever goes through. But it is entirely avoidable, and every failure burns one of your precious attempts. The expiry format is MM/YY.

4. Step 4: enter the name and the billing address

   Copy the name and address from the card detail page, set the country to United States, and put only the street in Address line 1, leaving line 2 empty (how to fill it in is in section 5). Then scan it once: do the country, state and ZIP all point to the same place?

5. Step 5: submit, then stop

   Click Subscribe. On success the page flips to Plus within seconds, a confirmation email arrives at your registered address, and a charge of roughly $20 appears on the card. If it fails — do not click a second time. Skip straight to the next section.

How to confirm the upgrade really went through

• The avatar dropdown shows My Plan: Plus.
• Plus-only model options appear in the model picker.
• A subscription confirmation email from OpenAI arrives at your registered address (check the spam folder).
• A successful charge with the descriptor OPENAI *CHATGPT SUBSCR appears in the card’s account statement.

The fourth is the hardest evidence. The first three can occasionally “look successful” because of page caching, but whether the money actually moved is settled by the statement alone.

9. What to Do When You Are Declined — Confirm the BIN Range First, Then Keep the Cooldown

Troubleshooting step one: confirm this card’s BIN range supports AI subscription scenarios

This takes under thirty seconds, and it decides whether everything that follows is worth doing at all. For some BIN ranges the issuer policy explicitly does not support AI subscriptions — the BIN range description on the card-issuing page states which scenarios that range supports. If the card in your hand happens to sit in the “AI subscriptions not supported” group, the failure is an unsupported BIN range: switch to a range that supports AI subscription scenarios; however finely you audit the account, the IP, the billing address and the funding, it will lead nowhere.

Once you have confirmed the BIN range supports AI subscription scenarios, go on — from here the causes of failure sit on your own side. First a discipline, then how to locate the cause.

The right cooldown pacing

Troubleshooting step two: check whether the card’s account statement has a record

This single cut splits the problem into two classes and saves you most of the guessing:

• There is a failure record in the statement → the decline happened on the card side, each entry carries a stated reason, and you fix it per the table below.
• There is no record at all → the decline happened in OpenAI’s or the acquirer’s upstream risk control, and the request never reached the card. Swapping cards does nothing here — ten cards give the same result. What to check instead: is the account less than a week old? Did the IP hop countries right before you attached the card? Are you on a shared node? Does the billing address country match the IP country? Did you go through the trial entry point?

The real breakdown of card-side failures (check in this order)

The table below is about layer 2 — on the premise that this card’s BIN range supports AI subscription scenarios, that is, the case where the card itself tests out fine. Layer 1 (an unsupported BIN range) is not in this table; it never gets this far.

Definition: a transaction-by-transaction attribution of failed authorizations in the OPENAI subscription merchant family in our own ledger, data through 2026-07-17, on the premise of a BIN range that supports AI subscription scenarios. Under that premise these four categories are the whole of it — every cause sits on the user side and the account side (limit, card status, balance), with not a single issuer-side risk-control rejection. In other words, once the range is chosen correctly, nothing about card-side failures is mysterious; each one has a definite fix. The breakdown differs by merchant family, so do not apply this set to another (the Anthropic / Claude merchant family, for instance, has a different distribution).

To work through the code-level error messages one by one, see troubleshooting a declined ChatGPT subscription payment.

10. After Subscribing: Renewals, Invoices, Cancellation, and Getting the Rest of Your Money Back

• Renewal: charged automatically on the same day each month, in one of the shapes from section 2. Two days before the billing date, confirm the card balance is enough — a failed renewal first drops you to the free tier (conversation history is kept, advanced features stop), and repeated failures also leave a bad record on OpenAI’s side.
• Changing cards: update the payment method under Settings → subscription management. Changing a card is another card-attach, bound by the same constraints as sections 5 and 9: first confirm the new card’s BIN range supports AI subscription scenarios, do not hop IPs that day, and do not hammer retries if it fails.
• Invoices: you can download each period’s invoice from the billing page, and it shows the billing address you entered. Worth noting if you need to expense it.
• Cancelling: Settings → My Plan → Manage my subscription → Cancel. What has already been charged for the current period is not refunded, benefits run to the end of that period, and nothing is charged on the next billing date. If you want to subscribe again later, just resume on the same account; there is no need to age a new one.
• What about the money left on the card if you stop: the card balance can be pulled back to your account balance from the card detail page, free of charge, but only 30 minutes after that card’s last transaction (so recent transactions finish syncing and the balance you pull back is accurate); $1 stays on the card when you pull funds back, and it comes back with the balance when you close the card. Your account balance then goes back to your own USDT wallet, a step called a prepayment refund, at a flat $2 per request, payment-processor fees included — note that this is not a “withdrawal”: it returns prepaid funds you have not used, your account is not closed, and you keep using it as normal.

11. FAQ

12. Related Reading

• ▸ What a ChatGPT subscription actually costs — a real cost comparison across the Plus / Pro / Business / API tiers
• ▸ Troubleshooting a declined ChatGPT subscription payment — start here if you have already been declined
• ▸ How to choose a Claude subscription (Pro / Max 5x / Max 20x)
• ▸ The top 10 reasons a virtual card gets declined
• ▸ What is a virtual credit card — get the three definitions straight first: limit, balance and fees