Updated 10 September 2026: the September reconciliation deadline in the original article is real. But the old checklist was too broad about which technology businesses Article 62 captures.
The Central Bank of the UAE has now published a detailed FAQ on Federal Decree-Law No. 6 of 2025. Its clarification is important: Article 62 does not create a new category of licensed financial activity simply because technology is involved. It preserves CBUAE jurisdiction when an activity already listed in Article 61 is carried on through technology, whether directly or indirectly.
| THE ROBIUS READ: Do not ask, “Does my app touch money?” Ask, “What exact Article 61 financial activity is my company itself practising, offering, issuing, arranging, promoting, marketing or facilitating?” Pure software, infrastructure and technical-service providers are not automatically licensed by CBUAE merely because a bank or payment company uses their technology. But a platform cannot escape financial regulation by calling itself software, Web3, infrastructure or a protocol if it is actually carrying on or facilitating a licensed financial activity. The Article 184 reconciliation period is now at its end. If your model sits near that boundary, this is a regulatory-scope question for CBUAE or qualified UAE counsel, not a three-question internet test. |
The Deadline Is Real — but Do Not Build Your Plan Around One Boundary Day
Federal Decree-Law No. 6 of 2025 entered into force on 16 September 2025. Article 184 requires agencies and persons subject to the law to reconcile their positions with its provisions within one year from entry into force. The CBUAE Board may extend that period.
CBUAE’s legislation FAQ, checked and displaying an update date of 10 September 2026, says the reconciliation period “ends one year after” the 16 September 2025 effective date. It does not announce a general extension on that page.
There is a small public interpretation difference over the final calendar day. Norton Rose Fulbright describes persons subject to the law as having until 16 September 2026 to reconcile. A September 2026 Hadef & Partners update calculates the current deadline as 15 September 2026. The statutory text itself says “within a period of one year.”
For a business whose compliance depends on that distinction, Robius would not recommend waiting for the final day. Treat the reconciliation window as closing now, confirm the applicable date directly with CBUAE or counsel, and document the position before the boundary becomes relevant.
Article 62 Does Not Create a New “Technology Licence”
This is the largest correction to the July article.
CBUAE’s current FAQ explicitly says Article 62 does not create new categories of licensed financial activities. Instead, if an activity already listed in Article 61 is conducted using “any technological means, technique, form, or model,” it remains within CBUAE’s licensing, regulatory and supervisory perimeter where the law applies.
The principle is activity-based regulation, not technology-based regulation. Blockchain, tokenisation, DeFi, a mobile app, an API, a protocol or another infrastructure model does not change the underlying regulatory question.
That means the old Robius test — “would removing your platform break the financial transaction?” — was invented shorthand, not a CBUAE test. A technically essential vendor can still be a pure technical service provider. Conversely, a platform can be only one layer in a transaction and still fall within scope if it itself carries on, offers, issues or facilitates a licensed financial activity.
Start With Article 61: What Is the Underlying Financial Activity?
CBUAE’s current FAQ lists prominent Article 61 activities that require Central Bank licensing, including:
- taking deposits, including Shari’ah-compliant deposits;
- providing credit facilities;
- providing funding facilities, including Shari’ah-compliant funding;
- providing open finance services;
- currency exchange and money-transfer services, including instant transfers;
- payment services using Virtual Assets;
- stored-value services, retail payments and digital-money services;
- arranging, promoting or marketing Licensed Financial Activities;
- certain principal dealing in financial products affecting a Licensed Financial Institution’s financial position; and
- insurance, reinsurance and Insurance-Related Professions, including Takaful and Re-Takaful.
The Board can add, delete or amend activities under the mechanism described in the law. So a founder should use the live CBUAE framework, not freeze this list into a permanent taxonomy.
Pure Technical Service Providers Are Not Automatically in Scope
The July article correctly sensed that there was an important technology-provider boundary, but it did not have the CBUAE clarification that now exists.
CBUAE now says Article 62 does not aim to regulate, license or prohibit technology service providers in that capacity. Providers of software, infrastructure, purely technical solutions or emerging technology fall outside the licensing perimeter unless they themselves engage in, present themselves as engaging in, offer, issue or facilitate an Article 61 financial activity, directly or indirectly.
The FAQ goes further: where a technology provider supplies software, infrastructure or technological solutions exclusively for the benefit of a licensed financial institution, that provision by itself is not treated as practising, offering, issuing or facilitating the financial activity for this purpose.
So “our software connects to a bank” is neither an automatic exemption nor an automatic licensing trigger. You need to identify what the technology company itself does in the regulated chain.
Where the Risk Boundary Gets More Serious
A technology business deserves closer regulatory review when its own role begins to look like the financial activity rather than neutral technology supplied to someone else.
Examples that CBUAE’s FAQ itself uses include operating a payment service, wallet service or Stored Value Facility, or otherwise professionally offering or facilitating a regulated financial service. It also specifically points to decentralized platforms, protocols and infrastructure that facilitate, enable or allow services such as deposits, payments, stored value or lending.
Article 61 also expressly includes arranging, promoting and marketing Licensed Financial Activities. A business therefore should not assume it is outside scope merely because a separate institution executes the final regulated transaction.
The exact legal line can depend on contractual role, customer journey, representations, control of funds or instructions, remuneration, discretion and the financial activity involved. That is why a generic product checklist cannot give a definitive licensing answer.
Five Better Questions Than the Old Three-Question Test
| Question | Why it matters |
|---|---|
| Which exact Article 61 activity is present? | Article 62 follows the underlying licensed activity; it does not regulate technology merely for being technology. |
| What does our legal entity actually do? | Separate the app brand from the company contracting with users, moving instructions, arranging products or supplying software. |
| Are we only a technical supplier to a licensed financial institution? | CBUAE explicitly says purely technical provision exclusively for an LFI is not automatically treated as practising or facilitating the financial activity. |
| Do we present, offer, issue, arrange, promote, market or facilitate the financial service ourselves? | Those functions can move a platform away from the pure-technology boundary and some are expressly listed in Article 61 or CBUAE’s Article 62 explanation. |
| Which regulatory perimeter applies? | The CBUAE law does not generally apply inside UAE financial free zones or to institutions supervised by their financial-free-zone authorities, although cross-perimeter activity requires separate analysis. |
DIFC and ADGM Need Their Own Perimeter Analysis
CBUAE’s FAQ confirms that, under Article 2, the Decree-Law does not apply to financial free zones within the UAE or to financial institutions under the supervision of those zones’ authorities.
That means DFSA-regulated financial activity in DIFC and FSRA-regulated financial activity in ADGM cannot simply be analysed as though CBUAE were the only regulator. But a company’s group structure, branches, mainland activity and services crossing regulatory perimeters can still require separate analysis.
The old article’s phrase “the new law governs the UAE mainland” was useful shorthand but too simple for multi-jurisdiction groups.
The AED 1 Billion Number Needs Context
The original article used the AED 1 billion maximum and criminal liability as a single warning. Both are real features of the law, but they are not one automatic penalty for missing the reconciliation date.
CBUAE’s current FAQ says Article 168 provides a range of administrative and financial sanctions. These can run from a caution and corrective requirements through restrictions and a financial penalty ranging from AED 100,000 to AED 1 billion. In some cases, the financial penalty can instead be linked to up to ten times the funds involved or illicit enrichment, as determined under the law.
The FAQ separately says criminal offences under Articles 169 to 180 can carry imprisonment and financial fines ranging from AED 50,000 to AED 500 million, depending on the offence.
So “you miss September 16 and owe AED 1 billion” would be nonsense. The relevant consequence depends on what obligation was breached, what activity was carried on and which enforcement provision applies.
What to Do Before the Reconciliation Window Closes
- Map products by legal entity: list every UAE entity, customer-facing product and regulated partner.
- Map each financial function: deposits, payments, stored value, credit, remittance, open finance, insurance, arranging, promotion and any other Article 61 activity relevant to the model.
- Separate pure technology from financial-service conduct: document what your platform controls and what the licensed partner controls.
- Review contracts and marketing: what your company says it offers can matter alongside technical architecture.
- Check the regulator perimeter: CBUAE, DFSA, FSRA and other specialist regimes should not be collapsed into one licence question.
- Record the conclusion and evidence: keep the legal analysis, partner licences, agreements and any regulator correspondence supporting the position.
- Escalate genuine edge cases now: if the business is close to the line, seek CBUAE clarification or qualified UAE regulatory advice rather than relying on this article or a self-made flowchart.
The Bottom Line
The September 2026 reconciliation window is real. The original Robius article was right to tell affected businesses not to ignore it.
But it overstated Article 62 by turning a broad technology provision into an unofficial “does your app touch the transaction?” licensing test. CBUAE’s own current clarification is better: start with the licensed financial activity in Article 61, then ask what role the technology company itself plays in providing, offering, issuing or facilitating it.
Pure technical providers are not automatically regulated just because their software is important to a financial institution. Equally, a company cannot avoid regulation by putting a regulated financial activity behind an API, protocol or app and calling itself technology.
With the Article 184 period now at its end, businesses that may be subject to the law should stop trying to solve the issue with labels and document the actual activity, entity, counterparty and regulator.
Sources
• Central Bank of the UAE — Legislation FAQ: current official explanations of Article 61 licensed financial activities, Article 62 technology scope, pure technical-service-provider boundary, financial free zones, sanctions and Article 184 reconciliation period — centralbank.ae
• CBUAE Rulebook — Article 184: one-year reconciliation period from the Decree-Law’s entry into force and Board power to extend — rulebook.centralbank.ae
• Norton Rose Fulbright: analysis of Federal Decree-Law No. 6 of 2025 and interpretation of the transition period as running until 16 September 2026 — nortonrosefulbright.com
• Hadef & Partners, September 2026: current reconciliation-deadline update calculating the current deadline as 15 September 2026 and noting no general extension announced at publication — hadefpartners.com
Checked 10 September 2026. This article is general information, not a legal opinion on whether any particular company needs a CBUAE licence. The law, implementing framework and any extension decision can change; confirm your own position with the regulator or qualified UAE counsel.
Robius.news — Dubai, UAE — 2026 | Built to be first. Built to be trusted.
