Category 1 VA Issuance Under VARA: Licensing, Disclosure, and Compliance

If you are planning to issue a token in Dubai and that token is tied to fiat, reserve assets, or another reference-value structure, one of the most important questions is not whether the token is “innovative” or “useful.”

It is whether the token falls into Category 1 VA Issuance under the VARA framework.

That matters because Category 1 is not the light token-issuance lane. Under VARA’s current VA Issuance Rulebook, Category 1 includes Fiat-Referenced Virtual Assets (FRVAs) and Asset-Referenced Virtual Assets (ARVAs), and Category 1 issuance requires a VARA Licence. The rulebook also treats Category 1 issuance itself as a regulated VA Activity.

So if your project is built around:

• a fiat-backed token,
• a reserve-backed token,
• an asset-linked token,
• a real-world-asset-referenced token,
• or another token with a stable or reference-value structure,

then you should assume the legal analysis begins with Category 1.

This guide explains:

• what Category 1 VA Issuance means,
• when it applies,
• what the licensing path looks like,
• what whitepaper and disclosure obligations attach to it,
• how compliance and prudential expectations become relevant,
• and why founders, exchanges, and token issuers should treat Category 1 as a full regulatory workstream rather than a token-launch formality.

1) The starting point: Category 1 is a regulated VA Activity

The core rule is clear. VARA’s Category 1 VA Issuance section 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. The same framework defines Category 1 issuance as the VA Activity of issuing any Virtual Asset that falls within Category 1.

That means Category 1 is not simply a disclosure category or a token-classification label. It is a regulated business activity in its own right. If your token falls into Category 1, the question is no longer just, “What should the whitepaper say?” The question becomes, “How do we get licensed to perform this VA Activity, and how do we remain compliant after that?”

This is why many token projects underestimate the framework at first. They assume issuance is mostly about token design and communications. Under VARA, Category 1 issuance is much closer to becoming a regulated VASP line of business.

2) What falls into Category 1

Under Rule I.C of the current VA Issuance Rulebook, Category 1 includes:

• Fiat-Referenced Virtual Assets (FRVAs)
• Asset-Referenced Virtual Assets (ARVAs)
• and any other VAs VARA may determine from time to time.

This is a crucial point for founders because many projects still ask the wrong question:

“Is this just a stablecoin?”

VARA does not use “stablecoin” as the primary legal category. It uses FRVA and ARVA, which are narrower and more important classifications. The rulebook also says token categorization depends on the token’s characteristics and the underlying business model associated with the VA.

So the legal test is not branding-based. A token is not outside Category 1 just because it is described as:

• utility-linked,
• reserve-backed,
• RWA-enabled,
• payment-friendly,
• or ecosystem-native.

If the token’s actual characteristics place it in FRVA or ARVA territory, Category 1 is likely central to the analysis.

3) FRVAs: the VARA category most people mean when they say “stablecoin”

An FRVA is a Fiat-Referenced Virtual Asset. The FRVA annex to the VA Issuance Rulebook sets out a dedicated regime for tokens that reference approved fiat currencies and are subject to specific issuance, backing, disclosure, redemption, and reserve rules.

In practical terms, this is the category most founders are talking about when they mean:

• USD stablecoin,
• EUR stablecoin,
• fiat-pegged token,
• reserve-backed fiat token.

But VARA does not stop at the idea of a peg. The FRVA rules deal with:

• approval requirements,
• additional whitepaper disclosures,
• additional ongoing disclosures,
• stable backing,
• reserve assets,
• redemptions,
• audits and reporting.

That structure tells you how seriously VARA treats FRVAs. They are not just tokens with a pricing objective. They are instruments that raise core regulatory questions around:

• backing quality,
• redemption integrity,
• disclosure accuracy,
• reserve management,
• and continuous oversight.

A founder planning a fiat-backed token in Dubai should therefore assume from day one that the project is likely not a simple token-launch exercise. It is probably an FRVA analysis, and FRVA means Category 1.

4) ARVAs: asset-referenced tokens are also Category 1

An ARVA is an Asset-Referenced Virtual Asset. The ARVA annex builds a separate regime for tokens that reference approved underlying assets, including RWA and/or Income, which are treated as Reference Assets for the ARVA.

This matters because many projects that do not think of themselves as “stablecoins” may still fall into ARVA territory. Examples can include tokens that are framed as:

• real-world-asset-backed,
• yield-linked,
• basket-referenced,
• reserve-backed by non-fiat assets,
• or otherwise linked to a reference-value base outside a single fiat currency.

The ARVA rules cover:

• approval requirements,
• additional whitepaper disclosures,
• additional ongoing disclosures,
• value of an ARVA,
• direct right of ownership,
• reserve assets,
• redemptions,
• audits and reporting.

