Compliance & Governance6 min read

Building a cross-border compliance framework for a UAE fintech expanding into Europe

A UAE-licensed payment services provider was preparing to extend its operations into three European markets. We designed a compliance architecture that satisfied both CBUAE requirements and the incoming MiCA obligations.

The challenge

The client held a Central Bank of UAE payment services licence and had been operating a cross-border remittance product for two years. Its expansion plan targeted Germany, the Netherlands, and Poland — three markets with materially different regulatory environments, all of which would be subject to MiCA from Q1 2027 given the client's stablecoin settlement layer.

The client's existing compliance function had been built for a UAE-only operation. It had no experience with GDPR, no PSD2 passporting structure, and no understanding of how MiCA's e-money token provisions would interact with its existing CBUAE licence. The board had set a twelve-month timeline for the first European market launch.

Our approach

We began with a regulatory mapping exercise: for each target market, we identified the applicable licensing requirements, the passporting options available under PSD2, the GDPR obligations that would attach to the client's data flows, and the MiCA provisions that would apply to its stablecoin settlement layer.

The mapping revealed that a direct licensing approach in all three markets simultaneously was not achievable within the twelve-month timeline. We recommended a sequenced strategy: establish a PSD2-licensed entity in the Netherlands first, use the European passport to enter Germany and Poland, and use the intervening period to build the MiCA compliance infrastructure before the Q1 2027 deadline.

We drafted the compliance architecture for the Dutch entity — AML/CFT policies calibrated to AMLD6, a GDPR data processing framework, and a MiCA readiness roadmap — and coordinated with a Dutch regulatory law firm for the licence application itself. We also updated the client's CBUAE compliance documentation to reflect the cross-border structure, ensuring the UAE licence remained in good standing throughout.

The outcome

The Dutch entity received its PSD2 licence ten months after the project commenced — two months ahead of the board's target. The client launched its remittance product in the Netherlands and Germany within the twelve-month window, with Poland following three months later using the passport.

The MiCA readiness programme was completed ahead of the Q1 2027 deadline. The client's stablecoin settlement layer was restructured as a MiCA-compliant e-money token, and the Dutch entity submitted its MiCA notification to the AFM on schedule.

Lessons from this matter

  • —Sequencing matters as much as substance. A technically sound compliance framework delivered too late is not a compliance framework — it is a liability.
  • —MiCA and existing UAE licensing obligations are not in conflict, but they require deliberate coordination. Businesses that treat them as separate workstreams create gaps that regulators notice.
  • —The PSD2 passport is a powerful tool, but it requires a genuinely operational entity in the passporting jurisdiction. Regulators in the host states will look through a shell.