Fri. Nov 20th, 2026

Paysafe portal outage extends to Skrill and Neteller

ByJohan Shamshad

November 20, 2026 #Paysafe
PaysafePaysafe

Paysafe’s emergency maintenance shutdown extended beyond its original November 19 schedule, leaving merchant portals across its payments business, including Skrill and NETELLER, unavailable as the company withdrew its latest restoration estimate.

Under incident reference INC0330782, Paysafe confirmed at 22:19 UTC on Thursday that maintenance was still underway and that its earlier projected completion time of 02:00 UTC on November 20 had been withdrawn. The company provided no replacement estimate, saying services would be restored when the work was completed.

The development followed a broader service-disruption disclosure at 13:12 UTC, when Paysafe confirmed that all merchant portals, including those operated by Skrill and NETELLER, were unavailable. The original maintenance window had been scheduled to run from 10:30 UTC to 22:30 UTC on November 19.

At 21:22 UTC, Paysafe had extended its expected completion time to 02:00 UTC on November 20, potentially adding three and a half hours to the original 12-hour shutdown. Less than an hour later, that revised estimate was withdrawn.

The replacement deadline lasted barely an hour, and then that deadline went away too.

The company had not published a confirmed restoration time in the latest availble incident information. Its status monitoring continued to identify the affected merchant portals as undergoing maintenance after the original deadline.

Maintenance expands across Skrill and Neteller portals

Paysafe initially announced urgent maintenance of its Business Experience Portal at 10:16 UTC on November 19, with work starting shortly afterward. The original disclosure warned merchants that the portal would be unavailable throughout the scheduled maintenance period.

As Dave Finances reported earlier on November 19, Paysafe also warned that merchants attempting to access the portal would receive an “Invalid Username/Email” error rather than a notification explaining the maintenance.

The log-in error was about credentials, when credentials were not the issue.

The subsequent expansion to Skrill and NETELLER merchant portals established that the interruption was not confined to the Business Experience Portal originally identified in the notice.

Paysafe’s public service dashboard classified the Skrill and NETELLER merchant portals as undergoing maintenance. At the same time, the dashboard continued to list the Skrill API, Skrill Consumer Wallet, NETELLER API and NETELLER Gateway as operational.

The wallets’ APIs were marked operational; the merchant portals, they were not.

Those seperate component classifications indicate that Paysafe was reporting a merchant-interface interruption rather than a confirmed shutdown of its digital-wallet transaction infrastructure.

There was no corresponding company-wide payment-processing outage established by the maintenance notice. Paysafe also did not report that Skrill or NETELLER consumer wallets had stopped processing payments or that customers were unable to access their funds.

Merchant reporting and account access remain unclear

The expanded shutdown raises questions about which administrative functions remained accessible to merchants during the maintenance.

Merchant portals commonly provide access to transaction histories, account-management settings, payment reports and settlement information. The functions available through each Paysafe interface can differ depending on the merchant’s products and integration arrangements.

Paysafe’s public notices did not specify whether the November 19 shutdown interrupted access to all those functions, whether merchants could retrieve the same information through alternative channels or whether any reporting data was delayed.

A merchant unable to retrieve settlement records might have difficulty completing its normal reconsiliation procedures, even if the underlying payments continued processing successfully. The available disclosures do not establish that such reporting difficulties occurred across all affected accounts.

The distinction between portal availability and transaction processing is particularly relevant given Paysafe’s other operational incidents during November.

Earlier in the month, Paysafe disclosed a seven-day processing problem affecting some merchants integrated with TSYS. Transactions entered Manual Intervention status between November 6 and November 12, disrupting normal merchant funding. The company said it had implemented a technical solution but was still correcting transaction statuses and releasing delayed payments when it published the incident.

Dave Finances previously examined those TSYS merchant-funding delays and recurring PagoEfectivo QR-payment failures, which involved different payment-processing functions.

Those were problems with payments and funding, this one is with access to a portal.

Paysafe also experienced a separate Apple Pay-related disruption on November 17. The company confirmed restoration of the affected services at 17:50 UTC following remediation by its partner, as documented in earlier coverage of Apple Pay failures affecting four processors.

Neither the Apple Pay incident nor the earlier TSYS and PagoEfectivo problems have been linked by Paysafe to the November 19 merchant-portal maintenance.

Prolonged maintenance adds operational uncertainty

For NYSE-listed Paysafe (PSFE), the extended maintenance adds another operational disruption to a month already marked by merchant-funding delays, digital-wallet service degradation and repeated payment-provider failures.

The financial impact of the latest interruption remains unquantified. Paysafe has not disclosed how many merchants were affected, the transaction volumes associated with those businesses or any lost revenue attributable to the maintenance.

In its third-quarter results released on November 12, Paysafe reported revenue of $439.6 million, up approximately 1% from $433.8 million a year earlier. Merchant Solutions generated $236.7 million in quarterly revenue, while the segment’s adjusted EBITDA declined approximately 5% to $45.2 million.

Those results cover the quarter ended September 30 and precede the latest operational incidents. They provide financial context for the size of Paysafe’s merchant business but do not permit an estimate of the November portal shutdown’s financial effects.

The interruption also comes against a regulatory framework that increasingly requires payment providers to document their ability to withstand operational disruption.

In the UK, the Financial Conduct Authority’s March 2026 operational resilience review reiterated requirements for regulated payment institutions and electronic-money institutions to identify important business services, establish impact tolerances and test their ability to recover from disruption.

Those requirements apply according to the regulatory status and activities of the relevant legal entity. The public maintenance notice does not identify which Paysafe entities or regulated business services were affected, preventing an assessment of whether any applicable impact tolerance was exceeded.

The extended outage also leaves several operational details unresolved. Paysafe has not explained why the maintenance became urgent, what technical work required the simultaneous unavailability of multiple merchant portals or why its revised completion estimate was withdrawn.

No technical root-cause analysis, merchant-impact count or detailed recovery timetable accompanied the latest update.

The clock kept running after the original window, but a new finish time never came.

Confirmation of service restoration would establish when merchants could resume normal portal access. An additonal disclosure identifying the affected reporting and account-management functions would clarify whether the maintenance created work for merchants beyond the interruption itself.

For now, the confirmed development is a merchant-portal shutdown extending across Paysafe, Skrill and NETELLER beyond its original schedule, with no established processing-wide failure and no published estimate of the financial impact.

Editor-in-Chief at  | More Posts

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.

Disclaimer: This content is for informational purposes only and does not constitute financial, investment, legal, or trading advice. Trading and investing involve risk. Read our full Disclaimer.