An ADGM applicant does not select a generic “crypto licence” from a simple product list. It identifies each regulated activity in the operating model, applies for the corresponding Financial Services Permission and then works through the prudential, governance and virtual-asset requirements that follow.
This article consolidates Ape Law’s earlier ADGM category, activity-list and FSRA overview pages. It was checked against the FSRA virtual-asset guidance and ADGM rulebook on 22 September 2026.
What Should You Classify First?
Describe the business in verbs rather than labels. Relevant questions include whether the firm will:
- deal as principal, agent or matched principal;
- arrange transactions or provide investment advice;
- manage assets or a collective investment fund;
- provide custody or control client assets;
- operate a multilateral trading facility;
- provide credit, staking or another feature connected to a regulated service; or
- issue, offer or operate infrastructure for a digital security.
One platform can perform several activities. The application, fees, capital, staffing and systems should be built from that complete activity map.
How Do Activities and Prudential Categories Differ?
A regulated activity describes what the firm is permitted to do. A prudential category helps determine the financial-resource and risk requirements applying to the firm. Endorsements, restrictions and virtual-asset requirements may then modify the permission.
That is why a five-row “licence category” chart is rarely enough. Two applicants described as crypto businesses can require very different permissions if one advises professional clients while the other controls assets and operates a trading venue.
Which Operating Facts Change the Route?
| Fact | Why it matters |
|---|---|
| Client asset control | Can engage custody, client-money and safeguarding requirements |
| Order matching or venue operation | Can point toward market-infrastructure permissions |
| Principal risk | Changes the dealing analysis and prudential burden |
| Retail or professional clients | Affects conduct, disclosure and distribution controls |
| Fund or managed-account structure | Changes manager, vehicle and custody questions |
| Token rights | May move the analysis from a virtual asset to a digital security or another product |
| Staking, lending or credit | Must be assessed as part of the actual regulated service |
The classification should match product diagrams, contracts, website language and financial projections. Inconsistent descriptions are a readiness problem, not merely a drafting problem.
What Is Separate From FSRA Authorisation?
The ADGM Registration Authority handles incorporation and commercial registration. The FSRA handles financial-services authorisation. An entity may require both, but registration is not a substitute for Financial Services Permission.
Similarly, an ADGM SPV is intended as a passive holding vehicle and does not authorise an operating financial service. The ADGM SPV guide explains that boundary.
What Should an Application Readiness Pack Contain?
Before filing, assemble:
- a product and transaction-flow map;
- the proposed regulated-activity list and reasoning;
- customer, jurisdiction and distribution assumptions;
- custody, wallet and settlement architecture;
- governance, controllers and senior-management responsibilities;
- AML/CFT, sanctions, market-conduct and risk controls;
- technology, security, outsourcing and business-continuity material; and
- a budget covering regulatory, entity and operating costs.
How Should You Use This Guide?
Use it to prepare the classification discussion, not to self-select a category from a headline. Confirm the current rulebook version and obtain advice based on the complete operating model. Our separate ADGM cost guide explains how activity fees and the virtual-asset add-on combine.
This article provides general information and does not determine an applicant’s permissions, capital or eligibility. ADGM and FSRA requirements must be checked against the current rules and the specific facts.
Stephan Roberto
