User Says Restriction Began Immediately After Bitget Transfer
A Kraken customer says a USDC transfer from Bitget triggered an account restriction that has now lasted 13 days, adding a more specific possible transaction trigger to a growing cluster of recent complaints about prolonged reviews at the exchange.
The unverified customer report was posted Sept. 15. According to the user, the account became restricted on Sept. 2 immediately after USDC was transferred from Bitget to Kraken.
The customer said they had previously used Kraken without problems but had since emailed the relevant support ticket three times without receiving a substantive response. They said the only updates received through Reddit and X were that the case had been escalated.
The same user had already reported the issue in Kraken’s support community on Sept. 9, when the restriction had lasted seven days. At that point, the customer specifically identified the Bitget-to-Kraken USDC transfer as the event preceding the restriction.
The complaint remains a customer allegation. There is no public evidence showing what Kraken’s internal systems flagged, whether Bitget itself was relevant to the review, which blockchain network carried the USDC, or whether the transaction interacted with an address carrying an elevated blockchain-risk score.
However, the specific transaction path makes the case more useful than a generic claim that an exchange froze an account.
Recent cases at other platforms have shown how a single destination or counterparty can become the apparent trigger for a much broader restriction. One Bybit customer, for example, said a $21 transfer to a previously accepted address triggered restrictions on roughly $25,000 after the destination was later classified as high-risk.
Kraken’s own documentation confirms that crypto transactions can prompt additional scrutiny.
The exchange says it may restrict account services for security and regulatory reasons, including suspected malicious activity and transactions involving wallets associated with prohibited, illegal or scam-related activity.
For customers covered by Kraken’s European terms, the exchange also reserves the right to verify the source of crypto assets added to an account and can freeze or block assets if it suspects a violation of its agreement or applicable law.
Separately, Kraken’s source-of-funds guidance says customers may be asked to provide records tracing crypto received from another exchange, including an external exchange statement identifying the account holder, wallet address and balance.
Exchange-to-exchange transfers can also carry additional regulatory data requirements in some jurisdictions.
For EU and UK customers, Kraken says Travel Rule requirements mean it may need to identify the virtual asset service provider on the other side of a transfer and confirm ownership information. A user sending crypto from another exchange may therefore be asked to identify that exchange and establish that the originating account belongs to them.
There is no evidence that the Sept. 2 Bitget transfer was held for a Travel Rule issue, and the customer’s jurisdiction has not been established publicly. The regulatory framework therefore provides possible mechanisms for a review, not an explanation for this individual restriction.
The complaint also arrives as other Kraken customers report extended manual reviews.
On Sept. 15, a separate user posted that a USDT withdrawal was being held for manual review under ticket #22619442 and asked Kraken’s support team to escalate it to the specialist handling the case.
Another customer said on Sept. 11 that their recent withdrawal had remained under internal review for seven days while their account was restricted. That user said the funds were legitimate and offered to provide source-of-funds documentation.
On Sept. 14, another Kraken customer said an account had been restricted since early the previous week despite proactively submitting identity documents. Kraken’s public support account replied that the case had been escalated and warned that resolution could still take several business days.
Those reports resemble broader extended withdrawal restrictions recently reported at Binance Kazakhstan, where a customer said source-of-funds documents had already been provided while the security review continued.
Similar operational tension is appearing across other platforms. Coinbase users recently reported withdrawal locks followed by identity-verification problems, while a cluster of Skrill customers described account restrictions and delayed reviews beginning around the same weekend.
None of those cases establishes a shared cause with Kraken.
They do show why it is important to distinguish a conventional technical outage from an account-specific risk review.
Kraken’s public status page has reported several recent blockchain-specific funding incidents, including delays affecting particular networks. But there is no published platform-wide USDC or USDT incident that explains the current account-restriction complaints as a general stablecoin outage.
Kraken separately restricted withdrawal access to several assets for UAE customers this month as part of a scheduled regulatory delisting process. That loss of withdrawal access was publicly announced and policy-driven, making it fundamentally different from an unexplained customer-specific restriction.
The Bitget Connection Is a Lead, Not Yet the Explanation
The most interesting detail in this case is Bitget.
Not because there is evidence Bitget did anything wrong. There isn’t.
It matters because the transfer gives investigators a precise starting point.
If the customer had simply said Kraken restricted the account one day, there would be dozens of possible explanations: login security, identity verification, source of funds, account behavior, sanctions screening, a chargeback or an unusual withdrawal.
Here, the user says the restriction happened immediately after an exchange-to-exchange USDC deposit.
That creates several testable possibilities.
The first is counterparty risk. Blockchain analytics systems continuously reassess addresses based on links to hacks, scams, sanctions, illicit services and other suspicious clusters. An address or transaction path does not need to be directly criminal to attract additional screening if its on-chain history intersects with elevated-risk infrastructure.
The second is ownership verification. A regulated exchange may need to establish that funds arriving from another trading platform actually came from an account controlled by the same customer.
The third is source-of-funds review. Kraken’s own documentation explicitly contemplates asking for an external exchange statement when cryptocurrency originates elsewhere.
And for customers subject to Travel Rule requirements, the exchange may also need information about the VASP on the other side of the transaction.
The problem is that all four possibilities can look identical from the customer’s side.
The balance becomes inaccessible. Support says the case is under review. A specialist team handles it. The customer receives very little information because compliance teams generally do not reveal detailed risk models while an investigation is open.
That dynamic is increasingly visible across centralized crypto platforms. Recent week-long withdrawal and account holds have shown how quickly a risk-control process becomes a customer-service problem once the user has no clear idea what is being reviewed or how long it will take.
This is where access risk starts to matter almost as much as custody risk.
A customer can see USDC sitting inside an account and still have effectively no liquidity if deposits, withdrawals or other account actions remain restricted.
That is one reason some crypto users prefer self-custodial blockchain infrastructure. It reduces the ability of an intermediary to stop a transfer after the user controls the asset, although it replaces platform risk with personal responsibility for keys, fraud and transaction mistakes.
The strongest investigation now would compare the Sept. 2 Bitget-to-Kraken transfer with the other recent Kraken cases.
The useful fields are straightforward: stablecoin, blockchain network, originating exchange, sending address, receiving address, transaction timestamp, account jurisdiction and any Travel Rule or source-of-funds questions received afterward.
If multiple customers entered prolonged review after transfers through the same route, network, Bitget address cluster or blockchain-risk provider, the pattern would become much more significant.
If the cases involve unrelated assets, networks and counterparties, the current cluster may simply reflect the normal visibility of individual Kraken compliance reviews rather than a new common trigger.
For now, the Bitget connection should therefore be treated as a lead rather than a conclusion.
What makes the Sept. 15 complaint worth following is that the user has identified a precise moment when an established Kraken account allegedly went from normal operation to a 13-day restriction.
The next piece of evidence is whether Kraken eventually explains what was unusual about that USDC transfer — or whether the customer simply regains access without ever learning why it triggered the review.
Michael Lebowitz is a financial markets analyst and digital finance writer specializing in cryptocurrencies, blockchain ecosystems, prediction markets, and emerging fintech platforms. He began his career as a forex and equities trader, developing a deep understanding of market dynamics, risk cycles, and capital flows across traditional financial markets.
In 2013, Michael transitioned his focus to cryptocurrencies, recognizing early the structural similarities—and critical differences—between legacy markets and blockchain-based financial systems. Since then, his work has concentrated on crypto-native market behavior, including memecoin cycles, on-chain activity, liquidity mechanics, and the role of prediction markets in pricing political, economic, and technological outcomes.
Alongside digital assets, Michael continues to follow developments in online trading and financial technology, particularly where traditional market infrastructure intersects with decentralized systems. His analysis emphasizes incentive design, trader psychology, and market structure rather than short-term price action, helping readers better understand how speculative narratives form, evolve, and unwind in fast-moving crypto markets.