So the practical takeaway is simple: if your token references assets rather than fiat, that does not usually move you into a lighter category. It often places you squarely in Category 1 through the ARVA route.

5) Category 1 is not just classification. It triggers the full licensing process

VARA’s FAQ states that entities seeking to carry out Category 1 VA Issuance must obtain a VARA Licence and follow the usual VARA licensing process. VARA’s public Licensed Activities page also lists VA Issuance Category-1 as one of the licensable activities.

That means a Category 1 issuer should think less in terms of:

• “approval to issue a token,”

and more in terms of:

• “licensing as a regulated VASP for Category 1 issuance.”

This has major consequences. Once you are in Category 1, you are not just preparing token disclosures. You are preparing for the VARA licensing journey, including:

• incorporation and ATI where relevant,
• the full application package,
• governance materials,
• Regulatory Business Plan,
• prudential support,
• technology and compliance buildout,
• and ongoing supervision after approval. VARA’s public licence-application page makes clear that licensed firms must comply with the compulsory rulebooks and the activity rulebooks for the VA Activities they are licensed for.

So Category 1 changes the question from “Can we issue this token?” to “Can we support this as a regulated licensed business line?”

6) Category 1 issuers must comply with more than the VA Issuance Rulebook

The rulebook is explicit that Category 1 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.

This is one of the most important practical points in the whole framework.

It means Category 1 is not just about token structure and disclosure. It is about whether the issuer can operate under the same kind of governance, compliance, technology, and conduct discipline expected of other serious regulated VA businesses.

In practical terms, that means a Category 1 issuer should expect to build and document:

• ownership and governance structure,
• fit and proper leadership,
• compliance and AML/CFT architecture,
• technology governance and security controls,
• market-facing and disclosure controls,
• prudential readiness,
• and the wider institutional support needed for a licensed VASP.

This is where many token projects discover that their launch plan is still at product level when VARA needs it to be at institutional level.

7) Each FRVA and each ARVA needs prior approval before issuance

One of the most practically important details in the current framework is that the licence itself is not the only approval step.

The 2025 VA Issuance Rulebook states that:

• each FRVA must be approved by VARA before issuance, and
• each ARVA must be approved by VARA before issuance.

This means a Category 1 issuer does not get a general licence and then freely issue whatever FRVA or ARVA it wishes under that umbrella. The specific token still requires approval.

That is a crucial control point in the regime. It allows VARA to assess not only the issuer as an institution, but also the specific instrument being brought to market.

For founders and exchanges, this means the project plan should assume:

• issuer licensing work, and
• token-specific approval work.

Those are related, but they are not the same thing.

8) Whitepaper and risk-disclosure obligations are central to Category 1

The VA Issuance Rulebook 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. Because FRVAs and ARVAs are Category 1 rather than Exempt, those obligations apply to them.

For Category 1 issuers, this matters even more because both the FRVA and ARVA annexes include Additional Whitepaper Disclosures and Additional Ongoing Disclosures.

So the disclosure burden is layered:

1. the general whitepaper rules apply,
2. the separate risk-disclosure-statement rules apply,
3. and category-specific additional disclosure rules apply for FRVAs and ARVAs.

This is one reason Category 1 issuance is so demanding in practice. The issuer is not only responsible for getting the token structure right. It must also sustain a disclosure architecture that matches the instrument and supports ongoing transparency.

9) Reserves, stable backing, redemption, and assurance are core compliance themes

The FRVA and ARVA annexes reveal what VARA sees as the core compliance risks in Category 1 issuance.

For FRVAs, the annex includes rules on:

• maintenance of stable backing,
• reserve assets,
• redemptions,
• audits and reporting.

For ARVAs, the annex includes rules on:

• value of the ARVA,
• direct right of ownership,
• reserve assets,
• redemptions,
• audits and reporting.

That means Category 1 compliance is not only about having a licence and a whitepaper. It is also about sustaining the operational integrity of the token after issuance:

• what backs it,
• how that backing is maintained,
• how token holders redeem,
• what rights attach to the token,
• what audits support confidence,
• and what reporting is produced.

This is why many “stablecoin-like” concepts fall apart once they meet regulatory reality. A token can be easy to describe in a deck. It is much harder to support it through reserve, redemption, audit, and disclosure discipline in a regulated environment.

10) AED-referenced FRVAs are not in the ordinary VARA approval lane

A crucial special rule applies to AED-referenced fiat-linked tokens.

The FRVA interpretation rule states that the issuance of any FRVA that purports to maintain a stable value in relation to the value of AED shall not be approved under the FRVA rules and remains under the sole and exclusive regulatory purview of the CBUAE.

This is highly important for founders and exchanges considering an AED stablecoin model.

