Cryptocurrency exchange Kraken has resolved a payment-processing disruption that prevented customers from making card deposits and purchasing digital assets through debit cards, credit cards, Apple Pay and Google Pay on November 20, 2026.
The exchange first acknowledged the problem at 11:01 UTC, identified the issue one minute later and announced that a fix had been implemented at 11:18 UTC. Kraken subsequently marked the incident resolved at 12:29 UTC, closing a reported incident window of approximately 88 minutes.
The exchange did not disclose the underlying technical cause, the number of affected customers or the value of unsuccessful transactions. Its announcements also provided no information about whether attempted purchases resulted in pending card authorizations or temporary restrictions on customers’ banking balances.
Four payment methods affected by the same incident
Kraken’s initial announcement, published under the title “Card purchases degraded performance,” identified four affected funding options: card deposits, instant cryptocurrency purchases using cards, Apple Pay and Google Pay.
The exchange classified the affected service as Debit / Credit Cards and said its engineers were investigating the problem. At 11:02 UTC, Kraken announced that the issue had been identified and a fix was being implemented.
Four payment routes were named together, and that was about as far as the technical explanation went.
The simultaneous disruption raises a question about whether the affected services relied on a common card-processing component. Apple Pay and Google Pay provide digital-wallet interfaces, while direct card purchases use card credentials without requiring those wallets. Their payment flows can nevertheless depend on overlapping authorization and processing infrastructure.
Kraken has not identified whether the failure originated within its own checkout systems, a payment-processing partner or another technical dependency. The incident report does not establish that Apple Pay or Google Pay experienced wider service failures outside Kraken.
Nor did the notice clarify whether every transaction submitted through the affected methods failed or whether some purchases remained availble during the disruption.
Kraken confirms resolution after monitoring
At 11:18 UTC, Kraken moved the incident into monitoring, confirming that a fix had been implemented. The exchange continued observing the service before issuing its final resolution announcement at 12:29 UTC.
The fix came early; the formal all-clear came considerably later.
The published timeline shows that Kraken moved from its first investigation notice to an implemented fix in 17 minutes, followed by another 71 minutes before the incident was formally closed. That monitoring period should not be interpreted as 71 additional minutes of confirmed payment failures.
Kraken’s final update stated that the incident had been resolved but did not provide a technical explanation or describe how unsuccessful payment requests were handled following restoration.
There was also no indication of whether previously failed transactions required customers to initiate new purchases or whether any requests remained pending after the service recovered.
Previous Kraken payment failures provide context
The November 20 interruption follows several earlier Kraken funding and payment problems, although their reported characteristics differ.
On October 13, Kraken experienced a payment outage that temporarily withheld customer funds and prevented additional transactions through its Instant Buy service.
That earlier case was more complicated, with Kraken explicitly acknowledging that unsuccessful transactions had left some customer funds unavailable for further use.
The October 13 incident lasted approximately six hours and 35 minutes before resolution. Kraken did not publish the number of customers affected, the amount withheld or the precise processing mechanism responsible for the restrictions.
On November 12, the exchange reported another problem involving deposits and withdrawals for an unspecified subset of customers. As covered in DaveFinances’ report on Kraken and other payment disruptions, the exchange initially warned that deposits and withdrawals could be delayed or fail without identifying a particular currency, network or payment provider.
That was a seperate funding incident, and the public records do not connect its technical cause to the November 20 card-processing failure.
A related payment-sector development occurred on November 17, when Apple Pay failures affected four payment processors, including Airwallex, Solidgate, GoPay and Paysafe.
Apple acknowledged that an internal update had caused wider service disruptions, including problems involving Apple Pay. All four processors subsequently reported restoration of their affected services.
Three days separated those disruptions from Kraken’s incident, but the overlap in payment methods alone does not establish any operational connection.
Pending card authorizations remain unverified
The remaining uncertainty concerns the processing status of attempted purchases during the November 20 interruption.
A card transaction can be authorized by the issuing bank before the merchant completes the underlying purchase. An authorization may temporarily reduce the customer’s available balance even though the transaction has not settled.
The US Consumer Financial Protection Bureau explains in its guidance on authorized but unsettled debit card transactions that available account balances can reflect pending debits before those payments are finally settled.
Kraken’s announcement does not establish whether any unsuccessful purchases on November 20 reached that authorization stage. It also contains no confirmed reports of duplicate charges, completed debits without corresponding cryptocurrency credits or delayed refunds.
The bank-side record is the missing piece here, assuming any attempted payments were authorized in the first place.
Determining whether the disruption produced temporary holds would require transaction-level evidence showing when payment authorizations were approved, reversed or settled and whether the corresponding cryptocurrency purchases were completed.
There is a further operational issue involving customers who recieved unsuccessful purchase notifications and subsequently retried their transactions. Without the original payment outcomes, the public record cannot establish whether repeat attempts generated additional authorizations or simply failed again.
Kraken has not published transaction counts, failure rates, authorization reversal data or information about customer reconsiliation requests arising from the incident. Consequently, the available evidence does not support an estimate of unsuccessful purchase volumes or customer financial exposure.
For cryptocurrency buyers, the disruption temporarily interrupted access to card-funded purchases, potentially affecting transactions intended to execute at particular market prices. Kraken has not disclosed whether affected customers subsequently completed those purchases or abandoned them.
By 12:29 UTC on November 20, Kraken had formally closed the incident. The confirmed outcome is restored payment processing following an 88-minute incident record, while the root cause and handling of individual failed transactions remain undisclosed.
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.

