Six payment providers reported operational problems on November 4, 2026, affecting bank transfers, merchant funding, QR payments and open-banking connections. Today’s payments roundup covers Wirex’s zero success rate for outgoing SEPA transfers, three separate QR-payment failures at Paysafe, and a two-business-day PayPal Direct funding delay affecting Worldpay merchants. In Africa, Paystack encountered another Nigerian Central Switch disruption while Flutterwave acknowledged an internal collections failure. Finland’s OP Bank payment-initiation connection also suffered a complete failure for five minutes, one day after a separate interruption.
Wirex SEPA transfers stall as Paysafe reports three QR failures
Wirex reported that outgoing SEPA transfers across its supported regions had stopped processing successfully on November 4, with affected payments remaining stuck in a Processing status.
The incident was identified at 13:35 UTC, when Wirex disclosed that the success rate for outgoing SEPA transfers had fallen to zero. The company escalated the issue to an unnamed third-party provider responsible for investigating the processing failure.
At 14:49 UTC, Wirex reported improving payment-processing conditions. A further update at 15:52 UTC confirmed continued monitoring, before the company marked the incident resolved at 19:27 UTC.
The resolution notice contained a qualification. Payments initiated after approximately 14:00 UTC were processing normally, but transfers submitted earlier were still awaiting finalization by the third-party provider.
The new transfers worked again, but the older ones were still there, still waiting.
Wirex had not confirmed whether every previously affected beneficiary had recieved their funds or when the remaining transactions would reach a final status. The public disclosure also did not establish whether customers had attempted duplicate transfers while their original requests remained pending.
The European Central Bank’s overview of SEPA credit transfers distinguishes conventional credit transfers from instant credit transfers within the European payments framework. Wirex’s notice did not identify whether the disruption affected both schemes or a particular processing route.
The latest failure follows another outgoing SEPA processing incident that Wirex marked resolved on November 2 at 17:39 UTC. That earlier problem also involved delays attributed to a third-party provider. Wirex has not established whether the two incidents shared the same technical cause.
Paysafe experienced a separate sequence of disruptions on November 4, recording three incidents involving its QR-code payment partner.
The first, INC0328507, began at 06:50 UTC and was resolved at 10:30 UTC after the partner restored service. Paysafe said it had redirected traffic to an alternative provider during the interruption and subsequently returned processing to the primary partner.
A second incident, INC0328564, began at 13:22 UTC, less than three hours after the first recovery. Paysafe again initiated failover procedures and confirmed full restoration at 13:52 UTC.
And then it happened again, another failure after another switch back.
The third incident, INC0328629, was reported at 20:04 UTC, affecting PagoEfectivo QR Payments and GMoney. Paysafe said the QR partner was experiencing service degradation and that traffic was being rerouted to an alternative solution. The incident remained classified as identified in the latest available notice, without a confirmed resolution time.
The first two failures lasted three hours and 40 minutes and 30 minutes, respectively. Paysafe has not identified the partner or explained why traffic was repeatedly restored to the primary provider before subsequent disruptions.
The recurring failures follow earlier Paysafe and Worldpay payment interruptions documented on November 1–2, including two PagoEfectivo merchant-notification problems and a separate Visa-network authorization incident.
The November 4 notices concern a QR-payment partner rather than a confirmed failure of Paysafe’s entire processing infrastructure. No transaction counts, duplicated charges or merchant reconciliation discrepancies have been disclosed.
Worldpay flags two-business-day PayPal funding delays
Worldpay disclosed a merchant-funding problem on November 4 involving PayPal Direct transactions processed through its GPPaaS platform.
At 16:45 UTC, Worldpay opened incident INC0716317, reporting that a third-party issue had caused funding delays of two business days for a subset of merchants using the payment method.
The company classified Funding & Payouts as degraded and said the responsible third party had been notified. Worldpay was continuing to monitor the delivery of delayed funds when its notice was checked.
The incident concerns merchant funding rather than a confirmed interruption of PayPal payment authorization. Worldpay did not report that customers were unable to initiate PayPal transactions or that the wider PayPal network had stopped operating.
Two business days sounds short, until it is the funding a merchant was expecting sooner.
The reported delay creates a timing gap between payment processing and merchant access to proceeds. The precise financial effect depends on the affected merchants’ contractual funding schedules and the value of payments awaiting settlement, neither of which Worldpay disclosed.
Worldpay also did not identify the third party responsible, the geographic regions affected or whether the delayed funding represented transactions from a particular processing date.
Without those details, the public notice does not establish whether the incident involved an isolated settlement batch, a broader provider-processing problem or another operational failure.
The new disruption follows Worldpay’s November 1–2 Visa authorization incident, which the company attributed to an external network problem. The two events involve seperate payment functions, and no common cause has been established.
Paystack and Flutterwave report fresh African payment failures
Paystack experienced another disruption involving Nigeria’s Central Switch on November 4, with incoming bank transfers affected for approximately three hours and 58 minutes.
The company opened the incident at 10:57 UTC after detecting increased failure rates across Pay with Transfer transactions and Dedicated Virtual Accounts.
Paystack attributed the failures to downtime involving the Central Switch, warning that customers could experience unsuccessful or delayed transfers into Paystack-managed virtual accounts.
At 12:03 UTC, the company reported implementing a fix and began monitoring transaction processing. The incident was formally resolved at 14:55 UTC.
The Central Switch had caused problems just days earlier, and now Paystack was dealing with it again.
Between October 30 and November 1, Paystack had recorded a separate 37-hour Nigerian bank-transfer disruption, also attributed to Central Switch downtime. That incident affected both incoming transfers and outgoing bank payments, whereas the November 4 notice specifically identified incoming payment routes.
During the earlier failure, Paystack said pending transfers would update automatically once processing recovered. Its November 4 notice did not provide a comparable breakdown of pending payments, failed transactions or amounts awaiting reconciliation.
The repeated Central Switch dependency is visible in the incident history, but Paystack’s disclosures do not establish whether the same underlying technical defect caused both outages. Nor do they demonstrate that every Nigerian bank or payment processor experienced the November 4 interruption.
Flutterwave separately acknowledged an internal collections problem affecting selected payment rails earlier on November 4.
In a resolution notice published at 07:57 UTC, the company stated that an internal issue had temporarily disrupted payment collections and that the affected services had returned to normal.
Flutterwave did not identify the countries involved, individual payment providers, transaction volumes or duration of the disruption.
The company also did not provide technical details explaining whether the incident originated in a common processing component or involved several unrelated internal systems. Its acknowledgement of an internal issue establishes the general location of the problem without identifying the exact failure.
The incident follows Flutterwave’s October 29 collections and Nigerian payout disruptions, when payment interruptions affected several African markets before a separate incident temporarily impaired naira payouts, wallet-balance visibility and foreign-exchange rate lookups.
Those earlier incidents involved explicitly identified payment channels and functions. The November 4 notice provided less operational detail, leaving the scope of affected collections and any subsequent merchant reconciliation work unconfirmed.
For both African processors, the reported restorations confirm that the identified service problems had been addressed. Neither company’s November 4 notice quantified the number of merchants affected or the value of delayed transactions.
Tink records 100% OP Bank payment-initiation failure
Open-banking infrastructure provider Tink reported a complete failure affecting its OP Bank payment-initiation connection in Finland on November 4, following a separate partial disruption the previous day.
The November 4 incident affected the connection identified as fi-opbank-ob between 16:53 and 16:58 Central European Time, equivalent to 15:53–15:58 UTC.
Tink recorded bank-side HTTP 503 errors and classified 100% of users of that connection as affected during the five-minute interval.
Five minutes only, but for that connection the failure reading was complete.
The incident followed an OP Bank payment-initiation problem on November 3, when Tink reported that approximately 80% of users of the same connection were affected. That earlier disruption involved bank unavailability and failures during the customer redirect process used to authorize payments.
The percentage figures refer to Tink’s monitored OP Bank integration rather than every OP Bank customer or payment channel. They do not establish that OP Bank’s own mobile banking services or card payments were unavailable.
Both incidents were marked resolved. Tink has not published transaction volumes or an explanation linking the two failures to a common root cause.
Repeated errors on the same open-banking connection can affect merchants relying on payment initiation, particularly when customers must complete a bank authorization before checkout can finish. The five-minute duration places a clear limit on the November 4 disruption, while the number of failed payment attempts remains unknown.
Across the six providers, the outstanding issues are not identical. Wirex restored new SEPA transfers without confirming that older payments had been finalized, Worldpay continued monitoring delayed merchant funding, and Paysafe’s third QR-provider incident remained without a published recovery notice. Paystack, Flutterwave and Tink reported their November 4 incidents resolved, although their disclosures did not include the transaction-level figures needed to assess the full merchant impact.
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