Do You Actually Need a VASP Registration? A Plain-Language Test for Founders

One of the most common questions we hear from crypto founders is also one of the most important, and the most misunderstood. Do you actually need to register as a virtual asset service provider, or are you outside the regime? Getting this wrong in either direction is costly, so it pays to apply a clear test before you build your structure around an assumption.

The starting point is what you do, not what you call yourself. The regime is built around providing virtual asset services to other people. If your business exchanges crypto for fiat, swaps one asset for another, transfers assets for clients, holds or safekeeps assets on their behalf, or runs a trading platform, you are very likely within scope. The label on your website does not change that analysis.

Holding crypto purely for yourself is a different matter. A person or company that buys and sells its own assets, without offering a service to others, generally sits outside the registration obligation. The dividing line is the presence of customers. Once you are doing something with virtual assets on behalf of other people, the obligation tends to follow.

Edge cases are where care is needed. Mining, for example, may not trigger registration on its own, but a mining operation that also exchanges or holds assets for others can find itself inside the regime after all. Models that combine several functions, or that evolve over time, are exactly the ones that benefit from a proper classification before launch rather than after a problem.

The consequence of getting it wrong is not trivial. Operating without registration where it is required can lead to fines, forced closure, frozen accounts and personal exposure for directors. On the other side, assuming you need a full registration when your model is genuinely out of scope wastes time and money you could spend building. Accuracy, not caution for its own sake, is the goal.

Consider a common example. A software company builds a product with no crypto features, clearly outside the regime, and then adds a simple option for users to swap one token for another inside the app. That single feature can move the whole business inside scope, because it is now providing an exchange service to others. Founders rarely notice the moment a product crosses the line, because it happens through a feature decision rather than a strategic one. That is exactly why classification should be revisited whenever the product changes, not just at launch. A model that was genuinely out of scope last year can be squarely inside it after a roadmap update, and discovering that through a regulator or a bank is the hard and expensive way to learn it. A quick review at each major release is far cheaper than a retrospective fix.

We assess a business model against the framework and give a straight answer on whether registration applies, before you commit to a structure. If you are unsure where your project sits, let us look at what you actually do and confirm your position, so you can plan with confidence rather than guesswork.