An exchange licensed under a national regime discovers that its grandfathering window closes in weeks, not months. The business believed the transitional arrangements bought time to prepare a full MiCA application; instead, the national competent authority now requires authorisation documents, governance attestations and prudential filings before the deadline or the platform goes offline. The legal question turns on what a crypto-asset service provider must complete before national grandfathering ends – and the sequence in which those tasks close the regulatory gap between the old VASP rules and the MiCA regime.
Under MiCA, the Markets in Crypto-Assets Regulation, every entity offering crypto-asset services in the European Union must hold CASP authorisation from a national competent authority. Operators who held a pre-MiCA VASP registration in a member state entered a transitional period that allowed them to continue business while they filed for the new licence. That period is drawing to a close across the Union. The precise end date and the documentation expected vary by member state, but the structural requirement is uniform: file a complete CASP application, demonstrate governance and prudential readiness, and secure authorisation before the grandfathering window shuts. Miss the deadline and the platform cannot legally serve EU clients. This guide sets out the action checklist in the order a business must work it.
What the transitional period was for
The transitional period gave existing VASP-registered operators time to transition from national frameworks to MiCA without an immediate operational shutdown. Under the Regulation, an entity registered under a pre-MiCA regime could continue to provide services in its home member state – but not passport across borders – while it prepared and submitted a CASP application. The period was not a permanent extension of the old rules; it was a filing runway. A business that does not file, or that files an incomplete application, loses the transitional cover and must cease activities.
The common mistake is treating the transitional window as an indefinite grace period. In practice, regulators in the leading hubs expect the application to be lodged weeks before the formal deadline, with all supporting documents complete at submission. An incomplete filing does not preserve the right to operate; the regulator simply rejects it and the business stops. The transitional period ends on a date set by each member state's transposition timeline, and extensions are rare.
Operators we advise routinely underestimate the governance and prudential work that precedes the filing. A CASP application is not a registration form; it is a full authorisation dossier covering the business model, the management team, internal controls, capital adequacy and – for platforms offering custody – safeguarding arrangements. The application must be ready when the filing window opens, not assembled in the final weeks.
Who must file before the deadline
Any entity that provides crypto-asset services to clients in the EU and relied on a national VASP registration to do so must file for CASP authorisation before its member state's transitional deadline. The regulated perimeter under MiCA includes exchanges, custody providers, order execution, portfolio management, advice, placing and receiving/transmitting orders. If the business offers any of these services, it needs the authorisation. The MiCA definition of "crypto-asset service" is activity-based, not label-based; calling the platform a "technology provider" does not remove it from scope if it holds client assets or executes trades.
For entities operating in multiple member states, the analysis depends on the licensing structure. A business that held a VASP registration in one state and served clients in others under that state's regime must now choose a single home-state competent authority for the CASP licence and file there. The CASP authorisation, once granted, allows EU-wide passporting under the mutual recognition framework. The operator cannot remain under different national transitional regimes in parallel; it picks one home authority and consolidates the application there.
Token issuers face a related but separate deadline. Entities issuing asset-referenced tokens or e-money tokens under MiCA must secure the corresponding ART or EMT authorisation and cannot rely on VASP grandfathering for issuance activities. The issuer analysis sits outside this guide's scope, but the deadlines overlap; a platform that both issues a stablecoin and operates an exchange must address two authorisation tracks simultaneously.
The governance and management files
The first substantive block in a CASP application is the governance file: organisational structure, management bios, fit-and-proper attestations, anti-money-laundering procedures and conflicts-of-interest policies. The competent authority expects named individuals in the management roles and evidence that those individuals meet the knowledge, experience and integrity standards under the relevant provisions. The application must include CVs, declarations of prior regulatory history and – in many member states – certified background checks or professional references.
The governance structure must show a clear reporting line from the compliance function to the board, independent oversight of custody operations where applicable, and documented escalation procedures for AML alerts and market-abuse suspicions. The regulator will not authorise a platform that runs compliance as a side task of the operations team. The structure must be in place and evidenced before submission; regulators in the leading hubs reject applications that promise to "hire a compliance officer post-approval."
For platforms operating under a parent group, the application must disclose the group structure, any shareholders holding a qualifying interest, and the source of the parent's funding. The competent authority conducts a fit-and-proper assessment not only of the management but also of controlling shareholders. A complex or opaque ownership chain slows the vetting process and may trigger additional information requests. The governance file must answer these questions in the initial submission, not in a follow-up round.
The prudential and capital requirements
MiCA imposes own-funds requirements that vary by the type and scale of the crypto-asset services the entity provides. The capital must be held in liquid form and available to absorb losses; it cannot be locked in operational infrastructure or in a token treasury. The competent authority will ask for audited financials, a capital-adequacy calculation and evidence that the own funds meet the regulatory minimum at the date of application. The specific threshold depends on the licence category and the member state's implementation choices.
The common mistake is waiting to raise the capital until the application is ready. The own funds must be in place when the business files, and the auditor's attestation must be current. If the platform relies on a capital injection from an investor or parent, that injection must clear and appear on the balance sheet before submission. A letter of intent to fund does not satisfy the requirement.
For custody providers, the prudential block also covers professional-indemnity insurance or an equivalent guarantee. The insurance must be proportionate to the risks inherent in safeguarding client crypto-assets and must cover loss from operational failure, theft or cyberattack. The policy must be live at filing, and the application must attach the certificate and a summary of the coverage terms. Regulators in jurisdictions with significant crypto activity expect high coverage limits; generic technology errors-and-omissions policies often do not suffice.
The safeguarding and segregation arrangements
If the CASP will hold or control client crypto-assets, the application must describe the safeguarding arrangements in detail: wallet architecture, key-management protocols, segregation of client assets from the firm's own holdings, and the recovery process in the event of insolvency or operational failure. The regulator expects a written policy, technical diagrams and evidence that the arrangements are already operational. A CASP cannot begin safeguarding client assets post-authorisation and work the policy out later; the policy must be built, tested and documented at application.
The segregation requirement under MiCA is strict. Client crypto-assets must be held separately from the firm's proprietary assets at all times, and the firm must be able to prove segregation on demand through transaction logs and wallet records. The application must explain how the platform tracks individual client balances, how it reconciles on-chain holdings with the internal ledger, and what happens if a discrepancy appears. The competent authority will examine the technical setup during the assessment phase; if segregation is not demonstrably robust, the application stalls.
For platforms using third-party custodians, the safeguarding section must disclose the custodian's identity, the jurisdiction of custody, and the legal basis on which the custodian holds the assets. If the custodian itself is a regulated entity, the application should state the type of authorisation it holds. The regulator will assess whether the custodian meets MiCA-equivalent safeguarding standards, particularly if the custodian sits outside the EU. A memorandum-of-understanding or service agreement with the custodian must be appended to the application.
The operational risk and continuity plan
The application must include a business-continuity plan that covers system outages, cyberattacks, key-person loss and a sharp market downturn. The plan must identify critical business functions, the maximum tolerable downtime for each, and the recovery steps the platform will take if a function fails. The regulator expects backup infrastructure, data-recovery arrangements and documented escalation procedures. A generic disaster-recovery template does not suffice; the plan must be specific to the platform's architecture and client base.
For exchanges handling high transaction volumes, the continuity plan must address how the platform will manage an order-book freeze or a liquidity crisis. The plan should describe the criteria for halting trading, the communication protocol for informing clients, and the process for resuming normal operations. The competent authority will test the plan's credibility during the assessment phase; if the plan assumes resources or systems the platform does not currently have, the application will be challenged.
The operational-risk section also covers AML transaction monitoring. The application must describe the monitoring systems, the threshold rules for flagging suspicious activity, and the firm's process for filing suspicious-transaction reports with the financial-intelligence unit. The regulator will not authorise a platform that relies on manual review alone for high transaction volumes. Automated monitoring tools must be in place, calibrated to the platform's risk profile, and evidenced in the application.
The filing sequence and timing
The work above must happen in sequence, not in parallel. Governance and management first: identify the key individuals, complete the fit-and-proper files, and secure their commitment before moving to the next layer. Prudential second: raise the capital, commission the audit, and obtain the insurance certificate. Safeguarding third: build the wallet architecture, write the policy, and run the segregation test. Operational risk and continuity last: document the systems, test the backup infrastructure, and prepare the monitoring protocols. Only when all four blocks are complete does the firm assemble the application and file.
The timeline from "we need to file" to "the application is ready" is measured in months, not weeks. Operators we advise who enter the process under time pressure typically need twelve to sixteen weeks to complete the governance and prudential work if they start from a standing position. Platforms that already have most of the governance infrastructure in place – because they operated under a robust national regime or held a financial-services licence in another sector – can compress the timeline to eight to ten weeks, but that is the floor. A business that begins preparation in the final month before the transitional deadline cannot file a complete application.
For a scoped assessment of where your application stands and what remains to close the gap, contact OBOLUS at info@oboluslaw.com. The transitional window is a hard deadline; the work does not extend beyond it.
Common filing mistakes that delay authorisation
The most frequent mistake is filing the application before the prudential block is complete. A business submits governance, safeguarding and operational-risk documents but attaches a capital plan instead of audited evidence of own funds. The competent authority rejects the filing as incomplete, and the operator must re-submit. The clock does not stop during the re-submission; if the transitional period ends while the business is assembling the missing documents, it loses the right to operate.
A second mistake is under-specifying the safeguarding arrangements. The application states that client assets are held in "cold storage" but does not describe the key-management protocol, the signing process, or how the firm proves segregation. The regulator issues an information request, the business spends weeks drafting a technical annex, and the assessment phase extends. For a platform with a large client base, that delay can mean missing the transitional cutoff.
A third mistake is assuming the competent authority in the home member state will accept the same documentation the business submitted under the old VASP regime. MiCA is a different framework with different evidence standards. The regulator will not simply roll over a VASP registration into a CASP authorisation; the application must meet MiCA's governance, prudential and safeguarding requirements in full. A business that copies its prior VASP filing into the CASP application without updating it to MiCA standards will face rejection.
What happens if the deadline passes
If a business does not file a complete CASP application before the member state's transitional deadline, it must cease providing crypto-asset services to EU clients immediately. The grandfathering cover ends, and the platform has no legal basis to operate. The competent authority will not extend the deadline on request; the date is set by the transposition timeline, and individual forbearance is not the regulatory practice. A platform that continues to serve EU clients after the deadline without authorisation operates illegally and exposes itself to enforcement, fines and potential criminal liability for the management team.
The business cannot solve the problem by re-domiciling to a member state with a later deadline. The transitional period applies only to entities that held a VASP registration in that state before MiCA came into force. A business that tries to register in a new jurisdiction after its home-state deadline passes does not gain transitional cover; it must file a full CASP application and wait for authorisation before it can operate. The processing time for a first-time CASP application is longer than the time remaining in any transitional window.
For platforms that miss the deadline, the only lawful path is to pause EU-facing operations, file the CASP application, and wait for authorisation. The platform can continue to serve non-EU clients if it holds the appropriate licence in those jurisdictions, but it cannot market to, onboard or execute trades for EU residents until the CASP authorisation is granted. The revenue impact is immediate, and the banking and payment rails that serve the EU client base often freeze when the licence lapses.
If a prior application stalled or an account was closed, a second read can surface the structural reason and the route back. For clients facing that situation, reach our regulatory desk now at info@oboluslaw.com.
Cross-border interaction: banking and payment rails
A CASP authorisation does not automatically unlock banking. EU banks remain cautious about onboarding crypto-asset service providers, and many conduct their own due diligence on the platform's AML controls and transaction-monitoring systems before opening an account. A business that secures CASP authorisation but cannot bank in the EU faces an operational impasse: it has the legal right to operate but no way to settle fiat legs of trades or pay operating expenses.
The banking conversation must begin in parallel with the CASP application, not after authorisation is granted. The business should approach prospective banks with a draft application pack, a summary of the safeguarding and AML procedures, and a transaction-volume forecast. The bank will want to see the same governance and risk-management documentation the regulator requires, and it will run its own compliance review. The bank's timeline is independent of the regulator's; a business that waits until authorisation is final before contacting banks can find itself licensed but unable to operate for lack of payment rails.
For platforms operating across multiple jurisdictions, the interaction between the CASP licence, third-country licences and the banking layer is complex. A business licensed in the EU and also in a non-EU hub must ensure that its EU banking arrangements do not create exposure to the non-EU operations. Banks often impose geographic or counterparty limits on crypto accounts; a payment that flows through an EU account to a non-EU exchange or custodian can trigger a compliance freeze even if both entities are licensed. The banking and licensing structure must be modeled as a single system before the business commits capital to either.
Decision matrix: which member state to file in
A business that operated under VASP regimes in multiple member states must choose a single home state for the CASP application. The decision turns on three factors: the competent authority's processing speed, its interpretation of MiCA's discretionary areas, and the depth of the local banking and advisory market. A platform with significant operations in a state that offers fast processing but limited banking may fare worse than one that files in a slower jurisdiction with robust payment rails.
Lithuania has historically been a fast-processing hub for VASP registrations, but under MiCA it aligns to the CASP authorisation standard, and the Bank of Lithuania's MiCA-specific timelines are still emerging. Malta's MFSA has deep experience with the prior VFA framework, and the transition to MiCA may benefit from that institutional knowledge, but the island's banking market for crypto remains constrained. France, Germany and the Netherlands offer large banking markets and sophisticated regulators, but application queues are longer and the prudential expectations are exacting. The optimal choice depends on the platform's business model, client base and risk appetite.
For a business with no prior EU footprint, the strategic question is whether to enter the EU at all or to serve EU clients from a third-country licence with appropriate restrictions. A CASP authorisation allows EU passporting, but the capital and governance overhead is significant. A platform focused on institutional clients or high-net-worth individuals may achieve better economics by licensing in Switzerland or Singapore and restricting EU marketing until the client base justifies the MiCA investment. The decision matrix must compare the MiCA compliance cost, the revenue from EU retail access, and the reputational value of an EU licence in the operator's target market.
The firm's position on transitional filings
At OBOLUS, we treat a transitional CASP filing as a compressed full-authorisation engagement. The work is not a registration-form exercise; it is the same governance, prudential and safeguarding build that a first-time applicant would complete, done under deadline pressure. We begin with a gap analysis: compare the platform's current governance and capital position to MiCA's requirements and identify what must be built, amended or evidenced before filing. The analysis typically surfaces three to five structural gaps – an under-capitalised balance sheet, missing AML monitoring tools, an informal custody policy – and we sequence the work to close them in order of regulatory priority.
In our cross-border practice, we regularly see platforms that believed their old VASP documentation would suffice and discover too late that MiCA's evidence standards are different. A VASP registration in one member state is not a draft CASP application; the governance files must be rewritten to address MiCA's specific fit-and-proper criteria, the safeguarding policy must meet MiCA's segregation and reconciliation requirements, and the capital calculation must reflect MiCA's own-funds rules. The transitional deadline does not reduce the substantive work; it compresses the timeline for completing it.
We structure the engagement as a fixed-scope package with a stated delivery timeline, and we run the application track, the banking conversation and any necessary group-restructuring work as parallel streams. The client does not coordinate three separate advisors; we manage the entire licensing, banking and entity stack as one mandate. The engagement opens with a strategy call under NDA, and the fee model is transparent from the outset. For a scoped proposal on your transitional filing, write to us at info@oboluslaw.com.
Related at OBOLUS
- Licensing & Registration for Digital-Asset Businesses – full-scope authorisation across 70+ jurisdictions, fixed-fee engagements.
- Stablecoin Reserve, Custody and Redemption Duties Explained – ART and EMT issuer obligations under MiCA.
- Licence Renewal and Variation Legal Counsel for Digital-Asset Firms – ongoing compliance, scope changes and capital-event filings.
FAQ
How long does a crypto licence take to obtain?
A CASP application in a major EU member state typically takes four to six months from submission to authorisation, assuming the application is complete and no additional information requests are issued. Platforms that must build governance infrastructure or raise capital before filing should add three to four months for preparation. Competent authorities in member states with lighter application volumes may process faster, but no regulator guarantees a timeline. The transitional filing deadline does not accelerate the regulator's assessment; it sets the date by which the business must file, not the date by which authorisation is granted.
Which jurisdiction suits my crypto business?
The optimal jurisdiction depends on where your clients sit, where you can bank, and what the capital and governance overhead will be. A platform serving EU retail clients needs a CASP licence in a member state with robust banking and a competent authority experienced in crypto supervision. A business focused on institutional or non-EU clients may fare better in Switzerland, Singapore or the UAE, where the regulatory model is more flexible and the banking market for digital assets is deeper. The decision turns on the revenue model, the target client base and the tax structure of the parent group. A cross-border licensing strategy models all three layers before the firm commits to a jurisdiction.
Do I need a separate custody licence?
Under MiCA, custody of crypto-assets on behalf of clients is a regulated service, but it is included within the CASP authorisation framework rather than being a separate licence. A platform that holds or controls client crypto-assets must apply for CASP authorisation covering custody and must demonstrate safeguarding, segregation and professional-indemnity arrangements that meet the relevant provisions. If the platform uses a third-party custodian, that custodian must itself be authorised or meet equivalent standards. A business that provides custody in the EU without CASP authorisation or an equivalent third-country recognition operates outside the regulatory perimeter and risks enforcement.
About OBOLUS
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. We map the licence stack across operating, custody and payment layers before you commit. We structure licensing, banking and tax as one mandate rather than three disconnected workstreams. To discuss your transitional filing or your MiCA authorisation strategy, contact info@oboluslaw.com.
By Aisha Tan, Licensing & Jurisdictions Analyst – specialising in EU digital-asset authorisation, MiCA compliance and cross-border licensing strategy for exchanges and token issuers.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.