Stripe

Affected: Acquirers and payment methods

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. identified 2026-10-20 10:46 UTC

   We're currently seeing elevated cancellations and expired errors with PayByBank payments. We've identified that this is caused by an outage at an upstream partner and our engineers will monitor for recovery. We will provide further updates once recovery is observed.

2. resolved 2026-10-20 13:04 UTC

   From 2026-10-20 10:47 UTC to approximately 11:18 UTC, we saw elevated cancellation and expired payment errors affecting PayByBank payments through a third-party payment partner. The issue was limited to payments processed through a specific issuing bank and has now recovered.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-20 07:09 UTC

   We’re investigating elevated errors affecting Revolut Pay, as well as 3D Secure authentication and authorization for some Revolut-issued card transactions. This issue is external to Stripe.

2. monitoring 2026-10-20 10:32 UTC

   We continue to observe elevated authorization errors and payment declines affecting Revolut-issued card transactions and Revolut Pay. We've identified that this issue is caused by an outage at an upstream partner and will continue monitoring for recovery. We will provide further...

3. resolved 2026-10-20 16:42 UTC

   From 06:00-13:24 UTC, we observed elevated authorization errors and payment declines affecting Revolut-issued card transactions and Revolut Pay. The issue is resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. identified 2026-10-15 18:35 UTC

   We're currently investigating elevated error rates and response times affecting MasterCard payment processing.

2. monitoring 2026-10-15 19:51 UTC

   As of 18:27 UTC, elevated Mastercard authorization errors have recovered. We're continuing to validate that this issue is fully resolved.

3. resolved 2026-10-15 20:53 UTC

   From 16:50 to 18:27 UTC on October 15, 2026, Mastercard payment processing experienced elevated error rates and response times, resulting in increased authorization declines. Failures were highly concentrated in wallet and tokenized transactions. The issue is resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. identified 2026-10-15 17:07 UTC

   We're currently investigating elevated error rates and response times affecting Visa payment processing.

2. identified 2026-10-15 17:20 UTC

   We're continuing to monitor elevated error rates and response times affecting Visa payment processing. We're working with our partner on recovery and will provide an update as soon as we have more information.

3. resolved 2026-10-15 18:01 UTC

   From 15:51–17:00 UTC, we experienced elevated errors and response times with Visa payments. This issue is now resolved, and payment processing has returned to normal.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Global payments, Acquirers and payment methods

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-15 02:06 UTC

   We're currently investigating elevated error rates and response times with Amazon Pay payments. We'll post an update soon.

2. resolved 2026-10-15 02:18 UTC

   From 01:30–01:56 UTC, we saw elevated error rates on Amazon Pay payments due to issues with an upstream payment processor. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-06 00:30 UTC

   As of 00:28 UTC, we've seen elevated errors on Swish payments. We're continuing to investigate and will post further updates.

2. resolved 2026-10-06 07:04 UTC

   From 00:00–03:00 UTC October 6th, we saw elevated errors on Swish payments as a result of scheduled maintenance. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-01 02:38 UTC

   We're currently investigating elevated error rates and response times with the API. We'll post an update soon.

2. resolved 2026-10-01 03:02 UTC

   From 02:24–02:27 UTC, we saw a brief increase in HTTP 5XX processing errors. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. identified 2026-09-30 02:00 UTC

   Some Visa transactions may experience lower authorization rates due to a network token processing issue, starting 00:53 UTC September 30th. Eligible payments can continue using card-number fallback. We're working to resolve the issue; no action is required.

2. monitoring 2026-09-30 03:02 UTC

   We're seeing improvement with authorization rates on Visa network token transactions, starting 02:24 UTC September 30th. We're continuing to monitor until the issue is fully resolved. We will provide further updates once we have observed sustained recovery.

3. resolved 2026-09-30 03:40 UTC

   Between 00:42 and 02:24 UTC September 30th, we saw lower authorization rates on Visa network token transactions. This issue is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe API, Stripe core components

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-27 01:03 UTC

   Starting 00:32 UTC, we’ve seen elevated failures with the API. We’re investigating and will post an update as soon as possible.

2. resolved 2026-09-27 01:21 UTC

   From 00:32 UTC to 01:01 UTC, we saw elevated API errors. This issue is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Global payments, Acquirers and payment methods

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-25 06:23 UTC

   We're currently investigating elevated error rates and response times with payments. We'll post an update soon.

2. resolved 2026-09-25 07:42 UTC

   From 06:03 to 06:26 UTC, we saw elevated error rates and response times for payments using Klarna. This issue is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe API, Stripe core components

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. identified 2026-09-23 15:53 UTC

   We're currently seeing elevated error rates and response times with the API. We've identified the cause, and are working on a fix.

2. resolved 2026-09-23 16:26 UTC

   From 15:30 UTC–16:07 UTC, we saw elevated error rates and response times with the API. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe API, Stripe core components

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. identified 2026-09-22 20:32 UTC

   We're currently investigating an issue affecting API accounts and capability call success rates. We've identified the root cause and are working on a mitigation. We will post further updates as we have more information.

2. monitoring 2026-09-22 21:27 UTC

   API error rates are recovering as part of our mitigations. We're continuing to monitor until the issue is fully resolved. We will provide further updates once we have observed sustained recovery.

3. resolved 2026-09-22 22:47 UTC

   From 19:13 to 22:19 UTC, we saw elevated error rates and response times with the API. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe core components

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-20 07:31 UTC

   We're currently investigating issues with our support systems due to an upstream partner issue, starting 07:10 UTC. We've currently disabled live support channels and are monitoring the affected service provider. We will provide further updates once we have observed recovery.

2. resolved 2026-09-20 08:10 UTC

   The partner issue affecting our support systems has been resolved. Stripe's live support channels have been restored and are operating normally. This issue has been resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-09-16 23:33 UTC

   We're currently investigating elevated error rates and response times with Visa payments. We'll post an update soon.

