outages.live
Live
AdyenIncident ·

Missing or changed payout descriptors for a subset of payouts

NoticeOfficial update
0

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. The engineering teams are engaged and are investigating.

State

Identified

Started

Ongoing for

2 h 8 min

Worst impact

Notice

Timeline

1 update
17:3418:0618:3819:1019:42
NoticeUpdate postedTimes in UTC

Identified

2 h 8 min 100%

Updates

Times in UTC

As posted by Adyen

Identified

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

1
Settlement and payouts

Adyen in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

11

Days with an incident

4

Median duration

3 h 32 min

This incident

39% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

47 h 14 min
median 3 h 32 min
90 days agoToday

Other Adyen incidents

All incidents

Adyen·Intersolve is experiencing higher error rates

Adyen reports higher error rates for transactions through Intersolve. The problem affects Payment methods and issuers. Adyen identified the issue outside its platform and contacted Intersolve.

Notice

Adyen·Givex is experiencing higher error rates on TEST

Givex transactions on TEST have higher error rates. The problem affects the Payment methods and issuers component. Adyen reports the cause is identified and is outside the Adyen platform. LIVE transactions with Givex are not affected. Adyen contacted Givex and will give an update.

Notice

Adyen·Swish is experiencing higher refusal rates

Adyen reports higher refusal rates for Swish transactions on the Payment methods and issuers component. Adyen identified the issue outside its platform and contacted Swish. The incident is resolved and lasted 2 hours and 11 minutes.

Resolved

Adyen·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.

Resolved

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.

Resolved

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=adyen
Slack
/feed subscribe https://outages.live/feed.xml?providers=adyen

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane