Stripe's Visa network token transactions saw lower authorization rates for 1h 39m on 30 September 2026. The fault sat with Visa's token processing, not with your integration or Stripe's core API.
Started
02:00 UTC
Duration
Lasted 1h 39m
Source
IsDown
Next time
Stripe is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
What happened?
Stripe filed one incident on 30 September 2026, titled "Visa authorization errors". Stripe's own timeline puts the actual start at 00:42 UTC, though the first public update was not posted until 02:00 UTC, over an hour later. The cause given was a network token processing issue affecting some Visa transactions, which lowered authorization rates. Stripe noted that eligible payments could continue through card-number fallback, and that no action was required from you. At 03:02 UTC Stripe reported improvement starting at 02:24 UTC, and by 03:40 UTC marked the incident resolved, stating the affected window ran from 00:42 to 02:24 UTC. That gives a total of 1h 39m by Stripe's own clock, which is the figure used on this page. No components list was published alongside this incident, and no severity grading beyond the three updates above was given. There were no user reports filed in this window. Stripe has not published a post-mortem, so no further detail on what specifically failed in Visa's token processing is on record. This is Stripe's only logged incident for the day.
Learning
UptimeRobot's own probes against Stripe's API, run from both the EU and North America at 60 second intervals, showed 100% uptime across the 24 hour, 7 day and 30 day windows, with no incident registered against this event. That is not a contradiction. Stripe's API itself stayed reachable and responsive the whole time, the fault was inside Visa's network token processing, a layer that sits behind Stripe and only shows up as degraded authorization rates on individual card transactions, not as an API error your monitoring would catch. If you were only watching your own endpoints or Stripe's general API status, you would have seen everything green while some of your customers' Visa payments were quietly failing to authorise. This is the shape of failure to watch for with payment processors generally: the API answers fine, but a downstream rail it depends on is degraded, and that only surfaces in your actual transaction success rates. Stripe's card-number fallback mitigated some of this, but not all of it, and nothing in Stripe's updates quantifies how many transactions were affected. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