2. monitoring 2026-09-17 00:10 UTC

   We’re currently seeing elevated card authorization errors related to an issuing bank in North America, which is impacting some Visa transactions. We've seen some recovery and are continuing to monitor.

3. resolved 2026-09-17 01:17 UTC

   Between 20:15 September 16th and 00:08 September 17th UTC, we saw elevated card authorization errors related to an issuing bank in United States which impacted some Visa transactions. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe core components, Acquirers and payment methods

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. monitoring 2026-09-16 10:05 UTC

   We're currently investigating elevated errors on Google Pay payments. We'll post an update soon.

2. monitoring 2026-09-16 17:20 UTC

   We've confirmed with the upstream partner that the Google Pay issue is recovering. We are monitoring and will provide an update when the issue is resolved.

3. resolved 2026-09-16 17:52 UTC

   The issue with Google Pay has been resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe core components

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-16 10:05 UTC

   We're currently investigating issues with our support systems due to a downstream partner issue. We've currently disabled live support channels and are monitoring the affected service provider. We will provide further updates once we have observed recovery.

2. resolved 2026-09-16 17:09 UTC

   The partner issue affecting our support systems has been resolved. Stripe's live support channels have been restored and are operating normally. This issue has been resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-13 04:45 UTC

   Since 03:46 UTC, we’ve observed elevated error rates and increased response times with Interac payments, affecting in-person transactions in Canada. We have reached out to Interac and will share updates as soon as they are available.

2. monitoring 2026-09-13 05:17 UTC

   We have observed recovery since 04:50 UTC but have been advised by Interac that ongoing maintenance will occur until 15:00 UTC. During this period, there may be intermittent errors and increased response times with Interac payments. We are monitoring closely and will share...

3. resolved 2026-09-13 15:49 UTC

   The maintenance at Interac has concluded successfully. We’ve observed reduced error rates and improved response times with Interac payments in Canada. The issue is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Global payments, Acquirers and payment methods

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-10 20:53 UTC

   We're currently investigating elevated error rates and response times with payments through Interac. We'll post an update soon.

2. resolved 2026-09-10 21:28 UTC

   There was an issue causing elevated error rates and response times with card payments through Interac. The issue is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Global payments, Acquirers and payment methods

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-08-30 13:16 UTC

   We're currently investigating elevated error rates and response times with payments. We'll post an update soon.

2. resolved 2026-08-30 14:42 UTC

   From 12:46–14:20 UTC, we saw elevated errors on Swish payments due to external impact on the Swish payment processor. This issue is now resolved and has returned to normal.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Global payments, Acquirers and payment methods

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-08-29 19:28 UTC

   We're currently investigating elevated error rates and response times with payments. We'll post an update soon.

2. resolved 2026-08-29 20:44 UTC

   From 18:53 UTC to 19:18 UTC on 2026-08-29, we saw elevated errors on Swish payments due to a service degradation on the Swish side. This is now resolved. We will continue to monitor for any further issues and will provide updates if needed.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-08-29 06:45 UTC

   As of 05:15 UTC, some card transactions in Mexico are experiencing elevated declines due to an issuing bank being temporarily unavailable. We're in touch with the card network and will post an update as soon as they become available.

2. resolved 2026-08-29 07:33 UTC

   Between 05:15 – 07:06 UTC, we saw elevated declines with some card transactions in Mexico due to an issuing bank being temporarily unavailable. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-08-16 22:39 UTC

   We're currently investigating elevated errors on Bancontact payments. We'll post an update soon.

2. investigating 2026-08-16 23:05 UTC

   We continue seeing elevated errors on Bancontact payments. We've identified the cause as external to the Stripe infrastructure. We will continue to monitor and will post an update as soon as possible.

3. resolved 2026-08-17 06:29 UTC

   From 21:00 on Aug 16 to 01:50 on Aug 17 UTC, some Bancontact payments experienced elevated processing errors. This issue has now been resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-08-15 04:49 UTC

   We're currently investigating elevated error rates and response times with Mastercard payments. We'll post an update soon.

2. identified 2026-08-15 05:25 UTC

   We're currently seeing elevated error rates and response times with Mastercard payments. We have confirmed the outage is external to the Stripe infrastructure.

3. monitoring 2026-08-15 06:04 UTC

   As of 05:42 UTC, elevated error rates and response times with Mastercard payments have began to recover. Stripe teams will continue to monitor until fully resolved.

4. resolved 2026-08-15 06:21 UTC

   Between 04:01 and 05:42 UTC, we saw elevated error rates and response times with Mastercard payments. This is now resolved. Our engineering teams will continue to monitor.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe core components

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-08-08 00:03 UTC

   We’re currently investigating increased Financial Connections authorization errors. We’ll post an update soon.

2. resolved 2026-08-08 00:39 UTC

   From 23:20 UTC on August 7th – 00:30 UTC on August 8th, we saw elevated Financial Connections authorization errors. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-08-06 15:52 UTC

   We're currently investigating elevated error rates for retrieving balance transactions for automatic payouts starting at 13:45 UTC. A further update will be provided once recovery is observed.

2. resolved 2026-08-06 16:24 UTC

   From 13:45 UTC to approximately 16:20 UTC, we experienced elevated errors retrieving balance transactions for automatic payouts. The issue is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-01 12:45 UTC

   From 12:04 to 12:26 UTC on August 1st, we saw elevated error rates and response times with the Stripe API. The issue is resolved and we will continue to monitor.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe API, Global payments

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-08-01 00:16 UTC

   We experienced elevated error rates and response times with the API starting at 23:55 UTC. We've started to see recovery and are continuing to monitor.

