Counterparty status
Transfers to unregulated counterparties are prohibited, so assess the receiving VASP's regulatory status before the transfer proceeds and record it.
The UAE has no single crypto regulator.
Dubai's VARA licenses virtual asset activity in Dubai outside the DIFC, ADGM's
FSRA and DIFC's DFSA cover their free zones, the federal CMA covers security
and commodity tokens, and the Central Bank (CBUAE) covers payment tokens
(stablecoins). A VARA-compliant build maps the VARA Rulebooks onto your
custody, AML and Travel Rule, technology and market-conduct controls, and no
regulator certifies software, so your licence application is the test. This document is for FinTech founders,
digital asset exchanges and Web3 funds in Dubai and Abu Dhabi. It also corrects
several points in the usual vendor pitch, because some commonly repeated claims
are not in the rulebooks.

A 2025 CMA-VARA partnership means VARA-licensed providers can serve the wider UAE outside DIFC and ADGM without a separate federal licence, according to DLA Piper's October 2026 summary. How CBUAE's payment token rules sit beside VARA and CMA licences is still described as unclear by some law firms, so get counsel's read before launching any stablecoin feature.
| Regulator | Territory | Covers | When it applies to you |
|---|---|---|---|
| VARA | Dubai, excluding DIFC | Licensing and supervision of virtual asset activities under its Rulebooks (company, compliance and risk, technology, market conduct, custody, exchange, issuance) | You operate an exchange, custody, broker-dealer or issuance business in Dubai |
| ADGM FSRA | ADGM free zone, Abu Dhabi | Virtual asset activities as regulated activities needing a Financial Services Permission; accepted virtual assets; fiat-referenced token framework | Your entity is in ADGM |
| DFSA | DIFC, Dubai | Crypto token regime; firms assess token suitability themselves, at least every six months | Your entity is in DIFC |
| CMA (formerly SCA) | Federal, onshore | Security and commodity tokens; a Virtual Assets Framework from April 2026 widens regulated activities from three to eight | You serve onshore customers beyond Dubai |
| CBUAE | Federal | Payment tokens (stablecoins) under the Payment Token Services Regulation | You issue, convert, custody or transfer dirham or foreign payment tokens |
Three corrections to the common pitch, which are points I could not find in the rulebook text I read: • MPC is not required. VARA sets key-control outcomes and asks firms to consider multi-signature approaches. MPC wallets are one valid way to meet them. • In-country hosting and NESA alignment are not stated in the Technology and Information Rulebook. It requires compliance with data protection laws on where data may be stored and gives VARA access to records wherever they are held. Confirm any residency requirement with counsel and your data protection analysis. "Continuous detection of spoofing, wash trading and layering" is not in the Market Conduct Rulebook text I read. Build surveillance anyway, but cite the specific VARA provision before you present it as a mandate.
| Pillar | What the VARA Rulebooks say | Architecture pattern | Evidence to keep |
|---|---|---|---|
| Custody and segregation | No rehypothecation; a separate wallet for each client holding only that client's assets; the VASP must control each asset at all times; custody sits in a separate legal entity from group members running other activities; keys encrypted, backups stored separately, seed phrases split into at least two parts; multi-signature approaches to be considered | Per-client wallet register; key ceremony and recovery runbooks; MPC or multisig custody tooling as one way to meet the key-control rules; automated wallet-to-ledger reconciliation | Wallet register, reconciliation records, monthly client statements, independent audit of hot and cold transfers, audit trail kept at least eight years |
| AML/CFT and Travel Rule | For transfers above AED 3,500, the sending VASP holds originator name, wallet or account and address plus beneficiary name and wallet or account before transferring; receiving VASPs hold it before releasing assets; due diligence on counterparty VASPs; manage unhosted-wallet risk | Travel Rule data capture in the transfer flow; hold-and-release state for unscreened counterparties; chain analytics and sanctions screening as pre-transfer checks | Counterparty due diligence files, Travel Rule logs, screening results, risk assessments |
| Technology and data | A CISO separate from the Compliance Officer; independent penetration testing at least annually and before new systems; independent smart contract audits at least annually and before new deployments; material incidents reported to VARA within 72 hours; annual business continuity test; compliance with UAE and foreign data-location rules | Segregated environments, change control tied to testing, tamper-evident logs, incident runbook with a 72-hour clock | Test reports, audit reports, incident log, BCDR test records |
| Market conduct | Insider lists kept at least eight years; ban on own-account trading with limited exceptions; written standards for listing each virtual asset, including price-manipulation susceptibility | Listing workflow with documented due diligence; order and trade records; surveillance alerts (see the market conduct section for what is and is not mandated) | VA Standards assessments, insider lists, trade records |
VARA's Travel Rule applies to transfers above AED 3,500. Before sending, you must hold accurate originator information (name, wallet or account, address) and beneficiary information (name, wallet or account). Receiving VASPs must hold the same before giving clients access to the assets. Both sides must produce it to VARA on request.
Transfers to unregulated counterparties are prohibited, so assess the receiving VASP's regulatory status before the transfer proceeds and record it.
Dealings are not permitted, so screening must identify and block them.
Transfers need enhanced due diligence, including extra identification and source-of-funds checks.
Client AML/CFT ratings are to be refreshed at least every three months, with enhanced measures for high-risk clients.
AML/CFT records are to be kept for at least eight years.
Monitor for transfers structured to stay under AED 3,500.
Engineering implications: capture Travel Rule fields at the point the transfer is requested, not afterwards; put every transfer in a hold state until counterparty checks pass; and make rejection a first-class path, because blocked transfers will be routine. The rulebook text I read does not name a messaging protocol, so choose Travel Rule protocols by which counterparties you need to reach. Chainalysis or Elliptic are common analytics vendors, and neither is mandated.
The law-firm summaries are not VARA's primary text, and VARA notes that the Arabic text prevails, so read the circular itself before finalising controls.Two practical points. VARA's issuance framework does not permit dirham-denominated fiat-referenced virtual assets, so a dirham stablecoin is a CBUAE matter, and licensed dirham tokens number three to four depending on the source, so confirm the current list. And the usual pitch of "open banking API integration with WPS" does not describe a real integration path. WPS only matters if you are building payroll for UAE employers, in which case you integrate through your bank or exchange house. For fiat on-ramps, expect to connect through a licensed bank or payment provider, so design a payment-provider abstraction that can switch rails without touching custody or ledger code.
| Rail | What it is | What it means for a VARA-regulated build |
|---|---|---|
| CBUAE Payment Token Services Regulation | Licensing for issuing, converting, and custody and transfer of payment tokens (stablecoins) | Dirham tokens need a CBUAE licence and may only be issued to UAE residents; foreign tokens are restricted to uses such as buying virtual assets; algorithmic stablecoins and privacy tokens are prohibited |
| Aani | CBUAE instant payments platform run by Al Etihad Payments, launched October 2023 | About three-second settlement and an AED 50,000 per-transaction cap, per a 2026 industry summary; integration is uneven across banks, exchange houses and wallets, so check your banking partner |
| Open Finance (AlTareq) | CBUAE Open Finance Regulation, Circular 3/2025, with a central platform run by Nebras | Phase 1 (banks and insurers) is in force; the later phase covering fintechs, exchange houses and payment providers has no announced date; activities regulated only by DFSA or FSRA are outside it |
| Wage Protection System (WPS) | MOHRE's channel for paying private-sector salaries through accredited banks and exchange houses | A payroll compliance system, not a crypto or open banking rail |