Worldpay recorded three separate authorisation disruptions on its Worldwide Payment Gateway (WPG) on October 13, 2026, while an unrelated banking problem continued to delay SEPA funding beyond the company’s expected recovery time.
The authorisation incidents affected WPG’s Latin America component and occurred between 03:06 and 14:00 UTC. Each was individually declared resolved before another failure emerged, according to Worldpay’s official incident records.
Separately, Worldpay acknowledged that a third-party banking issue had prevented some clients from receiving funds scheduled for October 12. The company initially expected those funds to arrive by 06:00 UTC on October 13, but a subsequent update at 10:23 UTC confirmed that the disruption was continuing.
The incidents concern different payment functions, and Worldpay has not established any technical connection between them. Together, however, they raise questions about repeated payment-processing interruptions, recovery stability and the reliability of external banking dependencies.
Three WPG Authorisation Incidents Recorded Within 11 Hours
Worldpay’s official WPG status page identifies three distinct authorisation incidents on October 13, each assigned a separate incident number.
- INC0686305: The first disruption began at 03:06 UTC and was declared resolved at 03:30 UTC, lasting 24 minutes.
- INC0686336: A second authorisation incident opened at 04:01 UTC and was resolved at 04:30 UTC, lasting 29 minutes.
- INC0687766: The third incident began at 13:31 UTC. Worldpay identified the issue at 13:32 UTC and declared it resolved at 14:00 UTC, another 29-minute interruption.
All three incident records specifically identify the affected service as Authorisations (Latin America). They do not establish a worldwide failure of WPG’s authorisation infrastructure.
The published incident windows total 82 minutes across a period of 10 hours and 54 minutes. That figure represents the combined duration of the three reported incidents, not a measurement of continuous downtime or failed transactions.
Following each incident, Worldpay stated that the technical problem had been resolved and normal operations restored. However, the public notices do not explain what caused the failures or whether the incidents shared an underlying technical dependency.
Latin America Gateway Had Already Experienced Repeated Failures
The October 13 sequence was not the first recent disruption affecting WPG authorisations in Latin America.
Worldpay’s incident archive shows two additional Latin America authorisation problems on October 8, identified as INC0681583 and INC0682095. Another disruption, INC0683712, occurred on October 10.
Including the October 13 incidents, Worldpay reported six separate authorisation disruptions affecting the same regional component between October 8 and October 13.
Worldpay’s broader status dashboard also recorded a separate Latin America acquiring incident on October 13, identified as INC0687729. The company reported increased transaction-authorisation failures between 02:54 and 13:14 UTC and said client traffic had been redirected to mitigate the impact.
That incident involved the Latin America acquiring platform rather than the three separately logged WPG authorisation events. The overlapping timelines are notable, but Worldpay has not confirmed whether the systems shared an affected dependency.
SEPA Funding Issue Continued Beyond Worldpay’s Expected Deadline
A separate incident involving Single Euro Payments Area (SEPA) funding introduced another operational problem for Worldpay customers.
On October 12 at 16:33 UTC, Worldpay reported that a third-party banking issue was delaying the receipt of SEPA funds on its Worldwide Payment Gateway.
The company initially expected the delayed funding to be delivered by 06:00 UTC on October 13.
That expectation was not met.
At 10:23 UTC on October 13, Worldpay updated incident INC0684879, confirming that the technical issue was continuing and had caused a client funding delay for October 12.
The update came four hours and 23 minutes after the previously communicated delivery target.
Worldpay said its technical teams were working with the third party to resolve the disruption but did not identify the banking institution, disclose the value of affected funds or provide a revised delivery estimate.
As of the October 14 status-page check, Funding & Payouts remained classified as experiencing degraded performance, while the SEPA incident had not been marked resolved.
Worldpay’s dedicated WPG dashboard, meanwhile, showed its authorisation components operating normally. The different statuses reflect separate operational functions rather than a contradiction between the two dashboards.
Scheduled Maintenance Overlapped With One Authorisation Incident
Worldpay also conducted scheduled maintenance on October 13 between 04:00 and 08:00 UTC, with completion recorded at 08:13 UTC.
The maintenance notice warned that order modifications could experience processing delays of up to 120 minutes. It explicitly stated that other services would remain unaffected.
The second Latin America authorisation incident began at 04:01 UTC, one minute after the maintenance window opened.
That timing deserves attention, but it does not establish a connection. Worldpay has not attributed the authorisation problem to maintenance activity, and the announced work concerned order modifications rather than transaction approvals.
Repeated Recoveries Create a Different Risk From a Single Outage
A payment gateway that fails once and recovers presents a relatively straightforward operational problem. A gateway that repeatedly returns to normal before failing again creates a more difficult question: did the recovery eliminate the original problem, or did it temporarily restore service while an underlying weakness remained?
Worldpay’s six Latin America authorisation incidents over six days do not prove a common root cause. Separate failures can occur in different systems within the same regional component.
Still, the recurrence makes a detailed explanation more important than it would be for an isolated interruption.
Dave Finances recently examined a similar pattern of repeated payment-system recoveries at Xendit, where an Indonesia payout disruption returned twice within 70 minutes of being declared resolved.
The operational concern is familiar. Merchants may resume sending transactions after receiving an all-clear notification, only to encounter another round of failures shortly afterward.
Possible explanations include unstable upstream connections, incomplete failover recovery or separate faults affecting the same processing route. None has been established as the cause of Worldpay’s incidents.
Funding Delays Put Merchant Liquidity at Risk
The SEPA incident presents a different financial risk from interrupted authorisations.
An authorisation failure can prevent a customer from completing a purchase, potentially affecting conversion rates and revenue. A funding delay, by contrast, can affect cash that a merchant has already been expecting to receive.
That distinction matters for businesses operating with limited working capital. Merchants may rely on scheduled receipts to pay suppliers, replenish inventory, cover payroll or meet other immediate obligations.
A delay of several hours may have little consequence for a well-capitalized company. For a merchant dependent on predictable daily funding, the same delay could create short-term liquidity pressure.
Dave Finances previously examined how failures across interconnected payment rails can interrupt individual banking and funding services even when the wider financial platform remains available.
Worldpay’s third-party banking problem illustrates that dependency risk. The company may maintain functioning gateway infrastructure while an external institution delays funds moving through the banking network.
A related payment infrastructure disruption involving Paystack and PawaPay showed how separate processors can face problems when they depend on the same upstream provider.
The unanswered question in Worldpay’s case is whether alternative banking arrangements were available to deliver the delayed SEPA funds and, if so, why those arrangements did not prevent the missed funding target.
What Worldpay’s Incident Pattern Means for Merchants and Investors
The most useful next disclosure would be a technical explanation of the six Latin America authorisation incidents and whether they shared infrastructure, routing providers or processing dependencies.
Worldpay could also clarify how many transactions were affected, whether merchants experienced elevated declines or timeouts, and whether the separate Latin America acquiring problem contributed to the WPG disruptions.
On the funding side, the company has not disclosed how much money was delayed, how many merchants were affected or when the outstanding October 12 funding would be fully delivered.
Those omissions make it impossible to calculate the incidents’ financial impact or determine whether any merchants suffered material losses.
For investors assessing payment infrastructure providers, the bigger issue is operational resilience rather than the headline number of outage minutes.
Payment companies compete partly on their ability to process transactions reliably and move funds predictably. Repeated interruptions can weaken merchant confidence even when individual incidents are relatively short.
Worldpay’s October 13 records establish that three separate authorisation incidents occurred on the Latin America WPG component and that each was subsequently resolved. Its separate funding notice establishes that the SEPA banking disruption outlasted the company’s initial delivery expectation.
What remains unanswered is whether Worldpay has eliminated the conditions behind the recurring regional failures and when the delayed merchant funding will be restored. Until those details are available, the incidents provide evidence of operational disruption, but not enough information to quantify the commercial damage or identify a common technical cause.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape. You can reach out to him via his social media accounts:
Linkedin: https://www.linkedin.com/in/johan-shamshad-742851262/
X: https://x.com/Yasmine_FX
Investing: https://www.investing.com/members/contributors/279781574