Exempt VAs Under VARA: When a Token May Fall Outside the Full Issuance Perimeter

If you are planning a token launch in Dubai, one of the first questions to ask is not simply whether the token is “regulated.” The more useful question is whether the token may qualify as an Exempt VA under VARA’s issuance framework. That matters because VARA’s current VA Issuance Rulebook divides issuances in the Emirate into Category 1, Category 2, and Exempt VAs, and each category has a different prior-requirement profile. Category 1 requires a VARA Licence; Category 2 does not require a VARA licence, but all placement or distribution must be carried out through or by a Licensed Distributor; and Exempt VAs have no requirements prior to issuance.

That sounds simple enough, but “exempt” is one of the most misunderstood words in the whole VARA framework. Many founders hear “Exempt VA” and assume it means:

• unregulated,
• outside VARA,
• no compliance burden,
• or “safe to launch without much analysis.”

That is not what the rulebook says. VARA’s Exempt VAs provision 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. The same provision also says issuers of Exempt VAs remain subject to VARA’s supervision, examination, and enforcement at all times under Part IV of the rulebook.

So the better way to understand Exempt VAs is this:

An Exempt VA may fall outside the full prior-approval or licensing perimeter for issuance, but it does not fall outside VARA’s broader regulatory reach.

This guide explains what Exempt VAs are, when a token may qualify, what the exemption really does and does not do, and what token issuers still need to prepare before launch.

1) Start with the bigger framework: every token issuance is classified first

The current VA Issuance Rulebook is explicit that all entities in the Emirate wishing to issue a Virtual Asset must follow the issuance rules, and that issuances are categorized into three buckets:

• Category 1
• Category 2
• Exempt VAs.

The rulebook’s category table sets out the logic clearly. Category 1 covers FRVAs, ARVAs, and any other VAs VARA may designate, with a VARA Licence required. Category 2 covers issuances that are neither Category 1 nor Exempt, with no VARA licence required, but all placement or distribution must be carried out through or by a Licensed Distributor. Exempt VAs cover issuances that are not Category 1 and are either:

• a Non-Transferable Virtual Asset,
• a Redeemable Closed-Loop Virtual Asset, or
• another Virtual Asset as VARA may determine from time to time,
  with no requirements prior to issuance.

That means the first legal task for any issuer in Dubai is classification. The right founder question is not:

“Can we issue this token?”

It is:

“Which of these three categories does the token fall into?” VARA also says it will consider all factors it deems appropriate when determining category, including the nature of the token, the rights and/or value it represents or purports to represent, and the underlying business model associated with it.

2) What Exempt VAs are in practical terms

Under the rulebook, an issuance can qualify as Exempt if it is not Category 1 and falls into one of the exempt types. The two express exempt types currently spelled out are:

• Non-Transferable Virtual Assets
• Redeemable Closed-Loop Virtual Assets.

This is important because it shows that Exempt VAs are not a broad catch-all for “small” or “simple” tokens. They are specific types of Virtual Assets that VARA has decided do not need prior approval or licensing before issuance.

In practice, that means the exemption analysis usually begins by asking whether the token is:

• functionally non-transferable, or
• redeemable only within a closed-loop environment.

If the token is transferable, market-facing, tradable, or structured like a broader crypto asset intended for open circulation, it may quickly move away from Exempt VA territory and into Category 2 or Category 1 instead.

3) Non-Transferable Virtual Assets: the first exempt category

The current definitions make the first exempt category quite narrow. A Non-Transferable Virtual Asset means a Virtual Asset that:

• is not sold by the issuer for, and cannot be converted into, exchanged or redeemed for, fiat currency, Virtual Assets, or any value in kind;
• is not redeemable or exchangeable for goods, services, discounts, purchases, or otherwise has no market, use, or application; and
• cannot be transferred between VA Wallets.

That definition is much stricter than many founders expect. It is not enough that the token is “not intended for trading.” To qualify as non-transferable, the token must also:

• not be sold for value,
• not be exchangeable for value in kind,
• not be redeemable for goods or services,
• and not be transferable between wallets.

So if a founder is thinking about:

• a tradable utility token,
• a community token,
• a reward token with open transferability,
• or any token that can move between wallets or be redeemed for something of value,

that token is unlikely to fit comfortably within the Non-Transferable VA exemption.

4) Redeemable Closed-Loop Virtual Assets: the second exempt category

