MiCA licensing & EU compliance for crypto businesses.
Best fit for exchanges, brokers, custody, on/off-ramp, stablecoin-related services, and token issuers entering the EU market.
- Which MiCA activities you actually fall under (and which you don’t).
- Where the substance should sit (people, governance, outsourcing).
- What regulators will question in your model (flows, custody, conflicts).
- What documents you must have before filing and before go-live.
- Activity mapping and role split (platform, issuer, agent, distributor).
- Client asset vs non-custodial models.
- Marketing and cross-border positioning baseline.
- Board / senior management responsibilities.
- Outsourcing chain and oversight logic.
- Conflicts, complaints, incident response baseline.
- Customer types, geography, product risk factors.
- Blockchain analytics & third-party tooling perimeter.
- Escalations, MLRO reporting, recordkeeping baseline.
- Service mapping and red flags.
- Substance & outsourcing readiness check.
- Document list and prioritised remediation plan.
- AML/CTF, sanctions, KYC/EDD procedures.
- Conflicts of interest, complaints, incident handling.
- Outsourcing oversight and vendor controls baseline.
- Client agreements (retail/professional where relevant).
- Risk disclosures tailored to your asset flows.
- Website disclosures and marketing guardrails.
- Entity and shareholder structure baseline.
- Governance documents and delegated authorities.
- Key commercial contracts alignment.
- Policy updates as product evolves.
- Periodic control testing baseline.
- Regulator Q&A and remediation support.
- Data processing and vendor DPAs baseline.
- IP chain clean-up and assignments.
- Platform terms and consumer-facing policies.
Model, jurisdictions, target clients, asset flows, custody, partners, and revenue logic.
Define applicable services, restrictions, and what must be built in governance and disclosures.
AML/CTF, sanctions, conflicts, outsourcing, incident handling, recordkeeping.
Client agreements, risk disclosures, website pages, and implementation guidance for ops.
- Short product description and target EU markets.
- Client types (retail / professional) and onboarding flow.
- Asset flows: who holds keys, who settles, who can move funds.
- Vendors (custody, KYC, blockchain analytics, payment providers).
If you don’t have this fully documented yet, we map it together in the kick-off.
- MiCA perimeter memo (clear scope and assumptions).
- Compliance pack (policies + procedures, role split, reporting lines).
- Outsourcing & vendor controls baseline.
- Client documentation and disclosure layer baseline.
For a fixed-scope start, use Packages or request a tailored scope via Contact.
Not necessarily, but non-custodial models still can be regulated depending on services, client flows, and how execution/transfer is organised. We start with a perimeter map.
Outsourcing is usually possible, but it must be governed: oversight, reporting, documentation, and continuity. We build the vendor-control layer and responsibilities split.
Clarity of the operating model (who does what), asset flows, conflicts of interest, AML/CTF controls, incident handling, and whether your disclosures match reality.
Yes. We align your Terms, disclosures, privacy/data layer, and marketing claims to your product and compliance logic so you don’t create avoidable regulatory or consumer-law risk.
- Entity structure and where your team sits.
- Product flows (wallets, custody, settlement).
- Client types and onboarding/KYC approach.
- Key vendors and partners.
Even 8–10 lines is enough to start.