ChatGPT Payment Declined: Payment Was Not Approved, Card Declined
“Payment was not approved.” and “Your card has been declined.” say a ChatGPT payment failed, not why. Check who bills you, the stage, and any charge first.
On this page

Do not pay again yet. A “payment declined” message can describe a failed first checkout, a renewal problem, a bank-authentication failure, or a charge that has not been matched to the account you are viewing. Retrying before you know which case you have can create a second subscription.
The exact wording does not add a cause. “Payment was not approved.”, “Your card has been declined.”, and “Your card was declined.” all say that the charge or card authorization did not go through. None of them says who refused it or why. OpenAI says it typically does not receive detailed decline reasons from banks, and as of October 22, 2026, no OpenAI help article explains “Payment was not approved.” itself. Nothing official describes these messages as an account ban. If the message appeared while you were claiming a free Plus offer or free trial, skip to that section below, because the next step is different.
Use these five checks before changing cards or platforms:
- Billing provider: Was the subscription purchased on chatgpt.com, through Apple, or through Google Play?
- Failure stage: Is this a first checkout, a free-offer or free-trial claim, a renewal, a charge with no paid access, or an account-binding problem?
- Region support: Are both your current location and the card issuer’s region supported?
- Charge status: Is there no charge, a pending authorization, or a posted charge?
- One next action: Correct one factual problem, complete bank authentication, contact the issuer, manage the current platform subscription, or open a private support case.
If the billing provider is unclear, a charge is pending or posted, or an existing subscription may still be active, stop. Do not purchase on another platform until that state is resolved.
Find the billing provider from a receipt, not from memory
The device where you use ChatGPT does not tell you who bills it. A person can use ChatGPT on an iPhone while paying on the web, or use the web while Apple owns the subscription.
| What the receipt shows | Billing provider | Where to investigate |
|---|---|---|
| A chatgpt.com or OpenAI web receipt | ChatGPT web | ChatGPT account payment settings and OpenAI Support |
| An Apple receipt or an entry in Apple Subscriptions | Apple App Store | Apple subscription and purchase history |
| A Google Play receipt or Play subscription entry | Google Play | Google Play subscription history and the applicable support channel |
| An API Platform invoice or credit purchase | API Platform | API billing, not this ChatGPT subscription flow |
| A Business workspace invoice | Business workspace | Workspace billing controls, not an individual Plus/Pro payment page |
OpenAI documents that ChatGPT and API billing are separate systems. A ChatGPT subscription does not fund API usage, and an API card problem should not be diagnosed with consumer subscription steps.
For an individual web subscription, the current official path is Settings → Account → Payment → Manage. An active subscription, scheduled cancellation, past-due invoice, or recent failure can affect what can be changed there; see OpenAI’s payment-method management guidance. Interface labels can change, so a current receipt and the live account page are more reliable than an old screenshot.
Name the failure stage before choosing a fix
The same short error can appear in different situations. Record one of these stages:
- First checkout: You have never had this subscription on the account and no payment completed.
- Free-offer or free-trial claim: The checkout showed a promotional Plus offer or trial with $0 (or ₹0, Rp0) due today, and the claim failed.
- Renewal: Paid access existed, but an automatic renewal failed or the account returned to Free.
- Charged but no access: The issuer shows a pending or posted transaction, yet the account does not show the expected plan.
- Duplicate or unauthorized charge: More than one platform charged, or you do not recognize the purchase.
- Mobile account binding: Apple or Google shows a subscription, but the ChatGPT account you are viewing does not.
This classification matters more than guessing whether a browser, bank, or payment processor “caused” the decline.
Confirm that both the user and issuer regions are supported
OpenAI’s current purchase guidance requires both the user and the card issuer to be in supported regions. The United States appeared on the official ChatGPT supported-country list as of July 22, 2026, and Indonesia and India were on it as of October 22, 2026. A country on the list does not prove an individual reader’s location, card-issuance region, account eligibility, or checkout availability.
If either side is not supported, stop. A VPN, false billing address, borrowed identity, or card issued for someone else does not turn an unsupported situation into a supported one and can add account and financial risk.
If both sides pass, continue with the exact error and the actual charge state.
Check whether money moved
A bank notification is a signal to investigate, not proof that a subscription completed.
| What you can verify | What to do now |
|---|---|
| No issuer record and no receipt | Continue with the first-checkout or renewal branch below |
| A pending transaction or authorization | Do not pay again; ask the issuer what the status represents and check the current billing provider |
| A posted charge but no paid access | Do not repurchase; match the receipt to the billing platform and ChatGPT account, then contact the support team for that platform |
| Charge status is unclear | Check the issuer’s transaction record and the platform receipt before another attempt |
Do not promise yourself that a pending item will disappear by a certain date. The issuer and billing platform own its status. Preserve the amount, time, platform, and last four digits only in a private, redacted record; never publish a full receipt.

