Stripe Status · History · Incident #3448
RESOLVEDElevated Swish errors
Minor · Started May 12, 2026 · 9:56 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Stripe Status · History · Incident #3448
RESOLVEDMinor · Started May 12, 2026 · 9:56 AM
Duration
36m
Severity
Minor
Detection lead
—
User reports
—
Summary
From 09:09–09:48 UTC, we saw a partial service disruption of the Swish payment method. This is now resolved.
Started
May 12, 2026 · 9:56 AM
Resolved
May 12, 2026 · 10:33 AM
Duration
36m
Severity
Minor
Event timeline
Investigating
May 12 · 9:56 AM StripeWe're currently investigating a Partial Service disruption of the Swish payment method that began at 09:35 UTC. This issue is external to Stripe and is causing increased error rates for transactions processed through the Swish payment method. We are actively monitoring the situation and will provide updates as more information becomes available.
Resolved
May 12 · 10:33 AM StripeFrom 09:09–09:48 UTC, we saw a partial service disruption of the Swish payment method. This is now resolved.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
By Designmodo
MONITORING
STATUS
SERVICE
COMPARE
ACCOUNT