New jurisdictions: consider both where the existing licence can be used and where clients are located
MiCA permits qualifying service providers to provide services across Member States, but Article 65 sets out specific notification arrangements; this does not confer automatic global operating rights. Entering non-EU jurisdictions requires separate review of local market-access, marketing and client-protection rules; even without an office, solicitation and actual services directed at local clients may be relevant. Geographic settings at product launch should align with legal determinations and the scope acceptable to banks.
New products: assess against specific activities rather than the company name
Article 59 of MiCA makes clear that a licence should specify the authorised services, and adding services requires an application to extend authorisation. For example, adding custody to exchange services should not be treated merely as an app version update. Credit payments, yield on balances or products with securities characteristics may also engage rules beyond the original crypto-asset services regime. Whether a partner undertakes the activity, with whom clients contract, and whether the platform still makes performance commitments all require fresh analysis.
Hypothetical scenario: a token with the same name on another chain also warrants review
Suppose a platform previously supported an issuer's native stablecoin on one chain and later plans to support a bridged version on another chain. Similar names do not mean the redemption entity, custody, smart contracts and freeze mechanisms are the same. A new token does not necessarily require a new licence, but legal classification, issuance and circulation conditions, service-provider support and technical risks should be verified; the fact that both tokens trade close to one dollar does not mean their risks are equivalent.
Embed compliance checks into the release process
For each material change, prepare a one-page note: what changed, which entity and market are affected, what regulatory action is required, and who has confirmed it. Then update client contracts, risk disclosures, monitoring rules, safeguarding of funds and exit plans accordingly. Legal advice should correspond to the final version rather than an early product sketch; if key features change again during development, they should be re-verified rather than relying on old advice to endorse a new business.
After launch, also verify that actual traffic matches the approved scope. For example, if the plan is to open only to specific markets but customer service accepts clients from other regions, or a partner automatically routes to an institution that has not been assessed, the paper scope will diverge from reality. Product, compliance and operations teams can jointly review the countries, assets and paths of the first orders and establish fallback arrangements for deviations. The post-launch review here is a risk-management recommendation; it does not mean that trading may begin where approval is required and the licence later supplemented through retrospective spot checks.
Recommended actions
- Establish a launch approval threshold for changes to jurisdictions, services, tokens and partners.
- Confirm notification, extension or new application requirements against the original licence text and current regulatory rules.
- Verify the issuer, chain and redemption arrangements of new assets, and update client disclosures and monitoring configurations.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
References
- MiCA Article 59: Authorisation — ESMA / EU legislature
- MiCA Article 65: Cross-border provision of crypto-asset services — ESMA / EU legislature
- USDC Terms (updated October 15, 2026, applicable to non-EEA holders) — Circle (primary issuer contractual materials, not regulatory rules)
