Flowdesk Secures Dubai VARA Broker-Dealer Licence After French MiCA Approval
Flowdesk, the institutional crypto market maker backed by Coinbase Ventures and BlackRock, has been granted a full broker-dealer licence by Dubai's Virtual Assets Regulatory Authority (VARA). The approval, announced on 11 August 2026, covers Flowdesk's local entity Flowdesk Omega FZE and authorises it to provide regulated broker-dealer services to qualified and institutional investors in and from the emirate. Coupled with the firm's earlier authorisation in France as a Crypto-Asset Service Provider (CASP) under MiCA, this marks a meaningful moment in the gradual convergence of regulated institutional crypto infrastructure across two very different regulatory regimes. For accounting firms, auditors, and CFOs whose clients interact with institutional market makers, the development has direct implications for counterparty due diligence, AML obligations, and the way transactions are classified in crypto accounting software.
What VARA's Broker-Dealer Licence Actually Authorises
VARA is the dedicated virtual-asset regulator for the Emirate of Dubai, operating under the Dubai Virtual Assets Regulation Law. A broker-dealer licence is one of the more demanding categories within VARA's activity-based licensing framework, permitting the holder to execute trades on behalf of clients, provide market-making services, and offer related custody and compliance infrastructure to institutional counterparties.
Scope of the Flowdesk Omega FZE Authorisation
The licence granted to Flowdesk Omega FZE allows the entity to serve both qualified investors and institutional investors in and from Dubai. The distinction matters for accounting and compliance teams: services directed at qualified investors carry specific suitability and disclosure obligations under VARA rules, while institutional-only mandates typically involve higher transaction thresholds and more prescriptive counterparty-verification requirements. Firms onboarding Flowdesk as a liquidity provider or market-making counterparty will need to confirm which investor category their own engagement falls into, because the applicable VARA conduct rules differ accordingly.
How VARA Fits Into the UAE's Broader Virtual-Asset Architecture
It is worth placing VARA in context. The UAE has a multi-regulator structure for virtual assets. The Securities and Commodities Authority (SCA) covers the federal layer, the Abu Dhabi Global Market (ADGM) through its Financial Services Regulatory Authority (FSRA) governs activities in that free zone, and VARA governs the Emirate of Dubai, including the Dubai International Financial Centre for virtual-asset activities outside DIFC's own financial services perimeter. A VARA licence does not automatically confer authorisation elsewhere in the UAE, and vice versa. Accounting teams servicing clients with UAE operations across multiple emirates should map each entity's activity to the correct regulator before drawing conclusions about a counterparty's regulatory status.
The MiCA Connection: Building a Dual Regulated Footprint
Flowdesk's VARA approval did not arrive in isolation. The company had already received authorisation as a CASP under MiCA, the EU's Markets in Crypto-Assets Regulation, through its French entity. MiCA creates a passportable licence across all EU member states, meaning a CASP authorised in France can, subject to notification procedures, provide certain services across the single market.
What MiCA CASP Status Requires
MiCA CASP authorisation requires compliance with ongoing capital requirements, organisational safeguards, conflicts-of-interest policies, and transaction-reporting obligations. For market makers specifically, MiCA imposes transparency requirements around liquidity provision arrangements. The AMF in France is the national competent authority responsible for supervising French-authorised CASPs, and it has been active in both granting and, where conditions are not met, withdrawing PSAN registrations. Accounting firms advising French clients should already be familiar with the AMF's evolving expectations, as we covered in our analysis of the AMF PSAN deregistration and what it means for French crypto firms.
Why the AE-FR Combination Signals a Strategic Direction
The combination of a Gulf broker-dealer licence and an EU CASP authorisation is not coincidental. Institutional market makers that operate in multiple jurisdictions face the challenge of serving clients who are themselves regulated in different places. A client in Paris and a client in Dubai may both require liquidity services, but the regulatory perimeter around each engagement differs substantially. By holding licences in both jurisdictions, Flowdesk can structure bilateral arrangements that satisfy the local regulatory requirements of each counterparty's home regulator. For a CFO or treasury team evaluating which liquidity providers to whitelist, this dual status is a meaningful piece of counterparty due diligence evidence, though it does not replace a full review of licence conditions, capital adequacy, and operational controls.
The Broker-Dealer Role in Institutional Crypto Markets
Broker-dealers occupy a specific structural position in crypto markets that differs from exchanges, custodians, and pure OTC desks. A licensed broker-dealer acts as an intermediary between buyers and sellers, often internalising flow to provide price improvement, and may also hold client assets in a regulated custody arrangement. In traditional finance, broker-dealers are subject to capital requirements, best-execution obligations, and client-money segregation rules. Virtual-asset regulators including VARA have adapted those concepts to the crypto context, though the precise rules vary by jurisdiction.
Accounting Implications of Transacting Through a Regulated Broker-Dealer
For accounting purposes, the regulatory status of a counterparty influences several downstream decisions. First, it affects the classification of the counterparty relationship for AML purposes: a regulated broker-dealer operating under VARA or MiCA may qualify for simplified due diligence in some frameworks, though firms should confirm this with their compliance counsel before relying on it. Second, it affects how transaction costs are captured. Broker-dealer spreads and commissions may need to be distinguished from exchange fees and recorded differently depending on the applicable accounting standard, whether IFRS, US GAAP, or a jurisdiction-specific framework. Third, where the broker-dealer also provides custody, the accounting team needs to determine whether digital assets held in that arrangement meet the recognition criteria for assets on the client's own balance sheet, or whether there are disclosure requirements around custodial arrangements.
Firms using crypto accounting software to automate transaction classification should verify that their system can handle the entity-level regulatory status of counterparties as a tagging variable. Without that granularity, AML transaction monitoring and financial-statement note disclosures may not reflect the true nature of the relationship. Our coverage of the FATF DeFi COSI test and its AML implications for accounting firms sets out the broader context for how regulators are thinking about intermediary identification across the digital-asset value chain.
AML and KYC Considerations for Counterparty Onboarding
When a client's counterparty obtains a new regulated licence in a jurisdiction as significant as Dubai, the onboarding file does not automatically update itself. AML policies at most regulated firms require periodic counterparty reviews, and a material change in a counterparty's regulatory status, whether positive or negative, typically triggers a mandatory refresh of the risk assessment.
What Accounting Firms and CFOs Should Do Now
Three practical steps follow from this development. First, identify whether any current or prospective clients use Flowdesk as a market-making counterparty, liquidity provider, or custodian. If they do, update the counterparty risk file to record the VARA broker-dealer licence, its scope, and the investor categories it covers. Second, assess whether the new licence changes the applicable KYC tier for that counterparty relationship under your firm's AML policy and the relevant jurisdiction's rules. Third, confirm with your crypto bookkeeping software provider that transaction flows from Flowdesk entities can be tagged with the correct regulatory label at the entity level, not just the asset level. This matters for both financial-statement classification and AML transaction monitoring.
Firms operating in the UAE should also note that VARA's licensing regime includes ongoing supervisory obligations on the licence holder, including periodic reporting and capital maintenance requirements. A counterparty's licence can be varied, suspended, or revoked, so periodic checks against VARA's public register are a prudent addition to any AML compliance calendar.
What This Means for the Broader Institutional Crypto Landscape
Flowdesk is not operating in a vacuum. The announcement coincides with a period of significant activity among institutional crypto intermediaries seeking regulated status in multiple jurisdictions simultaneously. The strategic logic is clear: institutional clients, particularly asset managers, banks, and corporates entering the digital-asset space, are increasingly unwilling to transact through unregulated counterparties. Regulatory authorisation is becoming a baseline commercial requirement, not merely a compliance checkbox.
For accounting firms and CFOs, this trend has a practical consequence. As more institutional intermediaries obtain regulated status across multiple jurisdictions, the complexity of counterparty classification in digital asset accounting software will increase, not decrease. A single market maker may now appear in client transaction data as a VARA-licensed entity for some trades and a MiCA-authorised CASP for others, depending on which legal entity executed the trade. Ensuring that your digital asset accounting software can distinguish between those entity-level classifications and apply the correct accounting and AML treatment to each is no longer an edge case. It is a mainstream requirement for any firm with institutional crypto-active clients.
Frequently Asked Questions
What is a VARA broker-dealer licence and how does it differ from an exchange licence?
A VARA broker-dealer licence in Dubai authorises the holder to execute trades on behalf of clients and provide market-making services to qualified and institutional investors. It is distinct from a virtual-asset exchange licence, which authorises the operation of a trading platform open to a broader range of participants. The broker-dealer category carries specific conduct obligations, including suitability assessments for qualified investors, and is generally considered more demanding to obtain.
Does Flowdesk's VARA licence cover the whole UAE?
No. The VARA licence covers the Emirate of Dubai only, including activities in Dubai outside the DIFC's own regulatory perimeter. It does not extend to activities regulated by the federal Securities and Commodities Authority or to the Abu Dhabi Global Market. Entities operating across multiple UAE jurisdictions need to assess their regulatory position under each applicable regime separately.
What does MiCA CASP authorisation require in France?
MiCA CASP authorisation requires the firm to meet ongoing capital requirements, maintain appropriate governance and internal controls, manage conflicts of interest, and comply with transaction-reporting obligations. In France, the AMF is the supervising authority. A French CASP authorisation can potentially be passported to other EU member states through the MiCA notification procedure, subject to the rules of each host state.
How should accounting firms update counterparty AML files following this announcement?
Firms should identify any client relationships involving Flowdesk, refresh the counterparty risk assessment to document the new VARA licence and its scope, reassess the applicable KYC tier, and set a calendar reminder for periodic register checks against VARA's public licence database. The refresh should be documented in the AML file even if the risk rating does not change, as it demonstrates ongoing due diligence.
Why does the regulatory status of a broker-dealer affect crypto accounting software requirements?
Regulated broker-dealers may be treated differently from unregulated counterparties for AML simplified due diligence purposes, and their fee structures, including spreads and commissions, may need to be recorded differently from exchange fees under applicable accounting standards. Where the broker-dealer also provides custody, additional disclosure or recognition considerations arise. Crypto accounting software needs to capture entity-level regulatory status as a tagging variable so that these distinctions are applied consistently and automatically across all client transaction data.
Source: Cointelegraph