The second explicit exempt category is the Redeemable Closed-Loop Virtual Asset. The current rulebook defines this as a Virtual Asset that can be redeemed or exchanged for goods, services, discounts, or purchases with the issuer and/or merchants designated by the issuer, provided that:

• the issuer is the legal owner and/or has the validly enforceable legal right to grant the redemption rights;
• the token is not sold or exchanged for, and cannot be converted into, exchanged or redeemed for, fiat currency or Virtual Assets;
• it cannot be used or accepted as a means of payment outside the issuer’s and/or designated merchants’ closed loop; and
• it cannot be transferred between VA Wallets other than for redemption from the issuer or designated merchants.

This is the exemption most likely to be relevant for projects that resemble:

• digital vouchers,
• merchant-network loyalty instruments,
• limited-purpose ecosystem credits,
• or closed-loop purchase/redemption tokens.

But again, the definition is narrower than many people think. A token does not remain exempt merely because the issuer describes it as “ecosystem-only.” The token must actually stay inside the closed loop. If it can become:

• a broader payment instrument,
• a tradable token,
• a wallet-to-wallet transferable asset,
• or something redeemable for fiat or other VAs,

the exemption may no longer fit.

5) What the exemption really removes: prior requirements

The main legal benefit of Exempt VA status is that the rulebook imposes no requirements prior to issuance. In contrast:

• Category 1 requires a VARA Licence,
• Category 2 requires distribution through or by a Licensed Distributor.

So if a token genuinely qualifies as Exempt, the issuer does not need:

• a Category 1 VARA licence,
• prior approval from VARA before issuance,
• or the Category 2 Licensed Distributor route as a precondition to issuance.

This is why Exempt VAs are often described as falling outside the “full issuance perimeter.” They sit outside the more burdensome prior-approval pathways. But that is only half the story. The exemption is about prior requirements, not total regulatory irrelevance.

6) What the exemption does not remove

This is where the framework is most often misunderstood.

VARA’s Exempt VAs rule expressly says that entities may issue Exempt VAs without prior approval, provided they comply with Part II of the VA Issuance Rulebook at all times. It also says Exempt VA issuers remain subject to VARA’s supervision, examination, and enforcement under Part IV.

That means the exemption does not remove:

• the general rules in Part II of the VA Issuance Rulebook,
• VARA’s ability to supervise the issuer,
• VARA’s ability to examine the issuer or issuance,
• VARA’s enforcement powers.

So the right practical reading is:
Exempt VAs are exempt from prior licensing/approval requirements, not from the whole rulebook environment.

This is a crucial distinction for founders. A project that assumes “exempt” means “we don’t need to worry about VARA anymore” is usually taking the wrong risk from the start.

7) Exempt VAs and whitepapers: one of the few real reliefs

One meaningful relief for Exempt VAs appears in Part III – Whitepapers and Public Disclosures. The rulebook says all entities issuing a Virtual Asset in the Emirate must publish both a Whitepaper and a Risk Disclosure Statement, but the only exception is that issuers of Exempt VAs do not need to publish a Whitepaper or a Risk Disclosure Statement in respect of those Exempt VAs.

That means an Exempt VA issuer does get a genuine documentation relief compared with Category 1 and Category 2 issuers. It does not have to publish the standard issuance whitepaper and standalone risk-disclosure statement for that exempt token.

This is one of the main reasons founders are often interested in the Exempt VA route. But it is important not to overread the relief. The absence of a whitepaper obligation does not change:

• the need for accurate classification,
• the need to comply with Part II,
• or VARA’s ability to supervise and enforce.

8) Exempt does not mean “any small or limited token”

Another common mistake is to treat Exempt VA as a category for:

• low-value tokens,
• early-stage tokens,
• internal utility tokens,
• or tokens “not meant for the public.”

That is not how the current rulebook is framed.

The express exempt categories are specific:

• Non-Transferable VAs
• Redeemable Closed-Loop VAs
• or any other VA VARA may determine from time to time.

Nothing in the current category table says that a token is exempt merely because it is:

• small,
• early-stage,
• low-volume,
• or called a utility token. VARA instead says it will look at the token’s nature, the rights or value it represents or purports to represent, and the underlying business model.

So if a founder’s real theory is:

“It’s exempt because it’s harmless,”

that is not a safe legal analysis.

The safer question is:

“Does it actually satisfy one of the exempt definitions?”

9) Exempt status can be lost if the token evolves

