OpenAI’s status page indicates payment declines for certain U.S. business Mastercards. The company identified the issue as it investigated declining transactions for these cards.OpenAI found that some business credit cards are being rejected for payments.OpenAI identified transaction failures for specific US business Mastercard BIN ranges affecting API billing.
The claim
OpenAI reported payment declines for certain U.S. business Mastercards, including some Brex cards.reported The impacted cards start with 544015, 546400, 543502, 543799, or 512998.reported Cards starting with 513989 are also impacted.reported
The response
OpenAI is collaborating with its payment partners to address the problem. OpenAI has not confirmed a root cause or a timeline for a fix.unverified The status remains listed as identified and investigating.
The practical upshot
These declines may block API users from making automatic recharges and one-time credit purchases. If a prepaid balance runs out, API requests may fail. OpenAI advises users to add a card from a different issuer prior to their next payment, regardless of whether they have experienced a decline.
Claims versus evidence
OpenAI’s status page serves as the primary evidence for this incident. The company explicitly lists the affected card prefixes and confirms the impact on API billing. There is no independent verification of the scope or cause. The claim is limited to US business Mastercards; personal cards or other issuers are not mentioned as affected. Uncertainty remains regarding how many customers are impacted or when the issue will be resolved.
Why it matters
- Product teams relying on automated API billing may face service interruptions if their prepaid credits are depleted.
- Engineers using affected Brex cards or the listed Mastercard prefixes must manually intervene to maintain service continuity.
- The lack of a confirmed fix means teams cannot rely on automatic recharges to restore functionality without adding alternative payment methods.
- Monitoring status pages becomes critical for operational resilience, as the issue affects financial transactions rather than model availability directly.
Topics: OpenAI, API billing, payment issues, Mastercard, business cards
Updated
Then / now / next
API customers could use their US business Mastercards for automatic recharges and credit purchases without issue.
OpenAI is investigating elevated error rates and payment declines for specific US business Mastercard prefixes.
Teams should watch for updates on the status page regarding a resolution or expanded scope of affected cards.
Story timeline
- Then API customers could use their US business Mastercards for automatic recharges and credit purchases without issue.
- 06 Nov 2026 Elevated error rates with some U.S. business Mastercards
- Now OpenAI is investigating elevated error rates and payment declines for specific US business Mastercard prefixes.
- Next Teams should watch for updates on the status page regarding a resolution or expanded scope of affected cards.
Ask the article
Local keyword search of this article; no generated answers.Did this article give you the evidence you needed?
Your choice stays on this device. No public tally.Questions readers ask
Which Mastercard prefixes are affected by the OpenAI payment issue?
Cards beginning with 544015, 546400, 543502, 543799, 512998, and some starting with 513989 are affected.
Does this issue affect personal credit cards?
No, the report specifies that only some US business Mastercards are affected.
What should I do if my API credit purchase failed?
Add a card from a different issuer and use it to retry the purchase.
Connected stories
Reading receipt
- OpenAI identified payment declines for US business Mastercards with specific six-digit prefixes.
- The issue affects automatic API recharges and one-time credit purchases, potentially causing request failures.
- Affected customers are advised to add a card from a different issuer to prevent service interruption.
Still open: What is the root cause of the payment declines?
Still open: When will a fix be implemented?