# Adyen: Partial degradation of Tap to Pay on iPhone on a subset of devices running iOS 27

> Adyen reports a problem with Tap to Pay on iPhone on some devices that run iOS 27, in the Payments component. The app shows an internal error at start, and these devices may not process Tap to Pay transactions. Adyen identified the issue and states that it occurs on devices where the passcode was disabled, the device was updated, and the passcode was added again. Adyen advises not to disable the passcode on Tap to Pay devices, especially during an update.

- Provider: [Adyen](https://outages.cc/adyen.md)
- Type: Incident
- State: identified
- Worst impact: Degraded performance
- Started: 2026-11-02 16:01 UTC
- Components: Payments
- Official update: https://status.adyen.com

## Updates from Adyen

### identified, 2026-11-02 16:03 UTC

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