One of the most important provisions in the category rules is Rule I.C.3. It says that if any change is proposed to a Virtual Asset that may result in its issuance no longer qualifying under the original categorisation, the issuer must comply with the requirements of the new category before the change takes effect. The rulebook explicitly says this may include obtaining a Licence from VARA and/or prior approval of the Whitepaper, where necessary.

This is a critical point for Exempt VAs.

A token may begin life in a closed-loop or non-transferable structure and later evolve into something:

• transferable,
• redeemable for broader value,
• usable outside the closed loop,
• or otherwise more open and market-facing.

If that happens, the issuer cannot simply continue calling it exempt. It must move into the category that now applies and satisfy that category’s requirements before the change takes effect.

So one of the smartest questions to ask at design stage is:
Will this token remain exempt over time, or are we building toward a later model that will force reclassification?

10) Practical examples of where Exempt VA analysis may matter

Without stretching beyond the rulebook, Exempt VA analysis is most likely to matter in models such as:

• non-transferable digital entitlements with no market or redemption value,
• issuer-controlled closed-loop redemption tokens usable only with the issuer or designated merchants,
• limited redemption instruments that cannot circulate as payment tools outside the issuer ecosystem.

By contrast, a token is less likely to fit the Exempt VA path if it is intended to be:

• traded,
• transferred between wallets broadly,
• redeemed for fiat or other VAs,
• used as a means of payment outside a closed loop,
• or structured as a value-bearing cryptoasset for general market participation.

That is why Exempt VA analysis tends to be strongest for genuinely limited-purpose tokens, and weakest for projects trying to achieve broad crypto functionality while still claiming exemption.

11) What issuers should do before relying on the exemption

Before relying on Exempt VA status, an issuer should be able to answer at least these questions:

First, is the token clearly not Category 1? Category 1 includes FRVAs and ARVAs, and if the token falls there, the exemption is not available.

Second, does the token actually satisfy the definition of:

• Non-Transferable Virtual Asset, or
• Redeemable Closed-Loop Virtual Asset?

Third, will the token remain within that definition over time, or does the roadmap include changes that would require reclassification?

Fourth, even without prior approval, is the issuer prepared to comply with Part II of the VA Issuance Rulebook and remain subject to VARA supervision, examination, and enforcement?

Fifth, is the project team careful not to overstate what “exempt” means in internal and external communications? Because if the business behaves as though the exemption eliminates regulatory risk altogether, it is starting from a mistaken premise.

12) The real practical answer

So when may a token fall outside the full issuance perimeter under VARA?

The best answer is:

A token may fall outside the full prior-licensing or prior-approval issuance perimeter if it qualifies as an Exempt VA — meaning it is not Category 1 and fits the definition of either a Non-Transferable Virtual Asset, a Redeemable Closed-Loop Virtual Asset, or another exempt class VARA may determine. In that case, there are no requirements prior to issuance.

But that is not the same as falling outside VARA altogether. Exempt VA issuers must still comply with Part II of the VA Issuance Rulebook and remain subject to supervision, examination, and enforcement by VARA. They also benefit from the fact that they do not need to publish the standard Whitepaper and Risk Disclosure Statement that apply to non-exempt issuances.

That is the practical balance:

• lighter prior requirements,
• but not a complete departure from the framework.

Final takeaway

If you want the clearest practical answer to:
“When may a token fall outside the full issuance perimeter under VARA?”

it is this:

A token may sit outside the full prior licensing/approval perimeter if it qualifies as an Exempt VA, but “exempt” under VARA does not mean unregulated. Exempt VAs currently include certain Non-Transferable Virtual Assets and Redeemable Closed-Loop Virtual Assets, and they require no prior approval or licence before issuance. But issuers must still comply with Part II of the VA Issuance Rulebook and remain subject to VARA’s supervision, examination, and enforcement. Exempt VAs also benefit from relief from the usual Whitepaper and Risk Disclosure Statement publication requirement.

So the right founder question is not:

“Can we call this exempt?”

It is:

“Does this token actually fit the exempt definitions, and can we keep it there over time?”

How CRYPTOVERSE Legal Can Help

At CRYPTOVERSE Legal Consultancy, we help founders, token issuers, exchanges, and digital-asset businesses assess whether a proposed token may qualify as an Exempt VA under VARA, and what that means for classification, launch structure, disclosure, and future re-categorisation risk. CTA: If you want tailored guidance on Exempt VAs under VARA and whether your token may fall outside the full issuance perimeter in Dubai, contact CRYPTOVERSE Legal Consultancy to discuss your regulatory strategy.

FAQs