Missing or changed payout descriptors for a subset of payouts
Adyen reports missing or changed payout descriptors for a subset of payouts in Settlement and payouts. Adyen identified an external issue that started on November 2, 2026. Engineering teams are engaged and continue to investigate.
State
Identified
Started
Ongoing for
1 h 33 min
Worst impact
Notice
Timeline
1 updateIdentified
1 h 33 min 100%
Updates
Times in UTCAs posted by Adyen
We have identified an external issue starting on November 2, 2026, resulting in missing or changed descriptors for a subset of payouts. As a result, a subset of customers may see a payout descriptor that is missing or different from the one configured on their account. Our engineering teams are engaged and are currently investigating. We will provide an update as soon as we have more information.
Affected components
1Adyen in the last 90 days
Full historyIncidents in 90 days
11
Days with an incident
4
Median duration
3 h 32 min
This incident
56% shorter than the median
Other Adyen incidents
All incidentsAdyen·Intersolve is experiencing higher error rates
Adyen reports higher error rates for transactions that use Intersolve in the Payment methods and issuers component. Adyen identified the issue and states the problem is outside the Adyen platform. Adyen contacted Intersolve and will give an update when one is available.
Adyen·Givex is experiencing higher error rates on TEST
Adyen reports higher error rates for transactions through Givex on TEST. The problem affects the Payment methods and issuers component. Adyen identified an issue outside of its platform and contacted Givex. LIVE transactions with Givex are not affected.
Adyen·Swish is experiencing higher refusal rates
Adyen reports higher refusal rates for Swish transactions. The problem affects the Payment methods and issuers component. Adyen resolved the incident after about 130 minutes.
Adyen·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.
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