ChatGPT: Elevated error rates with some U.S. business Mastercards
Timeline of updates
- identifiedEdited
Investigating — We’re seeing payment declines on some U.S. business Mastercards. Affected cards have numbers beginning with 544015, 546400, 543502, 543799, or 512998. Some cards beginning with 513989 are also affected.
For API customers, this can prevent automatic recharges and one-time credit purchases. If your prepaid balance runs out, your API requests may fail.
If you use one of these cards, we recommend adding a card from a different issuer before your next payment, even if you haven’t seen a decline. If an API credit purchase has already failed, use the new card to retry the purchase.
We’re working with our payment partners and will share updates here.
- identifiedEdited
Investigating — We’re seeing payment declines on some U.S. business Mastercards. Affected cards have numbers beginning with 544015, 546400, 543502, 543799, or 512998. Some cards beginning with 513989 are also affected.
For API customers, this can prevent automatic recharges and one-time credit purchases. If your prepaid balance runs out, your API requests may fail.
If you use one of these cards, we recommend adding a card from a different issuer before your next payment, even if you haven’t seen a decline. If an API credit purchase has already failed, use the new card to retry the purchase.
We’re working with our payment partners and will share updates here.
- monitoring
We’ve applied a mitigation and are monitoring the affected services to confirm recovery.
Changes Rewindex caught on this incident
- Incident updated: Elevated error rates with Brex Cards and U.S. business Mastercards
- Incident silently edited: Elevated error rates with some U.S. business Mastercards
- Incident updated: Elevated error rates with some U.S. business Mastercards
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-06 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
8c03ee115735c476…Version 2 captured
In the 2026-11-06 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
80f6d5aea8ae1ee3…Version 3 captured
In the 2026-11-06 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
bdceee6c956edf13…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.openai.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by ChatGPT, started 2026-11-06 18:38 UTC, not resolved, 3 update(s); edited after publishing.
- Title
- Elevated error rates with some U.S. business Mastercards
- Vendor
- ChatGPT
- Date
- URL
- https://rewindex.com/company/chatgpt/incidents/01M6S2FV5TZWQ753NHRB7BF5K7
ChatGPT profileRecent ChatGPT incidentsAll outages on November 6, 2026ChatGPT in November 2026MarkdownJSON