outages.live
Live
AdyenIncident ·

Settlement delay for a subset of SEPA Direct Debit transactions

NoticeOfficial update
0

Adyen reports a delay in settlement for a subset of SEPA Direct Debit transactions. The affected component is Settlement and payouts. Adyen identified an internal technical issue and the engineering teams work to resolve it.

State

Identified

Started

Ongoing for

1 h 1 min

Worst impact

Notice

Timeline

1 update
09:4910:0410:1910:3410:50
NoticeUpdate postedTimes in UTC

Identified

1 h 1 min 100%

Updates

Times in UTC

As posted by Adyen

Identified

We have identified an internal technical issue starting at 10:00 CET on November 9, 2026, resulting in a delay in processing a subset of SEPA Direct Debit transactions. As a result, customers might experience a delay in receiving the settlement of affected SEPA Direct Debit transactions processed between November 7 and 9, 2026. Our engineering teams have been engaged and are working to resolve this issue. We will provide an update on the expected delay 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

18

Days with an incident

10

Median duration

3 h 40 min

This incident

73% shorter than the median

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

6 days
median 3 h 40 min
90 days agoToday

Other Adyen incidents

All incidents

Adyen·JSC CB PRIVATBANK is experiencing higher refusal rates

Adyen reports higher refusal rates for JSC CB PRIVATBANK payments. Payment methods and issuers are affected. Adyen identified the issue outside its platform. The incident is resolved. The outage lasted 4 hours and 1 minute.

Resolved

Adyen·Pix is experiencing offer conversion issues

Adyen reports that Pix offer conversion does not work. This problem affects the Payment methods and issuers component. Adyen resolved the incident after 1 hour and 54 minutes.

Resolved

Adyen·PayU LATAM is experiencing higher error and decline rates

Adyen reports that PayU LATAM payment methods and issuers have higher error and decline rates. Adyen later confirmed that PayU LATAM resolved the issue. The outage lasted about 13 hours.

Resolved

Adyen·MB WAY is experiencing higher error rates

Adyen reports higher error rates for MB WAY transactions on the Payment methods and issuers component. Adyen identified the issue outside its platform and contacted MB WAY. The incident is resolved. It lasted about 12 hours and 42 minutes.

Resolved

Adyen·Multibanco is experiencing higher error rates

Multibanco payments had higher error rates. The problem affected the Payment methods and issuers component. Adyen reports that the outage is resolved. It lasted about 11 hours and 31 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