Paysafe reported two separate payment-processing problems, involving delayed merchant settlements and recurring QR-payment failures. The payments company disclosed a seven-day transaction backlog affecting merchants integrated with TSYS, while its PagoEfectivo QR-payment partner experienced four more disruptions on November 14. The latest payments roundup examines the unresolved merchant-funding problem, the repeated switching between QR providers and the financial context following Paysafe’s third-quarter earnings announcement.
Paysafe reveals seven-day TSYS merchant payment backlog
Paysafe disclosed a merchant-payment processing problem on November 13 involving businesses integrated with TSYS, after transactions accumulated in Manual Intervention status over seven consecutive days.
The company published incident INC0329317 at 15:07 UTC, reporting that daily batching and merchant-payment processing had been affected between November 6 and November 12.
According to Paysafe, the disruption caused an unusually large number of transactions to remain in MI (Manual Intervention) status, preventing normal processing of associated merchant funding.
Paysafe said its technical teams had identified the root cause and implemented a solution. However, the company was still correcting affected transaction statuses and releasing delayed payments to merchants.
The fix was there; the merchant money still had to follow.
The incident remained classified as identified in the latest available status report, with no subsequent confirmation that the outstanding transaction backlog had been fully cleared.
A week of daily batches, and the public notice came the day after.
The company did not explain when it first discovered the processing failure, how many merchants were affected or what proportion of their scheduled settlements had been delayed. It also provided no aggregate transaction value or estimated completion date for the remaining corrections.
The seven-day processing window does not establish that every affected payment was delayed for seven days. Individual settlement delays would depend on when transactions entered processing, their status and the applicable merchant funding schedules.
Paysafe has not disclosed whether some merchants recieved their funding during the affected period while other transactions remained pending.
The distinction between technical remediation and settlement completion is particularly relevant here because Paysafe explicitly described two unfinished activities: correcting transaction records and releasing delayed funding.
Four more QR-payment failures strike Paysafe on November 14
While the TSYS backlog remained unresolved, Paysafe’s PagoEfectivo payment infrastructure experienced another series of disruptions involving its QR-code processing partner.
The November 14 incidents followed an overnight failure that began at 22:55 UTC on November 13. Paysafe opened incident INC0330249 after identifying degradation at the QR provider and initiating measures to redirect transaction traffic. The company confirmed restoration of the primary provider at 04:20 UTC on November 14.
Further incidents appeared throughout November 14:
06:05 UTC: Under incident INC0330259, Paysafe confirmed that traffic had been successfully redirected to its alternative processing solution and that affected services were operational. The primary provider was restored by 06:18 UTC.
14:03 UTC: Incident INC0330264 recorded another deterioration at the QR partner. Paysafe confirmed successful failover at 14:04 UTC and restored the primary provider at 14:31 UTC, approximately 28 minutes after the initial notice.
14:59 UTC: A seperate incident, INC0330266, again required Paysafe to redirect payments to its alternative solution. The company announced that its primary provider had recovered at 15:31 UTC.
19:43 UTC: Paysafe reported incident INC0330269, confirming renewed service degradation and announcing another attempt to reroute transactions. At 21:46 UTC, the company marked the incident resolved, confirming that traffic had returned to the primary provider and that affected services were fully operational.
Then another interruption, and another after that.
The final November 14 incident remained open for approximately two hours and three minutes between its initial notification and formal resolution. Paysafe did not publish an intermediate update confirming when alternative processing became operational, so that interval cannot be treated as two hours of uninterrupted merchant downtime.
The incidents affected PagoEfectivo QR Payments, a payment method within Paysafe’s Peruvian operations. The company’s public dashboard also identifies GMoney among the services connected with the wider PagoEfectivo infrastructure, although the individual November 14 incident records specifically list QR Payments as the affected component.
Recurring QR failures extend an established pattern
The latest incidents extend a series of recurring partner failures already documented throughout November.
As DaveFinances reported on November 13, Paysafe recorded seven separate QR-provider incidents between November 9 and the early hours of November 13.
Including the additional interruption that began late on November 13 and the four incidents reported on November 14, the documented total reaches at least 12 QR-provider incidents since November 9.
The repeated problems were already visible earlier in the month. On November 4, Paysafe reported three QR-payment disruptions, with traffic repeatedly redirected after the primary provider experienced service degradation.
The same route came back, only to need replacing again.
The company’s incident records show that alternative processing arrangements have repeatedly restored payment availability before the primary provider recovered. In several cases, the backup route was confirmed operational well before the incident was formally closed.
Paysafe has not identified the affected QR partner or disclosed whether the prevoius failures and the November 14 incidents shared a common technical cause.
The company also has not explained why its primary processing route experienced repeated degradations after earlier restoration announcements or whether it has changed the conditions under which traffic returns to that provider.
The recent failures follow a more extensive PagoEfectivo service disruption in late October, when multiple connected payment functions experienced prolonged problems. That earlier incident involved broader service availability issues, and Paysafe has not established any technical connection with the latest QR-provider failures.
Neither the November QR incidents nor the TSYS settlement problem has been accompanied by a disclosure of affected transaction volumes, merchant compensation or associated financial losses.
Paysafe’s latest results provide financial context
The operational problems emerged shortly after NYSE-listed Paysafe (PSFE) reported third-quarter financial results on November 12.
According to the company’s SEC-filed third-quarter results, revenue reached $439.6 million, an increase of 1% from $433.8 million a year earlier.
Merchant Solutions generated $236.7 million in quarterly revenue, up 2% year over year. The segment’s adjusted EBITDA declined approximately 5% to $45.2 million, compared with $47.8 million in the corresponding period of 2025.
At the consolidated level, adjusted EBITDA fell 17% to $105.7 million, while the company reported a net loss of $247.5 million, including a $203.3 million non-cash goodwill impairment.
Those results cover the quarter ended September 30 and therefore predate the November TSYS and QR-payment incidents. They provide a financial reference for Paysafe’s operations but cannot establish the revenue or profitability effect of the later disruptions.
The money impact, that number is still missing.
For the TSYS issue, the outstanding operational question concerns the value of settlements awaiting release and the time required to complete merchant reconciliation. For PagoEfectivo, the available incident history establishes repeated provider failures and successful recovery through backup routes, but not the number or value of disrupted transactions.
There are also additonal questions about whether repeated QR failovers have generated merchant reconciliation work or changes to Paysafe’s processing arrangements. The public records do not quantify either outcome.
By the end of November 14, Paysafe had confirmed that its latest QR-payment incident was resolved, with traffic restored to the primary provider at 21:46 UTC. The TSYS merchant-funding incident, meanwhile, still lacked a published resolution confirming that every delayed transaction had been corrected and the associated funds released.
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.