Kraken’s UK presence is a good example of how crypto regulation actually works in practice: not as one broad approval, but as a patchwork of registrations, permissions, services, and limits.
The exchange operates in the UK through several FCA-regulated entities. Payward Limited is listed as a registered cryptoasset business for anti-money laundering purposes. Payward Services Limited holds an Electronic Money Institution license. Crypto Facilities Limited is FCA-authorized as an investment firm tied to derivatives activity.
That is a serious regulatory footprint, but it needs precise language.
This is not the same as saying Kraken has one sweeping UK “crypto custody license” that covers every activity under a future regime. The UK’s broader licensing framework for crypto custody and trading is still moving toward implementation, with applications expected to open on September 30, 2026, and the regime scheduled to take effect on October 25, 2027.
For users and institutions, that distinction matters.
TL;DR
- Kraken operates in the UK through multiple FCA-regulated entities.
- Its current status includes AML cryptoasset registration, EMI permissions, and derivatives-related authorization.
- This should not be described as a broad future-regime custody license.
Crypto Regulation Is Not One Box
Crypto companies often want a simple regulatory headline.
“Licensed.” “Approved.” “Registered.” “Regulated.”
Those words sound reassuring, but they can hide important differences.
A cryptoasset AML registration is not the same as a custody license. An EMI license is not the same as authorization to run a crypto exchange . A derivatives permission is not the same as approval for all spot trading and custody services.
Kraken’s UK structure shows why that nuance matters.
The company has built a regulated presence through multiple entities, each covering different activities. That can make the business more credible to users and institutions, but it does not mean every product is protected in the same way.
For example, FCA cryptoasset registration is primarily about anti-money laundering and counter-terrorist financing compliance. It does not mean customers receive the same protections they might expect from bank deposits or traditional investment products.
That is not a criticism of Kraken. It is simply how the UK framework works.
The UK Is Still Building Its Full Crypto Regime
The timing is important.
The UK has been gradually moving toward a fuller crypto regulatory structure, especially around custody, trading venues, stablecoins , and market conduct. But that future regime is not the same as the current registration system.
Applications for the new framework are expected to open before the regime fully takes effect, giving firms time to prepare. Once implemented, the rules should create clearer obligations for crypto custody and trading services.
Until then, companies operate through existing categories: AML registration, e-money permissions, investment firm authorization, and other regulated-activity permissions where relevant.
That creates a messy middle period.
Some firms are regulated for certain functions, but not in the broad way consumers might assume. Others may be registered for AML but not authorized for investment services. The wording matters because users can misunderstand what protections they have.
Why Kraken’s Footprint Still Matters
Even with those caveats, Kraken’s UK setup is significant.
Maintaining multiple regulated entities is not easy. It requires compliance teams, reporting, policies, audits, governance, and ongoing engagement with regulators . For institutional clients, that matters because they want counterparties that can operate inside existing legal frameworks.
Kraken has also been one of the longer-standing exchanges in the market, and its UK footprint gives it a base to compete as the country’s rules mature.
That could become more important once the new regime arrives.
Firms that already have regulated operations, compliance infrastructure, and relationships with the FCA may be better positioned than offshore platforms trying to enter late. The UK wants crypto activity to move into a more supervised environment, and established players have an incentive to meet that demand.
Users Still Need To Understand The Limits
The most important point for users is protection.
A regulatory registration does not automatically mean crypto assets are covered by the Financial Services Compensation Scheme. It does not remove platform insolvency risk. It does not make volatile assets safe. It does not guarantee every product offered by an exchange carries the same regulatory status.
That is why careful wording is not just legal pedantry.
It affects user expectations.
If a platform says it is registered or regulated, users need to ask: for what activity, under which entity, and with what protections?
Kraken’s UK structure gives a useful case study because it includes several pieces of the regulatory puzzle, but not a single all-purpose label.
The Direction Is Still Toward More Formal Oversight
The broader takeaway is that UK crypto regulation is moving from registration toward fuller licensing.
That should make the market clearer over time. Firms will know what permissions they need. Users will have a better sense of protections. Regulators will have more direct oversight of custody and trading activity.
But during the transition, precise language is essential.
Kraken’s regulated UK entities show that major exchanges are preparing for a more formal era of crypto oversight. The company has built meaningful regulatory infrastructure, and that gives it a stronger position as the UK framework develops.
Still, the correct read is not “Kraken has a broad UK custody license.”
The better read is that Kraken already operates through multiple FCA-regulated entities, while the UK’s more comprehensive crypto regime is still on the way.
That distinction may sound small, but in crypto regulation, it is everything.
This article is based on FCA register information relating to Kraken-linked entities .
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released in disclosures at primary source documentation .
