There is a moment in almost every conversation I have with a client who holds cryptocurrency somewhere inside a business structure when they look at me and say, with genuine frustration: "But we are not doing anything wrong. It is a very small part of what we do. Why does it attract so much attention?"
It is a fair question. I have heard some version of it many times.
The answer begins with a misunderstanding that is very common among otherwise sophisticated business owners. They assume the bank is looking at cryptocurrency in the same way they are: as one element of a wider commercial picture, to be weighed in proportion to its actual size and role. In practice, that is not how banks tend to read it.
A small crypto element can alter the entire tone of a banking relationship, not necessarily because the bank has formed a deep view about the substance of what the client is doing, but because crypto enters a system of compliance that was not built with it in mind and still does not handle it with much confidence. What the client sees as one modest operational feature, the bank often sees as a category-shifting fact.
In my experience, there are three questions that appear again and again whenever a bank is trying to decide how comfortable it is with cryptocurrency inside a corporate structure. The questions sound simple. But a great deal depends on whether the structure itself answers them clearly.
Every banking relationship begins with source of funds. That is true everywhere. With conventional financial activity, the answer is usually familiar: payment under a contract, proceeds of trade, a loan from an identified lender, a dividend, a sale. The paper trail may be lengthy, but it is recognisable.
With cryptocurrency, the same question becomes more difficult very quickly.
The bank does not only want to know that digital assets are present. It wants to know where they came from in a way that can survive scrutiny. Were they bought on a regulated exchange with proper KYC? Were they received from a counterparty, and if so, who was that counterparty and what comfort exists around the origin of those funds? Were they mined? Were they part of a documented transaction? Can the route from acquisition to present holding actually be shown, rather than merely described?
This is where many clients are caught off guard. They know how they received the crypto. They know why they received it. They know the commercial context. But they have never really stopped to consider that the asset may carry a history beyond their own involvement with it.
That history matters because the blockchain is public, and banks — or the compliance providers they rely on — have tools that read that history in ways the ordinary client usually does not. They are not just looking at what the client did. They are looking for what touched the asset before it arrived: sanctioned wallets, darknet exposure, mixers, high-risk services, problematic counterparties, indirect links that the client neither intended nor even knew existed.
That is one of the harshest features of crypto compliance. A client can receive funds in good faith, from a known counterparty, in the context of a perfectly legitimate business relationship, and still discover that the asset carries a past the client cannot explain and the bank cannot ignore.
For that reason, I do not treat source of crypto as a side issue. It has to be documented with the same seriousness as any other source of funds, and often with more. Not because every statute spells this out elegantly, but because the bank will ask the question whether the client is ready for it or not. And "we received it from someone we know" is almost never enough.
Once the bank has asked where the crypto came from, it moves very quickly to a second question: why does this structure contain it?
This is not a philosophical question. The bank is not asking whether the owner believes in digital assets, whether blockchain is important, or whether crypto is the future. It is asking something much more ordinary and much more important: what role does this activity play in this business?
That question is often harder for clients than the first one.
I have seen many situations in which the commercial logic was perfectly sound but had never been stated anywhere in a form the bank could actually read. A trading business starts accepting crypto from a handful of counterparties because that is how those counterparties prefer to pay. A group keeps part of its liquidity in digital assets for operational reasons. A business working in adjacent sectors needs occasional interaction with crypto infrastructure. None of this is inherently suspicious. But if the role of crypto exists only in the owner's head and nowhere in the structure's documentation, the bank is left looking at something that appears unexplained.
And unexplained things do not remain neutral for long inside a compliance review.
This is the point at which a perfectly ordinary business can begin to look strange to its bank. The bank thinks it understands the client: a trading company, a consulting group, a holding structure, an operating business with identifiable flows. Then crypto appears inside that picture without a visible place assigned to it. The business may still be entirely legitimate. But the picture no longer reads cleanly.
I have seen relationships become steadily more difficult for exactly this reason. Not because the crypto activity was large. Not because it was unlawful. Not because anyone had anything to hide. But because no one had ever taken the time to embed it properly into the narrative of the structure.
That is usually the real answer. The solution is not necessarily to remove the crypto. Often the solution is to make it legible: to ensure that the corporate documents, operating policies, and supporting explanations describe the role of cryptocurrency with the same clarity as any other part of the business. Sometimes a short paragraph in the right place does more than ten defensive explanations after the fact.
This is the question many clients do not think about until the bank has already started asking uncomfortable things.
From the client's point of view, the structure is often one business with several moving parts. From the bank's point of view, that is not how risk works. The bank has agreed to a relationship on the basis of a particular picture of the client. If a new layer appears inside the same perimeter and that layer carries a different risk profile, the bank does not experience that as a minor operational detail. It experiences it as a change in the relationship it thought it had accepted.
That is why separation matters so much.
Whether one agrees with the banking industry's view of crypto or not is almost irrelevant here. Most banks categorise cryptocurrency as carrying a higher compliance risk profile than ordinary commercial activity. That remains true even where the actual use case is limited, sensible, and legally clean. The category itself drives the response.
If the crypto activity sits inside the same legal entity as the banking relationships the client most values, the bank often stops distinguishing between parts of the picture. It sees one entity. If one part of that entity carries elevated risk, then, from the bank's perspective, the whole entity has changed.
The structural answer is not concealment. It is not cosmetic rearrangement. And it certainly is not the childish hope that using a different wallet will somehow solve the problem.
The answer is real separation.
That means crypto activity is held in the legal entity that is appropriate for it. It means there is a genuine operational boundary between that entity and the parts of the group whose banking relationships are more sensitive and more important to protect. It means the separation is visible in ownership, governance, money flows, internal documents, and the material presented to the bank. A separate wallet proves almost nothing. A separate company, with a defined role and a real boundary around it, says something the bank can actually read.
When clients ask me why this matters, I usually answer very simply. Banks do not close the door because the word "crypto" appears somewhere in a structure. They close the door when the structure stops making sense to them. If the architecture says clearly: this is the mainstream business, this is the crypto activity, this is the boundary between them, and this is why that boundary is real, then the bank at least has something it can assess rationally.
It may still decide the answer is no. But that is a very different situation from a bank declining because it cannot tell what it is looking at.
Source. Role. Separation.
On the surface, these are three different questions. In practice, they are all versions of the same one: can this structure be read clearly by somebody who did not build it and does not know its history?
Can the bank understand where the crypto came from and whether its past is acceptable? Can it understand why the crypto is present in this business at all? Can it see that the crypto element has been placed at a sensible distance from the parts of the group whose banking relationships are most exposed?
When a structure answers those questions in its documentation, its architecture, and its day-to-day operational logic, the existence of crypto does not suddenly become simple. But the picture changes. And in banking, what the picture looks like often matters just as much as the underlying reality.
In my experience, many of the banking problems businesses encounter around crypto are not caused by bad conduct, and not even by especially risky conduct. They arise because nobody ever paused long enough to ask the most important outside question: if a bank looks at this cold, what exactly will it think it is seeing?
That question is uncomfortable, but it is solvable. And it is much easier to solve before the relationship starts to deteriorate than after trust has already begun to disappear.
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