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.
State
Identified
Started
2 h ago
2026-11-02 16:01 UTC
Ongoing for
1 h 56 min
Worst impact
Degraded
Timeline
1 updateIdentified
1 h 56 min 100%
Updates
Times in UTCAs posted by Adyen
We have identified an issue which started on October 2, 2026, affecting Tap to Pay on iPhone on a subset of devices running iOS 27. This issue is resulting in an internal error when the app starts. As a result, affected devices may be unable to process Tap to Pay transactions. Based on our findings so far, the issue is occurring on devices where the passcode was disabled, the device was then updated, and the passcode was added again afterwards. This sequence has been seen in Jamf iOS upgrade workflows that remove the passcode, update the device and then re-apply the passcode. We recommend not disabling the passcode on devices used for Tap to Pay on iPhone, in particular when updating the device. If you manage your devices with Jamf or any other MDM solution, please review your workflows and avoid any step that removes the passcode. Our engineering teams are actively investigating and working with affected merchants and partners to restore service on impacted devices. We will share a fu
Affected components
1Adyen in the last 90 days
Full historyIncidents in 90 days
6
Days with an incident
2
Median duration
3 h 28 min
This incident
44% shorter than the median
Other Adyen incidents
All incidentsAdyen·Partial payout delay for USD payouts
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.
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.
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.
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.
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