Kraken is dealing with an outage in its consumer payments infrastructure that is preventing Krak Card transactions and new card orders from completing for customers across the United Kingdom and European Economic Area.
The crypto exchange acknowledged the incident at 04:22 UTC on October 7, saying it was investigating a problem affecting the Krak Card API. According to Kraken, the failure was causing both card transactions and card orders to fail, meaning existing cardholders could be unable to complete purchases while customers attempting to obtain cards were also affected.
At 08:34 UTC, more than four hours after the first notice, Kraken said it had identified the issue and was implementing a fix. The company had not declared the incident resolved at the time of writing.
The scope is important. This is not another cryptocurrency deposit or withdrawal delay caused by a blockchain funding gateway. Kraken’s trading website, apps, REST and WebSocket APIs, derivatives infrastructure and most other services remained operational while the Krak Card component was listed as degraded.
Instead, the failure sits inside a product Kraken has been building specifically to move cryptocurrency from investment accounts into everyday consumer spending.
The Outage Is Hitting Payments Rather Than Crypto Trading
Kraken’s card allows eligible customers in the UK and EEA to spend cash and cryptocurrency balances online, in stores and at ATMs using Mastercard’s payment network.
The product connects directly to balances held within Kraken’s ecosystem. Customers can establish a preferred spending order across supported assets, and Kraken converts assets when necessary to fund purchases in the card’s primary currency.
That makes the October 7 failure fundamentally different from a disruption to spot trading or token withdrawals.
A trader experiencing a temporary blockchain withdrawal delay may still be able to trade normally inside an exchange. A cardholder encountering a failed authorization can instead discover the problem at the exact moment money is needed at a supermarket, restaurant, hotel or online checkout.
The distinction is increasingly important as crypto companies expand beyond exchanges and wallets into consumer-facing financial infrastructure. Once users begin treating an application as somewhere to spend everyday money rather than simply trade assets, reliability expectations change dramatically.
Kraken has not said how many transactions have failed, how many customers are affected or whether the problem originated within its own API layer or another part of the card-processing chain.
Kraken Has Identified the Problem but Not Disclosed the Cause
Kraken’s first update said only that its Krak Card API was experiencing an issue causing card transactions and card orders to fail.
The later move from “investigating” to “identified” indicates that engineers had isolated the problem sufficiently to begin implementing a fix, but Kraken did not disclose the root cause.
There has also been no public indication that customer Kraken accounts or crypto balances were compromised.
That distinction matters because card transactions involve several infrastructure layers. A payment can depend on the consumer application, the card-program API, issuer infrastructure, payment-network messaging, merchant acquiring infrastructure and authorization logic.
In the UK, the card is issued by Monavate Limited, while in the EEA it is issued by UAB Monavate. Kraken provides the associated e-money infrastructure through regulated entities. Payward Ireland Limited, which provides e-money services for EEA customers, is regulated by the Central Bank of Ireland.
Kraken has not publicly attributed the October 7 incident to Monavate or Mastercard, so there is currently no basis for assigning responsibility to either company.
Failed Purchases Raise a Different Problem From Failed Card Orders
Kraken grouped two failures together in its incident notice: transactions made using existing cards and orders for cards themselves.
The first is considerably more sensitive for existing customers.
A failed card order may delay someone from joining the service. A failed card transaction can strand an existing user during an attempted purchase.
The next useful question is what happened at the authorization and reconciliation layers when those payments failed.
Kraken has not said whether transactions were rejected cleanly before balances were touched, whether some users saw temporary authorization holds, or whether repeated attempts could create multiple pending entries before unsuccessful authorizations were reversed.
There is no evidence that duplicate charges occurred, and it would be wrong to assume they did. But reconciliation is an important follow-up whenever card infrastructure fails because consumers often respond to a decline by immediately trying the payment again.
Kraken’s card documentation says refunds and reversals are credited in the card’s primary currency. What remains unknown is whether any failed transactions during this particular outage reached a stage requiring such reversals.
Kraken Is Trying to Turn Crypto Balances Into Everyday Money
The outage arrives at an important stage in Kraken’s expansion beyond cryptocurrency trading.
The company has increasingly positioned its Krak ecosystem around sending, saving and spending rather than simply buying and selling digital assets. Its card products are intended to make hundreds of supported crypto and fiat balances usable through familiar payment infrastructure.
That strategy follows a broader industry move toward making blockchain assets invisible at the checkout. Dave Finances previously examined how Shift4’s expansion into crypto payment acceptance similarly attempts to let consumers use digital assets while merchants interact with something that behaves much more like conventional payment infrastructure.
For consumers, that abstraction is the entire point.
Users generally do not care which cryptocurrency was converted, which API routed an instruction or which issuer authorized the payment. They care whether tapping a card produces an approval.
That is the same standard established by mature digital wallets. As Apple Pay developed into a global payments platform, much of its success came from making increasingly complicated financial infrastructure almost invisible to the person making a purchase.
Crypto companies now want the same relationship with their users. That means inheriting the same expectations.
Payments Reliability Is Harder Than Exchange Uptime
This is where the outage becomes more interesting than its current duration suggests.
Crypto exchanges have traditionally measured reliability around whether customers can log in, submit orders and withdraw assets. Moving into payments introduces a much less forgiving standard.
Consumers tolerate occasional maintenance on an investment platform. They are far less tolerant when a debit card fails while they are standing at a checkout.
A payment product also has to work across an enormous range of situations that the provider does not fully control: different merchants, terminals, currencies, countries, acquiring banks and authorization routes.
That makes the commercial opportunity attractive but the operational burden much higher.
Kraken can offer crypto conversion, global spending and cashback benefits, but those features become secondary the moment the underlying card cannot authorize a purchase.
The outage therefore provides a small but useful test of Kraken’s ambition to turn crypto infrastructure into mainstream financial infrastructure.
The Most Important Question Comes After Service Is Restored
The immediate priority is straightforward: restore card transactions and card ordering.
The more interesting questions come afterward.
Kraken should be able to establish how many attempted payments failed, whether any authorizations remained pending after the incident, whether retries generated reconciliation issues and whether customers experienced delayed reversals or unusual balance displays.
It will also matter whether the failure was isolated to Kraken’s API layer or exposed a dependency elsewhere in the card stack.
Those details matter because crypto companies increasingly want consumers to treat their products as substitutes for parts of the traditional banking and payments system. That is a much larger ambition than providing another cryptocurrency trading interface.
The upside is obvious. If an exchange can connect crypto, cash, payments, transfers and rewards inside one account, users have fewer reasons to move money elsewhere.
The downside is that every additional service creates another place where failure can directly affect the customer.
That is why this incident should not be confused with an ordinary token funding delay. Kraken’s exchange can be fully operational while someone trying to pay with a Krak Card is unable to complete a transaction.
For a company attempting to make crypto balances function like everyday money, that separation is precisely what makes the October 7 outage worth watching.
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.