# Before choosing a crypto-licensing jurisdiction: questions your adviser should answer

This FOL guide helps you prepare the business facts and questions for a licensing consultation. [Explore FOL crypto-licensing services](https://fastoffshorelicenses.com/crypto-license/).

Choosing a crypto-licensing jurisdiction starts with your business model: the services you provide, the customers you intend to serve and the people who will run the operation. A useful adviser should turn those facts into a documented route, a list of unresolved questions and a budget you can test.

Use the questions below before paying for an application package or committing to an entity structure. Ask for the source behind each regulatory claim and the assumptions behind each commercial estimate.

## Which activities and assets does the proposed route cover?

Describe what happens to a customer's money and crypto-assets from onboarding to withdrawal. Identify who holds assets or keys, who executes transactions, whether customers exchange crypto for funds, and whether you provide advice or operate a trading platform.

Ask your adviser to map each activity to the applicable legal category. For an EU application, MiCA Article 62 calls for a programme of operations and information specific to the services being proposed. A general description such as “crypto exchange” leaves important questions unanswered. [MiCA Article 62](https://www.esma.europa.eu/publications-and-data/interactive-single-rulebook/mica/article-62-application-authorisation-crypto)

Your asset list also matters. Ask whether any products fall outside the chosen framework and what separate analysis they require. Record exclusions in the scope of work so that the commercial plan and legal analysis describe the same product.

## Where can the business serve customers?

List the countries where customers live and where you plan to market the service. Keep that list separate from the proposed place of incorporation. Ask your adviser to explain the legal basis for serving each target market, including any notification or additional permission needed.

For services within the EU, Article 59 sets out two routes: authorisation as a crypto-asset service provider under Article 63, or provision by eligible financial institutions under the conditions of Article 60. Confirm which route applies to the actual entity and services. [MiCA Article 59](https://www.esma.europa.eu/publications-and-data/interactive-single-rulebook/mica/article-59-authorisation)

MiCA's CASP provisions have applied since 30 December 2024. The maximum transitional period ended on 1 July 2026, with some national periods ending earlier. An adviser should therefore explain your current position without relying on an expired transition or treating a former national VASP registration as EU-wide authorisation. [Article 149](https://www.esma.europa.eu/publications-and-data/interactive-single-rulebook/mica/article-149-entry-force-and-application), [Article 143](https://www.esma.europa.eu/publications-and-data/interactive-single-rulebook/mica/article-143-transitional-measures), [ESMA transition statement](https://www.esma.europa.eu/sites/default/files/2026-06/ESMA75-113276571-1710_Public_Statement_MiCA_transitional_period_ends.pdf)

## Who will run the regulated business?

Ask for a proposed operating structure with named responsibilities. Where will management make decisions? Who will own compliance, security, customer complaints and incident response? Which work will be outsourced, and who will supervise it?

For a MiCA application, Article 62 requires evidence about governance, management suitability, qualifying shareholders, risk controls and ICT arrangements. Use that requirement to identify what your team can already demonstrate and what it still needs to build. [MiCA Article 62](https://www.esma.europa.eu/publications-and-data/interactive-single-rulebook/mica/article-62-application-authorisation-crypto)

Request a responsibility list covering your team, the adviser and outside suppliers. For each document, identify who supplies the facts, who drafts it and who checks that it matches operations.

## What evidence is missing before an application?

Bring an ownership chart, product description, customer-country list, transaction flow, financial plan and inventory of existing policies. The adviser should identify gaps and explain which ones prevent the application from progressing.

Ask to see the current regulator checklist and relevant application forms. For each gap, record the required evidence, the person responsible and the dependency. This makes it possible to distinguish a document that needs editing from an operating capability that still needs to be established.

If a policy depends on a future vendor, obtain the vendor decision before treating that policy as complete. Keep versions and unresolved assumptions visible to the people signing the application.

## What is the full budget?

Ask for a budget that separates cash spending from prudential safeguards and explains when each commitment arises. Under MiCA Article 67, the safeguard must be at least the higher of the Annex IV permanent minimum for the relevant services and one quarter of the previous year's fixed overheads. A first-year provider uses projected fixed overheads for its first 12 months. The adviser should calculate the applicable requirement and explain the permitted form for your circumstances. [MiCA Article 67](https://www.esma.europa.eu/publications-and-data/interactive-single-rulebook/mica/article-67-prudential-requirements)

| Budget line | What to ask for |
| --- | --- |
| Regulator fees | Current official schedule, currency and payment stage |
| Capital and other safeguards | Calculation, permitted form and evidence required |
| Entity and people | Setup costs, staffing assumptions and continuing commitments |
| Systems and controls | Vendor scope, implementation, testing and recurring charges |
| Professional fees | Deliverables, exclusions and charges for additional work |
| Ongoing operations | Compliance, accounting, reporting and review costs |

Every estimate should have a date, scope and owner. Ask what happens to the budget if the regulator requests more information or the business changes its product. Compare proposals using the same assumptions.

## What determines the launch date?

Ask for a sequence of milestones: facts confirmed, documents prepared, application complete, regulator assessment, operational readiness and permission to start the relevant services. Ask which milestones depend on your team, the adviser, suppliers or the authority.

MiCA Article 63 separates completeness checks from assessment and allows requests for further information. A statutory assessment period therefore needs context before it can inform a project schedule. [MiCA Article 63](https://www.esma.europa.eu/publications-and-data/interactive-single-rulebook/mica/article-63-assessment-application)

Treat banking, payment access and vendor onboarding as separate workstreams with their own evidence and decision-makers. Ask your adviser to identify dependencies and the consequences if a provider declines the business. An introduction should have a clearly described scope.

## How would this work for an exchange expanding into the EU?

Consider a hypothetical exchange established outside the EU. It plans to offer crypto-to-funds exchange and custody to EU customers. Its founders have an existing entity and technology platform, but have not confirmed the EU operating structure or payment arrangements.

A useful first deliverable would map the proposed services, identify the applicable authorisation route and list the evidence needed for the operating structure. The comparison should show the assumptions behind each candidate location, outstanding legal questions and dependencies on people, systems and payment providers.

The founders can then compare feasible options against the same requirements. The example establishes no preferred country, cost or approval time; those conclusions require the actual facts and current local analysis.

## What should you leave the first consultation with?

Ask for a short written record containing:

- The services, customer markets and entity assessed.
- The proposed regulatory route and its official sources.
- The evidence gaps and responsibility for resolving them.
- The budget assumptions and next decision.

When checking an existing EU provider, use the [ESMA MiCA register](https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/markets-crypto-assets-regulation-mica) and the relevant authority's records. Match the legal entity and authorised services to the business you are evaluating.

Prepare a short summary of your activities, target customer countries, existing entity and intended launch window before requesting a crypto-licensing consultation.

For questions about FOL crypto-licensing services, [contact Mark Paat](https://gofaizen-sherle.com/about/mark-paat) at [mark.paat@gofaizen-sherle.com](mailto:mark.paat@gofaizen-sherle.com) for a free initial consultation. You can also [visit the FOL crypto-licensing page](https://fastoffshorelicenses.com/crypto-license/).

## Related FOL resources

- [Map your crypto-payment flows](https://cryptolicense.fastoffshorelicenses.com/map-your-crypto-payment-flows-before-choosing-a-licensing-route)
- [Prepare for a banking or EMI discussion](https://cryptolicense.fastoffshorelicenses.com/prepare-your-crypto-payment-business-for-a-banking-or-emi-discussion)