Live  /  Stripe  /  Incident

Stripe: Elevated Revolut Pay errors

Stripe · stripe.comResolved2026-10-20 16:42 UTC
Public — what happened

Summary

Stripe reported elevated errors affecting Revolut Pay, along with problems in 3D Secure authentication and authorization for some card transactions issued by Revolut. The company began investigating at 07:09 UTC on 2026-10-20 and said the issue was external to Stripe. By 10:32 UTC it said it was still seeing more authorization errors and payment declines, and that an outage at an upstream partner was the cause, so it was monitoring for recovery. Stripe marked the incident resolved at 16:42.

Affected

Acquirers and payment methods

As listed on Stripe’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Stripe against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Stripe: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Stripe report →

More from Stripe

Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.

The full archive is on the Stripe status & history page.

Related: Stripe status & history. SquidGrid is not affiliated with Stripe.