There is a moment in almost every conversation I have with a client who holds cryptocurrency within a business structure — a moment when they say something like: "But we're not doing anything wrong. It's a small part of our overall activity. Why does it generate such disproportionate attention?"
The question is entirely reasonable. And the answer requires understanding not what banks think about cryptocurrency in principle, but how they are trained to approach it in practice — and why even a modest crypto presence can change the entire character of a banking relationship.
Every business that operates internationally carries some form of complexity. Multiple jurisdictions, diverse counterparties, holding structures, intercompany flows — banks encounter all of this routinely and have developed ways of reading it. Complexity, on its own, is not a red flag.
Cryptocurrency is treated differently. Not because banks have made a considered judgement that it is inherently more dangerous than other financial activity, but because their compliance frameworks were built for a world in which it did not exist — and have been retrofitted, unevenly, to accommodate it. The result is a set of procedures that are simultaneously over-broad and under-informed.
A bank's compliance officer reviewing a corporate structure with a cryptocurrency component is not, in most cases, a specialist. They are working from a checklist. That checklist asks certain questions. And when those questions cannot be answered clearly from the documentation in front of them, the checklist produces a result that is adverse — regardless of what the underlying reality looks like.
Understanding the three questions that checklist always contains is, in my experience, the most useful starting point for any client who wants to maintain a banking relationship while operating with crypto.
Source of funds is the foundational question in any banking compliance review. For conventional financial flows, the answer is usually traceable: revenue from a contract, proceeds from a transaction, a loan from a documented lender. The paper trail may be complex, but it exists and can be followed.
For cryptocurrency, this question becomes considerably more demanding — and considerably more consequential.
A bank needs to understand not only that a client holds digital assets, but where those assets originated. Were they acquired on a regulated exchange with documented KYC procedures? Were they received as payment from a counterparty — and if so, who was that counterparty, and what is known about the source of their funds? Were they mined, and if so, under what framework? Were they received as consideration in a transaction, and is that transaction properly documented?
The blockchain is public. Everything that has ever happened to a given wallet address is technically visible to anyone with the right analytical tool. Banks and their compliance vendors use those tools. They are looking for connections — however indirect — to addresses associated with sanctioned entities, darknet markets, mixing services, or other high-risk activity. A connection does not need to be direct. It does not need to be intentional. It needs to exist.
This is the feature of cryptocurrency compliance that most clients find most surprising: that funds they received legitimately, from a counterparty they know well and have worked with for years, may carry a history they know nothing about. And that history — invisible to them, visible to the bank's analytical tools — can produce a compliance concern that no amount of explanation about their own behaviour can fully resolve.
The practical implication is this: the source of cryptocurrency must be documented with the same rigour as the source of any other funds. Not because the law always requires it in explicit terms, but because the bank's compliance process will ask the question — and an answer that consists of "we received it from a counterparty" is not, by itself, sufficient.
Source of funds tells the bank where the crypto came from. This second question asks something different: what is it doing here?
Banks are looking for a coherent business rationale for the presence of cryptocurrency within a corporate structure. Not a philosophical position on digital assets, and not a technical explanation of how blockchains work. A business rationale: why this company, in this structure, holds or transacts in cryptocurrency — and how that activity connects to the business model that the rest of the corporate documentation describes.
When that rationale is absent — or when it exists in the owner's mind but has never been articulated in any document the bank can read — the bank's default interpretation is unfavourable. The cryptocurrency does not fit the picture the bank has formed of the client. And when something does not fit the picture, compliance instinct is to treat it as a risk indicator rather than an oversight.
I have encountered this situation repeatedly. A client with a conventional trading business has, over time, begun accepting cryptocurrency as payment from a subset of counterparties. The business rationale is entirely sound: those counterparties prefer it, the client can convert promptly, and the volumes are not large. But no document in the corporate file explains this. The bank sees a conventional trading business with unexplained cryptocurrency flows. The result is a stream of information requests that eventually exhausts the relationship.
The solution is not to eliminate the cryptocurrency. The solution is to embed it — to ensure that the corporate documentation, the operational policies, and the banking narrative describe the role of cryptocurrency within the business with the same clarity as any other operational element. A paragraph in the right place, supported by the right documentation, changes what the bank sees entirely.
This is the question that most clients do not anticipate — because it requires thinking about the structure not from the inside, but from the bank's position.
A bank maintaining a relationship with a corporate client is, from its own perspective, taking on a risk. It has assessed that risk against the client's profile and decided it is acceptable. But that assessment is based on what it knew about the client at the time. When a new element appears within the same corporate perimeter — an element with different risk characteristics than what was originally presented — the bank's risk assessment changes. And the bank did not agree to that change.
Cryptocurrency, in the eyes of most banks, carries a higher compliance risk profile than conventional financial activity. This is true regardless of how the specific client uses it and regardless of whether it is, in substance, any more complex or problematic than other aspects of their business. It is true because that is how banks have categorised it, and their internal policies are built around that categorisation.
What this means in practice is that a cryptocurrency layer which sits inside the same corporate entity as the banking relationships the client values most creates a risk contamination problem. The bank looks at the whole entity. If part of that entity carries elevated risk, the entire entity carries elevated risk.
The structural answer to this is separation. Not concealment — there is no question of hiding anything from anyone. But deliberate architectural separation: ensuring that cryptocurrency activity is held within a legal entity whose risk profile is appropriate for it, and that this entity is kept at a defined distance from the legal entities whose banking relationships are most sensitive.
This separation must be real, not cosmetic. It must be reflected in the ownership structure, in the flow of funds, in the governance documents, and in the documentation presented to banks. A separate wallet is not separation. A separate company with a separate account and a clearly defined operational boundary — that is separation.
When a client asks me why this matters, I put it this way: banks do not close the door on cryptocurrency. They close the door on structures they cannot read. If the structure says clearly — here is the mainstream business, here is the crypto activity, here is the boundary between them, and here is why that boundary holds — the bank can make an informed decision. It may still decline. But it can make the decision on the basis of what is actually there, rather than on the basis of what it suspects might be there.
Source. Role. Separation. Each question asks something different, but all three are asking the same underlying question in different forms: can we read this?
Can we trace where the cryptocurrency came from and be satisfied that its history is clean? Can we understand why it is present in this structure and how it fits the stated business model? Can we see that it has been thoughtfully separated from the parts of the structure whose risk we have already assessed and accepted?
A structure that answers all three questions — not in a legal brief, but in its documentation, its architecture, and its operational logic — does not eliminate the complexity of having crypto inside a corporate group. But it changes what the bank sees. And what the bank sees determines what the bank does.
In my experience, most of the problems that international businesses encounter with banks over cryptocurrency are not problems of substance. The business is legitimate. The activity is legal. The volumes are often modest relative to the overall group. The problem is that no one ever sat down and thought about how the structure reads to someone who approaches it cold — and built the documentation and the architecture to match that reading.
That is a solvable problem. And unlike many of the situations I am asked to help with, it is far easier to solve in advance than to repair after the relationship has already broken down.
Vladimir Shuvalov is a legal and tax adviser with thirty years of experience in international corporate structuring, banking acceptability, and cryptocurrency architecture.
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