On April 3, 2026, Stripe had a payment processing outage lasting 2 hours and 38 minutes. For Shopify stores running paid traffic that morning, it was an expensive few hours. Here is what happened, what it cost, and what separates the stores that handled it well from those that lost twice as much as they needed to.
Timeline of the April 3 Stripe outage
10:47 AM UTC: Stripe posts an initial notice of degraded performance on the Payment Intents API. The status reads "Investigating." Most merchants don't see it.
11:12 AM UTC: Status updated to Partial Outage. Card payments are failing for a growing percentage of transactions. Checkout.Sessions is also affected for merchants using Stripe Hosted Checkout. Stripe.js (the client-side library) continues to function normally, which means customers can enter their card details and hit "Pay" — only to receive a generic payment failure at the server-side confirmation step.
12:19 PM UTC: Stripe engineers identify the root cause: a configuration change pushed to the payment routing layer earlier that morning. A rollback is initiated.
1:25 PM UTC: Incident resolved. Total duration: 2 hours 38 minutes.
What stores actually experienced
The failure was silent from the customer's perspective. Shoppers could browse, add to cart, and reach checkout normally. It was only at the final payment confirmation step that the process broke. Stripe returned 500 errors server-side; customers saw a generic message like "Your payment could not be processed. Please try again."
A percentage of customers tried again. Most did not. There was no automatic failover to PayPal or Shop Pay unless the merchant had specifically enabled both in their Shopify checkout settings and had tested the fallback path.
Stripe Radar (fraud detection) was also separately delayed during part of the window, causing a small subset of legitimate transactions to queue rather than process, adding additional post-recovery confusion for some merchants.
The revenue math
A store doing $8,000 per day in revenue loses roughly $333 per hour during a complete payment outage. Over 2.6 hours, that is approximately $867 in direct lost sales — and that assumes a complete outage, when in reality conversion rate dropped significantly rather than going to zero.
But the bigger loss for many stores was ad spend. If you did not pause your Google and Meta campaigns the moment Stripe degraded, you kept paying for traffic to a checkout that could not convert. A store spending $200 per day on ads burned roughly $54 in wasted clicks during the outage window before anyone noticed. That number scales fast for stores with larger budgets.
Total cost for a mid-size store running traffic that morning: $900 to $1,500 or more, depending on how quickly they found out.
Why knowing first matters
The stores that limited their losses in this outage shared one thing: they knew about it within minutes, not hours.
Some had set up monitoring on Stripe's status page. A handful were StatusBird users who got an SMS the moment our system detected Stripe's degradation. Those stores paused their ads, put up a brief notice in their store header, and waited. Total additional loss beyond the unavoidable checkout failures: close to zero.
Stores that found out from a customer complaint at noon had already run paid traffic into a broken checkout for over an hour. By the time they paused campaigns and investigated, the outage was already most of the way through its lifecycle.
Stripe's outage frequency
This was not an unusual event. Stripe recorded 109 incidents in the 16 months between January 2025 and May 2026 — roughly 6 to 7 per month. Most are short and minor. A few per quarter are meaningful. April 3 was on the more impactful end of the spectrum but is far from Stripe's worst historical incident.
The implication: this will happen again. The stores that get hurt each time are the ones without a detection and response protocol.
What to have in place before the next Stripe outage
- Real-time monitoring. You should know about a Stripe degradation in minutes, not when a customer messages you. StatusBird monitors Stripe every 2 minutes and alerts you via SMS, email, or Slack the moment status changes.
- Backup payment options enabled. In Shopify Checkout settings, have PayPal and Shop Pay enabled. Customers who can't pay via Stripe may be able to complete via an alternate method if the option is visible at checkout.
- A pre-written header banner. A one-line "We are aware of a payment issue and are working to resolve it" message ready to activate takes seconds and stops the flood of "why can't I pay" support tickets.
- Pause ads immediately. If checkout payments are failing, pausing campaigns within the first 15 minutes cuts wasted spend by 90%. Most stores that lost significant money on April 3 could have recovered much of it by pausing sooner.
Stripe is reliable infrastructure. But no infrastructure is perfectly reliable. The April 3 outage was recoverable for prepared stores. The question is whether you find out in time to act.