Category 2 Token Issuance in Dubai: What Issuers Need to Know

If you are planning a token launch in Dubai, one of the most important questions is not just whether the token is legal. It is whether the token falls into Category 2 under VARA’s issuance framework, and if it does, what that actually means for launch, distribution, whitepapers, and compliance.

A lot of founders hear “Category 2” and assume it means:

• lightly regulated,
• no licence,
• no real approval burden,
• or effectively “free to launch.”

That is not the right reading.

Under the current VA Issuance Rulebook, Category 2 covers any Virtual Asset issuance that is not:

• a Category 1 VA Issuance, and
• not an Exempt VA. The rulebook also says that no VARA Licence is required for Category 2 issuance, provided that all placement or distribution is carried out through or by a Licensed Distributor. If that condition is satisfied, the issuer does not need prior approval from VARA for the issuance.

That sounds lighter than Category 1, and it is. But it is not the same thing as unregulated token issuance. In practice, Category 2 means the issuer is still inside a rulebook-driven disclosure and distribution framework, and the launch must be structured around a Licensed Distributor that takes on real validation responsibilities.

So if you are searching for:

• Category 2 token issuance Dubai
• VARA Category 2 token
• Can I issue a token in Dubai without a VARA licence
• Licensed Distributor VARA
• Dubai token issuance rules
• VARA whitepaper requirements
• Category 2 VA issuance

then this guide is built for you.

1) The starting point: token issuance in Dubai is still regulated

Before getting into Category 2 specifically, it is important to understand the baseline rule. The VA Issuance Rulebook applies to entities in the Emirate that issue Virtual Assets in the course of business, and VARA’s issuance framework categorizes such issuances as Category 1, Category 2, or Exempt VAs.

That means there is no serious legal analysis in Dubai that begins with:

“It’s just a token, so maybe issuance isn’t really regulated.”

Issuance is already inside the framework. The real question is which lane the token sits in. Category 2 is one of those lanes, but it is still a lane inside the rulebook.

This is important because some founders use the phrase “utility token” as if it were the legal answer. Under the current rulebook, that is not enough. The framework turns first on whether the token is:

• Category 1,
• Category 2,
• or Exempt,
  and the rulebook says categorization depends on the token’s characteristics and the underlying business model.

So before asking how to launch, you need to answer the classification question properly.

2) What Category 2 means under VARA

The rulebook’s Category 2 VA Issuance section is the core starting point. It says Category 2 is the issuance of any Virtual Asset that does not constitute:

• Category 1 VA Issuance, or
• an Exempt VA. It then states that entities in the Emirate may only issue Category 2 VAs provided that all placement and distribution is carried out by a Licensed Distributor. If that condition is met, the issuer does not need prior approval from VARA.

That gives you the practical core of Category 2:

No issuer licence and no prior approval, but only if the distribution model is built around a Licensed Distributor.

That is a very different answer from:

• “no regulation,”
  or
• “self-launch freely.”

In other words, Category 2 is lighter than Category 1, but it is still a structured regulatory pathway. The key compliance burden moves away from issuer licensing and toward:

• classification,
• disclosure,
• and especially distribution through or by a Licensed Distributor.

3) Why Category 2 is often misunderstood

There are three main reasons founders misread Category 2.

First, they focus only on the part that says no VARA Licence required and miss the condition attached to it. That condition is not minor. The issuer only gets the lighter path if all placement and distribution is carried out through or by a Licensed Distributor.

Second, they treat Category 2 as though the issuer can launch however it wants, then regularize later. But the rulebook structure works the other way round: the distribution architecture must already fit the Licensed Distributor model.

Third, they assume that because Category 2 is not Category 1, the whitepaper and risk-disclosure burden must be minimal. In fact, the general issuance rule says that all entities in the Emirate issuing a Virtual Asset must publish both a Whitepaper and a Risk Disclosure Statement, except issuers of Exempt VAs. Category 2 is not Exempt, so those disclosure obligations still apply.

This is why Category 2 should be understood as:

• a lighter issuer-approval route,
  not
• a light overall compliance route.

4) The Licensed Distributor is the center of the Category 2 model

If there is one concept issuers need to understand in Category 2, it is the Licensed Distributor.

The rulebook says that all placement and distribution for Category 2 must be carried out through or by a Licensed Distributor. It also says Licensed Distributors providing Licensed Distribution Services to Category 2 issuers assume the responsibility for assuring and validating that the issuer complies with the VA Issuance Rulebook.

That means the distributor is not just:

• a placement agent,
• a sales channel,
• or a marketing partner.

It is a regulated gatekeeper in the Category 2 pathway. The distributor must validate compliance, and must itself continue complying with all applicable regulations, rules, directives, and licence conditions when providing those services.

This has several practical consequences.

First, issuers cannot treat distributor selection as a late commercial task. If Category 2 is the intended route, distributor strategy becomes part of the regulatory strategy from the start.

Second, the distributor will usually need documents and explanations that are strong enough for it to validate the issuance. That means the issuer’s whitepaper, risk disclosures, classification logic, and broader compliance story all need to be robust enough for a regulated intermediary to stand behind them.

