Last checked 17 Oct 2026, 06:08 UTC. Homepage reachable.
Stripe API
Global payments
Revenue and finance automation
Banking-as-a-service
Stripe core components
Acquirers and payment methods
No open incidents on the vendor status page.
Recent history
Elevated declines on Mastercard (resolved)
Elevated declines on Visa (resolved)
Elevated Amazon Pay errors (resolved)
Elevated Swish errors (resolved)
Elevated API errors (resolved)
Visa authorization errors (resolved)
Elevated API Errors (resolved)
Elevated Klarna errors (resolved)
The status panel shows what Stripe currently reports on its official status page, including the systems it lists separately and the text of any open incident. Recent incidents appear below with start and end times.
Why a Stripe problem feels worse
When payments fail, revenue stops and customers lose trust fast. It is tempting to start changing code. Before you do, find out whether Stripe has reported anything. Many payment errors come from the integration, the card network or the customer's bank rather than Stripe itself.
Signs it is Stripe
Requests to the API time out or return 5xx errors across many endpoints
The Dashboard will not load or shows errors for everyone on your team
Webhook events stop arriving, then arrive late in a batch
Stripe's status page lists an incident affecting the API or a product you use
Signs it is probably not Stripe
Card declines. A decline code like insufficient_funds or do_not_honor comes from the issuing bank, not a Stripe outage.
4xx errors. These usually mean a problem with the request: a missing parameter, a bad API key, a resource that does not exist.
Authentication errors. A rotated or restricted key, or a test key used in live mode.
3D Secure prompts failing for some customers only, which can be bank-side.
One payment method failing while others work. Check whether a specific card network or local method has an issue.
A quick check list
Look at Stripe's status page and the panel above.
Check your Stripe Dashboard's Developers section for recent API request logs. The response codes tell you a lot.
Compare error rates across payment methods and countries.
Check whether you deployed changes to your checkout or webhook handling.
Confirm your webhook endpoint is reachable and returning 2xx responses.
During a Stripe incident
Do not retry blindly. Use idempotency keys on payment requests so retries cannot charge twice.
Queue rather than drop. If you create charges from background jobs, let jobs retry later rather than marking orders failed.
Show a clear message at checkout. "Payments are temporarily unavailable, please try again in a few minutes" beats a generic error.
Watch for late webhooks. When delivery resumes, your handler may receive a burst of events. Make sure processing the same event twice is safe.
Note the times for reconciliation later.
After it is resolved
Check for payments that were created but not confirmed, orders stuck in a pending state, and subscriptions that failed to renew during the window. Stripe retries failed subscription payments according to your retry settings, but it is worth reviewing the incident window by hand.
Following Stripe with Outage Clock
Add Stripe to your vendor list. On paid plans, filter to the systems you use, for example the API and webhooks if you run your own checkout, or Checkout if you use Stripe's hosted page. Alerts reach email, Slack, Teams or a webhook, so your on-call person hears about it at the same time as the rest of the team.
Questions
Can you tell me if my account has a problem?
No. We only see Stripe's public status information, not your account.
Does the Stripe status page show card network issues?
Sometimes Stripe posts about issues with specific networks or payment methods. Bank-level declines for single customers will not appear.