On 20 October, Stripe's Acquirers and payment methods component carried two separate incidents tied to upstream partners, one lasting 9h 35m. If you took payments through Revolut Pay, Revolut-issued cards or PayByBank, you likely saw elevated declines, and the fault sat outside Stripe.
Started
07:09 UTC
Duration
Lasted 9h 35m
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.
Affected components: Acquirers and payment methods
What happened?
Stripe logged two incidents against the same component, Acquirers and payment methods, on 20 October. The first started at 07:09 UTC and ran for 9h 35m. Stripe said it was investigating elevated errors affecting Revolut Pay, plus 3D Secure authentication and authorization for some Revolut-issued card transactions, and flagged from the first update that the issue was external to Stripe. By 10:32 UTC, Stripe had identified the cause as an outage at an upstream partner and said it would watch for recovery. The resolution notice at 16:42 UTC narrowed the actual window to 06:00 to 13:24 UTC, meaning the problem had already cleared hours before Stripe closed the incident. The second incident began at 10:46 UTC and ran for 2h 18m, this time hitting PayByBank payments with a spike in cancellations and expired errors. Stripe again named an upstream partner outage as the cause within the same update that opened the incident. The resolution update at 13:04 UTC narrowed this to 10:47 to roughly 11:18 UTC, and specified the fault was limited to payments routed through a specific issuing bank. No user reports were filed during either window. No post-mortem has been published for either incident, so beyond "upstream partner outage" and, in the second case, "a specific issuing bank", the exact cause is not on the record.
Learning
Stripe's own probes stayed green across this stretch, with UptimeRobot's checks on Stripe's API showing 100% uptime over 24 hours, 7 days and 30 days, and that is consistent with what happened rather than a contradiction. Stripe's API itself was reachable and functioning: the failures sat one layer further out, in the authorization and settlement path run by Revolut and a separate issuing bank behind PayByBank. An uptime check against an API endpoint tells you the endpoint answered, not that every payment method routed through it cleared. This is the shape to watch for in your own product: your checkout calls succeed, your error rate on card or bank-redirect payment methods climbs anyway, and the two facts don't conflict because they're describing different systems. Watching your own endpoints would not have surfaced this, since nothing in your stack was down. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.