Worldpay has disclosed two separate merchant-funding disruptions affecting its Mexican acquiring operations and merchants receiving settlement files through TSYS Network Systems, with payments potentially delayed until November 16 and 17. In this November 14 payments roundup, the company reports an internal funding problem involving Prosa transactions in Mexico and a third-party file-processing issue on its Core Processing platform. Paysafe has separately reported two TSYS-related funding incidents, raising questions about potential shared processing dependencies, although the companies have not established a common technical cause.
Worldpay warns Mexican merchants of settlement delays until November 17
Worldpay reported a funding disruption affecting merchants processing Prosa transactions through its Latin American acquiring platform in Mexico, warning that affected settlements would not arrive until Tuesday, November 17.
The company opened incident INC0726917 at 18:09 UTC on November 13, identifying an internal technical problem within its Funding & Payouts operations. Worldpay said its technical teams had identified the issue and were working to deliver delayed funds as a priority.
The timing adds an additional complication. Monday, November 16, is a Mexican banking holiday commemorating the Mexican Revolution, leaving Tuesday as the next regular banking day for affected settlements.
The money is delayed, and the holiday means another day before merchants can recieve it.
Worldpay’s notice did not disclose when the affected transactions were originally expected to settle, making it impossible to calculate a uniform delay for every merchant. A payment scheduled for Friday would face a different interruption from one already overdue when the incident was announced.
The incident remained classified as investigating in the latest available notice, with no confirmation that the underlying technical problem had been resolved or that all delayed funding had been released for delivery.
Worldpay also did not identify the number of affected merchants, the aggregate amount awaiting settlement or whether any customers had access to alternative funding arrangements.
Its status dashboard continued to list Authorization & Payments and Acquiring Services as operational, while Funding & Payouts showed degraded performance. The reported problem therefore concerns merchant access to transaction proceeds rather than a confirmed interruption of customer card authorizations.
The distinction is visible in an earlier Worldpay incident involving Microsoft 365, reported on November 12 and resolved on November 14. That disruption delayed merchant emails and financial reports without affecting payment processing or settlements, according to Worldpay. The latest Mexican incident directly involves the delivery of funds.
TSYS file delays could push Worldpay funding into Monday
A seperate Worldpay incident, INC0727190, concerns merchants using its Core Processing (RAFT) platform and receiving settlement files through TSYS Network Systems.
At 00:57 UTC on November 14, Worldpay reported that a third-party problem had delayed funding for a subset of customers. A further update followed at 00:59 UTC, confirming that some payments expected on November 12 could reach next-day-funded merchants on Monday, November 16.
Worldpay said its technical resources had successfully processed the delayed file at 02:00 Eastern Time on November 13 and completed the necessary recovery actions.
But the file had been processed, and the actual delivery of funds, that was still awaiting validation.
The company said it would issue a final communication after confirming that merchants had recieved their money. The incident remained under monitoring rather than being formally resolved.
Although Worldpay described the disruption as a one-business-day funding delay, the expected November 16 payment date is four calendar days after November 12. The weekend extends the period between the original expected funding date and the revised delivery date.
The public notice identifies TSYS Network Systems as the settlement-file channel involved but does not name the third party responsible for the underlying failure. Nor does it establish whether the delayed transmission originated with file creation, delivery, acceptance or another processing step.
Worldpay experienced another merchant-funding incident on November 4, when a third-party issue delayed PayPal Direct funding on its GPPaaS platform by two business days, as documented in earlier coverage of Worldpay and Paysafe payment disruptions.
The November 4 and November 14 incidents concern different processing platforms and payment arrangements. No common technical cause has been disclosed.
Paysafe reports parallel TSYS funding problems
The Worldpay disclosure coincides with two separate notices from Paysafe concerning delayed merchant funding involving TSYS integrations.
In incident INC0330139, published November 13, Paysafe said its partner Global Payments had reported that processing of Cycle 20 on Thursday, November 12 took longer than expected, delaying file transmissions to some partners.
Paysafe warned that some merchants could experience funding delays of up to one day. Its latest notice, published at 17:33 UTC on November 13, placed the incident under monitoring without confirming that all affected payments had arrived.
A second Paysafe incident, INC0329317, involved a different problem affecting daily transaction batching and merchant-payment processing for a subset of TSYS-integrated merchants.
Paysafe reported that an unusually high number of transactions had remained in Manual Intervention status between November 6 and November 12. Its November 13 notice said technical teams had identified the root cause and implemented a solution, but were still correcting transaction statuses and releasing delayed merchant funding.
There are two Paysafe cases here, not one incident with two updates.
The overlapping dates invite closer examination of the underlying processing arrangements. Worldpay’s RAFT notice and Paysafe’s US payment-processing disclosure both concern settlement-file delays around November 12, while Paysafe’s separate Manual Intervention backlog extends across an earlier seven-day period.
Neither company has established that these cases arose from the same system failure. Worldpay has not identified the third-party provider responsible for its RAFT disruption, and Paysafe has not connected its two TSYS-related incidents to Worldpay’s settlement-file problem.
The corporate relationships also require care. According to Global Payments’ September 2026 quarterly SEC filing, the company completed its acquisition of Worldpay on January 9 while divesting its Issuer Solutions business to FIS.
That transaction history establishes Worldpay’s ownership and the transfer of Global Payments’ former issuer-processing business. It does not demonstrate that the November disruptions arose from integration work, shared infrastructure failures or a common operational dependency.
Merchant funding remains the unresolved issue
The latest incidents follow earlier payment-processing failures involving Paysafe and Worldpay during November 1–2, including QR-payment interruptions and a Visa-network authorization problem.
Those incidents primarily involved transaction execution or confirmation. The November 13–14 disclosures instead concentrate on the subsequent transfer of transaction proceeds to merchants.
For businesses using next-day funding, the difference between a successfully processed transaction and a completed bank settlement can affect scheduled supplier payments, payroll and cash availability. The practical exposure depends on the proportion of merchant revenue awaiting settlement and the availability of other cash resources.
The published notices do not contain enough information to calculate that exposure. No provider has disclosed the aggregate value of delayed funding or the number of merchants affected across the incidents.
There is also a reconsiliation problem left open: Worldpay has confirmed successful processing of its delayed TSYS file but has not published final validation of fund delivery, while Paysafe is still correcting transaction statuses associated with its Manual Intervention backlog.
The next confirmed funding dates are November 16 for Worldpay’s affected RAFT merchants and November 17 for its Mexican Prosa merchants. Those dates are expectations, not evidence of completed settlement.
For now, processed files and promised funding dates are not the same thing as money in a merchant’s bank account.
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.