GENIUS Act vs MiCA: one settlement design for two regimes

The GENIUS Act and MiCA share a headline: both regulate stablecoins, both arrived in roughly the same eighteen-month window, both require reserve backing and disclosure. Underneath, they are built on different architecture, and the gap between them is not academic. It is the reason a US settlement design that looks clean on a whiteboard turns into a compliance scramble the moment a European merchant or supplier enters the flow.

The two regimes, side by side

Dimension	US: GENIUS Act	EU: MiCA (+ PSD2)
Regulatory structure	Single federal issuer-licensing law	EU-wide regulation implemented via national competent authorities
What is licensed	The issuer of the payment stablecoin	The issuer of the e-money token, plus, separately, custody/transfer as a payment service
Effective dates	Signed 18 July 2025; rules proposed Aug 2026, phasing from 18 Jan 2027	EMT rules from 30 June 2024; full framework from 30 Dec 2024; PSD2 overlap from 2 March 2026
Key structural risk	Using a non-compliant issuer's token once sales restrictions phase in	Needing two licences, MiCA plus PSD2, for one activity

The GENIUS Act architecture: one door, one licence

The US model is comparatively simple in shape, if not yet finalised in detail. A single entity type, the qualified payment stablecoin issuer, whether a bank subsidiary, a federal-qualified nonbank, or a state issuer under an equivalent regime, carries the reserve, redemption and disclosure obligations. Everyone downstream, PSPs, merchants, remittance firms, uses the token without needing a parallel issuer licence themselves, though their existing money-transmission and BSA obligations still apply, as covered in our companion piece on GENIUS Act compliance for payment companies. One door, one type of licence to worry about upstream.

The MiCA architecture: two doors for the same activity

MiCA's e-money token rules have applied since mid-2024, and on their own they resemble the US model: an issuer is authorised, reserves and redemption are regulated, and downstream users transact with the token. The complication arrived on 2 March 2026, when a European Banking Authority no-action letter transition period ended and custody and transfer of e-money tokens on behalf of clients was confirmed as a payment service under PSD2, requiring its own separate licence from the same or a partnered entity. A European operator can now face a MiCA authorisation hurdle and a distinct PSD2 payment-services hurdle for what looks, operationally, like one activity: holding and moving a client's stablecoin balance. That is a second door the US regime simply does not have.

Designing one architecture for both

The instinct to build separately for each region is understandable and usually wrong; it doubles engineering cost and creates two systems to maintain instead of one with configurable compliance edges. A design that survives both regimes tends to share three features:

• A single internal settlement ledger, region-agnostic. The core system that tracks who owes what, in which token, settles the same way regardless of jurisdiction. Regulatory wrapper, which licence covers this transaction, which entity is the merchant of record, sits as a configuration layer around the ledger, not baked into its logic. This is the difference between "we can add a market" and "we need a new system for this market."
• Licensed intermediaries carrying the local licence. Rather than the core company holding a US money-transmitter licence, a state trust charter, an EU e-money licence and a PSD2 authorisation simultaneously, most workable designs partner with regional providers who already hold the relevant licence, and let those partners carry the regulatory surface for their region. The core company integrates via API into a licensed partner on each side, rather than becoming a licensed entity everywhere.
• Issuer selection that clears both bars where possible. A handful of large stablecoin issuers are building toward compliant status in both the US and EU. Using one of these where feasible avoids a second-token problem; using a US-only issuer for European flows means either finding an EU-compliant token for that leg or building a bridge, which is a design decision, not an afterthought.

What this looks like in a real settlement flow

Take a PSP settling merchants in both the US and the EU. Under a well-designed shared architecture: a merchant payout is initiated on the internal ledger regardless of region; the system checks which region the payout lands in and routes through the appropriate licensed partner, a US-qualified issuer relationship for a domestic payout, an EU e-money and PSD2-licensed partner for a European one; the settlement token used may differ by region, but the reconciliation, reporting and merchant-facing experience are identical. The merchant does not know or care which regulatory door the payment walked through; the compliance team does, and the system makes that visible without requiring two codebases.

The mistake we see most often

Companies that build for the US first, because the US market is larger or the founding team is US-based, routinely design as if "add Europe later" means adding a market. It means adding a second licensing architecture, potentially a second issuer relationship, and a PSD2 obligation that does not exist in the US framework at all. The cost of that mistake is not theoretical: it is a rebuild, usually discovered under time pressure when a European merchant or investor asks for a timeline that assumes the hard part is already done.

Getting this sequencing right before the architecture is built, rather than after a European customer is already signed, is the single highest-leverage piece of advice we give payment companies expanding across the Atlantic. It is also, not coincidentally, the kind of scoping work an unconflicted advisor is positioned to do that a vendor selling one region's rail is not.

North Settlements provides business advisory services, not legal advice. Regulatory summaries reflect public information as of August 2026 for a fast-moving area of law; confirm current requirements with qualified counsel licensed in each relevant jurisdiction before making architectural or licensing decisions.