2. investigating 2026-08-01 00:33 UTC

   We're currently investigating elevated error rates and response times with the API. We're starting to see recovery and are continuing to monitor.

3. investigating 2026-08-01 00:40 UTC

   We experienced elevated error rates and response times with the API starting at 23:55 UTC. We've seen recovery and are continuing to monitor.

4. resolved 2026-08-01 00:50 UTC

   From 23:55 July 31st - 00:17 August 1st UTC, we saw elevated error rates and response times with the API. We are now seeing recovery and will continue monitoring.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-07-29 03:18 UTC

   We're currently investigating elevated card authorization errors starting 02:25 UTC related to an issuer in Mexico. We'll post an update soon.

2. monitoring 2026-07-29 03:40 UTC

   As of 03:24 UTC, elevated card authorization errors related to an issuer in Mexico which is impacting card transactions in Mexico have recovered. We're continuing to validate that this issue is fully resolved.

3. resolved 2026-07-29 04:23 UTC

   From 02:25 - 03:24 UTC, we saw elevated card authorization errors related to an issuer-side degradation in Mexico. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe API, Stripe core components

1. investigating 2026-07-24 12:00 UTC

   We’re currently investigating elevated error rates and response times with the API. We’ll post an update soon

2. resolved 2026-07-24 12:14 UTC

   From 10:56 - 12:00 UTC, we saw elevated error rates and response times with the API. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

1. resolved 2026-07-21 10:26 UTC

   From 09:59 UTC to 10:13 UTC on July 21, 2026, we saw elevated error rates on BLIK payments affecting multiple customers. This issue is now resolved. We confirmed that the issue was upstream and was restored without Stripe actions.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Global payments, Acquirers and payment methods

1. investigating 2026-07-20 21:42 UTC

   We're currently investigating elevated error rates and response times with payments. We'll post an update soon.

2. identified 2026-07-20 22:09 UTC

   We're currently seeing a degradation of the Blik payment method. Our partner has identified the cause and is working on a fix.

3. resolved 2026-07-20 22:32 UTC

   From 19:40 to 22:10 UTC, we saw elevated errors for Blik payment method payments. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe API

1. identified 2026-07-17 19:56 UTC

   Starting 19:00 UTC we started seeing elevated error rates affecting Issuing API requests, resulting in failing credit card transactions. We've identified the cause and are working to mitigate. We will provide an update when we start seeing recovery.

2. resolved 2026-07-17 20:24 UTC

   From 19:00–19:55 UTC on July 17, 2026, Issuing users did not receive real-time authorization request webhooks and experienced declined transactions. All systems have recovered and are operating normally.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

1. identified 2026-07-15 08:06 UTC

   We’re observing elevated 3DS errors for Mastercard transactions starting 07:00 UTC. We are engaging with the Mastercard team and we will provide an update as soon as we have more information.

2. investigating 2026-07-15 09:01 UTC

   We are starting to see improvement in the elevated 3D Secure errors affecting Mastercard transactions. The impact still continues however Stripe engagement with Mastercard teams continue. We will provide further updates once we have observed recovery.

3. monitoring 2026-07-15 09:17 UTC

   As of 09:06 UTC, we can confirm that the elevated 3D Secure errors on Mastercard transactions have recovered following certificate rotation by Mastercard. We're continuing to validate that this issue is fully resolved and will provide further updates once we have observed...

4. resolved 2026-07-15 09:42 UTC

   From 2026-07-15 07:00:00 UTC to 09:06:00 UTC, we experienced elevated 3D Secure errors on Mastercard transactions due to an expired certificate on the upstream Mastercard service. Mastercard identified and resolved the issue on their end. We have verified that all certificates...

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

1. investigating 2026-07-02 13:37 UTC

   We're currently investigating a degradation of the WeChat Pay payment method that began at 7:10 UTC. This issue is external to Stripe and is causing increased error rates for transactions processed through the WeChat Pay payment method. We are actively monitoring the situation...

2. identified 2026-07-02 15:07 UTC

   We’re currently seeing a degradation of the WeChat Pay payment method. Our partner has identified the cause and is working on a fix.

3. identified 2026-07-02 19:23 UTC

   WeChat Pay has confirmed they are addressing the issue and it will take some time to implement the fix. We are actively monitoring and will provide a further update as more information becomes available.

4. resolved 2026-07-03 03:56 UTC

   From 07:10 July 2 to 01:20 July 3 UTC, we saw elevated errors which affected WeChat Pay payment method transactions. This issue has now been resolved by our partner.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

1. investigating 2026-07-02 10:59 UTC

   We're currently investigating a Partial Service disruption of the P24 payment method that began at 10:52 UTC. This issue is external to Stripe and is causing increased error rates for transactions processed through the P24 payment method. We are actively monitoring the situation...

2. resolved 2026-07-02 11:36 UTC

   From 10:52–11:34 UTC, we saw a partial service disruption of the P24 payment method. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

1. investigating 2026-06-11 05:05 UTC

   As of 04:16 UTC, some card transactions in Mexico are experiencing elevated declines due to an issuing bank being temporarily unavailable. We're in touch with the card network and will post an update as soon as they become available.

2. resolved 2026-06-11 05:16 UTC

   From 04:16 - 05:00 UTC, some card transactions in Mexico experienced elevated declines due to an issuing bank being temporarily unavailable. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

1. investigating 2026-06-10 05:17 UTC

   As of 04:16 UTC, some card transactions in Mexico are experiencing elevated declines due to an issuing bank being temporarily unavailable. We're closely monitoring the issue and will post an update once we have observed recovery.

2. resolved 2026-06-10 07:41 UTC

   Between 04:16 – 07:06 UTC, we saw elevated declines with some card transactions in Mexico due to an issuing bank being temporarily unavailable. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

