Swish is experiencing higher refusal rates
Swish transactions have higher refusal rates. The problem affects the Payment methods and issuers component. Adyen reports that it identified the issue and contacted Swish.
State
Identified
Started
2 h ago
2026-11-03 01:52 UTC
Ongoing for
2 h 3 min
Worst impact
Notice
Timeline
1 updateIdentified
2 h 3 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
41% shorter than the median
Other Adyen incidents
All incidentsAdyen·Swish is experiencing higher error rates
Swish payments fail more often for the Payment methods and issuers component. Adyen reports that the issue is resolved. The outage lasted 51 minutes.
Adyen·Partial payout delay for USD payouts
Adyen reports delayed payouts for a subset of USD and EUR transactions through wire and instant transfers, and for cross-border transfers in all currencies. The problem affects Settlement and payouts. Adyen reports that the incident is resolved. It lasted about 3 hours and 36 minutes.
Adyen·Partial degradation of Tap to Pay on iPhone on a subset of devices running iOS 27
Tap to Pay on iPhone does not work for some devices that run iOS 27. The Payments component is affected. Adyen identified the problem. An internal error occurs when the app starts, and affected devices cannot process Tap to Pay transactions. Adyen recommends that you do not disable the passcode on devices used for Tap to Pay, especially during an update. If you use Jamf or another MDM solution, review your workflows and remove any step that disables the passcode.
Adyen·Capture failures and payout delay for Mastercard transactions in Australia
Adyen reports capture failures for some Mastercard transactions processed in Australia. The failures affect Settlement and payouts. Adyen identified an internal issue that started at 20:00 CET on November 1, 2026. Some refunds stay pending, and payouts for these transactions can arrive up to one day late. Adyen engineering teams are working to recapture the affected transactions.
Adyen·MB WAY and Multibanco are experiencing offer conversion issues
Adyen reports that MB WAY and Multibanco offer conversion does not work. The affected component is Payment methods and issuers. Adyen resolved the incident after 82 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.live/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.live/feed.xml?providers=adyen/feed subscribe https://outages.live/feed.xml?providers=adyenFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane