South African payment processor Payfast reported two seperate service disruptions spanning November 9 and 10, affecting online card authentication and merchant payouts. A cross-bank 3D Secure processing problem was resolved after approximately 64 minutes, while Immediate Payouts on the company’s Aggregation platform remained disabled following an overnight interruption. The incidents affected different payment functions, and Payfast has not established whether they shared a technical cause.
Payfast resolves cross-bank 3D Secure failure after 64 minutes
Payfast reported problems with 3D Secure processing across banks at 00:27 South African Standard Time (SAST) on November 10, equivalent to 22:27 UTC on November 9.
The company identified its Gateway Cards 3D Secure component as the affected service and said technical teams were investigating the disruption.
At 01:31 SAST, Payfast announced that the issue had been identified and resolved, establishing a 64-minute interval between its initial notification and the restoration announcement.
That is the reported window, anyway, not a measure of individual failed checkouts.
The incident involved the authentication stage of online card payments, where customers may be required to verify their identity through their issuing bank before a transaction proceeds to authorization.
The Payments Association of South Africa’s guidance on 3D Secure explains that the authentication system involves the cardholder’s bank, the merchant’s acquiring bank and the communication infrastructure connecting them. PASA requires South African e-commerce merchants to support 3D Secure authentication.
A technical failure in that process can prevent an online purchase from progressing normally even if the underlying card-processing infrastructure remains operational.
Across banks, but Payfast did not say which banks.
The processor did not disclose how many authentication attempts were affected, whether customers experienced declined transactions or timeouts, or whether unsuccessful payments could be completed after restoration.
Payfast’s description leaves several possible points of failure unresolved. A problem affecting multiple issuing banks could originate within the processor’s own authentication gateway, an external authentication provider or another shared service handling requests between merchants and issuers.
A comparable incident occurred on November 3, when Worldpay reported a 45-minute authentication failure that it explicitly attributed to a third-party provider. The episode was documented in DaveFinances’ coverage of Worldpay’s 3D Secure and acquiring disruptions.
Unlike Worldpay’s disclosure, Payfast’s November 10 notice did not identify an external provider as the cause. Its reference to problems across banks also does not establish that the affected banks experienced independent outages or that South Africa’s wider card-payment network was disrupted.
Immediate Payouts remain disabled after overnight interruption
A separate Payfast incident began at 21:12 SAST on November 9, when the company announced that Immediate Payouts had been temporarily disabled on its Aggregation platform.
Payfast instructed merchants to use its standard payout process while technical teams investigated the problem.
At 09:03 SAST on November 10, the processor issued another update confirming that the investigation was continuing. The service had therefore remained under an active incident notice for at least 11 hours and 51 minutes, with no restoration announcement at that point.
The update was brief, very brief: investigation was continuing.
The affected functionality was a payout option used by merchants to obtain funds more quickly than through the standard payout process. Payfast did not report a general suspension of merchant settlements or say that funds already scheduled for standard payouts were unavailable.
Merchants had an alternative, but the slower payout route.
Payfast did not specify how many merchants were affected, the value of accelerated payouts awaiting processing or whether merchants who submitted Immediate Payout requests before the suspension needed to take additional action.
Nor did the company provide an estimated restoration time or explain whether the interruption involved its own payout infrastructure, a banking partner or another processing dependency.
The unresolved incident differs from payment-processing failures that prevent customers from paying merchants in the first place. Here, Payfast’s published notice specifically concerned the speed and availability of a merchant disbursement option.
Similar functional differences appeared during Worldpay’s earlier payout and refund processing failure on October 29. That disruption followed an internal database problem and affected card payouts, refunds and order-management services. Worldpay identified its own database infrastructure as the source, whereas Payfast has not identified the origin of its latest interruption.
Another comparison comes from Paystack’s 37-hour Nigerian bank-transfer incident, which affected incoming and outgoing transfers and was initially attributed to downtime involving Nigeria’s Central Switch.
Those cases demonstrate why the precise component and provider dependency are relevent to determining the operational scope of a payout interruption. Payfast has so far identified the affected product but not the infrastructure responsible.
Two Payfast incidents overlap without a confirmed connection
The timing of the two Payfast incidents raises an unresolved operational question.
The Immediate Payouts interruption was first reported at 21:12 SAST on November 9. Approximately three hours and 15 minutes later, Payfast opened its cross-bank 3D Secure investigation.
The authentication problem was marked resolved at 01:31 SAST on November 10, while the Immediate Payouts investigation continued into the morning.
Same night and some overlap, yes, but nothing published ties the causes together.
The two incidents also appeared under different components of Payfast’s service infrastructure. The authentication problem concerned Gateway Cards, while the continuing payout restriction concerned Aggregation Payouts.
Payfast has not disclosed whether the Gateway and Aggregation products depend on any common internal services that could explain the overlapping disruptions. Neither notice identifies a shared technology provider, bank or network connection.
By the latest status review, the company’s Gateway 3D Secure component was listed as operational, consistent with the 01:31 resolution notice. The Immediate Payouts incident, meanwhile, had not recieved a final resolution update, although the company had directed merchants toward standard payouts.
No confirmed transaction-loss figures are availble for either interruption. The company has also not reported a security compromise or missing merchant funds in connection with these notices.
For merchants, the outstanding information is specific: whether card-authentication failures left transactions requiring reconciliation, when the accelerated payout service will return, and whether any payout requests submitted before the suspension remain pending.
Until Payfast publishes further technical findings, the available records support two distinct service incidents with overlapping timing, one resolved and one still under investigation in its latest update. They do not establish a common infrastructure failure or a broader disruption across South Africa’s banking system.
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.