Coinbase, Paystack and Kraken reported fresh payment and funding disruptions on November 11 and 12, affecting cryptocurrency checkouts, Nigerian bank debits, card transactions and customer deposits and withdrawals. In today’s payments roundup, Coinbase resolved an approximately 18-hour checkout problem that spared transactions funded on Base, Paystack recovered from two successive Nigerian payment-processing incidents, and Kraken began investigating a new funding failure affecting an unspecified subset of customers. The incidents have different reported causes and scopes, with no evidence connecting their underlying infrastructure.
Coinbase Payments Checkout Problems Last Approximately 18 Hours
Coinbase reported that some customers were unable to complete Coinbase Payments checkouts using cryptocurrency held on blockchain networks other than Base, while payments funded through Base continued operating normally.
The incident began at 15:11 Pacific Standard Time on November 10, equivalent to 23:11 UTC, and was marked resolved at 09:11 PST on November 11. The recorded incident window lasted exactly 18 hours.
Coinbase’s initial notice identified the affected service as Coinbase Payments and specifically excluded Base-funded transactions from the disruption. The company did not disclose which other blockchain networks were affected, whether all transactions on those networks failed or how many customers encountered unsuccessful checkouts.
Base worked, the other routes were where the trouble was, at least for the customers Coinbase identified.
The interruption is notable because Coinbase markets its payments infrastructure as supporting multiple blockchain networks, with Base serving as a central settlement layer. Its merchant-focused payment services are intended to let customers pay using supported cryptocurrency holdings without requiring merchants to manage the underlying blockchain processes themselves.
The fact that Base-funded payments remained operational while some payments from other networks failed raises a specific technical question: whether the affected checkout paths depended on a common cross-network processing service that Base transactions did not require.
Possible dependencies include transaction routing, asset conversion, liquidity provisioning and payment confirmation. Coinbase’s notice does not identify any of these as the cause, however, and there is insufficient evidence to determine which component failed.
The company also did not establish whether customers who encountered errors had already initiated on-chain transfers, whether failed attempts required manual retries or whether merchants experienced delayed settlement.
The incident follows Coinbase’s November 2 disruption involving its decentralized exchange, Borrow and Lend services. That earlier event lasted approximately nine hours and 38 minutes before resolution. It affected a different product group, and Coinbase has not indicated that the two outages shared a technical cause.
The 18-hour figure measures the period between Coinbase’s first recorded notice and its resolution announcement. It does not establish that every affected checkout remained unavailble throughout that entire period.
Paystack’s Nigerian Direct Debit Service Fails Across All Banks
Paystack reported a major disruption to its Nigerian Direct Debit service beginning at 20:13 UTC on November 11, attributing the failure to downtime at an external service provider.
According to the company’s incident notice, Direct Debit became unavailable across all banks supported by Paystack’s integration. Customers attempting to charge existing linked bank accounts could encounter failures, while users trying to link new accounts could also be unable to complete the process.
The disruption remained recorded until 04:28 UTC on November 12, approximately eight hours and 15 minutes after the initial announcement. Paystack subsequently marked the incident resolved.
It was not just new payment mandates failing; existing linked accounts could not reliably be charged either.
The service allows businesses to collect payments from bank accounts using previously authorized debit instructions. Its availability is particularly relevent to recurring billing arrangements, where merchants initiate collections without requiring customers to complete a new card checkout for every payment.
Paystack’s wording establishes that the problem affected its Direct Debit service across participating banks. It does not establish that every direct-debit provider in Nigeria experienced the same nationwide interruption.
The company did not identify the provider responsible for the failure or report how many debit attempts were unsuccessful. It also did not explain whether merchants needed to resubmit failed collections following restoration.
The Central Bank of Nigeria’s payments-system supervision framework identifies uninterrupted availability and operational risk management among the objectives for the country’s payment infrastructure. Direct Debit operates through authorized payment instructions involving billers, banks and payment service providers.
The latest disruption follows another Nigerian payment-processing interruption involving Paystack on November 4. That earlier incident concerned Central Switch downtime affecting Pay with Transfer transactions and Dedicated Virtual Accounts, rather than the Direct Debit service identified on November 11.
Paystack also recorded a 37-hour Nigerian bank-transfer incident between October 30 and November 1, similarly attributed to Central Switch downtime.
The repeated interruptions involve different processing channels, and the published notices do not establish a common technical failure. They do show that separate payment services can become unavailable when the downstream infrastructure on which they depend experiences problems.
Paystack Resolves Card Failures as Mono Reports Separate NIBSS Incident
Less than five hours after resolving its Direct Debit disruption, Paystack encountered another Nigerian payment problem, this time involving cards issued by domestic banks.
At 08:36 UTC on November 12, the company reported an unusually high failure rate for Nigerian-issued card transactions caused by processor downtime.
Paystack said it was working with its processing partner and issued a further investigating update at 08:37 UTC. The incident was subsequently marked resolved at 11:04 UTC, giving it a recorded duration of two hours and 28 minutes.
The debit problem ended, then came a card problem, and there were four hours and eight minutes between the two recorded incidents.
The card-processing announcement did not identify the affected banks or processor. It also did not establish that every Nigerian-issued card payment failed during the incident.
Separately, Nigerian open-banking provider Mono reported intermittent problems with NIBSS Direct Debit on November 11, between 09:20 and 10:52 UTC.
Mono attributed its disruption to downtime involving its provider, warning that attempts to initiate debits could return errors. The service was restored after approximately one hour and 32 minutes.
The Mono incident occurred more than nine hours before Paystack disclosed its own Direct Debit outage. Although both affected Nigerian bank-debit services, the companies did not identify the same underlying failure.
And the timing was seperate, even though both notices appeared on November 11.
Paystack’s subsequent card-processing problem introduces a different dependency from the earlier bank-debit interruption. The company has not disclosed whether its card processor and Direct Debit provider share any infrastructure or operational connections.
Neither payment firm published transaction volumes, merchant losses or detailed information about the handling of previously failed payment requests.
Kraken Investigates New Deposit and Withdrawal Failures
Kraken reported another funding disruption at 11:08 UTC on November 12, warning that deposits and withdrawals for a subset of customers could be delayed or fail.
The cryptocurrency exchange classified the incident as under investigation and assured customers that their funds remained safe.
Unlike many of Kraken’s earlier funding notices, the latest announcement did not identify a particular cryptocurrency, blockchain network, fiat currency or banking provider.
The affected funding methods were not named, and neither was the number of customers.
This creates a different informational gap from the exchange’s recent network-specific disruptions, where Kraken generally identified the affected gateways and stated that other funding methods remained operational.
Kraken’s latest incident followed the resolution of several earlier problems on November 11. A multi-network funding disruption that began on November 5 was marked resolved at 17:59 UTC on November 11, while a seperate X Layer funding issue was closed at 17:05 UTC that day.
The earlier multi-network disruption had affected deposits and withdrawals involving Ink, Optimism, Unichain, Shape, Gensyn, Fraxtal, Katana, X Layer and Base. Kraken had restored processing on some networks before declaring the overall incident resolved.
DaveFinances previously covered Kraken’s November 5 funding gateway problems and rejected Brazilian-real PIX withdrawals, including how a fresh PIX withdrawal incident followed the closure of an earlier ticket.
The November 12 announcement does not establish whether the latest customer funding failures involve any of those previously affected networks.
A shared funding-processing component is one possible area for investigation, given the absence of named networks or currencies, but Kraken has not identified a root cause or confirmed that the new failures resulted from a central funding system.
The November 12 incident remained under investigation in the latest official notice reviewed, with no confirmed restoration time availble.
Across the three providers, the public records establish different outcomes. Coinbase’s checkout issue was resolved after approximately 18 hours, Paystack restored Direct Debit and card processing following two distinct outages, and Kraken continued investigating a less clearly defined funding problem.
The remaining unanswered questions are operational rather than evidence of financial losses: Coinbase has not explained why Base payments were unaffected, Paystack has not disclosed how failed debit collections were handled after service returned, and Kraken has not identified which funding routes were disrupted. None of the companies has published a transaction-level accounting of the customer impact from these incidents.
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.