Issuing an AED-Backed Stablecoin: CBUAE Requirements for Payment Token Issuers

 The AED stablecoin issuance requirements set out by the Central Bank of the UAE stand apart from every other digital asset framework operating in this country, and the distinction is not a technicality. It is a jurisdictional line that determines which regulator you answer to, which capital thresholds apply, and whether your token can legally reference the national currency at all. Anyone building a payment token business around the dirham needs to understand this line before drafting a single clause of their business plan.

Why AED Reference Changes Everything

Virtual asset regulators across the UAE have carved out a clear boundary. VARA's own Virtual Asset Issuance Rulebook states plainly that any Fiat-Referenced Virtual Asset purporting to maintain a stable value against AED cannot be approved under VARA's framework. That authority sits exclusively with the Central Bank. It is a deliberate design choice, not an oversight, and it reflects how seriously the UAE treats anything that touches its sovereign currency.

This matters because founders sometimes assume a virtual asset license from VARA, ADGM, or another free zone regulator gives them a runway to issue dirham-pegged tokens. It does not. The moment your token references AED value, you are in CBUAE territory, full stop. There is no dual pathway, no overlap, no choice of regulator based on convenience.

What the CBUAE Actually Requires

The Central Bank's payment token framework treats stablecoin issuance as a licensed activity, not a side business bolted onto an existing money services operation. A few requirements consistently surface when advising issuers in this space.

Reserve backing sits at the center of the framework. Issuers must hold reserve assets that match the value of tokens in circulation, typically in low-risk, highly liquid instruments held with licensed UAE financial institutions. This is not a suggestion. Regulators expect issuers to demonstrate, on an ongoing basis, that every token in circulation is backed one to one, and that redemption can happen without friction or unnecessary fees.

Capital adequacy follows a similar logic to what we see in adjacent frameworks. VARA's own asset-referenced token rules, for comparison, mandate paid-up capital of at least AED 1,500,000 or 2% of average reserve value over a trailing 24 month period, whichever is higher. The CBUAE's approach to payment tokens tracks similar prudential thinking, scaled to the risk profile of a currency-referenced instrument rather than a multi-asset basket.

Governance and reporting obligations round out the picture. Licensed persons must maintain their books and records within the UAE, remain available for Central Bank examination, and operate strictly within the scope of whatever license they are granted. The CBUAE payment token licence is not a blanket permission to issue any stablecoin structure an issuer dreams up. It is scoped, conditional, and subject to variation if the Central Bank identifies emerging risk.

The Practical Path for Issuers

Anyone serious about launching an AED-referenced payment token should start with a structural question rather than a product question. Is this token designed purely for use within a payments rail, or does it touch the broader virtual asset ecosystem? That distinction shapes which rulebook applies and, in some adjacent structures, whether VARA's Money Services Provider restrictions even permit crypto token involvement at all.

From there, the practical steps tend to follow a familiar sequence. Founders map their reserve structure and banking relationships first, since no application moves forward without evidence of where reserve assets will sit and how they will be safeguarded. They then build out compliance infrastructure, AML and CFT controls, and the reporting mechanisms the Central Bank will expect to see functioning before any license is granted, not after.

Timelines vary considerably depending on how mature the applicant's existing financial infrastructure is. An entity that already operates as a licensed payment service provider will typically move faster than one starting from a pure technology background with no prior regulatory footprint in the UAE.

Compliance as a Foundation, Not an Afterthought

What separates issuers who succeed from those who stall out mid-application usually comes down to sequencing. Building the token first and figuring out digital asset compliance UAE requirements later is a pattern that rarely ends well. Reserve structuring, banking partnerships, and governance frameworks take months to establish properly, and the Central Bank's review process rewards applicants who arrive with these pieces already in place rather than promising to build them post-approval.

The dirham stablecoin space in the UAE remains relatively young, but the regulatory architecture around it is not improvised. It draws on years of banking supervision experience layered onto a new asset class. Issuers who respect that foundation, rather than treating it as a checklist to satisfy quickly, tend to build the kind of trust that lets a payment token actually function at scale.