Live

Partial payout delay for USD payouts

0

Adyen reports a partial payout delay for some USD and EUR payouts through wire and instant transfers. Some cross-border payouts in all currencies are also delayed. Adyen identified the issue and its engineering teams are working to resolve it.

State

Identified

Started

1 h ago

2026-11-02 17:03 UTC

Ongoing for

1 h 10 min

Worst impact

Notice

Timeline

1 update
17:0317:2117:3817:5518:13
NoticeUpdate postedTimes in UTC

Identified

1 h 10 min 100%

Updates

Times in UTC

As posted by Adyen

Identified2026-11-02 17:06 UTC

We have identified an internal technical issue which started at 16:00 CET on November 2, 2026, resulting in a partial payout delay for a subset of USD and EUR transactions processed through wire and instant transfers. Additionally, there is a partial payout delay for a subset of cross-border transfers in all currencies. As a result, a subset of customers might experience a delay in receiving their payouts scheduled for November 2, 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

6

Days with an incident

2

Median duration

3 h 28 min

This incident

67% shorter than the median

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

3 h 40 min
median 3 h 28 min
90 days agoToday

Other Adyen incidents

All incidents

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.

Degradedupdated 2 h ago

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.

Noticeupdated 2 h ago

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.

Resolvedresolved 3 h ago

Adyen·INTERSOLVE is experiencing higher error rates

Adyen reports higher error rates for INTERSOLVE transactions on the Payment methods and issuers component. Adyen identified an issue outside of its platform. The incident is resolved and lasted 3 hours and 28 minutes.

Resolvedresolved 3 h ago

Adyen·Givex is experiencing higher error rates

Adyen reports higher error rates for transactions processed through Givex on the Payment methods and issuers component. Adyen identified the problem outside its platform and contacted Givex. The incident is resolved and lasted 3 hours and 41 minutes.

Resolvedresolved 17 h ago

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