VARA Licence Application Process & Documentation

A practical guide to the full VARA licensing journey in Dubai — starting with our Sharpen the Axe readiness stage, then moving through Stage 1 (ATI) and Stage 2 (Full VASP Licence). Strong pre-submission preparation reduces avoidable regulator queries and supports a smoother path to approval.

Licensing Journey — At a Glance

🪓

Stage 0 (Sharpen the Axe): 4–8 week readiness phase before formal VARA process begins

🏛️

Stage 1 (ATI): IDQ, preliminary docs, 50% fees — authorises incorporation and setup only

Stage 2: Full document pack, VARA review, clarification rounds, FMP licence issuance

📋

4 document categories — non-exhaustive; VARA may request additional materials at any point

📊

The RBP is the heart of the file — weak RBPs create weak applications across every pillar

We help applicants scope the correct licence, build the Regulatory Business Plan, prepare the documentary pack, align prudential readiness, and manage regulator engagement from pre-filing to approval. 

Why the Application Process Matters

A VARA Licence Is Secured by Readiness — Not by Filing Forms Alone

VARA's framework is a staged regulatory process that tests scope, governance, capital, liquidity, compliance maturity, technology readiness, and documentary quality. Because the framework is activity-based, the application must be aligned to the exact VA Activity — or combination of activities — the applicant intends to carry on. That is why the strongest applicants do not begin with submission. They begin with readiness.

In practice, delays rarely happen because VARA dislikes the business model in principle. Delays usually happen because the licence scope has not been properly defined, the Regulatory Business Plan is underdeveloped, policies are incomplete or inconsistent, prudential assumptions are weak, or the applicant is still building key internal materials after submission has already begun.

The three-phase approach — Stage 0 (Sharpen the Axe), Stage 1 (ATI), and Stage 2 (Full VASP Licence) — is designed to prevent these failure patterns by front-loading the workstreams that determine application quality.

💡

Key Principle: Document quality, prudential readiness, and internal consistency are the decisive factors at Stage 2 — not the breadth of the business ambition. A complete, consistent, and well-evidenced file outperforms a complex but underprepared one every time.
 

The Three-Phase VARA Licensing Journey

S0

Sharpen the Axe — 4–8 Weeks

Structured readiness phase to make the application regulator-ready before it reaches VARA. Builds the foundation that everything else depends on.

01

Stage 1 — Approval to Incorporate (ATI)

Formal first step: IDQ, preliminary documentation, 50% of licence fees. ATI enables incorporation and setup — not regulated operations.

02

Stage 2 — Full VASP Licence (FMP)

Full document submission, VARA review, clarification rounds, remaining 50% fees and first year supervision fees, FMP licence issuance.

🪓

4–8 Weeks

Sharpen the Axe readiness phase — before the formal VARA process begins

📋

4 Doc Categories

Corporate, Risk & Compliance, Technology, and Other Supporting — non-exhaustive

💰

50% + 50%

Fees split: 50% at ATI stage, remaining 50% plus first year supervision at Stage 2

📊

RBP = The File

The Regulatory Business Plan ties together every other document — weak RBPs create weak applications

The Full VARA Licensing Journey

Stage 0, Stage 1 & Stage 2 — In Full

Each stage of the VARA licensing journey has a defined purpose, specific outputs, and clear limits on what it does and does not permit. Understanding the boundaries between stages — particularly what ATI does and does not allow — is essential for correct commercial and regulatory planning.

S0

Pre-Submission — Not a Formal VARA Step

Sharpen the Axe — Structured Readiness Phase

Before the formal VARA process begins, we introduce a preliminary readiness stage called Sharpen the Axe. This is a focused 4–8 week preparation phase designed to ensure that the applicant's documentation, governance framework, control architecture, and operational model are properly built before entering the two formal VARA stages. Delays rarely happen because VARA dislikes the business — they happen because the application was not ready when it was filed.

What Happens During This Stage

Why This Is Critical

Sharpen the Axe is how serious applicants avoid looking unprepared once VARA starts asking real questions. The preparation investment here directly reduces the review timeline at Stage 2.

01

Formal VARA Step — New Firms

Stage 1 — Approval to Incorporate (ATI)

Stage 1 is the first formal VARA step for new firms. At this stage, the applicant submits the Initial Disclosure Questionnaire, provides preliminary documentation, and pays 50% of the licence application fees. ATI, once granted, allows the firm to incorporate and set up operationally — but does not authorise regulated VA activities.

What Happens in Stage 1

What ATI Allows

What ATI Does NOT Allow

✕ Commencing any regulated Virtual Asset activities

✕ Onboarding clients or executing VA transactions

✕ Operating a soft launch or limited-access platform

⚠️

VARA expressly reserves the right not to issue ATI/IPA where the proposed activity falls outside the regulatory perimeter or the firm may not meet appropriate regulatory standards.