It means the answer to “Can VARA approve our AED stablecoin?” is not the same as for a non-AED FRVA. Under the current FRVA interpretation, AED-referenced FRVAs sit under the Central Bank of the UAE rather than the standard VARA FRVA approval pathway.

So one of the first practical steps in Category 1 analysis is to ask:

• Is this FRVA referencing AED?
  If yes, the regulatory conversation changes materially.

11) Category 1 has visible fee implications too

The fee structure reinforces how seriously VARA treats Category 1 issuance.

Under Schedule 2 – Supervision and Authorisation Fees, Category 1 VA Issuance carries:

• AED 100,000 licence application fee
• AED 200,000 annual supervision fee.

The fee schedule also says VARA may, in its discretion, impose a fee for:

• applications by prospective issuers for approval to issue a Virtual Asset, and/or
• Category 1 licensed VASPs submitting whitepapers to VARA.

This is another practical reminder that Category 1 is not a light-touch pathway. Even before considering capital, reserves, compliance staffing, legal support, and technology controls, the visible regulatory-fee profile already places it in the heavier tier.

For founders, that means budgeting for Category 1 should never focus only on “token launch costs.” It needs to include the economics of becoming and remaining a licensed, supervised issuer.

12) Category 1 can expand into a broader regulated-business model

Another practical mistake is assuming Category 1 is the whole story.

The VA Issuance Rulebook says its rules operate in addition to the regulation of VA Activities carried out in the Emirate.

That means a Category 1 issuer also needs to ask whether the broader business model triggers other VA Activities, such as:

• broker-dealer functions,
• custody,
• exchange,
• management and investment,
• or transfer and settlement. VARA’s activity schedule and public licensed-activities page make clear that issuers may also be involved in other separately regulated activities depending on how the token is distributed, traded, held, or used.

This is especially important for:

• exchanges issuing listed tokens,
• token issuers planning treasury or reserve management structures,
• projects with in-house wallets,
• projects with transfer or settlement layers,
• or any project combining issuance with wider service infrastructure.

So the smart legal question is not just:

“Are we Category 1?”

It is also:

“Does our broader business model trigger anything else under VARA?”

13) What a Category 1 issuer should prepare before applying

A serious Category 1 project should expect to prepare for four workstreams at once.

First, classification: confirm whether the token is really FRVA or ARVA, and not merely described that way commercially. The rulebook makes classification depend on characteristics and business model, not issuer preference.

Second, licensing: prepare for the full VARA licence pathway, not just token disclosure. VARA’s FAQ and public licensing materials make clear that Category 1 follows the usual VARA licensing process.

Third, token-specific approval: remember that each FRVA and ARVA still requires approval before issuance.

Fourth, ongoing compliance: build for whitepaper, risk disclosure, reserves, redemption, audits, and ongoing disclosure from day one, rather than trying to bolt them on after launch.

In practical terms, that means the strongest Category 1 applicants usually work on:

• legal-entity and group structure,
• Regulatory Business Plan,
• governance and control framework,
• whitepaper and risk disclosure,
• reserve and redemption model,
• technology and wallet architecture,
• compliance and AML/CFT design,
• and launch/distribution strategy

as one integrated project rather than separate workstreams.

Final takeaway

If you want the clearest practical answer to:
“What does Category 1 VA Issuance under VARA involve?”

it is this:

Category 1 VA Issuance is a regulated VA Activity under the VARA framework. It includes FRVAs and ARVAs, requires a VARA Licence, and brings with it a wider licensing, disclosure, and compliance burden than lighter issuance routes. Category 1 issuers must comply not only with the VA Issuance Rulebook, but also with the Company, Compliance and Risk Management, Technology and Information, and Market Conduct Rulebooks. In addition, each FRVA and each ARVA must be approved by VARA before issuance.

That means the right founder question is not:

“Can we launch this token?”

It is:

“Is this token Category 1, and can we support the licensing, disclosure, reserve, redemption, audit, and ongoing compliance obligations that come with that classification?”

How CRYPTOVERSE Legal Can Help

At CRYPTOVERSE Legal Consultancy, we help founders, exchanges, treasury platforms, and token issuers assess whether a proposed token falls into Category 1 VA Issuance under VARA and what that means for licensing, approval, whitepapers, risk disclosure, reserve design, redemption structure, and ongoing compliance. We support FRVA and ARVA classification analysis, issuer-licensing strategy, whitepaper and disclosure review, regulatory business plan preparation, and broader VARA token-issuance structuring. CTA: If you want tailored guidance on Category 1 VA Issuance under VARA and what it means for your token project in Dubai, contact CRYPTOVERSE Legal Consultancy to discuss your regulatory strategy.

FAQs