What happened
In an updated OpenAI Help Center article, the company explains that ChatGPT applies card and device limits as privacy and security protections. If too many subscriptions are associated with one payment card or device, ChatGPT may stop a new subscription purchase. The checkout message for this case is “Too many subscriptions associated with this card or device. We can’t complete this purchase,” which OpenAI says is different from a bank declining a card.
The same policy limits how many paid accounts may be used on one device. A person who reaches that threshold can see “Device limit reached” when signing in. OpenAI says the warning can also arrive through a later check: an account may initially work after purchase and then be signed out. Signing out of one paid account does not guarantee another becomes eligible, because this device rule is separate from the number of accounts concurrently signed in. It is also separate from ChatGPT’s account-switching limits.
The documented device limits cover ChatGPT Go, Plus, Pro 100, Pro 200, and Pro 500. ChatGPT Free does not count toward the limit. Neither do ChatGPT Business, Enterprise, and Edu workspace plans. OpenAI does not publish the numerical threshold for cards or devices in the article. It does state that subscriptions purchased before the restrictions took effect can continue under an existing-subscription exception, while canceling such a subscription does not guarantee that a replacement purchase will be available.
For people who need more capacity on an account that remains permitted, OpenAI directs them to eligible credit purchases or usage resets. Credit options appear in Settings > Usage in ChatGPT and in Usage & Billing in the Codex app. Credits cover eligible usage after included limits are exhausted, but they do not unlock models unavailable on a plan, merge subscriptions, transfer usage between accounts, or clear a card or device restriction. If a restriction appears wrong, users can ask Support to review it and should provide the warning, their account details, plan, purchase route, timing, and relevant receipt information without sharing passwords, one-time codes, or full card details.
What the archive adds
This is a new access fact on a known Codex-and-ChatGPT account workflow. Earlier coverage noted that ChatGPT Auto-review became free for ChatGPT-account users, reducing the cost of a particular approval step without granting blanket autonomy. The new documentation addresses a different constraint: whether a paid account can be used on a device at all.
Trend signal
No supplied pattern cleanly fits: this is an account-access policy with practical consequences, not evidence that a product boundary or agent operating model has durably changed.
Why it matters
A team or individual may have regarded several paid ChatGPT subscriptions as interchangeable capacity pools, especially where Codex usage is involved. This documentation says that assumption is unsafe on a shared machine or with a shared payment card. The restriction is not merely a usage cap: it can stop a purchase or deny use of an already paid account on a device. Nor is it solved by logging out, resetting included usage, or buying credits.
The operational implication is to separate two questions that are often blurred together: how much usage an account has, and whether that account is eligible to operate on a given device. Credits can extend eligible usage on an existing permitted account, subject to account, plan, region, and feature availability. They are not a mechanism for turning multiple subscriptions into a single expandable pool. Workspace plans being outside the count is also a meaningful distinction for organizations evaluating how to provision access.
Limits and uncertainty
The Help Center article does not disclose the number of paid accounts permitted per device, the number of subscriptions permitted per card, how a device is identified, or when a given account becomes eligible again. It does not say that every person using more than one account will be blocked, and it does not quantify any impact on Codex specifically. The connection to Codex is limited but practical: OpenAI explicitly points affected users to Usage & Billing in the Codex app for available credit options. Support review may correct an unexpected restriction, but the article does not promise a review timeline or outcome.
Skill to build now
Audit how your team obtains AI coding capacity. List the paid accounts used on each shared laptop, devbox, or public workstation; note whether payment cards are shared; and identify the owner of each subscription. Then test the permitted account’s Usage or Usage & Billing page before an urgent work session. Treat credits, reset windows, and workspace provisioning as distinct options rather than fallback aliases for another account. Keep subscription IDs and purchase receipts accessible to the account owner in case Support needs to review a restriction.
Reader takeaway
Multiple paid ChatGPT accounts are no longer a dependable capacity workaround on one machine. OpenAI’s documented device and card limits can block checkout or remove device access after purchase; use the capacity options available on an already permitted account, and do not cancel an existing subscription assuming it can be replaced.
Open question
Will OpenAI publish numeric card and device thresholds, or a clearer eligibility and appeal process for legitimate shared-device teams?