Use the exact error without inventing a cause
OpenAI’s current declined-card guidance says it typically does not receive the bank’s detailed decline reason. That is why “your card was declined” cannot safely be translated into a precise claim about an IP address, card range, or fraud score.
“Your card was declined” or “payment was not approved”
For a web checkout with no charge, verify:
- the card number, expiration date, and security code;
- the billing address and postal code exactly as held by the issuer;
- sufficient available funds;
- whether the issuer permits the relevant online, recurring, or international e-commerce transaction;
- whether both the user and issuer regions meet the current requirements.
Change one fact at a time. If the data is correct and the issuer confirms no visible problem, move to OpenAI Support rather than cycling through cards and accounts. A different payment method is appropriate only when it appears in the live official checkout and there is no unresolved charge or subscription.
The two exact messages, “Payment was not approved.” and “Your card has been declined.”, each have a short note below on where they usually appear and what they leave out.
What “Payment was not approved.” means at ChatGPT checkout
“Payment was not approved.” means the checkout asked for a payment or card authorization and did not get one. It does not say whether the card issuer, a payment-risk check, or something about the offer stopped it. OpenAI’s Help Center has no article for this exact wording; the closest pages are the general declined-card and renewal pages.
It usually appears at one of two points:
- a first web checkout for Go, Plus, or Pro, right after you press Subscribe;
- a free-offer or free-trial claim with nothing due today, which is the situation behind many OpenAI Community reports since June 2026.
What the message does not tell you:
- It is not a ban or blacklist notice. Nothing official describes it that way.
- It is not the bank’s reason. Browser-console traces posted by users show ChatGPT’s web checkout sending requests to Stripe, and Stripe’s decline-code documentation tells merchants to show fraud and risk-system declines with the same generic wording as an ordinary decline. The same words can therefore cover a bank refusal or a risk check on the checkout side.
The next step depends on the stage:
- First checkout with no charge: work through the checklist above once, then ask the issuer whether it saw and refused an attempt at that time.
- Free offer or free trial: use the free-offer section below. In community reports, swapping cards did not change the result.
- Renewal: use the renewal section. The subscription may not be canceled.
- Money moved: stop and use the charged-but-no-access section.
Avoid rapid attempts with several cards or accounts, a VPN or false billing address, someone else’s card, and a new purchase on Apple or Google while the web attempt is unresolved. None of these explains the decline, and the last one can leave you with two subscriptions.
What “Your card has been declined.” means for a ChatGPT payment
“Your card has been declined.” usually means the card itself was refused, either by the issuer or by a risk check before the charge reached the issuer. No published source distinguishes it from “Your card was declined.”, so treat both as the same card-level decline and start with the checklist above.
The message hides the one fact your issuer can give you, so check the issuer’s app or call before trying again:
- If the issuer shows a declined attempt at that time, ask which rule stopped it: online purchases, international purchases, recurring charges, or a fraud hold. Fix that one thing and try once.
- If the issuer shows no attempt at all, the refusal most likely happened before the bank. Only OpenAI Support can look at that side, and switching cards does not tell you anything new.
- Confirm the card was issued by a bank in a supported country. OpenAI requires that as well as a supported location for you.
If the message appeared while you were claiming a free trial or free offer, including a Plus trial, the free-offer section below applies instead.
“Authentication required,” “authentication failed,” or a 3DS/SCA error
3D Secure or Strong Customer Authentication passes control from checkout to the card issuer. The useful question is not “Does my card support 3DS?” but “Where did the challenge stop?”
- Allow the legitimate bank redirect or pop-up to open.
- Keep the checkout page open while completing the bank-app or one-time-code approval.
- Do not close or refresh the page during the bank verification.
- If the challenge never appears, try a clean browser session or another browser, device, or ordinary network in the same supported context.
- If approval fails or loops, ask the issuer whether 3DS/SCA is enabled for the relevant online, recurring, or international transaction.
OpenAI’s declined-card guidance lists three messages that belong in this branch: “authentication required,” “card may be invalid or authentication may be needed,” and “3D Secure attempt failed.” The steps above apply to all three. If the challenge still fails after the issuer has checked 3DS, OpenAI also suggests a different card.
“We are unable to authenticate your payment method. Please choose a different payment method and try again.” belongs here too. Merchant help pages for Stripe checkouts describe it as a failed authentication: the 3D Secure step was not completed (the window closed or the connection dropped), or the card does not support the required authentication. Despite the wording, complete the challenge once in a clean session first, and switch methods only if the issuer says the card cannot complete 3DS for this purchase.
Never send an OTP to OpenAI Support, a forum, or anyone offering to “fix” the payment. An OTP is an authorization secret.
“Unable to verify your payment method”
Treat this as a generic failure unless the page or issuer provides a more specific reason. Record the exact wording and whether a bank challenge appeared. Do not infer that the account, IP address, or card range is blocked.
Four other checkout messages and the one check each needs
OpenAI does not publish explanations for these messages. The middle column reads the wording itself, matched to Stripe’s decline descriptions where they use the same words.
| Message on screen | What the wording points to | First check |
|---|---|---|
| “Check your billing details and try again.” | A mismatch in the card details or billing address | Compare card number, expiry, CVC, billing address, and ZIP or postal code with the issuer’s record, then correct once |
| “Your card does not support this type of purchase.” | Stripe uses nearly the same words for a card that is not enabled for this kind of purchase | Ask the issuer whether online, recurring, or international purchases are allowed on this card |
| “This payment method was declined. Try another payment method.” | The chosen method was refused, with no reason given | Confirm the method appears in the live checkout for your country; switch only if no charge is pending and no other subscription is active |
| “Checkout could not be completed. Please try again.” | The checkout did not finish, and it may not have reached the bank | Check the issuer for a pending item first, then make one attempt in a clean browser session without blockers |
OpenAI’s declined-card page says prepaid cards cannot be used for API credits. It does not say the same about ChatGPT subscriptions, so do not read “does not support this type of purchase” as a prepaid-card rule.
First web checkout: take one bounded action
When there is no charge, no existing subscription, both region checks pass, and this is a first web checkout, choose the first action that matches the facts:
- incorrect or mismatched details → correct those details once;
- bank challenge appeared but was not completed → repeat only to complete that challenge correctly;
- issuer says online, recurring, or international purchases are blocked → ask the issuer about that transaction type;
- browser prevented the legitimate challenge → retry in a clean session after removing the interference;
- no fact changed and the decline repeats → stop and contact OpenAI Support.
“Try everything” is not a diagnostic method. One changed fact and one new attempt produce clearer information than rapid card switching.
“Payment was not approved” when claiming a free offer or free trial
When the failure happens only while claiming a free offer or free trial, OpenAI has published no cause and there is no self-serve fix. The useful step is a support request with the offer details, not more cards.
A “free offer” is what OpenAI calls a promotional subscription or free trial invite: an emailed or in-app Plus offer with nothing to pay today. OpenAI’s promotional subscription and free trial FAQ sets out the conditions that matter here:
- Some promotions require a valid payment method at redemption, so the card or wallet is still part of the claim even at $0.
- When the trial or promotional period ends, ChatGPT renews as a paid plan on that payment method unless you cancel before the period ends.
- Trial invites generally go to Free-plan users; an existing paid subscriber may see a not-eligible message instead.
- Promo codes are single-use and cannot be stacked. Entering several may apply only one or block redemption.
- OpenAI may revoke trials in suspected misuse or fraud, which is one more reason not to cycle through accounts and cards.
Before contacting anyone, confirm the offer really exists on the account you are signed into. The ChatGPT Plus free trial guide shows how to verify an offer on your account.
From September 21 to October 17, 2026, users in an OpenAI Community thread reported offer claims ending in “Payment was not approved.” with cards, UPI, Google Pay, and Apple Pay. Several users say the same account, browser, and card reached the bank’s OTP page or paid normally when they chose a regular paid plan. As of October 22, 2026, no OpenAI staff member had replied in that thread. These are user reports, not a confirmed bug, and in them changing cards did not settle the claim. Do not buy the regular plan as a “test”: that starts a paid subscription and does not restore the offer.
Contact OpenAI Support through the chat bubble at help.openai.com and include:
- the account email;
- the promo code, if there is one;
- where the offer came from (email, in-app banner, or a partner);
- the exact error and a redacted screenshot.
Support may ask for a HAR file, a browser recording of the failed attempt. Send it only inside that private case, never on a forum. No source promises that a failed claim will be honored later.
GoPay in Indonesia and UPI in India: supported, still failing
A GoPay or UPI failure is not an unsupported-method error. OpenAI’s multicurrency billing page lists GoPay for Go, Plus, and Pro in Indonesia, and UPI for Go and Plus in India. UPI is not offered for Pro or Business.
- GoPay, Indonesia: from June 17, 2026, users reported that “Start your free Plus trial (1 Month)” failed with “Payment was not approved.” using GoPay and debit cards. OpenAI support staff confirmed on June 18 that GoPay is supported there and asked users to open a support ticket; on July 19 they asked for a HAR file of the failed attempt inside that case. The thread ended on August 7 without a published fix.
- UPI, India: in a July 10, 2026, report, the UPI QR code never appeared on a Plus free trial, and Subscribe returned “Payment was not approved.” Staff suggested trying a credit card and, if that failed, emailing support@openai.com with the case number.
One Indonesian user’s browser console showed a Stripe request failing with ERR_BLOCKED_BY_CLIENT, which browsers report when an extension such as an ad blocker stops a request. That is one observation, not a confirmed cause. OpenAI’s declined-card guidance already says to disable ad and pop-up blockers during checkout, so one attempt without extensions is reasonable before you open a case.
Renewal failure is not the same as cancellation
A previously successful subscription can still have a failed renewal. Follow OpenAI’s current Plus/Pro renewal guidance: check the existing payment method, exact billing details, available funds, issuer restrictions, supported user and issuer regions, browser state, and account status.
Then verify the billing provider:
- For web billing, review the current payment settings and any past-due state.
- For Apple, inspect Apple Subscriptions and the payment method attached to the Apple account.
- For Google Play, inspect the Play subscription and payment record.
A failed renewal does not prove that the subscription was canceled. In particular, an Apple renewal that initially failed may recover after its payment method is updated. Buying again on the web while that subscription can recover may create two active subscriptions.
Before switching among Web, Apple, and Google
OpenAI warns that starting a subscription on a second platform before canceling the first can produce multiple active subscriptions and charges.
Before any platform switch:
- Identify the current billing provider from the receipt.
- Check whether the subscription is active, past due, scheduled to cancel, or able to renew.
- Manage or cancel it through that provider.
- Verify that the old subscription is no longer active before purchasing elsewhere.
For detailed cancellation steps after the provider is known, use the platform-specific ChatGPT cancellation guide.
Mobile purchase exists, but the ChatGPT account looks Free
A mobile subscription is tied to both the Apple/Google store account and the ChatGPT account used at purchase. OpenAI says that association cannot be transferred, and reinstalling the app does not change it.
Start by signing into the original ChatGPT account used during purchase. Compare the store receipt with the account email using only private, redacted records. Do not purchase again from another ChatGPT account to “force” activation; that can create another charge without moving the first subscription.
Charged but no access, duplicate charge, or unauthorized charge
If a charge posted but the plan did not appear:
- do not buy again;
- confirm the billing provider and the ChatGPT account tied to the purchase;
- preserve the date, amount, platform, charge status, and a redacted receipt;
- contact the support team for that platform.
When the charge was for Plus and the account still shows Free, the ChatGPT Plus paid but still Free checks cover that case step by step.
Refund handling follows the purchase platform. Apple refund requests go to Apple; web and Google Play purchases follow the applicable OpenAI/Play process described in OpenAI’s refund guidance. For a fuller document checklist, see the ChatGPT subscription refund guide.
If you do not recognize the charge, report it promptly to both the bank and OpenAI using the unauthorized-charge process. Do not share full card or account details in a public forum.
A payment-failure email can also be a phishing lure. Instead of following an urgent email link, open chatgpt.com, Apple Subscriptions, or Google Play directly and verify the state there.
What to give the bank or Support
Useful, non-sensitive information includes:
- the exact on-screen error;
- date, time, and time zone;
- billing provider and failure stage;
- whether 3DS appeared and where it stopped;
- no charge, pending transaction, or posted charge;
- the ChatGPT account context and a redacted screenshot;
- for a free-offer claim, the promo code and where the offer came from;
- a support case ID if one already exists.
Never send or publish:
- a full card number or full bank-account number;
- CVC/CVV;
- OTP or bank-app approval code;
- banking credentials;
- full billing address;
- API keys, access tokens, session cookies, or an unredacted receipt;
- a HAR file anywhere except a private support case that asked for one.