1. identified 2026-06-05 05:33 UTC

   We’re currently seeing elevated error rates and response times with some Cartes Bancaires payments due to an issuer-side degradation starting 07:23 UTC June 4th. We believe this outage is outside of Stripe's infrastructure. This is likely impacting a number of payment...

2. identified 2026-06-05 12:22 UTC

   We are continuing to see elevated error rates and response times with some Cartes Bancaires payments due to an issuer-side degradation starting 07:23 UTC June 4th. We are actively monitoring and will provide a further update as more information becomes available.

3. resolved 2026-06-05 14:41 UTC

   Between 07:23 UTC on June 4th and 13:51 UTC on June 5th, we saw elevated error rates and response times with some Cartes Bancaires payments. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

1. monitoring 2026-05-20 13:50 UTC

   We're currently investigating a Partial Service disruption of the Bancontact payment method that began at 13:38 UTC. This issue is external to Stripe and is causing increased error rates for transactions processed through the Bancontact payment method. We are actively monitoring...

2. resolved 2026-05-20 14:06 UTC

   From 13:38–13:53 UTC, we saw a partial service disruption of the Bancontact payment method. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

1. investigating 2026-05-19 11:58 UTC

   Instant payouts in EUR to bank accounts and Bank Transfers payments are experiencing delays and some might fail due to a broader industry issue affecting SEPA Instant. All other payouts, including instant payouts to debit cards, are unaffected. We're investigating and will...

2. identified 2026-05-19 15:14 UTC

   Instant payouts in EUR to bank accounts and Bank Transfers payments continue to experience delays due broader industry issues affecting SEPA Instant. All other payouts, including instant payouts to debit cards, remain unaffected. We will provide further updates as soon as...

3. identified 2026-05-19 21:15 UTC

   Instant payouts to bank accounts and Bank Transfers payments in Europe continue to experience delays due to broader issues affecting SEPA Instant. This issue is also resulting in elevated errors on Pay by Bank payments beginning at 08:40 UTC. All other payouts, including instant...

4. resolved 2026-05-20 06:47 UTC

   Instant payouts in EUR to bank accounts, Pay by Bank payments, and Bank Transfers payments in Europe are now working successfully. There was no impact to other payouts, including instant payouts to debit cards during this time.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

1. investigating 2026-05-16 16:01 UTC

   We're currently investigating elevated MobilePay errors. We'll post an update soon.

2. resolved 2026-05-16 18:53 UTC

   Between 14:18–17:20 UTC May 16th, we saw elevated error rates and response times with MobilePay requests. This is now resolved.

3. investigating 2026-05-16 23:45 UTC

   Between 14:18–17:20 UTC May 16th, we saw elevated error rates and response times with MobilePay requests. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

1. investigating 2026-05-16 03:38 UTC

   We're currently investigating elevated Apple Pay errors. We'll post an update soon.

2. resolved 2026-05-16 05:21 UTC

   Between 02:59–04:58 UTC May 16th, we saw elevated error rates and response times with Apple Pay requests. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

1. investigating 2026-05-12 09:56 UTC

   We'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...

2. resolved 2026-05-12 10:33 UTC

   From 09:09–09:48 UTC, we saw a partial service disruption of the Swish payment method. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

1. investigating 2026-05-08 14:07 UTC

   We are currently observing elevated Authentication Requests related to issuing banks in the UK and France which is impacting some card transactions.

2. resolved 2026-05-08 14:47 UTC

   Between 11:40 UTC and 14:35 UTC we observed elevated Authentication Requests for card transactions in SCA scope. This issue has now been resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe core components

1. investigating 2026-05-07 13:07 UTC

   We're currently investigating elevated authentication errors affecting some Dashboard features. We'll post an update soon.

2. resolved 2026-05-07 13:53 UTC

   From 10:04 - 13:38 UTC, we experienced issues with elevated authentication errors affecting some Dashboard features. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe API

1. resolved 2026-05-06 18:51 UTC

   From 18:15 - 18:33 UTC we saw elevated error rates and response times with requests to Invoicing and Billing-related APIs. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe core components

1. resolved 2026-04-29 14:39 UTC

   From 13:42 – 13:55 UTC on April 29th, we saw certificate warning banners on stripe.com and dashboard login caused by a issue with on a downstream provider. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Acquirers and payment methods

1. investigating 2026-04-19 14:58 UTC

   We're currently investigating a Partial Service disruption of the Swish payment method that began at 14:37 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...

2. resolved 2026-04-19 15:36 UTC

   From 14:37–15:10 UTC, we saw elevated errors on Swish payments. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe core components

1. investigating 2026-04-18 03:48 UTC

   We're currently experiencing SMS delivery issues in the US, affecting 2-Factor authentication for dashboard users as well as the OTP code for Link and Express users. We'll post an update as soon as we have it.

2. identified 2026-04-18 04:40 UTC

   Since 01:35 UTC, we’ve been experiencing US SMS delivery issues affecting 2FA and OTP codes for Dashboard, Link, Issuing, and Express users. Non-SMS 2FA methods (security keys, authenticator apps) still work. We’re actively monitoring and will update when resolved.

3. resolved 2026-04-18 06:42 UTC

   From 01:35 - 05:20 UTC, we saw elevated errors with SMS delivery in the US. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

Affected: Stripe core components

1. investigating 2026-04-14 17:20 UTC

   Due to a processing issue with our banking partner, some Canadian Payouts processed on April 14, 2026 are experiencing a delay of a few hours. We are actively working with our banking partner to resolve this issue to ensure all affected payouts land today.

2. monitoring 2026-04-15 00:47 UTC

   As of 22:00 UTC, we have identified the root cause with our banking partner and expect affected payouts to land by the end of the day. We will continue to monitor closely and post further updates as needed.

