Swish is experiencing higher refusal rates
Swish transactions have higher refusal rates. This affects the Payment methods and issuers component. Adyen has identified the issue as outside its platform and has contacted Swish. The state is identified.
State
Identified
Started
2 h ago
2026-11-03 01:52 UTC
Ongoing for
1 h 58 min
Worst impact
Notice
Timeline
1 updateIdentified
1 h 58 min 100%
Updates
Times in UTCAs posted by Adyen
We have identified an issue outside of our platform resulting in higher refusal rates for transactions processed through Swish starting at 02:06 CET. We have contacted Swish and we will provide an update as soon as it becomes available.
Affected components
1Adyen in the last 90 days
Full historyIncidents in 90 days
8
Days with an incident
3
Median duration
3 h 28 min
This incident
43% shorter than the median
Other Adyen incidents
All incidentsAdyen·Swish is experiencing higher error rates
Swish payments have higher error rates. The problem affects the Payment methods and issuers component. Adyen reports that the outage is resolved. It lasted 50 minutes.
Adyen·Partial payout delay for USD payouts
Adyen reports a partial payout delay that affects a subset of USD and EUR transactions through wire and instant transfers, and a subset of cross-border transfers in all currencies. Adyen resolved the issue on November 2, 2026 at 20:39 UTC, 3 hours and 35 minutes after it started.
Adyen·Partial degradation of Tap to Pay on iPhone on a subset of devices running iOS 27
Adyen reports a problem with Tap to Pay on iPhone on some devices that run iOS 27, in the Payments component. The app shows an internal error at start, and these devices may not process Tap to Pay transactions. Adyen identified the issue and states that it occurs on devices where the passcode was disabled, the device was updated, and the passcode was added again. Adyen advises not to disable the passcode on Tap to Pay devices, especially during an update.
Adyen·Capture failures and payout delay for Mastercard transactions in Australia
Adyen reports capture failures for some Mastercard transactions in Australia. The affected component is Settlement and payouts. Adyen identified an internal issue and the engineering teams work to recapture the affected transactions. Some refunds can stay pending and payouts can be one day late.
Adyen·MB WAY and Multibanco are experiencing offer conversion issues
Adyen reports that MB WAY and Multibanco offers do not convert correctly. The problem affects the Payment methods and issuers component. Adyen identified the issue and confirmed that it is resolved. The outage lasted about 81 minutes.
Follow Adyen
Your coding agent knows when Adyen is down, and tells you when a failure is theirs, not yours. You can also get Adyen incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "adyen" and tell me if Adyen has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=adyen/feed subscribe https://outages.cc/feed.xml?providers=adyenFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane