Read This Before Subscribing to ChatGPT or Claude: Card Setup, Limits and Fixing Declines
Subscribing to ChatGPT or Claude with a virtual card for the first time? Confirm your BIN range supports AI subscriptions, use an aged account and a dedicated US IP, copy the card's billing address and keep the tax-inclusive price on the card; if a charge is declined, stop and read the Transactions tab. We turned months of ledger reconciliation and support tickets into steps a beginner can follow, with three real cases, a cool-down schedule and an FAQ.
- First, Understand the Three Checkpoints
- Step 1: Make Sure Your BIN Range Supports AI Subscriptions
- Step 2: Prepare Your Account, Network and Billing Address
- Step 3: Setting Your Limit and Balance
- Step 4: Attaching the Card, Paying and 3DS
- Declined? Stop, Then Read the Transactions Tab
- Three Real Cases
- After You Subscribe: Renewals, Cancelling, Leftover Money
- FAQ
- Further Reading
Subscribing to ChatGPT or Claude with a virtual card for the first time? One sentence covers it: confirm your BIN range supports AI subscriptions, get your account, network and billing address ready, and keep enough on the card to cover the tax-inclusive price; if you are declined, stop and read the card's transactions — do not keep retrying. This guide is written for complete beginners. Every point in it comes from months of reconciling our ledger transaction by transaction and working through support tickets one at a time — not internet folklore, but steps you can follow and see results from.
First, some reassurance: on a BIN range that supports AI subscription scenarios, "the card itself doesn't work" is almost never the reason a payment fails. We re-check OpenAI and Anthropic (the company behind Claude) transactions every month: the $0 verification at card binding shows no failure records in our ledger, and no proactive issuer declines. With user-side causes excluded — insufficient balance, a wrongly entered billing address, mistyped card details and the like — charges at the major AI subscription merchants have mostly gone through in our ledger (definitions and the latest monthly figures are in the AI Payment Compatibility Index). So when you are declined, the real question is "which step did I not get right?" — and the sections below walk through them in order.
1. First, Understand the Three Checkpoints a Subscription Charge Passes
After you click "Subscribe", the payment has to clear three checkpoints in a row. The most common beginner mistake is to conclude "the card is broken" the moment it is declined — but each checkpoint looks at completely different things, and once you know which one stopped you, the problem is half solved:
| Checkpoint | Who checks | What they check | If it fails here, you will see |
|---|---|---|---|
| First | The merchant (OpenAI, Anthropic) and its payment provider | How old the account is, how clean the network (IP) is, whether you behave like a normal user, whether the billing address and the IP are in the same country — it vets the person, not the card | An error on the payment page, but not a single record in the card's transactions |
| Second | The card network (Visa / Mastercard) | Whether the card number is well-formed and the request can be routed to the issuer — a pure format check | Usually only a mistyped card number gets stuck here |
| Third | The issuing bank | Whether the expiry date and CVC are correct; whether this amount exceeds what is left on the card — a mechanical check with no "mood" involved | A failure record stating the specific reason in the transactions (with one exception when the limit is short — see section 6) |
- There is a failure record in the transactions → the request reached the issuer (checkpoint three); fix whatever reason the record states — a matter of minutes.
- There is nothing in the transactions → first check whether the card has enough money for this charge; if it does, the first checkpoint (the merchant) stopped you — and ten different cards would get the same result. What needs fixing is the account and the network.
Before these three checkpoints there is one more "foundation": which BIN range your card belongs to. If the foundation is wrong, the three checkpoints do not even matter — which is why it is step one.
2. Step 1: Make Sure Your BIN Range Supports AI Subscriptions
Every card belongs to a "BIN range" — think of it as the "product line" an issuer sets up for a batch of cards. Issuer policy differs from range to range: some BIN ranges explicitly support AI subscriptions, some do not. If you use an unsupported range for ChatGPT or Claude, the failure is an "unsupported BIN range" problem — no amount of work on your account, network or address will help; just switch to a BIN range that supports AI subscriptions.
How to check, in three situations:
- You have not opened a card yet: on the "Open a new card" page, click "Pick by purpose" and choose the AI subscriptions category — the BIN ranges listed there are the ones that support it. Each BIN range's description states which scenarios it supports and which categories it prohibits; spend 30 seconds reading it before you open the card.
- You already have a card: open the card detail page and check whether the BIN range's usage notes mention AI subscriptions.
- You want to buy API credits: read the BIN range description once more — some ranges state that they do not support API credit top-ups, so do not use them to top up an API account.
The scenarios listed in a BIN range's description are the ones we have tested and seen work; anything not listed is not necessarily impossible, but we will not vouch for it. The page is always authoritative.
3. Step 2: Before Attaching the Card, Prepare Your Account, Network and Billing Address
This step decides whether you clear the first checkpoint. Start preparing a day or two in advance — do not leave it to the moment you pay.
Account: at least a week old, and actually in use
- Ideally the account is at least a week old and has seen normal use every few days during that week (a few chats on the free plan, for example). An account that was just created — especially one created through a proxy and immediately used to attach a card — is very likely to be declined; even if it squeaks through, the merchant may later ask it to verify its identity.
- For your first subscription, skip the "free trial" entry. A trial still requires a card but charges almost nothing, and merchants vet that entry more strictly, so the success rate is low. Use the normal subscription entry — getting through on the first try is worth far more than a free month.
- One card per account. We do not limit how many accounts a card can be attached to, but merchants may treat "several accounts sharing one card" as a risk signal.
Network: one fixed, dedicated US IP
- For 24–48 hours before attaching the card, stay on the same US node — not the US today and Japan tomorrow, and not hopping between the US east and west coasts either. Already hopped? Wait a day before attaching the card; forcing it only burns attempts.
- The key word is "dedicated". Public proxy nodes and IPs shared by many people have very likely been blacklisted by merchants already, and then everything else you did right will not help. A residential IP is better than a data-center IP, but that is a bonus; being dedicated is the pass mark.
- Self-check before paying: open ipinfo.io and confirm that country shows US.
Three things must be in the same country
The card's issuing country, the country of the IP you pay from and the country of the billing address you enter must all match (for a US card, all three are the US); ideally, the state of your IP and the state of the billing address match too. A country mismatch is the most typical reason for being stopped at the first checkpoint.
Billing address and name: copy the full set from the card detail page
Open the "Billing address" section of the card detail page: the system has already assigned the card a full set of details — a name plus a US address. It exists precisely for you to copy into the checkout page — if you are unsure what to enter, use it exactly as shown. This matters: on BIN ranges that support AI subscription scenarios, among the card-side failures we attributed one by one, the most common kind is exactly "the address entered at checkout does not match the set on the card detail page", followed by insufficient available balance on the card, with the remaining causes scattered (per our ledger, reconciled transaction by transaction and re-checked monthly).
- Name (Full name / Name on card): enter the "Name" shown in the billing address. Do not enter the card nickname (that is only for telling your own cards apart), and do not enter your own name — the name and address belong to the same set.
- Address line 1: street only — house number plus street name.
- Address line 2: leave it empty. Writing N/A, a company name or the street again in this field is a common, avoidable failure.
- City / State / ZIP: copy city, state and ZIP code exactly; the three must match each other.
- Phone, email: usually optional — you can leave them blank.
- Watch out for browser autofill: it can quietly put an old address you used before back into the checkout page, so check before submitting.
- ⛔ Do not copy "universal US addresses" circulating online: thousands of people sharing one address is itself a pattern risk systems watch for.
This is one of the questions our support team hears most, and there is no one-size-fits-all answer: issuers behind different BIN ranges handle billing addresses differently. So whether you may change it, and whether changing it affects payments, always follow what the card detail page shows and says — do not apply someone else's experience on a different BIN range to your card.
In practice one rule is enough: when you are declined, retry with the card's original address set first, instead of switching straight away. The original set was issued together with the card and is the most reliable starting point; once you have ruled out the address with it, move on to the account, network and balance — that keeps the troubleshooting orderly.
Card number, expiry date, CVC: always use the copy buttons
- How to see the full card number: the full card number is shown as soon as you open the card detail page; for the expiry date and CVC, click “Show card details (expiry / CVV)” and pass two-factor authentication (2FA). The first time, you need to turn on 2FA under "Security settings" and complete identity verification.
- Do not copy by hand — use the copy buttons on the page. One misread digit is one failed attempt — we have seen tickets where the same wrong CVC was submitted four times in a row.
- The expiry date format is month/year (MM/YY) — for example, 07/28 means July 2028. Do not swap the month and the year.
4. Step 3: Setting Your Limit and Balance (Where Beginners Trip Most)
First, tell the two kinds of "money" apart
- Account balance: the money you topped up to the platform — think of it as your wallet.
- Card balance: the money you move from your account balance onto a particular card — the cash you put in that card's pocket. A merchant charge only looks at how much is on that card; it never touches your account balance.
Every successful charge takes something out of the pot, and when it is used up, it is gone; topping up the card makes the pot bigger. So a card opened with $30 is not "$30 a month" but "$30 in total, plus whatever you top up". "It worked last time but not this time" most likely means the last charge already used the money up (see the $17.64 case in section 7).
The list price is not what gets charged: budget with this table
| Subscription | List price (per month) | Keep at least this on the card |
|---|---|---|
| ChatGPT Plus | $20 | ≥ $26 |
| ChatGPT Pro | $200 | ≥ $210 |
| Claude Pro | $20 | ≥ $25 |
| Claude Max 5x | about $100 | ≥ $110 |
| Claude Max 20x | about $200 | ≥ $210 |
Why keep more than the list price: in our ledger, ChatGPT charges take three shapes — exactly $20.00; around $21 (where the billing address's state charges sales tax on subscriptions); and $24–25 (when the account has an unpaid bill, the next charge collects it too). Sales tax is calculated from the billing address location — it is not a variable you can act on; just budget for it, and do not fiddle with addresses over a dollar or two. In our ledger, Claude charges show neither tax differences nor catch-up charges. The minimum issuance limit on the card-issuing page (currently 30 USD — the page is authoritative) already covers all of these for the $20 tier, so for your first card, following it is enough.
Keep only this period's money on the card, and leave renewals to auto top-up
- Keep only what this billing period needs on the card and leave the rest in your account balance. If anything goes wrong, the impact is as small as possible, and unused money is not locked up on one card.
- Worried you will forget to top up before a renewal? Turn on "Auto top-up" on the card detail page and set a monthly auto top-up cap. The system will then top the card up from your account balance when a subscription bill is due or when a charge fails because the card balance is too low. The fee is the same as a manual top-up, and the amount you top up is the amount credited.
- With auto top-up on, remember to keep enough in your account balance — it moves money from your account balance to the card, so it cannot help once the account balance is empty.
Two kinds of small fees worth knowing
- Card top-up service fee: topping up a card (including the limit you load when opening it) carries a service fee tiered by that month's cumulative card top-up volume; the amount you enter is the amount credited, and the fee is deducted separately from your account balance. For the exact rates, see the pricing page.
- Per-transaction fees: some BIN ranges charge a "Declined transaction fee" for each failed charge, and each 3DS verification a merchant starts carries a small verification fee — they differ by BIN range and are itemized under "Fees for this card" on the card-issuing page. That is one more reason not to keep retrying after a decline: every extra attempt may cost another fee.
5. Step 4: Attaching the Card and Paying — Don't Panic at 3DS
For your first subscription, use a desktop browser
- ChatGPT: open the web version in a desktop browser and click Upgrade. Do not pay the first charge inside the mobile app — the app's upgrade button goes through app-store in-app purchase, which adds another layer of risk control, and cancelling later also has to go through the app store. Once you subscribe on the web, you can log in to the same account on your phone and use it there.
- Claude: subscribe on the web version as well (avatar at the bottom left → Settings → Billing).
The "$0 verification" when attaching a card is not a charge
- Many merchants first send a $0 or small (commonly $1) verification when you attach a card, just to confirm the card is live, and reverse it shortly afterwards. If you see such "authorized" or "reversed" records in the transactions, there is nothing to worry about.
- On BIN ranges that support AI subscription scenarios, this step shows no failure records in our ledger — as long as the card number, expiry date and CVC are copied correctly, "this card won't attach" does not exist in the data. If attaching the card fails right away, it is almost always the first checkpoint (account / network) or mistyped card details.
- But a successful card attachment ≠ every later charge will succeed: the real charge still has to clear the card balance and the merchant's risk control.
What to do when a 3DS check appears
- Some merchants add an extra security check (3DS) at payment time and ask you for a code. The code appears in real time in the "3DS verification code" section of the card detail page, and is also sent to your registered email.
- Keep the payment page open and enter the code as soon as you get it; if it times out, you have to start the payment again.
- Each verification a merchant starts (including frictionless ones where you enter no code) carries a verification fee by BIN range (currently $0.20 each — the card detail page is authoritative); BIN ranges without 3DS support are not affected.
How to confirm the subscription really went through
It only counts when both sides agree: the merchant shows the paid plan (a Plus badge next to your ChatGPT avatar, the current plan on Claude's Billing page), and the card's transactions show a charge of the matching amount. The charge record is what counts — a page can occasionally "look successful" because of caching, but only the transactions tell you whether money actually left.
6. Declined? Stop First, Then Read the Transactions
One premise first: all of the troubleshooting below assumes your BIN range has already been confirmed to support AI subscriptions. If the range itself is unsupported (section 2), just switch ranges — there is no need to go further.
First: stop — do not keep retrying
When the same account and the same card fail several times in a short period, merchants and payment gateways treat it as "card testing" fraud; the risk score keeps climbing, until even a perfectly clean setup and a good card are declined instantly — and some BIN ranges charge a declined transaction fee for every failure. Most importantly: if the cause is not fixed, retrying a hundred times gives the same result.
| Situation | What to do | Minimum wait |
|---|---|---|
| 1st failure | Find the cause using the method below, fix it, then try again | Wait at least 1 hour |
| 2nd failure | Stop completely and recheck the account, network, "same country for all three" and card balance from scratch | Cool down 10–24 hours |
| 3rd time | Never make a third attempt in a row. A third consecutive attempt may well trigger an anti-fraud lock | Change your approach, not your card |
Note: merchants and payment gateways never publish their exact thresholds. This table reflects what our support team has observed over a long period, and it is deliberately on the cautious side — it is not an official number.
Second: open the card detail page and read the Transactions tab
The card detail page has a "Transactions" tab that records every charge, verification and failure on the card (some people call it the card's spending history).
Case A: there is a failure record in the transactions. The request reached the issuer. Every failure record states its reason; fix it using the table below:
| Reason shown in the transactions | What it means | How to fix it |
|---|---|---|
| Not enough balance on the card | What is left on the card does not cover this charge (often because tax was not counted, or another subscription was charged first) | Top up the card to at least this charge's tax-inclusive amount; or turn on auto top-up |
| The card is not usable right now | The card is frozen, closed or not yet activated | Check its status under "My cards": unfreeze a frozen card; replace a closed one |
| The CVC security code did not match | The CVC was entered wrongly | Re-enter it with the copy button on the card detail page |
| The expiry date is wrong | The expiry date was entered wrongly, or month and year were swapped | Re-enter it as month/year (MM/YY) |
| This merchant category is not supported by the card | The card's BIN range (or the allowlist set when the card was opened) does not cover this kind of merchant | Switch to a BIN range that supports AI subscription scenarios; the allowlist is fixed when the card is opened and cannot be changed afterwards |
| The card issuer does not allow this card to be used with this merchant | The issuer restricts this merchant | Switch to another BIN range |
| The bank did not return a specific reason | An occasional decline with no stated cause | Try again later following the cool-down pace above; if it keeps failing, contact support |
Case B: there is nothing at all in the transactions. Check in this order:
- Do the math first: does what is left on the card cover this charge's tax-inclusive amount? If not, the issuer declines it; such a decline usually leaves a failure record in the transactions, but some leave no record at all (case 2 in section 7 is exactly this) — just top up the card.
- Enough money, still no record: then the merchant's risk control at the first checkpoint stopped your account or network, and the request never reached the card. In that case switching cards will not help. Check: is the account a week old and in normal use? Did your IP jump countries before you attached the card? Are you on a shared node? Do the "three things in the same country" match? Did you go through the free-trial entry?
Still unsure? Come to us
Open the live chat at the bottom right of the site, or submit a support ticket, and tell us three things: which platform (e.g. ChatGPT, Claude, OpenAI API), roughly when, and a screenshot of the error on the payment page. From the card-side records we can locate that exact attempt and tell you which checkpoint it stopped at.
7. Three Real Cases (From Support Tickets, Anonymized)
Case 1: declined when attaching the card — yet not a single record on the card
A user added a payment method in OpenAI's API dashboard, filled in the card number, clicked continue, and got the red message "Your card was declined". His conclusion: the card was broken, and he wanted a refund.
What really happened: OpenAI and its payment provider stopped the attachment at the first checkpoint; the request never reached the issuer. The reasons had nothing to do with the card — the account was only a few days old, the node was shared by many people, and the card was attached right after sign-up with repeated attempts. Ten cards would have produced the same result; what needed fixing was the account and the network (section 3).
Case 2: the $17.64 limit mystery
This case shows best what "the limit is a total pot" means. Here is what the user did:
- Opened a card with a limit of $17.64;
- Attached it once at Anthropic and once at OpenAI — both succeeded ($0 verification passed);
- Bought $10 of OpenAI API credit — succeeded;
- Then tried $16 of Claude credit — failed;
- Went back and tried $10 of OpenAI credit again — also failed;
- The user's conclusion: "it worked this morning and broke in the afternoon".
The most confusing part is "the same $10 succeeded the first time and failed the second" — because the first success itself used up the limit. If "the same action sometimes works and sometimes doesn't", check how much is left on the card before suspecting the card.
Case 3: declined 8 times in 7 minutes, succeeded once after a 5-minute pause
On the day of a monthly Claude renewal, Anthropic charged $20 to the user's card and was declined. Over the next 7 minutes:
- The user retried $20 at once — declined; tried again — declined again. Declined 8 times in a row within 7 minutes, each time for the same reason: the card's limit at the time did not cover this charge;
- The $0 card verifications in between succeeded every single time — the card itself was working;
- After the 8th failure, the user stopped and raised the card's limit enough to cover the charge;
- Five minutes later, the same $20 went through on the first try. No renewal has failed since.
The lesson: none of the first 8 attempts was "almost there". The cause never went away; retrying only piled up risk score and left a trail of failure records. The right order is: failure → read the transactions to find the cause → fix it → try once more. This user did not switch cards or open a ticket, and solved it alone in five minutes.
8. After You Subscribe: Renewals, Cancelling and Leftover Money
- Renewals: the charge repeats automatically on the same day each month. The card needs enough money before each renewal; with auto top-up on, you do not have to think about it (as long as your account balance is enough).
- To stop renewing: cancel the subscription in the merchant's settings (ChatGPT manages it under Settings; Claude under Settings → Billing). Do not freeze the card instead of cancelling — freezing only makes the renewal charge fail, the merchant may record it as an unpaid bill, and whenever you resume, the next charge collects the arrears too.
- When a merchant refunds you: once the merchant refund arrives it is released automatically, back to the card or to your account balance depending on the card type (shared cards refund to your account balance); how long it takes to arrive depends on the merchant. Merchant refunds carry a refund fee under the platform's rules — see the pricing page.
- Money left on the card: if you will not use the card again, you can move the card balance back to your account on the card detail page, or simply close the card and get the balance back to your account balance in full — neither costs anything. Moving funds back has a few conditions (for example, 30 minutes since the card's last transaction, and $1 stays on the card); the page shows how much you can move right now.
9. FAQ
The payment page says "Your card was declined" — does that mean the card is broken?
Not necessarily. It is the merchant's generic message and does not tell you which checkpoint declined it. First check the card's transactions for a record and its reason (section 6), then draw conclusions. In our data it comes more often from the merchant's own risk control (case 1) or from too little money on the card (cases 2 and 3).
Why did the same card work yesterday but not today?
The most common answer is money: the card's limit is a one-time total pot, and every successful charge reduces it (case 2); next most common, another subscription's renewal took the money first. "Sometimes it works, sometimes it doesn't" is almost always a numbers problem, not a card-status problem.
The card attached successfully — does that mean every later charge will go through?
No. Attaching a card is a $0 verification that only proves the details are right and the card is live; the real charge still has to clear the card balance and the merchant's risk control, and occasionally 3DS.
What is the harm in retrying right after a decline?
Three harms: if the cause is not fixed, the result will not change; consecutive failures push up your risk score and can get you temporarily locked; and some BIN ranges charge a declined transaction fee for each failure. Follow the cool-down pace in section 6: after fixing the first failure, wait at least an hour, and never make a third attempt in a row.
Can I just enter any US address as the billing address? Can I change it myself?
We do not recommend entering just any address. The safest approach is to copy the full set assigned on the card detail page (name + address); what matters is that it is in the same country as the IP you pay from, ideally the same state. Whether you may change it, and whether changing it affects payments, depends on the BIN range — follow what the card detail page shows and says; when declined, retry with the original set first.
I subscribed to the $20 ChatGPT Plus — why was I charged a little over $21?
Some US states charge sales tax on subscriptions, calculated from the billing address location, so the amount charged can be a little above the list price; if the account has an unpaid bill, the next charge also collects it and can reach $24–25. Nobody is overcharging you — just keep a little extra on the card, per the table in section 4.
Buying API credits keeps getting declined — what should I do?
First check whether the BIN range description allows API credit top-ups (section 2). If it does, note that merchants vet "a new card whose very first charge is a credit purchase" more strictly than a monthly subscription — in our experience, it goes much more smoothly if you first complete a subscription (or at least one successful transaction) with the card and buy credits a day or two later. Card-side failures here are mostly just not enough money — keep enough on the card for the amount you plan to buy.
Where do I find the 3DS verification code?
It appears in real time in the "3DS verification code" section of the card detail page and is also sent to your registered email. Keep the payment page open and enter the code as soon as it arrives.
10. Further Reading
- ▸ How to Subscribe to ChatGPT Plus — the Complete Guide to Sign-Up, Card Payment and Cancellation
- ▸ How to Subscribe to Claude Pro — Choosing Between Pro and Max, Payment Setup, and Canceling
- ▸ ChatGPT Plus Payment Declined: Check the BIN Range First, Then Your Account
- ▸ Card Binds Fine but Every Charge Fails: A Full Investigation of a Claude API Top-Up Failure (Root Cause: 3DS)
- ▸ AI Payment Compatibility Index (updated monthly)
Sources: transaction-by-transaction reconciliation of AI-merchant activity in the platform ledger (re-checked monthly) and real support tickets; identifying details in the cases are anonymized. Fees, minimum amounts and similar figures mentioned here follow what the pages show. By the RDVCC Payments Research Team · Original text reviewed by Steven Cai
Pain point solved? Try RDVCC Virtual Credit Card
issuance from $1 · USD deposits · Works with 100+ international platforms