A five-item private record
Write one private line before the next action:
Billing provider: [write here] · Stage: [write here] · User + issuer supported: yes/no/unknown · Charge: none/pending/posted/unknown · Exact error or 3DS stop: [write here] · One next action: [write here]
That record is not a guarantee that a payment will be approved. It prevents the most expensive mistake in this troubleshooting flow: treating every decline as permission to pay again somewhere else.
Sources12
External pages this guide links to, in the order they appear. Last updated Oct 22, 2026.
Sources12
External pages this guide links to, in the order they appear. Last updated Oct 22, 2026.
- 1.OpenAI documents that ChatGPT and API billing are separate systemshelp.openai.com/en/articles/9039756-billing-settings-in-chatgpt-vs-platform
- 2.OpenAI’s payment-method management guidancehelp.openai.com/en/articles/12362718
- 3.official ChatGPT supported-country listhelp.openai.com/en/articles/7947663-chatgpt-supported-countries
- 4.current declined-card guidancehelp.openai.com/en/articles/7232916-why-was-my-credit-card-declined
- 5.decline-code documentationdocs.stripe.com/declines/codes
- 6.OpenAI’s promotional subscription and free trial FAQhelp.openai.com/en/articles/8381046-chatgpt-promotional-subscriptionsfree-trial-invites-faq
- 7.OpenAI’s multicurrency billing pagehelp.openai.com/en/articles/10421635-multicurrency-billing
- 8.OpenAI’s current Plus/Pro renewal guidancehelp.openai.com/en/articles/7242622-why-did-my-chatgpt-plus-or-chatgpt-pro-renewal-transaction-fail
- 9.multiple active subscriptions and chargeshelp.openai.com/en/articles/20001043
- 10.OpenAI says that association cannot be transferredhelp.openai.com/en/articles/20001056
- 11.OpenAI’s refund guidancehelp.openai.com/en/articles/7232895-how-do-i-request-a-refund-for-my-chatgpt-subscription
- 12.unauthorized-charge processhelp.openai.com/en/articles/7242625-unauthorized-chatgpt-or-api-credit-purchase-charges-how-to-request-a-refund





