Originally reported November 11, 2026, at 13:53 (UTC+8). This is a crypto-payment settlement question, not a Lightning payment-channel arrangement.
Consider the hypothetical posed by Shao Jiadian of Mankun Blockchain Legal Services: a buyer has USDT, a merchant’s Dubai sales company wants to receive dirhams, and an Asian payment provider proposes to accept the token at checkout, convert it and pay the merchant. A Dubai Virtual Assets Regulatory Authority (VARA) Transfer and Settlement license alone may not authorize that entire service. The answer depends on what the buyer is paying for, who handles each step and which permissions each provider holds.
First, identify the purpose of the token transfer
In Dubai’s mainland and VARA-regulated free zones, services involving non-payment tokens such as BTC and ETH for investment, crypto-to-crypto trading, custody or transfer do not, by themselves, require an additional Central Bank payment permission—provided they do not involve purchases of goods, conversion to fiat, remittances or another Central Bank-regulated financial service. Each VARA activity still requires its own appropriate authorization.
The Central Bank law effective September 16, 2025, draws a related distinction: Article 61 places payment services using virtual assets among licensed financial activities, while Article 187 excludes virtual assets used for investment, crypto-to-crypto exchange or trading swaps from that law’s scope, without exempting them from other applicable rules. VARA’s Transfer and Settlement rules, effective June 19, 2025, also require compliance with applicable Central Bank payment and remittance rules; cross-border transfers must be lawful in every jurisdiction involved.

Buyer pays USDT; merchant receives dirhams
Under Article 2(7) of the Central Bank’s Payment Token Services Regulation, a local merchant accepting tokens for ordinary goods or services can accept dirham payment tokens issued by a Central Bank-licensed issuer. Foreign-currency payment tokens issued by a registered issuer may, under that provision, be used only to buy virtual assets or their derivatives. A buyer therefore cannot simply send USDT directly to the Dubai sales company as payment for ordinary goods.
Converting the USDT before paying the merchant in dirhams does not automatically resolve the issue. Under Article 2(4), a licensed or registered provider offering a regulated payment-token service cannot process the token transfer if it knows the USDT is being used to pay for ordinary goods. If the buyer instead makes a separate exchange through a compliant channel and then pays with fiat under their control, the exchange and purchase must each be assessed under their own rules. Whether they are genuinely separate depends in practice on who controls the conversion proceeds and when the purchase is settled.
The original report cited two arrangements with different disclosed details:
- In September 2026, Network International piloted DDSC payments at a Marks & Spencer store in Dubai Festival City. Buyers scanned a checkout QR code with a DDSC-supporting wallet; the merchant could receive DDSC in a wallet or settle in dirhams. DDSC was a dirham payment token issued by a Central Bank-licensed issuer.
- In August 2026, Dubai Duty Free introduced Crypto.com Pay in stores and online. Eligible UAE residents could authorize checkout through a Crypto.com account, while Dubai Duty Free received dirhams. The provider, Foris DAX Middle East FZE, held both a VARA virtual-asset service license and a Central Bank stored-value facility (SVF) license; Crypto.com said it offered the service under the SVF license. Its announcement did not disclose which asset was debited in each transaction, when conversion occurred or the complete flow of funds.
Neither example establishes that another provider can run a USDT-to-dirham checkout under a VARA Transfer and Settlement license alone.

Who holds the token, converts it and pays the merchant?
The Payment Token Services Regulation has applied since August 31, 2024. It covers the relevant category of fiat-referenced payment tokens, including dollar stablecoins such as USDT and USDC. A provider offering an activity within its scope needs the applicable Central Bank permission unless an exclusion or exemption applies—even before it connects that activity to merchant checkout.
A business that holds customers’ payment tokens or the private keys used to hold and transfer them, or receives, holds and transfers tokens for customers, generally needs a Payment Token Custodian and Transferor license. Article 8(3) provides a possible no-objection registration route for foreign-currency payment-token custody and transfer where the applicant already has qualifying virtual-asset custody authorization from the Capital Markets Authority (formerly SCA) or a relevant local authority. A VARA Transfer and Settlement license is not, on its own, custody authorization; eligible applicants must still obtain Central Bank approval.
A business buying or selling payment tokens for compensation, or enabling parties to post and accept sale offers, must assess the Payment Token Conversion licensing requirement or an applicable no-objection registration route. The Article 8(1) route is for operators that meet the regulation’s definition of a virtual-asset exchange platform. A VARA Transfer and Settlement license alone does not qualify its holder for that registration.
Exclusions are activity-specific. Services licensed—or required to be licensed—under retail-payment or stored-value rules follow those rules, and Article 39 addresses the transition from older licenses. Applicants for the two Central Bank payment-token licenses must be UAE-incorporated companies outside financial free zones under Article 6; Article 17 also limits what other business the same company may conduct.
Finally, paying dirhams into the merchant’s account is a separate question. A provider that itself offers fiat acquiring, payment aggregation, payment accounts or funds transfers needs authorization for those activities. Sending proceeds to Asia likewise requires the actual cross-border transfer provider to be authorized for its role. A qualified bank or payment provider can contract directly with the merchant to receive and settle funds. But if the Asian provider signs the merchant contract, collects and forwards proceeds and handles refunds, a bank merely maintaining its account does not make those payment services the bank’s instead.
The practical check is to trace who contracts with the merchant, controls each wallet or account, receives the payment instruction, handles refunds and is responsible if settlement fails. A team supplying only software may fall within a relevant exclusion, but regulated payment initiation or services provided or facilitated through a smart contract still require assessment. Where conversion forms part of a VARA Transfer and Settlement service, the provider must use a VARA-licensed exchange, or obtain VARA approval to use an institution outside Dubai emirate; the transfer provider remains responsible to its customer for completing its service.
The regulation’s UAE scope includes services provided in the UAE or to people there, even if the merchant is abroad. The relevant definition excludes financial free zones such as the Dubai International Financial Centre (DIFC); VARA also does not regulate the DIFC, where the DFSA oversees financial services.
For the hypothetical provider, one possible starting structure in the original analysis is fiat checkout with merchants contracting directly with an appropriately authorized settlement partner, while the Dubai company handles product integration. Taking over collection, transfers or refunds later would require reviewing—and obtaining—the necessary permissions before changing the contracts and funds flow.
Source: techflowpost.com (originally published 2026-11-11 13:53 UTC+8)