3. resolved 2026-04-15 15:43 UTC

   We have confirmed with our banking partner that the issue has been resolved. All impacted Canadian payouts scheduled for April 14th have successfully posted on the same day. Thank you for your patience.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-04-14 11:08 UTC

   Between 10:11 - 10:50 UTC there was a disruption with the Swish payment method causing increased error rates for Swish transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-04-14 09:40 UTC

   Between 08:31 - 09:34 UTC there was a disruption with the BLIK payment method causing increased error rates for BLIK transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-03-30 11:10 UTC

   Between 09:48 - 11:02 UTC there was a disruption with the Bancontact payment method causing increased error rates for Bancontact transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-03-30 10:04 UTC

   From 07:55 - 09:59 UTC, we experienced issues with Dashboard, Express Dashboard on all platforms and Mobile surfaces. This is now resolved. API requests and payment processing were unaffected by this issue .

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-03-25 14:59 UTC

   Between 14:25 - 14:45 UTC there was a disruption with the iDEAL payment method causing increased error rates for iDEAL transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-03-23 11:27 UTC

   Between 14:13 UTC on the 22nd March and 01:40 UTC on the 23rd March, we observed a service disruption that impacted the Pix payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-03-19 14:18 UTC

   Between 10:45 - 13:39 UTC there was a disruption with the Klarna payment method causing increased error rates for Klarna transactions. The issue is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-03-10 20:53 UTC

   Between 19:22 to 20:49 UTC on March 10th, file downloads were returning 404 errors. The issue is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-03-06 18:36 UTC

   From 18:00–18:23 UTC, we saw elevated error rates and response times with Stripe API. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-03-06 14:31 UTC

   From 04:42 – 13:37 UTC, we saw issues with exporting in the Dashboard. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-03-05 22:49 UTC

   From 21:25 to 22:03 UTC, we saw elevated error rates and response times with the API on card payments requests. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-03-03 20:07 UTC

   The US Federal Reserve's ACH system (FedACH) experienced an outage which delayed ACH processing, including US payouts, top ups, bank debits, and bank transfers. The issue is now resolved. ACH processing expected to be received March 3rd should settle later today.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-03-03 12:41 UTC

   From 10:59 - 12:18 UTC, we saw elevated errors for multiple payment methods (Bancontact, Blik, iDEAL etc). The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-02-21 13:31 UTC

   Between 06:00 - 12:47 UTC, we observed elevated failures for transactions on cards issued by a French issuing bank due to 3DS authentication errors on the Cartes Bancaires network. This issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-02-12 19:53 UTC

   From 17:49 – 19:45 UTC, we saw elevated error rates and response times with Visa EU payments due to an issue experienced by an upstream partner. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-02-05 10:07 UTC

   Between 09:09 UTC and 09:57 UTC we observed elevated failures for 3DS transactions on Commonwealth Bank of Australia issued cards. This issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-01-29 14:27 UTC

   From 13:20 - 14:20 UTC, we saw elevated errors with the Bancontact payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-01-29 12:32 UTC

   Between 09:07 UTC and 11:54 UTC we observed elevated failures for 3DS transactions on Commonwealth Bank of Australia issued cards. This issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2026-01-26 23:32 UTC

   There was an issue between 22:58 to 23:29 UTC, wherein support.stripe.com was not loading and users were seeing 'service not found' on the page. The issue is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-12-22 16:36 UTC

   From 15:33 - 16:21 UTC, we saw elevated errors with the iDeal payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-12-22 07:39 UTC

   Between 05:30 and 07:30 UTC, Swish experienced a service disruption. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-12-16 19:50 UTC

   From 18:40 to 19:35 UTC on December 16th, we observed elevated errors on attempts to load the Express Dashboard. Other Dashboard pages were not impacted by this issue. The issue is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-12-09 12:13 UTC

   Between 10:22 and 11:33 UTC, we observed a service disruption that impacted the Swish payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-12-06 22:19 UTC

   From 21:50 - 22:08 UTC, we saw elevated errors with the BLIK payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-12-06 15:41 UTC

   From 12:21 - 15:03 UTC, we saw elevated errors with the BLIK payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-12-01 16:16 UTC

   From 15:45 - 16:05 UTC, and again from 16:35 - 17:25 UTC, we saw elevated errors with the Swish payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-11-25 17:05 UTC

   From 14:32 - 17:04 UTC, we saw a full service disruption with a downstream provider that impacted Stripe's Live Chat and Request a Callback functionality. The service provider has recovered and services have been restored. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-11-18 14:53 UTC

   From 11:35 UTC to 12:08 UTC Paypal, Alma, FPX and Payto had brief periods of unavailability due to a widespread outage external to Stripe which is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-11-10 11:41 UTC

   From 11:00 - 11:40 UTC, we saw elevated errors with the iDeal payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-11-06 16:28 UTC

   From 14:23 UTC - 16:02 UTC on November 6th, we saw an increase in errors and latency for report and chart generation on the Dashboard. This issue is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-11-05 11:31 UTC

   From 10:14 - 11:12 UTC, we saw elevated errors with the iDeal payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-11-04 23:49 UTC

   From 20:40–21:15 UTC, we saw elevated errors on Blik payments. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-11-03 14:38 UTC

   From 12:52 - 14:06 UTC there was a disruption with the Blik payment method causing increased error rates for Blik transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-11-01 10:24 UTC

   From 07:28 - 09:52 UTC there was a disruption with the Blik payment method causing increased error rates for Blik transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-10-20 23:00 UTC

   From 07:45 to 22:32 UTC, we disabled live support channels as a result of a widespread outage external to Stripe. Our Email channels remained unaffected by this issue. The issue is now resolved and all channels are operational.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-10-20 09:52 UTC

   From 6:45 UTC to 9:41 UTC, Affirm, Klarna, and Amazon Pay had brief periods of unavailability due to a widespread outage external to Stripe. As a result, users experienced elevated '500' errors when using these payment methods. These issues appear to be resolved, and the...

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-10-20 07:04 UTC

   From 02:34 UTC until 05:30 UTC and also from 06:11 until 06:23 UTC on 2025-10-20, we observed Elevated Afterpay and Clearpay errors. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-10-18 09:46 UTC

   Between 08:58 and 09:38 UTC, we observed a service disruption that impacted the Swish payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-10-16 17:19 UTC

   From 15:28 – 16:26 UTC, we saw elevated errors on PayPal payments. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-10-16 01:32 UTC

   From 23:10 on 14 October to 18:17 on 15 October UTC, Mastercard experienced an incident impacting global settlements. This is now resolved. Stripe immediately took action to protect normal operations for users. As a result, there was no delay or impact to payouts.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-10-05 10:44 UTC

   Between 07:25 and 10:12 UTC, we observed a service disruption that impacted the Bancontact payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-09-30 11:26 UTC

   Between 10:26 - 10:42 UTC there was a disruption with the Klarna payment method causing increased error rates for Klarna transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-09-26 08:53 UTC

   Between 04:50 and 07:44 UTC, we saw elevated error rates with Discover and Diners Club payments. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-09-29 21:23 UTC

   Between September 17th and September 29th, we saw elevated card authorization errors related to an issuing bank in France which impacted some Visa transactions. Visa has confirmed resolution, card authorization errors have subsided, and there are no current disruptions to Visa...

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-09-25 10:41 UTC

   Between 10:14 and 10:36 UTC, we observed a service disruption that impacted the Swish payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-09-22 20:14 UTC

   From 13:05–19:15 UTC, we saw elevated errors on iDeal payments. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-09-19 11:15 UTC

   From 08:06 to 10:59 UTC, we saw a decline in success rates that resulted in 500 errors affecting dashboard availability across multiple services. Users were experiencing issues when accessing the dashboard interfaces. This has now been resolved. Please note that there were no...

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-09-11 09:34 UTC

   Between 08:55 and 09:10 UTC, we observed a service disruption that impacted the Blik payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-09-04 01:43 UTC

   We have confirmed with our upstream partners that the issue has been addressed. All impacted US ACH payouts and pay-ins scheduled for September 2nd have been successfully posted by September 3rd. There is no need to retry any transactions, as everything is back to normal. Thank...

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-09-02 10:51 UTC

   Between 09:00 - 10:20 UTC there was a disruption with the Klarna payment method causing increased error rates for Klarna transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-09-01 03:16 UTC

   Between 23:33 August 31st - 03:10 September 1st UTC, there was a disruption with the Bancontact payment method causing increased error rates for Bancontact transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-08-25 20:41 UTC

   From 18:03–20:15 UTC, we saw elevated errors on FPX payments due to a maintenance period. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-08-24 12:08 UTC

   Between 11:36 - 12:05 UTC there was a partial disruption with the Bancontact payment method causing increased error rates for Bancontact transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-08-23 09:33 UTC

   From 04:15–08:40 UTC, we saw elevated card authorization errors related to an issuing bank in MX which is impacting some BANCO SANTANDER MEXICO transactions. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-08-20 23:50 UTC

   From 19:40–22:57 UTC, we saw elevated card authorization errors related to an issuing bank in Canada. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-08-20 14:05 UTC

   Between 11:30 - 13:41 UTC there was a disruption with the iDEAL payment method causing increased error rates for iDEAL transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-08-19 10:52 UTC

   Between 08:00 and 10:30 UTC, we observed a partial service disruption that impacted the FPX payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-08-10 11:19 UTC

   From 04:29-10:51 UTC, we saw elevated error rates and response times with card payments processed via Interac. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-08-06 08:45 UTC

   Between 06:31 and 08:10 UTC, we observed elevated transaction decline rate with the issuer BBVA MEXICO S.A. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-08-06 07:55 UTC

   From 03:50 - 06:18 UTC, we saw elevated errors with SMS delivery in the US. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-08-01 14:16 UTC

   Between 12:27 and 13:55 UTC, we observed a partial service disruption that impacted the PayPal payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-07-30 10:13 UTC

   Between 09:16 and 10:02 UTC, we observed a partial service disruption that impacted the Bancontact payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-07-24 17:19 UTC

   Between 16:09 to 18:02 UTC on July 24th we saw elevated error rates and response times with the API. This issue has been resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-07-23 12:13 UTC

   Between 11:07 and 12:11 UTC, we observed a service disruption that impacted the Przelewy24 payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-07-22 10:08 UTC

   Between 08:50 and 09:52 UTC, we observed a service disruption that impacted the Przelewy24 payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-07-21 15:13 UTC

   Between 14:44 and 15:05 UTC, we observed a service disruption that impacted the Blik payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-07-18 13:24 UTC

   Between 11:56 and 13:06 UTC, we observed a service disruption that impacted the Blik payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-07-17 20:56 UTC

   Between 18:45 and 20:21 UTC we saw elevated errors with Apple Pay. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-07-14 09:21 UTC

   Between 08:06 and 09:03 UTC, we observed a service disruption that impacted the Discover payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-07-09 16:28 UTC

   We've confirmed with our upstream banking partners that this issue is resolved, and all impacted payouts should have been posted on or before July 9, 2025.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-07-06 12:34 UTC

   Between 10:29 and 12:20 UTC, we observed a partial service disruption affecting transactions involving Bancontact. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-07-05 08:06 UTC

   Between 07:31 and 07:57 UTC, we observed a service disruption that impacted the Swish payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-30 20:37 UTC

   Between 17:08 and 20:00 UTC, we saw elevated errors on Cartes Bancaires. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-30 13:28 UTC

   Between 11:21 and 11:56 UTC, we observed a partial service disruption affecting transactions involving Bancontact. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-27 12:20 UTC

   Between 11:33 and 11:58 UTC, we observed a partial service disruption affecting transactions involving Bancontact. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-18 19:14 UTC

   Between 17:29–18:45 UTC June 18th, some users experienced intermittent login issues. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-17 12:10 UTC

   Between 11:00 and 11:55 UTC, we observed a service disruption affecting transactions involving Regions Bank-issued cards. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-15 19:02 UTC

   Between 18:08 and 18:45 UTC, we observed a service disruption that impacted the Swish payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-13 12:44 UTC

   Between 11:36 and 12:13 UTC, Swish experienced a service disruption due to a disturbance with Skandiabanken. The issue has been resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-12 20:29 UTC

   Between 18:24 - 19:43 UTC there were elevated errors on Affirm payments. The issue is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-12 09:48 UTC

   From 08:38–08:53 UTC, we saw elevated errors on Swish payments. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-10 07:08 UTC

   Between 04:00 and 06:17 UTC, Swish experienced a service disruption due to a disturbance with Swedbank. The issue has been resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-10 00:08 UTC

   The Blik payment method was unavailable due to a scheduled maintenance from 23:00 June 9th - 00:00 June 10th UTC. The maintenance has been concluded.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-07 21:15 UTC

   From 19:39–20:52 UTC, we saw elevated errors on BLIK payments. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-06 19:04 UTC

   From 17:23–18:30 UTC, we saw elevated errors on Swish payments. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-05 21:23 UTC

   From 18:11 until 20:55 UTC, we saw elevated error rates and response times with the API. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-05 18:24 UTC

   Between 16:45 and 18:00 UTC, Swish experienced a service disruption that impacted the Swish payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-05 14:57 UTC

   Between 13:40 and 14:17 UTC, Swish experienced a service disruption that impacted the Swish payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-05 12:44 UTC

   Between 11:59 and 12:16 UTC, Swish experienced a service disruption that impacted the Swish payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-04 23:41 UTC

   Between 19:03 and 21:30 UTC, Swish experienced a service disruption that impacted the Swish payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-03 13:01 UTC

   Between 06:27 and 07:15 UTC, Mastercard experienced errors that impacted card authorization processes. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-06-02 16:45 UTC

   From 05:05–16:06 UTC, we saw elevated errors on Multibanco payments. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-29 22:14 UTC

   From 17:11 - 21:30 UTC, Blik experienced a service disruption that impacted the Blik payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-29 17:13 UTC

   Between 15:44 and 16:08 UTC, Swish experienced a service disruption that impacted the Swish payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-29 13:54 UTC

   Between 12:22 and 13:32 UTC, Blik experienced a service disruption that impacted the Blik payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-29 10:44 UTC

   Between 09:51 and 10:05 UTC, Blik experienced a service disruption that impacted the Blik payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-25 17:42 UTC

   Between 16:55 and 17:25 UTC, Swish experienced a service disruption that impacted the Swish payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-25 01:53 UTC

   We have confirmed the maintenance being performed by PayNow has concluded and error rates have subsided. This incident is resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-22 19:38 UTC

   Between 13:52 and 19:17 UTC, Swish experienced a service disruption that impacted the Swish payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-22 14:04 UTC

   Between 11:14 and 13:56 UTC, Swish experienced a service disruption that impacted the Swish payment method. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-20 14:08 UTC

   Between 13:29 - 13:59 UTC there was a disruption with the Bancontact payment method causing increased error rates for Bancontact transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-20 14:07 UTC

   Between 13:29 - 13:59 UTC there was a disruption with the iDEAL payment method causing increased error rates for iDEAL transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-20 11:50 UTC

   Between 10:35 - 11:34 UTC there was a disruption with the iDEAL payment method causing increased error rates for iDEAL transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-20 01:39 UTC

   From 00:06 – 01:19 UTC, we saw elevated errors with Paypal transactions. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-19 00:21 UTC

   Between 15:51 May 18th - 00:01 May 19th UTC, there was a disruption with the Blik payment method causing increased error rates for Blik transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-18 14:06 UTC

   Between 13:20 - 13:58 UTC there was a disruption with the Blik payment method causing increased error rates for Blik transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-18 08:57 UTC

   Between 07:57 - 08:46 UTC there was a disruption with the Blik payment method causing increased error rates for Blik transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-17 21:54 UTC

   From 17:30 - 21:35 UTC there was a disruption with the Blik payment method causing increased error rates for Blik transactions. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-16 18:07 UTC

   From 15:13-17:04 UTC, Apple Pay experienced a service disruption impacting a number of service providers. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-16 12:33 UTC

   From 10:58-11:55 UTC, we saw elevated errors impacting Stripe.js. Users will have experienced impact to multiple related products and services, including Elements, 3DS, Checkout, Link, and several hosted Billing surfaces. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-15 19:14 UTC

   From 18:15-19:08 UTC, Swish experienced a service disruption impacting a number of service providers. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-14 11:29 UTC

   From 10:12 to 12:07 UTC, the Multibanco payment method experienced a service disruption affecting transaction processing. The issue was external to Stripe and has now been resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-12 15:50 UTC

   From 14:37 to 15:15 UTC, the EPS payment method experienced a service disruption affecting transaction processing. The issue was external to Stripe and has now been resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-08 12:08 UTC

   From 11:14-11:43 UTC, Swish experienced a service disruption impacting a number of service providers. The issue was external to Stripe and is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-07 20:33 UTC

   From 19:44–20:11 UTC, Swish experienced a service disruption impacting a number of service providers. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-07 12:51 UTC

   As of May 07, 2025, 12:45 UTC, we have successfully resolved the issue that was preventing real-time data from loading within the authentication dashboard. All dashboard charts are now recovered.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-06 20:43 UTC

   From 15:10–19:28 UTC, Swish experienced a service disruption impacting a number of service providers. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-06 11:22 UTC

   From 10:03 - 10:36 UTC, we saw elevated errors on Swish payments. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-05-06 17:04 UTC

   As of May 05, 2025, 16:45 UTC, we have successfully resolved the issue that was preventing real-time data from loading within the Billing Analytics dashboards. All dashboard charts are now recovered.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-04-30 12:11 UTC

   The external issue impacting the Klarna purchase flow, which began at 10:09 UTC and may have caused offers to remain open until manually cancelled, has now been resolved as of 11:50 UTC. We have received confirmation of stability and will continue to monitor the situation.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-04-29 13:07 UTC

   As of April 29, 2025, the external issue affecting power grids responsible for delivering electricity in some European countries, particularly in Spain and Portugal has been mostly restored. Stripe services were not impacted by these events. Our teams will continue to monitor...

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-04-25 00:09 UTC

   From 22:31–23:21 UTC, an issuing bank in the North America region experienced a service disruption impacting multiple payment providers, resulting in elevated card payment declines. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-04-24 06:18 UTC

   From 17:00 April 23rd - 05:57 April 24th UTC, we experienced elevated errors with Swish due to an outage in BankID and a Swedish issuer. This has now been resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-04-22 09:49 UTC

   From 09:04 UTC until 09:14 UTC, we observed an issue with iDEAL transactions performed by RegioBank, SNS Bank and ASN Bank cardholders. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-04-17 23:47 UTC

   Between 20:16–23:04 UTC, we experienced an issue with engaging Stripe's support teams by phone or chat. During the time of this issue, no other methods to engage Stripe support were affected. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-04-19 00:42 UTC

   We have resolved the underlying issue that resulted in stale or incomplete data for Revenue Recognition and some Stripe Dashboard views, including Acceptance, Authentication, and Payment methods. This impact was limited to data generated between 13:57 UTC on 04/15 and 00:19 UTC...

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-04-15 13:40 UTC

   From 10:44 to 13:35 UTC, we saw Dashboard search results not including objects created for some users. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-04-11 17:15 UTC

   The issues with Google Pay have been resolved and payment options have been enabled. We're continuing to monitor the issue.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-04-09 20:06 UTC

   We have observed recovery with Affirm as of 19:38 UTC. All services have returned to normal. We will continue to monitor and update if required.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-04-08 06:51 UTC

   Some AU payouts scheduled for 2025-04-03 and 2025-04-04 were delayed. The issue is now resolved, and all payouts have been processed as of 2025-04-07.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-04-02 10:55 UTC

   From 08:55–10:10 UTC, we saw elevated errors on Klarna payments due to a reported outage. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-03-24 17:04 UTC

   Between 16:00 and 16:54 UTC on March 24, 2025 some users may have experienced elevated error rates with Mastercard transactions. This issue has been resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-03-23 00:13 UTC

   From 19:10 - 23:40 UTC March 22nd, we saw elevated errors on PromptPay payments as a result of an external issue. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-03-20 15:57 UTC

   Between 15:25-15:32 UTC, users experienced an error message when performing searches on the Stripe Dashboard. This issue has been resolved

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-03-19 04:56 UTC

   The Gross Volume and Net Volume from Sales charts in the Dashboard were displaying incorrect data for transactions from March 16th-17th. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-03-13 00:36 UTC

   From 20:45–23:15 UTC, we saw elevated error rates and response times with the API. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-03-12 03:33 UTC

   From 00:21–01:48 UTC, certain dashboard pages were failing to load properly. This has now been resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-03-09 11:10 UTC

   We have confirmed that as of 09:42 UTC, Mastercard has resolved the underlying issue. At this time, we are no longer seeing errors or elevated response times. We will continue to monitor and provide another update if required.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-03-03 23:14 UTC

   From 22:27 - 22:35 UTC, we saw elevated error rates and response times with the API. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-02-28 07:19 UTC

   From 06:00–06:35 UTC, we saw Stripe.com failing to load for some users. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-02-27 20:58 UTC

   From 10:50 to 19:00 UTC on February 27, 2025, an external technical issue resulted in partial delays for both inbound and outbound transfers via Target 2 EUR wires. This issue is now resolved. We will continue monitoring and provide any further updates, if necessary.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-02-04 13:25 UTC

   The issues with GBP Debits payment processing, Top Ups, and UK Bank Transfers are now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-01-29 04:57 UTC

   From 02:44-03:57 UTC, we saw an elevated rate of errors for Apple Pay payments due to an external issue. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2025-01-20 04:17 UTC

   From 00:21–04:10 UTC, chat support for Link was unavailable. Requests to our other support channels were unaffected. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2024-12-02 11:57 UTC

   We have been working with our banking partner through the weekend to minimize payout delays for European users. We have confirmed that Euro payouts have been processed as of 10:30 UTC Monday, December 2nd. We expect all impacted payouts due on Friday, November 29th to become...

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2024-11-29 20:39 UTC

   Between 10:24 UTC on November 28th and 17:10 UTC on November 29th, we saw service disruptions for Issuers and Acquirers in Italy. This issue was caused by damage to the physical infrastructure used to provide internet service to Italy. All repairs have been completed and...

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2024-11-26 04:48 UTC

   From 20:28 November 25th – 03:28 November 26th UTC, we saw elevated errors on Affirm payments. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.

1. resolved 2024-11-21 13:16 UTC

   From 11:38 –13:00 UTC, we saw elevated errors on Paypal payments. This is now resolved.

Excerpts are shortened. Read the full incident on Stripe's status page.