If there is one area in the VARA framework where founders, token issuers, and digital asset businesses most often get overconfident too early, it is token issuance.
Why?
Because many teams start with the wrong assumption:
- “It’s just a utility token.”
- “It’s only for ecosystem access.”
- “It’s not a stablecoin, so the rules should be light.”
- “We’ll figure out the legal category later.”
Under VARA, that is not a safe way to think about token issuance.
Dubai’s issuance framework is more structured than that. The Virtual Asset Issuance Rulebook divides issuance into three core categories:
- Category 1 VA Issuance
- Category 2 VA Issuance
- Exempt VAs.
That categorisation is not just legal housekeeping. It has direct consequences for:
- whether a VARA licence is required,
- whether prior approval is needed,
- whether distribution must happen through a Licensed Distributor,
- whether a Whitepaper and Risk Disclosure Statement are required,
- and how the token should be described, marketed, and launched in Dubai.
So if you are searching for:
- VARA token issuance
- VARA Category 1 issuance
- VARA Category 2 issuance
- Exempt VAs under VARA
- Can I issue a token in Dubai?
- VARA stablecoin rules
- VARA whitepaper requirements
- Dubai token issuance law
then this guide is built for you.
This article explains:
- how VARA classifies token issuance,
- what each category actually means,
- which categories require a licence,
- which require licensed distribution,
- what the disclosure burden looks like,
- and why token founders should stop using labels like “utility token” as though they answer the legal question by themselves.
Because under VARA, the real question is never just what the token is called.
The real question is:
What category does the token actually fall into?
1) Why VARA classifies token issuance this way
VARA does not treat all tokens as though they create the same legal or market risk.
And that makes sense.
A fiat-referenced token is not the same as a closed-loop redemption token.
A transferable ecosystem token is not the same as a non-transferable internal reward asset.
A reserve-backed token is not the same as an access token used only inside one merchant environment.
The Rulebook reflects that reality by creating different issuance categories with different consequences. Rule I.C of the VA Issuance Rulebook sets out the three categories and the prior requirements attached to each. It also states that when determining the category of a VA issuance, VARA may consider all factors it deems appropriate.
That last point is especially important.
It means the answer does not depend only on what the issuer chooses to call the token. VARA may look at the actual structure, use case, rights, transferability, and economic design of the asset when deciding what category it belongs in.
This is why serious token issuers should not leave classification until the last moment.
Category analysis affects:
- licensing,
- distribution,
- disclosures,
- and launch strategy.
And once you understand that, the three-part structure becomes much easier to work with.
2) Category 1 VA Issuance: the most heavily regulated issuance tier
Let’s start with the highest-regulation category.
Under the VARA Rulebook, Category 1 VA Issuance means the issuance of:
- Fiat-Referenced Virtual Assets (FRVAs),
- Asset-Referenced Virtual Assets (ARVAs),
- and any other Virtual Assets as may be determined by VARA from time to time.
This category matters because it is not just “regulated issuance” in a general sense.
It is a licensed VA Activity.
The Category 1 VA Issuance rule states that no entity in the Emirate may carry out any Category 1 VA Issuance unless it is authorised and licensed by VARA for that issuance. VARA’s FAQ says the same thing in practical terms: entities seeking to carry out Category 1 issuance must obtain a VARA licence and follow the usual VARA licensing process.
That is one of the most important distinctions in the whole issuance framework.
What that means in practice
If your token is a:
- stable-value token linked to fiat,
- asset-referenced token,
- or another token VARA treats as Category 1,
then the issuance itself may become a licensable activity rather than just a product feature.
And VARA does not stop with the issuance rulebook alone.
For Category 1 VA Issuance, the rulebook states that issuers must comply not only with the VA Issuance Rulebook, but also with the:
- Company Rulebook
- Compliance and Risk Management Rulebook
- Technology and Information Rulebook
- Market Conduct Rulebook.
That tells you how seriously VARA treats this category.
It is not just asking:
“Is the token described properly?”
It is asking:
“Is the issuer structured and governed like a business that can responsibly issue this kind of asset into the market?”
FRVAs and ARVAs
Category 1 specifically captures:
- FRVAs — fiat-referenced virtual assets
- ARVAs — asset-referenced virtual assets.
For ARVAs, the Category 1 rule also points issuers to the ARVA Rules in Annex 2 of the VA Issuance Rulebook. VARA’s FAQ similarly notes that FRVA issuers must comply with the compulsory rulebooks and the FRVA Rules in Annex 1 of the VA Issuance Rulebook.
That means stable-value and referenced-value issuance models should be treated with particular care. These are not the types of assets founders should casually assume can be issued the same way as a generic ecosystem token.
Important special note on AED-referencing FRVAs
VARA’s FAQ makes an especially important point: AED-referencing FRVAs are not approved under the VA Issuance Rulebook and remain under the sole and exclusive regulatory purview of the CBUAE.
That is a critical point for anyone thinking about AED-linked stablecoin concepts in Dubai.
Best-suited examples
Category 1 is most naturally relevant to:
- fiat-backed stablecoins,
- reserve-backed settlement tokens,
- asset-backed tokens,
- and other reference-based token structures where market trust and value reference are central to the product logic.
3) Category 2 VA Issuance: regulated, but not licensed in the same way
Now let’s move to the middle category.
Under the Rulebook, Category 2 means the issuance of any Virtual Asset that does not constitute:
- a Category 1 VA Issuance, or
- an Exempt VA.
This is where a very large number of market-facing token projects are likely to land.
Category 2 often captures the kinds of assets people loosely refer to as:
- ecosystem tokens,
- governance tokens,
- utility tokens,
- reward tokens,
- platform-access tokens,
- gaming tokens,
- fan or creator tokens,
provided they are not Category 1 and not genuinely exempt. That classification outcome is driven by the structure, not by the label.
Does Category 2 require a VARA licence?
This is where a lot of confusion exists.
The Category 2 rule states that entities in the Emirate may only issue Category 2 Virtual Assets provided that all placement and distribution is carried out by a Licensed Distributor. It also says that, provided this requirement is met, entities issuing Category 2 assets do not need prior approval from VARA.
That means Category 2 is not licence-free in a practical sense, but it is not licensed in the same direct way as Category 1 issuance.
This is a very important nuance.
The issuer may not need a Category 1-style VARA issuance licence, but the distribution channel is still regulated because all placement and distribution must be carried out through or by a Licensed Distributor.
Why this matters commercially
A lot of founders hear “no prior approval” and assume:
“Great, we can issue freely.”
That is not the right conclusion.
The rule is more careful than that:
- no prior approval from VARA, provided the Licensed Distributor requirement is satisfied.
So the key commercial implication is this:
Category 2 issuance still requires a structured distribution pathway.
That affects:
- launch planning,
- partner strategy,
- platform distribution,
- whitepaper preparation,
- and how the token is marketed and offered.
Best-suited examples
Category 2 is often the most relevant home for:
- transferable utility tokens,
- governance tokens,
- ecosystem tokens,
- transferable gaming or fan tokens,
- and broader Web3 issuance models that are neither reserve-backed nor exempt.
4) Exempt VAs: the lightest category, but only when the structure truly fits
This is the category many founders hope their token falls into.
Sometimes that hope is justified.
Quite often, it is not.
Under the Rulebook, Exempt VAs are issuances that do not constitute a Category 1 VA Issuance and are either:
- a Non-Transferable Virtual Asset,
- a Redeemable Closed-Loop Virtual Asset,
- or another Virtual Asset as may be determined by VARA from time to time.
The immediate attraction here is obvious.
The Exempt VA rule states that entities in the Emirate may issue Exempt VAs without prior approval from VARA, provided that they comply with Part II of the VA Issuance Rulebook at all times. It also states that issuers of Exempt VAs remain subject to VARA’s supervision, examination, and enforcement.
That means Exempt VAs are lighter — but not outside the regulatory world altogether.
The most important misunderstanding about Exempt VAs
A lot of issuers assume “exempt” means:
- no rules,
- no oversight,
- no need to think carefully.
That is wrong.
The Rulebook is explicit that even Exempt VA issuers remain subject to VARA’s supervisory and enforcement powers.
So the category is lighter, but it is not lawless.
Whitepaper and disclosure treatment
One of the clearest practical distinctions appears in the Whitepapers and Public Disclosures part of the VA Issuance Rulebook.
The current VA Issuance Rulebook states that all entities in the Emirate issuing a Virtual Asset must publish both a Whitepaper and a Risk Disclosure Statement, but that the only exception is for issuers of Exempt VAs, who do not need to publish a Whitepaper or Risk Disclosure Statement in respect of Exempt VAs.
That is a very significant difference.
It means exempt treatment can materially reduce the disclosure burden — but only if the token genuinely fits the exemption.
Best-suited examples
Exempt VAs are most naturally relevant to:
- non-transferable loyalty or reward tokens,
- closed-loop merchant redemption tokens,
- non-transferable internal credits,
- and other token concepts deliberately structured to remain outside broader transferable market circulation.
5) Whitepapers, Risk Disclosures, and why category matters before launch
One of the most important operational consequences of the category structure is the disclosure burden.
The VA Issuance Rulebook states that all entities issuing a Virtual Asset in the Emirate must comply with Part III of the Rulebook and publish both a Whitepaper and a Risk Disclosure Statement. The one exception is for Exempt VA issuers, who do not need to publish those documents for Exempt VAs. The Rulebook also requires prior versions to be retained, and the published PDF excerpt confirms that prior versions must be kept for at least eight years after the VA ceases circulation.
This matters because a lot of founders still treat the whitepaper as:
- a branding document,
- a community explainer,
- or a market-launch narrative.
Under VARA, it sits inside a regulated disclosure framework.
And that means token classification should happen before marketing and launch mechanics are finalised.
Why?
Because category affects:
- whether a licence is needed,
- whether a Licensed Distributor is mandatory,
- whether a Whitepaper and Risk Disclosure Statement are required,
- and how the issuance should be presented to the market.
This is exactly why teams that delay classification often create unnecessary legal and commercial friction for themselves later.
6) The category question is about structure, not marketing language
This is perhaps the biggest practical lesson in the whole issuance framework.
Founders and token teams often talk in labels:
- utility,
- governance,
- rewards,
- community,
- ecosystem,
- access,
- creator.
VARA’s framework does not begin with those labels. It begins with category definitions and regulatory consequences. Rule I.C confirms that VARA will determine category by considering all factors it deems appropriate.
So the right question is not:
“What do we want the token to be called?”
It is:
“What does the token actually do, how is it structured, is it transferable, is it closed-loop, is it value-referenced, and how will it be issued and distributed?”
That is the real legal analysis.
And it is why the same marketing phrase — for example “utility token” — can be nearly useless if it does not answer the actual structural question.
A transferable market-facing token may well end up in Category 2.
A reserve-backed token may trigger Category 1.
A genuinely non-transferable closed-loop token may fit Exempt VA.
The category is not chosen by the issuer’s branding preference.
It is shaped by the asset’s real design.
Final takeaway
If you are issuing a token in Dubai, the first serious legal question is not simply:
“Can we launch this token?”
It is:
“What issuance category does this token fall into under VARA?”
That is the question that drives everything else.
Under the VARA VA Issuance Rulebook:
- Category 1 VA Issuance covers FRVAs, ARVAs, and other designated assets, and requires authorisation and a VARA licence.
- Category 2 covers issuances that are neither Category 1 nor Exempt, and while they do not need prior VARA approval, all placement and distribution must be carried out through or by a Licensed Distributor.
- Exempt VAs include non-transferable and redeemable closed-loop assets and may be issued without prior approval, though they remain subject to VARA supervision and enforcement.
That is why token classification is not a side issue. It is a core launch, licensing, and distribution issue.
And the businesses that get it right early usually save themselves a great deal of confusion later.
How CRYPTOVERSE Legal Can Help
At CRYPTOVERSE Legal Consultancy, we help founders, token issuers, and digital asset businesses assess how their token should be classified under the VARA VA Issuance Rulebook and what that means for licensing, distribution, whitepaper preparation, and market entry in Dubai.
Our support includes token-category analysis, issuance strategy, Category 1 / Category 2 / Exempt VA assessment, whitepaper and disclosure support, Licensed Distributor pathway analysis, and regulator-ready structuring guidance.
We help clients move beyond vague labels like “utility token” and toward a clearer, more defensible issuance strategy aligned with the VARA framework.
If you are planning to issue a token in Dubai and want tailored guidance on whether it falls into Category 1, Category 2, or Exempt VA status, contact CRYPTOVERSE Legal Consultancy to discuss your token issuance strategy.
FAQs
1. What are the VARA token issuance categories?
VARA classifies token issuance into Category 1 VA Issuance, Category 2 VA Issuance, and Exempt Virtual Assets (VAs). Each category has different licensing, distribution, and compliance requirements under the VA Issuance Rulebook.
2. Does Category 1 token issuance require a VARA licence?
Yes. Category 1 VA Issuance, which includes Fiat-Referenced Virtual Assets (FRVAs) and Asset-Referenced Virtual Assets (ARVAs), requires prior authorisation and a VARA licence before issuance in Dubai.
3. What is the difference between Category 2 and Exempt Virtual Assets?
Category 2 tokens generally do not require prior VARA approval but must be distributed through a Licensed Distributor. Exempt Virtual Assets, such as certain non-transferable or closed-loop tokens, may be issued without prior approval but remain subject to VARA supervision.
4. Is a whitepaper required for token issuance under VARA?
Yes. Most Virtual Asset issuers must publish a Whitepaper and a Risk Disclosure Statement. The primary exception is for qualifying Exempt Virtual Assets, which are not required to publish these documents.
5. How can I determine my token’s VARA issuance category?
A token’s category depends on its actual structure, transferability, economic design, rights, and intended use—not simply whether it is labelled as a “utility token” or “governance token.” A proper legal assessment is essential before launching a token in Dubai.