Apple Pay payment failures disrupted checkout services at Airwallex, Solidgate, GoPay and Paysafe on November 17, 2026, with the four payment processors reporting different incident windows and restoration times. Apple subsequently acknowledged that an internal update had caused outages affecting several of its services, including Apple Pay and iCloud.
The incidents affected merchant-facing payment infrastructure rather than a single retailer or banking application. Official status records confirm that all four providers restored their affected services, although none disclosed the number or value of unsuccessful transactions.
Apple told Reuters that many of its systems had recovered following the faulty internal update and that work was continuing on remaining services. The company also said the broader disruption was not caused by a cyberattack.
The failures were reported together, but their clocks, they did not line up neatly. Airwallex identified a 45-minute period of elevated errors, GoPay reported an 11-minute interruption, and Solidgate kept its incident open until 20:10 UTC. These were seperate provider records, not a consolidated measurement of Apple Pay’s total downtime.
Airwallex and Solidgate report different recovery times
Airwallex recorded Apple Pay payment errors between 16:50 and 17:35 UTC on November 17. The processor initially identified the problem as external to its own infrastructure and published an investigation notice at 18:06 UTC.
At 18:26 UTC, Airwallex confirmed that the problem had been remediated and that its engineers were monitoring service metrics. It formally closed the incident at 18:50 UTC, stating that affected systems had returned to full functionality.
The difference between the reported error window and the final incident closure is 75 minutes. Airwallex therefore did not report 120 minutes of continuous payment failures; its stated period of elevated errors lasted 45 minutes, followed by monitoring and administrative closure.
Solidgate identified Apple Pay integration problems at 17:23 UTC, reporting difficulties involving its payment form and third-party provider integrations. The company said its team was investigating the impact and communicating with the provider.
A monitoring update followed at 17:35 UTC, but Solidgate did not mark the incident resolved until 20:10 UTC. That establishes an incident-record interval of two hours and 47 minutes, without proving that Apple Pay transactions failed throughout the entire period.
A green status came, but not for everyone at once. Airwallex had already identified the end of its error window when Solidgate was still tracking the incident, and their published closure times were 80 minutes apart.
GoPay and Paysafe confirm additional disruptions
GoPay independently reported an Apple Pay payment-gateway outage on November 17. Its incident record identifies a disruption from 18:12 to 18:23 Central European Time, equivalent to 17:12–17:23 UTC.
The 11-minute interruption occured within the period of elevated errors subsequently disclosed by Airwallex. GoPay published its investigation and resolution notices at approximately 18:52 and 18:53 CET, after the reported disruption had already ended.
GoPay’s window was short, quite short compared with Solidgate’s incident record. The company classified the event as a major incident affecting its payment gateway but did not provide the number of transactions involved.
Paysafe also acknowledged an Apple Pay partner disruption under incident reference INC0330671. The processor issued a resolution notice at 17:50 UTC, confirming that affected services had been restored after remediation by its Apple Pay partner.
The notice did not identify when Paysafe first experienced transaction problems, preventing a reliable calculation of its total disruption duration.
Paysafe has separately reported several merchant-payment interruptions during November. Earlier payment failures involving Paysafe, Xendit and Worldpay included QR-payment problems, delayed merchant notifications and potential Visa authorization failures.
Those earlier incidents involved different processing systems and should not be attributed to the November 17 Apple Pay disruption. They do, however, provide documented examples of payment providers experiencing interruptions originating outside their own infrastructure.
Apple identifies internal update behind wider outage
Apple’s acknowledgement provides additional context beyond the individual processor notices. The company confirmed that an internal update had disrupted multiple customer services, including Apple Pay and iCloud, and said recovery was underway on November 17.
The admission establishes an internal software-related cause for Apple’s wider service interruption, although the company has not published a detailed technical account connecting each processor’s observed errors to a specific affected system or deployment.
The available records show overlapping Apple Pay failures across multiple payment providers, with several explicitly identifying an external dependency. They do not establish that every processor experienced identical technical errors or that each provider’s recovery process followed the same sequence.
Merchant recovery records can also differ from upstream service recovery. A processor may continue monitoring its own integrations after a payment partner reports that its systems are available, particularly when it needs to verify that checkout requests are being handled normally.
Worldpay’s recent merchant-communications disruption linked to Microsoft 365 illustrated a different third-party dependency: transaction processing and settlements continued while email communications and financial reporting were interrupted.
The Apple Pay incidents concerned payment acceptance itself, with Airwallex reporting elevated errors and Solidgate identifying problems in its payment form and integrations. Neither processor published transaction-level evidence showing how many checkout attempts were rejected, timed out or successfully repeated.
Some merchants could have recieved successful payments while others encountered errors, but the public records do not identify affected merchant groups or establish their individual transaction outcomes.
Merchant transaction losses remain undisclosed
The financial exposure from the November 17 disruption remains unquantified. None of the four providers published failed-payment volumes, processing values, lost merchant revenue or compensation figures. No aggregate Apple Pay transaction-loss estimate was publicaly disclosed in the reports reviewed.
For merchants, transaction reconsiliation is the remaining operational issue that can be identified from the available evidence. An unsuccessful checkout notification does not independently establish whether an authorization was declined, a request timed out or a subsequent attempt completed successfully.
The providers have not disclosed whether merchants were required to reconcile disputed payment attempts, whether any transactions needed manual review or whether delayed processing confirmations continued after the restoration notices.
The money side of this, it is still mostly a blank. The published records confirm interruptions and service recovery, but they do not provide a basis for calculating lost sales or financial liabilities at Apple, Airwallex, Solidgate, GoPay or Paysafe.
The growing use of digital wallets gives such interruptions a substantial potential reach, although overall payment-market statistics cannot establish the impact of this particular incident.
According to the European Central Bank’s payment statistics for the second half of 2025, the euro area recorded 47.8 billion card payments worth €1.8 trillion during that six-month period. Contactless card payments at physical terminals reached 32.9 billion transactions, an 11.9% increase from the corresponding period in 2024.
Those figures include physical cards and payments initiated through digital wallets, not Apple Pay alone. They demonstrate the scale of card-based payment activity but cannot be used to estimate the number of November 17 failures.
Wallet acceptance is also continuing to expand among major merchants. As previously reported, Walmart’s Apple Pay acceptance rollout began in August 2026, extending contactless payment options across a major US retail network.
For investors following Apple and listed payment processors such as Paysafe, the November 17 reports establish a widespread but subsequently resolved operational interruption. They do not establish a measurable earnings effect, customer attrition or financial liability.
The documented recovery sequence is narrower and more precise: GoPay reported an 11-minute disruption, Airwallex identified 45 minutes of elevated errors, Paysafe confirmed restoration at 17:50 UTC, and Solidgate closed its incident at 20:10 UTC.
With all four incidents resolved, the outstanding question is not whether the processors restored service. It is how many attempted payments failed during the disruption, how many were completed on retry, and whether individual merchants have recieved all the transaction information needed to reconcile their checkout records.
Johan Shamshad is Editor-in-Chief at Dave Finances, covering financial markets, digital assets, trading platforms, brokers, fintech, payments and regulation. Since 2023, he has also worked as an editor at Gulf News, the UAE English-language newspaper published by Al Nisr Publishing LLC. His work focuses on market-moving developments, company disclosures, regulatory changes and trading infrastructure, with an emphasis on primary-source verification and practical context for traders and investors.

