Crypto, Blockchain & MiCA

A limited model or a specific exception may reduce the initial requirements, but small size alone is not an exemption. We define the permitted features, customer limits and any sandbox conditions before launch, then identify the changes that would require a new assessment or authorization.

The required route follows the business model. Token issuance, exchange, custody, payments and trading infrastructure can trigger different rules. We begin with the customer rights, asset flows and control arrangements before identifying the relevant permissions.

A token’s economic function and rights affect the rules applicable to issuance, transfer and related services. Payment, utility and asset characteristics can overlap. Classification should inform the structure and launch documents before the project makes commitments to customers or investors.

It may be appropriate for some AML-supervised models, but not every activity. Custody, deposit-like claims, securities dealing and infrastructure functions can introduce additional requirements. The answer needs an assessment of the actual service, including planned features.

The holder’s claim, reserve structure and redemption process can raise banking, collective-investment or other regulatory questions in addition to AML duties. We analyze those relationships rather than assume every token with a stable reference price has the same treatment.

No. Effective control, recovery powers, execution and the other services performed still need review. A technical description alone does not determine the legal position. We examine the architecture alongside contracts and the actual customer journey.

The category concerns specified multilateral trading in DLT securities and related features defined by Swiss law. The instruments, participant access, custody and settlement model all matter. Some platforms fall under other routes, so the infrastructure should be assessed before selecting a license.

Relevant transfers may require originator and beneficiary information and controls for incomplete data or external wallets. The implementation depends on the supervisory framework and transfer model. Legal procedures, technical capabilities and operational decisions need to work together.

No automatic MiCA passport follows from a Swiss license or SRO affiliation. EU offers, services and marketing need their own analysis. We coordinate the Swiss and target-market work around the same product facts and identify the required entities and responsibilities.

Yes, once the important mechanics can be described. We record the assumptions about rights, control and asset flows, then identify which later changes need another review. Early analysis can help the technical team understand the boundaries the product must support.

A product summary, token or payment model, asset-flow diagram, intended markets and any draft terms are useful. Share what exists rather than delay for a polished pack. We use the first review to identify the missing facts and agree the next deliverables.