Three legally distinct forms of digital money now operate in the UAE: tokenised deposits, stablecoins, and the Digital Dirham. Banks keep asking me which one to build first. The answer is straightforward once you look at the legal structure underneath each one - only one of them is a direct bank liability with no licence gap.
Start with what each instrument actually is. A tokenised deposit is a bank's own deposit liability, issued on a distributed ledger, legally equivalent to a traditional deposit. It requires no new licence beyond the one the bank already holds. A stablecoin is a licensed non-bank issuer's liability pegged to fiat, governed in the UAE by the Payment Token Services Regulation - a Dirham Payment Token if AED-denominated, requiring a full CBUAE licence, or a Foreign Payment Token if non-AED, requiring CBUAE registration. A CBDC - the Digital Dirham - is a central-bank liability outright; banks don't issue it, they distribute it to customers through CBUAE-approved wallets. It's in advanced pilot stage as of July 2026, with full commercial launch targeted for late 2026.
Same word, three different balance sheets
The industry talks about all three under the umbrella of "digital money," which obscures the point that matters most to a bank's board: where does the liability sit, and under whose licence. A stablecoin issuer is either your bank operating under a Dirham Payment Token licence, or a third party you now have counterparty exposure to. A CBDC is the central bank's liability - you're a distribution channel, not an issuer. A tokenised deposit is the one instrument where the liability, the licence, and the balance sheet are all already yours.
Only one of them is a direct bank liability with no licence gap - and that's the one you can launch fastest.
The market is already proving this out
HSBC UAE didn't wait for the stablecoin conversation to resolve. It launched a live tokenised deposit programme on 22 June 2026 - a single-bank, closed network covering AED and five other currencies, serving corporate and institutional clients. It's the clearest in-market precedent so far for a bank issuing its own liability on-chain, and it did so without seeking a PTSR licence, because a tokenised deposit doesn't require one.
That doesn't mean stablecoins are irrelevant - the opposite. The UAE stablecoin market is active and getting more crowded: AE Coin has been live since October 2024 as the first licensed AED stablecoin, Zand Bank's AED stablecoin followed in November 2025, RAKBank received in-principle approval in January 2026, and USDU launched the same month as the first USD-backed Foreign Payment Token with reserves at UAE banks. USDC and RLUSD gained ADGM and DIFC recognition by December 2025. The AED Sovereign Stablecoin from the ADQ, FAB and IHC consortium settles on ADI Chain and expanded to retail via VARA-regulated platforms in July 2026, with over AED 150 million transacted. PTSR - CBUAE Circular 2/2024 - governs all of this, and its transitional period ended 14 June 2025; it is now fully in force.
Sequencing, not either/or
The strategic point isn't to pick one instrument and ignore the others. It's sequencing. Tokenised deposits carry the lowest regulatory lift because they need no new licence, so they should be the first thing a bank builds. Stablecoin issuance and CBDC distribution are capabilities you add on the same underlying platform once the tokenised deposit infrastructure is proven - not separate projects requiring separate technology stacks.
That's the architecture decision we make explicit in every deployment of our orchestration platform. The platform is built to hold fiat and tokenised deposits side-by-side on one bank-owned ledger, so the institution that starts with the defensible move - a tokenised deposit - isn't rebuilding anything when it's ready to add stablecoin issuance or Digital Dirham distribution. Start with the liability you already own the licence for. Add the rest when the regulation and the market are ready for it.