S2

Formal VARA Step — Full Licensing

Stage 2 — Full VASP Licence Application (FMP)

Once ATI has been granted, the applicant proceeds to the full licensing phase. Stage 2 is where document quality, prudential readiness, and internal consistency become decisive. This is the stage where a well-prepared Sharpen the Axe file translates into a smoother, faster review process.

What Happens in Stage 2

What Makes Stage 2 Succeed

For legacy firms — VARA operates a separate transition pathway (AAN, LOP, or NOC route) for firms carrying out VA activities prior to February 2023. This route is exclusively for Legacy VA Operators.

Documentation VARA Expects

The 4 Document Categories — Non-Exhaustive

The application documentation list is non-exhaustive. VARA expressly states that further documents may be required during the licensing process — meaning firms should prepare for a dynamic review process, not a closed checklist exercise. Document quality and internal consistency across all four categories determine how efficiently Stage 2 proceeds.

Category 1 — Foundation Documents

🏗️

Corporate Structure & Governance Documents

This category confirms that VARA is assessing ownership transparency, governance credibility, management substance, and financial readiness from the outset. It is the largest category and the one most frequently incomplete at first submission.

Category 2 — Control Environment

🛡️

Risk & Compliance Documents

This is one of the clearest indicators that VARA expects a functioning control environment — not just a legal shell. The documentation must evidence that AML, risk, compliance, and conduct systems are operational, not aspirational.

Category 3 — Technology & Security

💻

Technology Documents

Technology documentation aligns with VARA's Technology and Information rulebook expectations — where cyber governance, resilience, wallet control, and tested operational recovery are licensing issues, not post-approval enhancements.

📋

Penetration testing results must reflect the actual live or near-live architecture — not the planned future state

Category 4 — Model-Specific Materials

📑

Other Supporting Materials

Depending on the business model, VARA may also require additional model-specific documentation. This is particularly relevant for models that go beyond simple advisory or intermediary structures and involve token issuance, payments, DeFi exposure, or proprietary trading.

⚠️

Non-Exhaustive List. VARA expressly states that published documentation lists are non-exhaustive. Additional materials may be requested at any point during the review — firms should prepare for a dynamic process, not a fixed checklist.

The RBP & What VARA Is Really Looking For

The Regulatory Business Plan — The Heart of the File

In practice, the RBP is one of the most important documents in the entire application. It ties together the business model, governance, customer journey, financial assumptions, risk framework, technology stack, outsourcing logic, and prudential positioning. Weak RBPs create weak applications across every other category.

A Strong RBP Should Explain

The business model must be coherently mapped to the specific VARA activity perimeter — not described generically across all possible activities.
The complete client lifecycle — from first contact through to account closure — must be described with enough specificity to satisfy AML and conduct reviewers.
Every fiat and VA movement — entry, internal movement, custody, settlement, and exit — must be mapped completely, consistently with the fund flow diagrams.
Every technology vendor, outsourced function, custody provider, and third-party service must be identified and the control relationship explained.
The prudential section must show that capital is available, NLA is modelled, reserves are held, and insurance is in place — not that these are planned for post-approval.
The post-licensing compliance framework — ongoing reporting, audit, supervisory engagement, and material change controls — must be described as an operational reality, not an intention.

What VARA Will Look For Across the File

Correct VA Activity Scope Selected

The activity classification is right for the operating model — not over-licensed or under-licensed relative to what the business actually does.

Real Management, Governance & Ownership Transparency

The people behind the business are credible, fit and proper, and demonstrate genuine substance in Dubai — not nominally appointed.

Capital, Liquidity & Prudential Obligations Met

Paid-up capital is available and held in approved form. NLA is modelled and demonstrated. Reserve assets and insurance are in place at submission.

Policies & Systems Match the Actual Business Model

There are no contradictions between the RBP, fund flows, AML framework, governance documents, and technology policies. Every document tells the same regulatory story.

Credible Responses to Review Questions

The file was built properly before submission — meaning query responses are consistent with the application rather than improvised under review pressure.

How We Help

Full VARA Application Lifecycle Support — What We Deliver

We support the full VARA application lifecycle — from the Sharpen the Axe readiness phase through to the FMP licence and post-approval compliance buildout. Every workstream is managed as part of an integrated application strategy, not handled in isolation.

🪓

Stage 0 — Sharpen the Axe Readiness Planning

We run the structured 4–8 week readiness phase — building the document matrix, identifying all applicable rulebooks, scoping the activity perimeter, and ensuring the application is regulator-ready before a single document is filed with VARA. This is where application quality is determined.

🗺️

Activity-Scope & Perimeter Analysis

