OpenAI API recharges fail for select US business Mastercard prefixes
Developers see payment declines on specific card numbers, risking failed API requests if prepaid balances are exhausted.
Key points
- Specific US business Mastercard prefixes are experiencing payment declines.
- API customers may face failed automatic recharges and credit purchases.
- OpenAI recommends adding an alternative issuer card to prevent service interruption.
OpenAI has identified elevated error rates affecting payments from specific US business Mastercards. The status page lists several card number prefixes that are currently being declined by the payment system.OpenAI is having trouble processing payments from certain business credit cards.Specific BIN ranges for US business Mastercards are triggering declines in OpenAI's payment gateway.
How we got here
Cards starting with 544015, 546400, 543502, 543799, or 512998 are impacted.reported Some cards beginning with 513989 are also affected.reported
What is new
The company notes that some Brex cards are included among the affected issuers. This represents a specific subset of business cards rather than a total Mastercard outage.
What to watch
OpenAI is working with its payment partners to resolve the issue. Updates will be shared on the status page as the situation develops.
Availability and limits
Payment declines may block automatic recharges and single credit purchases for API users. Exhaustion of prepaid funds may cause API requests to fail. OpenAI recommends that holders of these cards add a payment method from another issuer prior to their next billing, regardless of whether they have experienced a decline. If an API credit purchase has already failed, use the new card to retry the purchase. Aggregate availability metrics are reported, so individual customer experiences may differ depending on their subscription tier and the specific models or API features they use.reported
Why it matters
- API integrations relying on automatic top-ups may experience sudden downtime if balances deplete.
- Developers must manually verify payment methods to ensure continuous service availability.
- The issue is limited to specific card prefixes, allowing for targeted mitigation strategies.
- Brex cardholders should prioritize adding alternative payment methods immediately.
Topics: API, billing, OpenAI, payment issues, developers
Updated
Then / now / next
Payments processed normally for all card types.
Specific US business Mastercard prefixes are being declined.
OpenAI will share updates as they work with payment partners.
Story timeline
- Then Payments processed normally for all card types.
- 06 Nov 2026 Elevated error rates with some U.S. business Mastercards
- Now Specific US business Mastercard prefixes are being declined.
- Next OpenAI will share updates as they work with payment partners.
For readers
Developers
- Check if your default payment method matches the affected prefixes.
- Implement fallback payment methods in your billing configuration.
Business
- Review corporate card policies to ensure alternative options are available.
- Monitor API usage to prevent unexpected service interruptions.
Investors
- Note potential short-term friction in customer billing processes.
- Observe OpenAI's ability to resolve payment partner issues quickly.
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?
Cards beginning with 544015, 546400, 543502, 543799, 512998, and some starting with 513989.
Does this affect all Mastercards?
No, only specific US business Mastercards with the listed prefixes are currently affected.
What should I do if my card is affected?
Add a card from a different issuer and use it to retry any failed purchases.
Connected stories
Reading receipt
- Specific US business Mastercard prefixes are experiencing payment declines.
- API customers may face failed automatic recharges and credit purchases.
- OpenAI recommends adding an alternative issuer card to prevent service interruption.
Still open: How long will the resolution take?
Still open: Are other payment processors affected?