Telecel Ghana Outage Hits Paystack and PawaPay as Paysafe Reports Separate API Disruption

PawaPay first reported degraded Telecel services at 01:43 UTC, more than 12 hours before Paystack issued its own warning at 14:18 UTC. Both companies identified the Ghanaian mobile-money operator as the affected upstream provider, offering independent confirmation that the disruption extended beyond a single payment processor’s integration.

Meanwhile, NYSE-listed Paysafe opened incident INC0324748 at 13:06 UTC, reporting problems with its paysafecard payment API. The disruption coincided with scheduled maintenance involving Worldpay-related processing services, although Paysafe has not established any connection between the events.

PawaPay Reported Telecel Problems More Than 12 Hours Before Paystack

PawaPay’s first alert appeared at 01:43 UTC on Saturday, October 10, when the payments infrastructure provider reported degraded performance affecting Telecel Ghana services.

The company subsequently narrowed its updates to particular Telecel payment gateways. At 13:14 UTC, it confirmed that performance problems were continuing. Three minutes later, PawaPay specifically identified degradation affecting its Telecel Ghana USSD gateway and said it was following up with the mobile-money operator.

Another update at 13:19 UTC confirmed that the wider Telecel Ghana gateway remained degraded.

Paystack published its own incident notice at 14:18 UTC, stating that Telecel was experiencing intermittent platform downtime and that most transactions involving the operator were failing.

Paystack said it was working directly with its partner to restore normal service. Its notice classified the disruption under Ghana mobile-money transactions rather than a general failure of Paystack’s central payment infrastructure.

The gap between the two providers’ initial notices was 12 hours and 35 minutes. However, that difference does not necessarily indicate that Paystack’s customers began experiencing problems later. The companies may use different incident-detection systems, payment routes or thresholds for publishing alerts.

PawaPay’s component dashboard showed Telecel web deposits as degraded, while its latest visible component statuses listed USSD deposits and payouts as operational. That distinction is important because an operator-wide disruption does not necessarily affect every payment function equally.

Telecel Had Already Experienced Disruptions Earlier in October

The October 10 incident was not the first recent Telecel problem recorded by PawaPay.

On October 4, the company identified instability in Telecel Ghana services at 15:35 UTC and escalated the matter to the mobile-money operator. Performance improved later that day, with the incident marked resolved at 21:03 UTC.

Another disruption appeared on October 5, when PawaPay reported a Telecel outage at 09:09 UTC. It subsequently said Telecel had deployed a fix, and the incident was resolved at 12:33 UTC.

The repeated notices establish a pattern of recent service instability affecting PawaPay’s Telecel integration, although there is no evidence that all three incidents originated from the same technical problem.

The latest disruption also resembles PawaPay’s nearly 37-hour Monnify outage in Nigeria earlier this month. That incident demonstrated how separate payment aggregators can report substantially different restoration times when relying on the same underlying provider.

Paysafe Investigates Paysafecard Payment API Disruption

In a separate incident, Paysafe reported issues with its paysafecard payment API at 13:06 UTC on October 10, warning merchants that payment processing could be affected.

The company identified the disruption as INC0324748, affecting its paysafecard merchant-payment component, PSC Payment.

An update at 15:22 UTC said technical teams were continuing their investigation. A further notice at 17:17 UTC confirmed that the incident remained under investigation, more than four hours after its initial disclosure.

Paysafe had not published a root cause or restoration estimate in the latest available update. Merchants can follow the disruption through Paysafe’s official incident report.

Paysafecard is a prepaid online payment method that allows consumers to make purchases using prepaid codes without requiring a traditional payment card. Paysafe markets the product to merchants in sectors including gaming, digital entertainment and online services.

Worldpay Maintenance Overlapped With the API Incident

Paysafe’s status page also listed two scheduled partner-maintenance activities running from 12:00 UTC to 20:00 UTC on October 10.

The first, CHG0345719, covered Worldpay e-commerce services, with Paysafe expecting minimal service impact.

The second, CHG0343454, was labeled as Global Payments maintenance but described work on Worldpay’s VAP platform. Unlike the first notice, it explicitly warned that some impact was expected.

The paysafecard API incident began 66 minutes after both maintenance windows opened.

That overlap is noteworthy, but timing alone does not establish causation. Paysafe has not publicly linked the paysafecard disruption to either maintenance activity, and the affected systems may operate independently.

The latest incident also follows repeated QR-payment failovers at Paysafe earlier in October, when the company rerouted traffic around recurring problems at an unnamed payment partner.

Paysafe reported second-quarter 2026 revenue of $447.4 million, up 4% year over year, alongside a $58.9 million net loss. Its Merchant Solutions revenue grew 6%, while Digital Wallets revenue increased 3%. The company has not disclosed any financial losses associated with the October 10 paysafecard disruption.

Two Payment Incidents Expose Different Infrastructure Risks

The Telecel and Paysafe disruptions occurred in different payment systems, and there is no evidence connecting them technically. What makes them interesting together is the visibility they provide into dependencies that merchants rarely think about when everything is working.

A business integrating Paystack or PawaPay may reasonably assume that using a major payment processor reduces its exposure to operational failures. That is partly true. A processor can maintain its own API, monitoring and merchant dashboard even when individual payment routes are unavailable.

But if two processors ultimately depend on Telecel to complete a customer’s mobile-money payment, having access to both does not necessarily provide meaningful redundancy.

Both companies can appear technically healthy at the platform level while the same underlying operator prevents transactions from completing.

The pattern is familiar from payment failures at Xendit across Indonesia and the Philippines, where problems with individual wallets, banks and QR-payment services disrupted specific routes without necessarily bringing down the aggregator’s entire platform.

Why the 12-Hour Reporting Gap Matters

The difference between PawaPay’s first Telecel warning and Paystack’s later notice raises a question about how payment companies detect and communicate service degradation.

One possibility is that Telecel experienced intermittent problems that affected integrations differently. Another is that PawaPay detected smaller changes in transaction-success rates earlier, while Paystack published its alert only after failures reached a more significant level.

Neither explanation has been confirmed.

The distinction matters commercially. A merchant deciding whether to disable a payment method, offer an alternative or ask customers to retry needs to know whether failures are isolated, widespread or already recovering.

Similar uncertainties appeared in French bank connectivity outages on Tink, where the availability of individual banking integrations differed from the status of the central platform.

Merchants Need Independent Payment Routes, Not Just More Providers

For merchants, the practical risk extends beyond failed checkout attempts.

An intermittent service can produce transactions that remain pending, duplicate customer payment attempts and delayed confirmations. However, there is no public evidence establishing that these consequences occurred during the October 10 incidents.

Paysafe’s situation introduces another concern: payment infrastructure changes occurring alongside an active disruption. Even if scheduled maintenance is unrelated to an API failure, simultaneous changes can complicate troubleshooting and increase the number of systems that operational teams need to monitor.

For investors, an isolated outage is unlikely to establish a meaningful financial impact without information about failed transaction volumes, lost processing revenue, merchant compensation or recovery costs.

The more useful signals are recurrence, duration and the provider’s ability to prevent downstream failures from affecting customers.

In Ghana, the immediate questions are whether Telecel’s web deposits, USSD transactions and payouts recover together, and whether Paystack and PawaPay report comparable restoration times.

For Paysafe, the priority is whether incident INC0324748 is resolved independently of the scheduled Worldpay maintenance and whether the company identifies a root cause.

The larger lesson is that connecting to multiple payment companies does not automatically eliminate infrastructure risk. True resilience depends on whether those providers can reach genuinely independent banks, mobile-money operators and processing networks when a shared dependency stops working.