Paysafe’s paysafecard payment API remained degraded on October 23, 2026, more than two days after the payments company identified the root cause of a disruption affecting merchant payments, payouts and refunds. Despite repeated assurances that technical teams were working on a solution, Paysafe had not published a restoration notice when its status page was checked on Friday.
The incident began at 19:03 UTC on October 20 and had already lasted 54 hours and 36 minutes when Paysafe issued another unresolved update at 01:39 UTC on October 23. By later that morning, the disruption had crossed 60 hours, substantially exceeding the duration of several earlier paysafecard incidents.
The prolonged disruption raises questions about service reliability and recovery capabilities at NYSE-listed Paysafe (PSFE), particularly after multiple interruptions involving the same payment infrastructure during October.
Why Has Paysafecard’s Payment API Remained Degraded for Days?
According to Paysafe’s official incident report, the company began investigating problems with its paysafecard payment API at 19:03 UTC on October 20, warning merchants that the disruption could affect their businesses.
At 09:34 UTC on October 21, Paysafe announced that its technical teams had identified the root cause and were implementing a solution. However, a further update at 15:34 UTC confirmed that remediation was still underway.
The same message appeared again at 18:43 UTC on October 22 and at 01:39 UTC on October 23, with Paysafe saying it was continuing to work on a fix. Neither update provided an estimated restoration time, an explanation of the technical failure or confirmation that affected services had recovered.
The October 23 update came approximately 40 hours after the root cause was identified. By 09:34 UTC that day, another eight hours had passed, taking the unresolved incident beyond 48 hours from Paysafe’s initial diagnosis.
The disruption was also reflected in the status reports of payment infrastructure provider PPRO. On October 21 at 10:33 UTC, PPRO identified a paysafecard service degradation at the external provider level. Its October 22 update confirmed that the company was still awaiting a resolution schedule from its technical partner.
That independent report indicates that the problem was visible beyond Paysafe’s own operational dashboard, although neither company disclosed the number of affected merchants or unsuccessful transactions.
Which Paysafecard Services and Merchant Operations Are Affected?
Paysafe’s incident report identifies several affected merchant-payment functions, including PSC Payment, PSC Payment myPaysafe, PSC Payout & Refund and Paysafecash Payment.
The incident listing also includes related eCash services such as PagoEfectivo, SafetyPay, settlement reporting and reconciliation functions, alongside certain distribution services. The status dashboard classified the affected components as experiencing degraded performance rather than declaring a complete shutdown of Paysafe’s global payment infrastructure.
For merchants, disruptions across these functions can create different operational problems. Customers may encounter unsuccessful or delayed checkouts, while businesses relying on the affected interfaces could experience difficulties processing payouts or refunds.
Paysafecard is a prepaid payment method that allows consumers to make online purchases without using a traditional credit or debit card. It is particularly relevant to online gaming, digital entertainment and other businesses serving customers who prefer prepaid payment options.
Paysafe has not disclosed transaction failure rates, financial losses, geographical concentrations or the proportion of its merchant network experiencing problems. Consequently, the incident’s commercial impact cannot yet be quantified.
How Does the Latest Outage Compare With Earlier Paysafecard Failures?
The latest disruption follows several paysafecard incidents recorded earlier in October, including interruptions on October 15, 16 and 18. Several notices carried the same INC0325720 reference, although that identifier alone does not establish that the underlying technical cause was identical.
On October 15, Paysafe reported an API disruption at 22:07 UTC and marked it resolved at 22:20 UTC, a period of just 13 minutes. On October 18, another incident began at 17:06 UTC and was declared resolved at 17:32 UTC, lasting 26 minutes.
A separate October 16 entry extended from 06:33 UTC until a resolution notice at 15:58 UTC. Nevertheless, the current incident is substantially longer than those earlier events.
DaveFinances previously reported on Paysafe’s unresolved API disruption after the incident passed 20 hours on October 21. The additional updates on October 22 and 23 show that identifying the cause did not produce a rapid recovery.
The company also experienced an earlier paysafecard API disruption on October 10, illustrating that payment-service instability has featured repeatedly in its recent operational disclosures.
Paysafe reported second-quarter 2026 revenue of $447.4 million, up 4% year over year, while recording a net loss of $58.9 million. Merchant Solutions revenue grew 6% to $246.1 million, and Digital Wallets revenue increased 3% to $206.6 million. The company has not attributed any financial impact to the latest outage.
Why Does Identifying the Root Cause Not Guarantee a Quick Recovery?
The most revealing part of this incident is the gap between diagnosis and remediation. Identifying what caused a failure is important, but the more commercially relevant question is how quickly a payment provider can restore dependable transaction processing.
A technical team may understand the source of a problem without being able to deploy a safe correction immediately. Fixes can require testing, coordination across dependent systems or measures to avoid introducing additional failures. Paysafe has not indicated which, if any, of those complications explains the current delay.
For merchants, the distinction offers little immediate comfort. A payment method that operates inconsistently for several days can become difficult to retain as a primary checkout option, even when the underlying provider understands the problem.
Repeated disruption also changes how merchants assess operational risk. A single brief incident may be manageable. Several incidents over a short period, followed by a much longer degradation, can encourage businesses to reconsider transaction routing, payment-method redundancy and their dependence on one provider.
The broader payments industry has experienced similar challenges. DaveFinances documented how PawaPay’s Monnify integration remained disrupted for nearly 37 hours, with different payment functions recovering at different times.
There is also an important difference between prolonged disruption and repeated short failures. In the latter case, as illustrated by Xendit’s 20 LinkAja payment interruptions, merchants may face repeated uncertainty about transaction completion even when each individual outage is brief.
What Should Paysafe Investors Watch After the Outage?
For Paysafe investors, the immediate concern is not necessarily a measurable earnings hit. Without transaction volumes, affected merchant counts or disclosed losses, assigning a financial cost to the disruption would be speculative.
The bigger question is whether repeated API instability could weaken merchant confidence in payment reliability. Payment providers compete partly on transaction acceptance, availability and predictable settlement. A prolonged disruption can challenge those expectations, particularly among merchants operating continuously.
There is also a potential opportunity for Paysafe to demonstrate operational improvement. A detailed incident review, effective preventive measures and evidence of sustained service stability could help reassure businesses that the latest disruption was contained.
Investors should watch for three developments: a confirmed restoration timestamp, a meaningful technical explanation and any subsequent evidence of recurring instability. Merchant retention, payment volumes and management commentary in future earnings disclosures could help establish whether the incident had consequences beyond temporary operational disruption.
The current evidence does not establish a structural failure across Paysafe’s wider business. It does, however, expose an important weakness in the recovery timeline: more than two days after identifying the root cause, the company still had not announced a completed fix.
For a payment provider, the ability to diagnose a problem matters. The ability to restore reliable service before merchants begin looking for alternatives matters considerably more.
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