Worldpay reported disruptions to merchant communications on November 12 as a global Microsoft 365 outage affected its email systems. The payment processor confirmed that transaction processing and settlements remained operational, although merchants faced delays receiving financial reports and email responses. This payments roundup examines Worldpay’s incident, the wider Microsoft Exchange disruption and recent cases involving Mercado Pago and CMC Markets where payment information became unavailable or delayed even as underlying financial services continued operating.
Worldpay confirms Microsoft 365 outage affecting merchant emails
Worldpay opened incident INC0726074 at 18:44 UTC on November 12 after identifying technical difficulties involving Microsoft Exchange and Outlook that could delay incoming and outgoing emails.
At 19:13 UTC, the company confirmed that the problem originated from a global third-party outage affecting Microsoft 365 products. Worldpay’s technical teams began monitoring the disruption and assessing its effects across the company’s infrastructure.
The incident remained active on November 13. At 01:49 UTC, Worldpay said its recovery team was continuing to monitor Microsoft’s restoration efforts, with no estimated resolution time available.
Further updates at 04:21 UTC and 07:43 UTC confirmed that the company was still awaiting a full Microsoft recovery. Worldpay explicitly stated that customer funding, settlement and transaction processing were unaffected.
Its service dashboard continued to list Authorization & Payments, Acquiring Services, and Funding & Payouts as operational. Portals & Reporting was the only degraded service category associated with the incident.
The emails were delayed, but the card-processing systems, those were still running normally according to Worldpay.
The company did not disclose how many merchants were affected, the volume of delayed correspondence or whether specific customer-support requests had missed contractual response deadlines.
The incident contrasts with Worldpay’s October 29 payment-processing disruption, when an internal database failure affected card payouts, refunds and several order-management functions on its Worldwide Payment Gateway.
That earlier problem directly involved payment-related operations and was resolved within approximately 51 minutes of its initial public notification. The latest Microsoft incident concerns communications infrastructure, with no demonstrated interruption to payment authorization or settlement execution.
Worldpay for Platforms reports delayed settlement documents
A separate status notice from Worldpay for Platforms provided additional detail about the effect on merchants.
At 22:40 UTC on November 12, the service reported that it could not send or receive emails because of the Microsoft outage. The affected communications included settlement reports, transaction activity reports, rejection reports, fee invoices and responses to customer email requests.
Worldpay for Platforms said settlements remained unaffected and merchants would continue to recieve funds in their nominated bank accounts according to their usual arrangements.
Reports that could not be delivered during the interruption would be sent after Microsoft restored the affected services.
So a merchant could receive the settlement, while the document explaining it, that might arrive much later.
Its status dashboard identified Reporting and Settlement as degraded, while its portal, REST API, SOAP API, bank/payment gateway services and partner portal remained operational.
This provides a more specific picture of the incident than a general service-degradation alert. Merchants were not being told that funds had failed to settle. They were being told that documents normally distributed by email were unavailable.
The missing reports could complicate daily reconsiliation for businesses that rely on emailed settlement records to match bank credits against individual transactions, rejected payments and processor fees.
Worldpay has not reported inaccurate settlement amounts, missing customer funds or incorrect transaction records. It has also not established whether merchants could retrieve all affected reports directly through the portal while email delivery remained unavailable.
The company did not provide a schedule for clearing accumulated reports and customer correspondence after the Microsoft service is restored.
Microsoft begins phased recovery after Exchange infrastructure failures
The disruption formed part of a broader Microsoft 365 service incident that began on November 12, affecting Exchange Online mailbox access and several connected Microsoft services.
Microsoft’s Exchange Online incident, identified as EX1550543, recorded a start time of 16:17 UTC. Users experienced difficulties accessing mailboxes through Outlook on the web, Messaging API connections, Exchange ActiveSync and REST interfaces.
The company also identified connectivity problems across other Microsoft 365 services, including Teams, SharePoint Online, Copilot and certain administrative and security tools.
Microsoft initially reported elevated infrastructure load across multiple regions. Subsequent investigations found that servers were failing automated health checks and becoming unavailable, transferring additional traffic onto the remaining infrastructure.
Engineers investigated a component involved in establishing secure connections and began applying configuration changes, restarting affected servers and redistributing traffic to restore capacity.
By 08:06 UTC on November 13, Microsoft reported improved server stability following deployment of an authentication and routing configuration patch to part of its infrastructure.
At 11:01 UTC, the company said recovery measures had been completed across portions of its Asia-Pacific infrastructure, with gradual improvements in mailbox access and delayed email processing.
The recovery was coming through, but unevenly, and not across all regions yet.
Microsoft also extended its email timeout window to 48 hours to help preserve delayed messages while accumulated mail queues were processed.
The company said it had found no evidence of malicious activity associated with the incident. A final root-cause report had not been published, and a complete restoration timetable remained unavailable.
Worldpay’s public disclosures did not establish whether its email delays were concentrated in particular countries or whether some merchant communications had already recovered as Microsoft restored regional capacity.
Payment notifications and third-party resilience under scrutiny
The Worldpay incident adds to several recent examples of financial platforms experiencing interruptions to merchant-facing information without a confirmed failure of the underlying payment transaction.
On November 5, Mercado Pago reported delays affecting its instant payment notification service and webhook processing. The notification disruption lasted approximately 76 minutes, while the associated webhook incident was resolved sooner.
As documented in DaveFinances’ roundup of Kraken, Wise and Mercado Pago payment disruptions, the processor’s issue involved delayed transaction notifcations rather than confirmed failures in the payments themselves.
CMC Markets disclosed a related problem on November 2, when customer payments stopped appearing in the History tab of its CFD trading platform. The broker said its Account Summary should remain unaffected.
The incident, examined in DaveFinances’ report on CMC Markets’ payment-history display fault, concerned the visibility of account transactions rather than a confirmed interruption to deposits or withdrawals.
Those were seperate incidents, with different systems affected and no established technical connection to Microsoft’s latest outage.
Worldpay’s disruption is also distinct because it involves externally delivered financial documents and customer correspondence, rather than the processor’s own transaction database or customer account interface.
There is a regulatory dimension to the dependence on external technology providers. On November 11, Britain’s Financial Conduct Authority published new operational resilience observations emphasizing the need for regulated firms to identify critical third-party dependencies and demonstrate how they can maintain important services during disruptions.
The regulator’s publication was not a response to the Microsoft incident and did not identify Worldpay as having breached any operational-resilience requirement.
It nevertheless describes a concern illustrated by the outage: essential financial processes can remain technically available while connected communications and reporting channels fail.
For Worldpay merchants, the current evidence supports a narrower assessment than a general payments outage. Settlement funds are continuing to reach bank accounts, according to the company, while emailed reports and support correspondence face delays.
The processing continued. Getting the records to customers, though, was another matter.
The outstanding operational questions concern how quickly Microsoft can stabilize the remaining affected infrastructure, when Worldpay will distribute delayed financial documents and whether the interruption left any unresolved merchant-support or reporting backlogs.
As of Worldpay’s latest November 13 update at 07:43 UTC, there was no confirmed impact on transaction processing or client funding and no announced resolution time for the communications disruption.
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.