BEFORE YOU BEGIN

  • The maximum legacy CASP transition ended on 1 July 2026.
  • Authorisation has a service scope; check the actual legal entity.
  • A permission to provide crypto services is not a bank-account approval.

Map the activity before naming the permission

Start with what the business does for clients: custody, exchange, order execution, transfers, advice or another activity. A company converting its own treasury and a provider converting assets for clients require different analysis. Write the activity description in operational language before asking counsel to assess the regulatory perimeter.

Article 59 provides the core MiCA authorisation framework. Certain already-regulated financial entities can provide specified services through the Article 60 route, subject to its conditions. “Every company using crypto needs the same licence” is therefore not an accurate starting point.

The transition is no longer a future deadline

As of this article’s review on 18 November 2026, the maximum CASP grandfathering period ending on 1 July 2026 has passed. Some national transitional periods ended earlier. ESMA’s April 2026 statement stressed the need for authorisation or orderly cessation of the relevant services.

When checking a counterparty, do not treat an old national registration or an application receipt as equivalent to current permission. Match the contracting entity, authorised services and any status changes against official records. Save a dated record of the check rather than relying on a sales presentation.

Build an evidence-led application project

Article 62 requires an application package covering the business and its control arrangements, with service-specific information. A practical implementation plan turns those requirements into named owners, approved documents and evidence that the process works.

  • Map each intended service to the relevant control and responsible person.
  • Keep governance, ownership and operating documents consistent.
  • Test the link between customer onboarding, transaction monitoring and escalation.
  • Describe the systems and third parties actually used, not a future ideal design.

Keep permission and commercial readiness separate

An authorisation assessment is not the same project as securing banking, liquidity, custody or a suitable payout route. Track those dependencies alongside the regulatory work. A provider can be authorised for one service and still be unsuitable for your particular asset, transaction size or operational needs.

For a launch decision, retain a short sign-off file: service scope, legal assessment, current register evidence, counterparties and remaining conditions. Review the file when the business changes. This article is a map of the questions; the application and perimeter decision require the relevant professional review.

Read the source in context. Provider policies, eligibility and national implementation can change. This field note explains an operating framework, not an account approval or individual legal opinion.

Back to all field notes