We confirm which VA Activities the operating model requires authorisation for, map the full compliance scope across baseline and activity-specific rulebooks, and identify the combination risks that arise from multi-activity licence strategies — before the application architecture is designed.

🏛️

ATI & Stage 2 Application Strategy

We manage the ATI submission — IDQ preparation, preliminary documentation, fee timing — and design the Stage 2 application strategy to ensure that the full document pack is built, sequenced, and submitted in the most efficient order for VARA review.

📊

Regulatory Business Plan (RBP) Drafting

We draft the complete Regulatory Business Plan — the primary narrative document in the VARA application — presenting a coherent, credible, and commercially grounded picture of the business that ties together governance, capital, AML, technology, and operating model in a single consistent document.

📋

Document Matrix & Submission Tracker

We build and maintain the document matrix and submission tracker — mapping every required document across all four categories, tracking completion status, identifying dependencies, and ensuring nothing is missing when the application is filed with VARA.

💰

Prudential Capital & Liquidity Planning

We model paid-up capital, NLA, reserve assets, and insurance requirements — including the overhead-based PUC calculation — and integrate the prudential plan into the RBP and capital sections, ensuring VARA sees a financially coherent and evidenced submission from day one.

🛡️

Governance, AML & Technology Documentation

We prepare the full governance framework, AML/CFT programme, and technology documentation across all four document categories — ensuring internal consistency between the RBP, fund flows, compliance manual, AML policies, technology architecture, and BCDR documentation.

🔄

Regulator Response Drafting & End-to-End File Management

We manage all VARA interactions throughout Stage 1 and Stage 2 — drafting query responses, managing the issue log, coordinating VARA meetings and interviews, and carrying the file through IPA conditions and operational readiness to final FMP licence issuance and post-approval compliance buildout.

From Sharpen the Axe Through to FMP Licence — End-to-End Application Management

The strongest applicants do not begin with submission. They begin with readiness. Sharpen the Axe is how a VARA application is won before VARA ever asks its first question.

FAQs

Frequently Asked Questions — VARA Application Process

What is the Sharpen the Axe stage?

Sharpen the Axe is our pre-submission readiness phase — typically 4–8 weeks — designed to build the application properly before the formal VARA process begins. During this phase, we conduct the regulatory perimeter analysis, draft the Regulatory Business Plan, build the compliance and governance framework, prepare the prudential and capital planning materials, and assemble the document matrix and submission tracker. The goal is to ensure that by the time the IDQ is filed at Stage 1, the entire application is already in a state that can withstand VARA’s review process without generating avoidable queries or delays.

Do new firms need ATI before the full VASP licence application?

Yes. For new firms, ATI (Approval to Incorporate) is the first formal VARA step and must be obtained before the full VASP licence application can proceed to Stage 2. The ATI process involves submitting the Initial Disclosure Questionnaire to Dubai Economy and Tourism or the relevant Free Zone, providing preliminary documentation, and paying 50% of the applicable licence fees. Once ATI is granted, the firm may incorporate its legal entity, secure office space, open bank accounts, onboard employees, and establish systems — but may not commence regulated VA activities until the full VASP licence is granted at Stage 2.

Can a firm operate once ATI is granted?

No. ATI allows incorporation and operational setup only. Regulated VA activities may not begin until the full VASP FMP Licence is granted at Stage 2. This means no client onboarding, no VA transaction execution, no platform access for external users, and no commercial operations relating to VA activities — even in a soft launch or beta format. VARA expressly reserves the right not to issue ATI or IPA where the proposed activity falls outside the regulatory perimeter or the firm may not meet appropriate regulatory standards.

Is the VARA documentation list fixed and final?

No. VARA expressly states that the published documentation list is non-exhaustive and that additional materials may be requested at any point during the licensing review. This means firms should prepare for a dynamic process — not a closed checklist exercise where submission of the listed documents guarantees the end of the information request phase. The quality and consistency of the initial submission directly determines how many additional requests VARA will make. A well-prepared, internally consistent file with a strong RBP generates far fewer additional requests than a file that is technically complete but inconsistent or unclear on key points.

Can existing firms use a different application route?

Potentially, yes. VARA has a separate transition pathway for Legacy VA Operators — firms that were carrying out VA activities prior to February 2023. This pathway involves the AAN (Activity Acknowledgement Notice), LOP (Letter of Permission), or NOC (No Objection Certificate) route, depending on the firm’s specific circumstances and regulatory status at the relevant time. This route is exclusively available to Legacy VA Operators and is not available to new market entrants. Firms that believe they may qualify for the legacy pathway should seek specific advice on the applicable route before engaging with the standard ATI and Stage 2 process.

Ready to Start Your VARA Application?

Book a VARA Licensing Strategy Call

Whether you are at the readiness planning stage or ready to build the full document pack, a strong VARA application starts before submission — with the right scope, the right file, and the right preparation.