Third, the distributor model changes founder assumptions about control. A project that wants to self-distribute broadly in Dubai while relying on Category 2 may find that its planned go-to-market model does not actually fit the rulebook.

That is why the Licensed Distributor is not just part of Category 2.
It is the mechanism that makes Category 2 possible.

5) What the Licensed Distributor must validate

This is one of the most practically important parts of the framework.

The rulebook portal’s “entire section” text shows that a Licensed Distributor providing services to a Category 2 issuer is responsible for validating several things, including:

• that the Virtual Asset complies with the distributor’s VA Standards,
• that the Whitepaper complies with Part III.B of the VA Issuance Rulebook,
• that the Risk Disclosure Statement complies with Part III.C,
• and that investor-classification requirements under Part IV of the Market Conduct Rulebook are satisfied.

This is extremely important for issuers.

It means that even though the issuer itself does not need a Category 1-style licence for Category 2, the issuer still needs to produce materials and a compliance posture that are good enough to pass review by a regulated distributor.

In practice, that means a Category 2 issuer should expect to prepare:

• a whitepaper that satisfies the general issuance rules,
• a standalone risk-disclosure statement,
• classification analysis explaining why the token is Category 2 rather than Category 1 or Exempt,
• and enough legal, commercial, and technical support for the distributor to validate the launch.

So while Category 2 removes the need for prior approval by VARA, it does not remove the need for regulatory-grade preparation.

6) Category 2 is not Category 1 — and that difference matters

To understand Category 2 properly, it helps to contrast it with Category 1.

Under the current issuance framework:

• Category 1 includes FRVAs and ARVAs and requires a VARA Licence. It is itself treated as a regulated VA Activity.
• Category 2 includes any issuance that is neither Category 1 nor Exempt, and does not require a VARA licence or prior approval if all placement and distribution is through or by a Licensed Distributor.

That distinction is the legal heart of the matter.

If your token is:

• fiat-referenced,
• asset-referenced,
• or otherwise caught by Category 1,
  then Category 2 is not available as a shortcut. The project moves into the heavier licensing and approval lane.

So one of the most important issuer tasks is making sure the token really is Category 2. If the project lazily assumes Category 2 and is wrong, the launch structure can become fundamentally misaligned with the rulebook.

This is why token classification should be done before whitepaper drafting and before distributor onboarding, not after.

7) Category 2 is also not the same as Exempt VA

Category 2 also needs to be distinguished from Exempt VAs.

The rulebook says Exempt VAs may be issued without prior approval from VARA, but the issuer must comply with Part II of the VA Issuance Rulebook and remains subject to VARA supervision, examination, and enforcement.

Importantly, Part III of the rulebook says issuers of Exempt VAs do not need to publish a Whitepaper or Risk Disclosure Statement in respect of those Exempt VAs. By contrast, Category 2 issuers do, because the whitepaper/risk-disclosure exemption applies only to Exempt VAs.

So Category 2 sits in the middle:

• lighter than Category 1,
• heavier than Exempt.

That means founders should not collapse Category 2 into “basically exempt.” It is not.

A Category 2 issuer still needs:

• a Licensed Distributor,
• a Whitepaper,
• a Risk Disclosure Statement,
• and a launch structure that satisfies a regulated distributor’s validation requirements.

8) Whitepaper requirements still matter in Category 2

One of the most common misconceptions is that if no VARA licence is required, the whitepaper probably becomes flexible or optional.

That is incorrect.

The current issuance rule says all entities issuing a Virtual Asset in the Emirate must publish both a Whitepaper and a Risk Disclosure Statement, except Exempt VAs. Category 2 is not Exempt, so the requirement remains.

That means a Category 2 issuer should prepare a whitepaper as a regulatory disclosure document, not just as launch marketing material. The rulebook also requires the whitepaper to be published prior to issuance, in a machine-readable format, and retained for a long period after the token ceases to circulate.

This matters even more because the Licensed Distributor must validate that the whitepaper complies with Part III.B of the VA Issuance Rulebook.

So for practical purposes, a weak whitepaper can still derail a Category 2 launch, even if the issuer is not applying for a Category 1 licence.

The whitepaper remains a central part of the regulatory package.

9) The separate risk-disclosure statement also applies

The same logic applies to the Risk Disclosure Statement.

Part III.C of the VA Issuance Rulebook requires issuers to publish a statement that includes a detailed description of all material risks related to the virtual assets being issued, and it must be:

• concise,
• clear,
• non-technical,
• and comprehensible. It must also be made available in the same easily accessible location as, but remain separate from, the whitepaper.

This means Category 2 issuers cannot simply bury risks deep inside the whitepaper and assume that is enough. The risk disclosure is a separate regulatory deliverable, and the Licensed Distributor must also validate that it complies with Part III.C.

This is one more reason why Category 2 should not be treated like “marketing-first, legal-later.” The disclosure framework is still real, and it still needs to be fit for regulatory review.

10) Investor classification still matters in Category 2 distribution

Another point founders often miss is that distribution rules can bring in conduct obligations beyond the issuance rulebook itself.

