The question of whether to include cryptocurrency in a corporate structure has, for most businesses I work with, already been answered. The crypto is there. It arrived incrementally — a client who preferred to pay in stablecoins, a treasury decision to hold a portion of working capital in digital assets, an investment that happened to be denominated in a token. Each decision was taken individually, for sound commercial reasons. Nobody made a decision to build a crypto layer. The crypto layer built itself.
The question that follows — the one that most businesses have not yet answered — is where does the crypto sit, and what does that position mean for everything else?
Banks do not close accounts because a client holds cryptocurrency. They close accounts — or restrict relationships, or apply enhanced due diligence that makes the relationship unworkable — because they cannot read the structure. And a structure in which cryptocurrency activity is housed inside the same legal entity as the banking relationships the business depends on is, from a compliance perspective, a structure that cannot be read cleanly.
The mechanism is worth understanding precisely, because clients often believe the problem is the crypto itself, and that the solution is to reduce the crypto exposure or explain it more thoroughly. Neither is true in most cases. The problem is the position of the crypto within the structure — and the solution is architectural.
When a bank assesses a corporate client, it assesses the entity. Not the parts it approves of and the parts it does not — the entity as a whole. A legal entity that generates conventional trade revenues, holds cash in conventional accounts, and also holds a portfolio of digital assets and processes periodic cryptocurrency receipts is, from the bank's compliance framework, a single risk object. The risk profile of the conventional business and the risk profile of the crypto activity blend into a single assessment. That assessment reflects the most elevated risk element present.
This is the contamination logic. It is not a judgement about the legitimacy of the crypto activity. It is a structural reality: things held inside the same legal perimeter are assessed together. The only way to change what the bank sees is to change what is inside the perimeter it is looking at.
There is an obvious question that follows from this — if the logic is clear, why do most structures not have the separation built in?
The answer is the same as the answer to most structural gaps in international businesses: because the separation was never the problem being solved at the moment the structure was being built. The crypto arrived as a series of individual decisions, each of which was taken in response to a specific commercial need. The separation would have required someone to step back and look at the whole construction — to ask not "how do we process this payment?" but "where should crypto activity live within this group?" That question requires a view of the whole structure, and that view is rarely available when the business is moving.
The result is a structure that reflects the history of decisions rather than a considered architecture. The crypto sits where it landed, not where it belongs. And the cost of that — in banking friction, in compliance reviews, in relationships that become harder to maintain over time — accumulates quietly until someone looks at the whole picture.
The term "separation" is used loosely in discussions of corporate structure, and its loose use has caused genuine harm. I have reviewed structures described as "separated" — where the cryptocurrency activity had been assigned, nominally, to a different function within the same entity, or where a different wallet had been opened, or where a note in an internal document designated certain activities as distinct. None of these is separation.
Genuine separation is legal, operational, and documentary. It has three components.
Legal separation means that the cryptocurrency activity is held in a distinct legal entity — a company with its own registration, its own directorship, its own bank or custodial account, its own governance structure. Not a wallet. Not a function. A legal person. The entity that holds the crypto is not the entity that maintains the banking relationships the business depends on. They may be related through ownership. They should not be operationally entangled.
Operational separation means that the flows between the crypto entity and the main operating entity are deliberate and documented. Money moves between them for specific reasons, at specific times, under specific conditions that are written down. The crypto entity does not share personnel with the main entity in ways that create ambiguity about which entity is conducting which activity. The decision-making authority within the crypto entity is clearly defined and exercised separately from the decision-making of the main business.
Documentary separation means that the structure, as described to a bank, reflects the separation that actually exists. The ownership chart shows two distinct entities with their own functions. The intercompany agreements describe the relationship between them. The treasury policy describes how digital assets are held and how they are liquidated or transferred. A compliance officer reviewing the documentation can see, without additional explanation, where the crypto sits and why it does not affect the risk profile of the entity they are actually banking.
Each of these components is necessary. None is sufficient on its own. A legal entity without operational separation is a shell. Operational separation without documentation is invisible to a bank. Documentation without genuine legal and operational separation is, when examined closely, a misrepresentation. The three components work together or they do not work at all.
Legal separation does not require the crypto entity to be owned by a different person. In most cases, it is owned by the same individual or holding structure that owns the main operating business. What matters is not who owns the entity, but what the entity does and how that is described.
A holding structure that owns a conventional operating business and a separately registered crypto entity — each with its own management, its own accounts, its own documented function — presents a coherent picture to a bank reviewing either entity. The bank sees a group with two distinct risk profiles held by the same beneficial owner. It can assess each entity on its own terms. It can maintain a relationship with the operating entity without being required to accept the risk profile of the crypto entity as part of that relationship.
This is materially different from a structure in which the crypto activity and the conventional activity are held in the same entity. In the former case, the bank has a clear object of assessment. In the latter, it does not — and a bank that cannot clearly assess what it is looking at will resolve its uncertainty conservatively.
A separate entity for cryptocurrency activity, properly governed, also signals something to the compliance officer that matters: that the owner understands the risk profile of digital assets and has made a considered decision about how to manage it. Compliance officers are looking for evidence of governance — for signs that the people behind the structure have thought about it. A separate entity, properly documented, is that evidence.
I am asked, sometimes, why this separation matters now — why a structure that has operated without difficulty for several years requires architectural attention.
The first part of the answer is that the banking environment is not static. A structure that passed a KYC review three years ago is not automatically acceptable today. The criteria have changed. The scrutiny has increased. What was readable in a more permissive environment may not be readable in the current one.
The second part is that the moment at which separation becomes urgent is almost always the moment at which it is most difficult to achieve. When a banking review is underway — when an information request has arrived, when an account is under restriction, when a new banking relationship is being sought because the existing one has ended — the options narrow. Restructuring during an active banking difficulty is possible, but it is slower, more expensive, and viewed with greater suspicion than restructuring conducted as deliberate governance before any difficulty has arisen.
The question of when to build the separation is answered the same way as the question of when to prepare a structure for due diligence: before someone else makes it necessary.
There is a direct answer to what changes when the separation is built correctly.
A bank looking at a properly separated structure sees two things. First, it sees a conventional operating business with conventional financial flows, held in a legal entity whose documentation describes a coherent business model with no unexplained cryptocurrency elements. The KYC review of that entity produces a clean picture. Second, it sees, separately, a crypto entity whose ownership connects to the same beneficial owner — and which has its own documentation describing exactly what it does, what digital assets it holds, and how it relates to the conventional business.
The bank can now make a decision. It may decide to bank the operating entity and decline the crypto entity. It may decide to bank both, having assessed each on its own terms. What it cannot do — and what, without the separation, it had no choice but to do — is treat the entire group as a single indecipherable risk object and respond to that indecipherability with caution.
The choice moves back to the bank. And a bank that has a clear picture of what it is assessing makes better decisions for the client than one that is operating in the dark.
Separation is an architectural answer to a structural problem. It is not a compliance solution, a regulatory authorisation, or a substitute for the source-of-funds documentation that banks will always require for cryptocurrency activity.
A crypto entity that is cleanly separated from the main operating business still needs to be able to answer the three questions that every bank asks about cryptocurrency: where did the funds originate, what is the business rationale for holding them, and what framework governs how they are held and transacted. Separation makes those questions easier to answer — because the answers apply to a single, clearly defined entity rather than to a commingled structure. But it does not answer them.
The architectural work and the documentary work are different tasks. The separation creates the structure within which the documentation can be placed. The documentation gives the structure its legibility. Neither works without the other.
Vladimir Shuvalov works with international businesses and private clients on corporate structure, banking acceptability, and cryptocurrency architecture from Nicosia, Cyprus.
Thinking Globally — thinking-globally.com
Thinking Globally Consulting Limited
Registered in England & Wales · Company No. 17138834
128 City Road, London EC1V 2NX, United Kingdom
© 2026 Thinking Globally Consulting Limited · All rights reserved