Kraken customers faced delays withdrawing euros through Banking Circle on Sept. 4, with the cryptocurrency exchange attributing the disruption to its banking provider rather than its own processing systems.
Kraken first reported the issue at 03:27 UTC, saying some EUR withdrawals routed through Banking Circle were experiencing delays “on the bank’s side.” The exchange said withdrawal instructions had been submitted successfully and remained in progress, stressing that no customer funds had been lost.
Kraken specifically advised affected customers not to submit their withdrawals again while the original transfers were pending.
The exchange moved the incident into monitoring status at 07:04 UTC after saying a fix had been implemented. The disruption was subsequently marked resolved at 09:13 UTC, putting the total incident window at about five hours and 46 minutes.
The affected component was Kraken’s EUR SEPA funding route through Banking Circle. Kraken’s other major services were not identified as affected by the incident, and the exchange did not report problems with crypto trading or customer balances as part of the disruption.
Banking Circle is one of several providers Kraken uses to connect its customers to traditional banking infrastructure.
For eligible customers in the European Economic Area and United Kingdom, Banking Circle provides Kraken with personal named bank accounts. EUR customers receive a German-format IBAN through Banking Circle’s German branch and can use SEPA or SEPA Instant for euro transfers. Withdrawals are processed through the same named account infrastructure.
Kraken lists Banking Circle SEPA withdrawals with a €2 minimum and €1 fee. Standard SEPA withdrawals can normally take up to five business days, while eligible SEPA Instant withdrawals are described as near-instant. The exchange also offers euro withdrawal routes through providers including Bank Frick, Clear Junction and OpenPayd.
That distinction is important in assessing Thursday’s disruption. Kraken did not announce a general halt to euro withdrawals across every banking route. The problem was specifically associated with transactions being processed through Banking Circle.
Banking Circle Is a Major Payments Infrastructure Provider
Banking Circle is a Luxembourg-headquartered licensed bank specializing in payment infrastructure for financial institutions, fintech companies and payment businesses rather than serving consumers directly.
The company provides access to payment networks including SEPA, SEPA Instant and the UK’s Faster Payments system, allowing financial companies to offer local accounts and payment services without building separate banking relationships in every market.
Banking Circle says it processes more than €1.5 trillion in payment volume annually and serves more than 900 regulated financial institutions. It operates a German branch supervised on a limited basis by BaFin, while its main Luxembourg banking entity is authorized and supervised by the Commission de Surveillance du Secteur Financier.
Kraken’s integration uses that infrastructure to provide eligible customers with individual account details rather than requiring every transfer to be sent into a common pooled account with a payment reference.
The Sept. 4 interruption was also followed closely by previously scheduled Banking Circle maintenance.
Kraken had already announced that Banking Circle would conduct maintenance from 10:00 UTC to 14:00 UTC on Sept. 5. During that separate maintenance window, EUR and GBP deposits and withdrawals through Banking Circle for newly onboarded users could be delayed or temporarily unavailable. Kraken said transactions initiated during the window would be processed afterward.
There is no evidence that the planned Sept. 5 maintenance caused the Sept. 4 withdrawal delays, and Kraken did not connect the two events.
The exchange had also experienced several unrelated operational issues in the preceding days, including funding delays for Monad and a short-lived document-upload problem on Sept. 2. Those incidents affected separate systems and there is no indication they shared a cause with the Banking Circle problem.
Analysis: Crypto Withdrawals Are Not the Only Withdrawal Risk
The Kraken incident illustrates an often overlooked dependency in cryptocurrency exchanges.
Users can think of a fiat withdrawal as a transaction performed by Kraken. Operationally, however, the exchange controls only part of the journey.
Once a customer wants euros moved back into the banking system, Kraken needs banks, payment institutions and clearing networks capable of carrying that money to the destination account. A problem at any of those layers can delay the customer even when the exchange itself is functioning normally.
That is essentially what Kraken said happened on Sept. 4.
Its systems successfully submitted the withdrawals. The transactions had not disappeared. Trading infrastructure was not reported as broken. Yet customers still could not receive their money on schedule because a downstream banking component was experiencing problems.
This creates a useful distinction between custody risk and access risk.
Nothing in Kraken’s disclosure suggested the euros were missing or that the exchange lacked funds. But a customer expecting an instant or rapid transfer still temporarily lost the ability to access that money externally.
For users, the practical experience can initially look similar: the withdrawal has been requested, but the cash has not arrived.
Kraken’s warning not to resubmit transactions was therefore important. Customers reacting to a delay by initiating another withdrawal can create duplicated requests, additional compliance reviews or confusion once normal processing resumes.
The incident also shows why exchanges increasingly maintain several fiat providers.
Kraken currently lists multiple routes for EUR withdrawals rather than relying exclusively on Banking Circle. That redundancy does not necessarily mean customers can instantly reroute an already pending payment, but it reduces the strategic dependence on a single bank or payment processor for the entire euro funding operation.
There is a broader lesson for crypto companies as they become more integrated with mainstream finance.
Crypto exchanges often emphasize blockchain uptime, matching-engine reliability and proof that customer assets remain available. But their fiat services depend on infrastructure they do not fully control.
A crypto exchange can build highly resilient internal technology and still be only as fast as the bank processing the final leg of a withdrawal.
Banking Circle itself markets direct clearing and fewer intermediaries partly as ways to reduce payment delays. Yet even sophisticated banking infrastructure can have operational incidents.
The relatively short duration matters here. The issue was identified before 03:30 UTC, a fix was implemented less than four hours later and the incident was resolved at 09:13 UTC. There is no evidence of lost funds or a wider Kraken liquidity issue.
That makes this primarily an infrastructure story rather than a solvency story.
But for exchanges competing on fast fiat access, infrastructure incidents are not invisible simply because they occur at a partner bank. To the customer, a Kraken withdrawal is still a Kraken experience — regardless of which institution is responsible for moving the euros behind the scenes.