As noted above, the Licensed Distributor validating a Category 2 issuance must also ensure that investor-classification requirements under Part IV of the Market Conduct Rulebook are satisfied.

That is important because it means Category 2 distribution is not only about token classification and disclosure. It is also about who the offering is being distributed to and whether the distributor’s client-classification obligations are being respected. The Market Conduct Rulebook is one of the compulsory rulebooks that applies across VARA-licensed activity.

In practical terms, this means token issuers need to think early about:

• target investors,
• distribution audience,
• and whether their launch narrative aligns with the regulatory expectations of the distributor.

A project that says “we’ll figure out distribution later” is often underestimating how important distribution structure is to the Category 2 path.

11) Category 2 issuers still need a strong regulatory file, even without a licence application

Because Category 2 does not require a VARA licence or prior approval when the Licensed Distributor condition is met, some founders assume they do not need a serious legal and compliance file.

That is usually a mistake.

The distributor’s validation role means the issuer still needs to be ready with:

• a classification analysis,
• whitepaper,
• risk disclosure,
• token mechanics explanation,
• business model explanation,
• and enough supporting material for the distributor to be comfortable that the issuance complies with the rulebook.

In practice, this can look surprisingly similar to building a lighter version of a licensing file:

• not for direct submission to VARA as a Category 1 application,
• but to support distributor diligence and rulebook compliance.

That is why Category 2 issuers should still expect serious upfront work. The absence of a licence requirement does not remove the need for regulatory readiness. It just changes where the regulatory gate sits.

Instead of sitting directly at the issuer-licensing step, a large part of the gate sits at the Licensed Distributor validation step.

12) Category 2 launch strategy lives or dies on classification discipline

The biggest strategic risk in Category 2 is misclassification.

If a project assumes Category 2 but the token is actually:

• Category 1,
  or
• Exempt,
  then the entire launch structure may be wrong.

If it is really Category 1, the issuer may need:

• a VARA licence,
• token-specific approval,
• and a much heavier ongoing compliance model.

If it is actually Exempt, some of the whitepaper and risk-disclosure assumptions may be different.

That is why a Category 2 strategy should always begin with rigorous classification, not with distribution or branding decisions.

The right question is not:

“Can we fit this into Category 2?”

It is:

“Does the token actually belong there under the rulebook as written?”

That is the difference between using the framework properly and trying to reverse-engineer a lighter pathway.

13) What Category 2 issuers should prepare before launch

Before launching a Category 2 token in Dubai, a serious issuer should be able to answer at least these questions:

• Why is the token not Category 1 and not Exempt?
• Which Licensed Distributor will handle all placement and distribution?
• Is the distributor satisfied that the token complies with its VA Standards?
• Is the Whitepaper complete, compliant, and publishable prior to issuance?
• Is the Risk Disclosure Statement complete and separate from the whitepaper?
• Does the launch audience and offering structure fit the investor-classification expectations that the distributor must validate?
• Does the broader business model trigger any other VA Activity under VARA, such as broker-dealer, custody, exchange, or transfer and settlement?

If these questions are unresolved, the project is probably not ready for a Category 2 launch, even if it sounds close commercially.

14) The real practical answer

So what do issuers need to know about Category 2 token issuance in Dubai?

Category 2 is the route for token issuances that are neither Category 1 nor Exempt, and it allows issuers to avoid a VARA licence and prior approval only if all placement and distribution is handled through or by a Licensed Distributor.

That is a lighter route than Category 1, but it is still a regulated route.

The key implications are:

• you still need a Whitepaper,
• you still need a Risk Disclosure Statement,
• the distributor must validate compliance,
• and the launch must be structured around a regulated distribution model.

So the right founder question is not:

“Can we launch a token without a VARA licence?”

It is:

“Is this really Category 2, and can we meet the Licensed Distributor, disclosure, and conduct requirements that come with that path?”

Final takeaway

If you want the clearest practical answer to:
“What do issuers need to know about Category 2 token issuance in Dubai?”

it is this:

Category 2 token issuance under VARA is not a licensing route, but it is still a structured regulatory route. It applies only where the token is neither Category 1 nor Exempt, and the issuer can rely on it only if all placement and distribution is carried out through or by a Licensed Distributor. In that case, the issuer does not need a VARA licence or prior approval for the issuance, but still needs to comply with the disclosure framework, including the Whitepaper and Risk Disclosure Statement, and the distributor must validate compliance.

That means Category 2 is lighter than Category 1, but it is not the same as unregulated token issuance.

How CRYPTOVERSE Legal Can Help

At CRYPTOVERSE Legal Consultancy, we help founders, token issuers, exchanges, and digital asset businesses assess whether a proposed token falls into Category 2 under VARA, and what that means for classification, Licensed Distributor strategy, whitepaper drafting, risk disclosure, investor targeting, and launch structure. CTA: If you want tailored guidance on Category 2 token issuance in Dubai and how to structure your token launch correctly under VARA, contact CRYPTOVERSE Legal Consultancy to discuss your regulatory strategy.

FAQs