Meet Dr. Marcus Hartmann
Dr. Marcus Hartmann has spent over two decades at the intersection of financial law and emerging technology. Based in Zug, Switzerland's Crypto Valley, he has guided exchanges, custodians, and institutional founders through the full lifecycle of building and licensing a trading venue, from jurisdiction selection to the AML framework regulators sign off before launch.
He has structured exchange launches under the EU MiCA regime, the Singapore Payment Services Act, and offshore VASP frameworks across the Gulf and the Caribbean, and advises founders on the trade-off between building a custom matching engine and deploying a white-label platform across more than 60 jurisdictions.
To start a crypto exchange you define the business model, choose and obtain a licence such as an EU MiCA CASP or a VASP authorisation, incorporate and capitalise the entity, build or licence the trading technology, secure banking and liquidity, and stand up the AML, KYC, and Travel Rule compliance program before going live. The licence is usually the longest phase, so the work runs in parallel.
- A crypto exchange is a regulated financial business: the licence, not the code, is usually the critical path, and most projects take six to eighteen months end to end
- In the EU, operating a trading platform is a MiCA CASP service with a EUR 150,000 minimum-capital tier; offshore VASP routes are faster and cheaper but harder for banking
- The core tech stack is a matching engine, wallet and custody system, KYC and AML tooling, and liquidity, which you either build or buy white label
- White-label launches in weeks from roughly USD 8,000 to 30,000 at entry tier; a custom build runs USD 50,000 to 250,000 over four to nine months
- Ongoing compliance, an MLRO, Travel Rule data-sharing, sanctions screening, and segregated custody is permanent, not a one-time setup
The Roadmap in Brief
A crypto exchange is not a software project with a compliance afterthought. It is a regulated financial-services business with a software core. Founders who treat it the other way around lose months, because the regulator, the banking partner, and the liquidity provider all gate the launch in ways no amount of engineering can shortcut. The roadmap below breaks the work into six phases that, in practice, overlap rather than run strictly in sequence.
The single most useful framing is this: there are three parallel workstreams, the licence, the technology, and the compliance program, and the licence almost always sets the timeline. You can deploy a white-label exchange in a fortnight, but you cannot legally take a customer until your authorisation is granted. So the smart sequence is to lock the business model and jurisdiction first, file the licence application early, and build the technology and compliance framework while the regulator reviews. For a broader view of the surrounding company-setup steps, see our companion guide on how to start a crypto business.
This guide assumes you are building a centralized exchange, a CEX with an order book and a matching engine, rather than a decentralized protocol. The licensing and custody logic differs sharply between the two, and the centralized model is where the regulatory and operational roadmap below applies most directly.
Sources: MiCA Regulation (EU) 2023/1114 and Annex IV; ESMA MiCA hub; industry cost estimates for white-label and custom builds. USD ranges are vendor and industry estimates, not a single official figure.
Define the Business Model First
Everything downstream, the licence, the capital, the custody design, flows from the business model. Decide early whether you are running a pure spot order-book exchange, a brokerage that fills customer orders against your own book, a derivatives venue, or a hybrid. Each carries a different regulatory classification and a different risk profile. A spot exchange is the most common starting point and the simplest to licence.
Next, define your target customers and markets, because that decides which regulator owns you. Serving EU retail users pulls you into MiCA. Serving Singapore users pulls you under the Payment Services Act. Serving US users pulls in FinCEN and state money-transmitter regimes. Many founders narrow to one or two markets at launch precisely to keep the licensing and banking workload manageable.
Finally, model the revenue and the unit economics honestly. Trading fees on a thin order book generate little until volume arrives, and liquidity is expensive to rent. A clear-eyed business model that accounts for the cost of liquidity, compliance staff, and capital is what separates an exchange that launches from one that runs out of runway during the licence review.
Choose the Jurisdiction and File Early
The licence is the spine of the whole project. Operating a crypto exchange almost always requires an authorisation, and the regime you choose shapes your capital, your timeline, and your access to banking. The three reference regimes below cover most launches. Our detailed walkthrough on how to get a crypto licence covers the application mechanics, and the VASP licence overview sets out the baseline VASP route many offshore exchanges take.
In the European Union, operating a trading platform for crypto-assets is a regulated service under the Markets in Crypto-Assets Regulation (MiCA). It carries the highest own-funds tier under MiCA Annex IV, EUR 150,000, against EUR 125,000 for custody and exchange and EUR 50,000 for advisory or transfer-only services. A MiCA crypto-asset service provider authorisation passports across all EU member states, which is its biggest draw. The transitional window for firms operating before MiCA closes around 1 July 2026 in most member states.
In Singapore, digital payment token services are licensed by the Monetary Authority of Singapore under the Payment Services Act, typically via a Major Payment Institution licence for an established exchange. MAS requires an AML/CFT compliance officer, an independent external auditor assessment, and segregated, safeguarded customer assets. In the United States, you register with FinCEN as a money services business and, to serve New York, obtain a BitLicense from NYDFS, which carries a USD 5,000 application fee and a famously demanding review.
| Regime | Regulator | Capital / Fee | Key Feature |
|---|---|---|---|
| EU MiCA CASP (trading platform) | National competent authority | EUR 150,000 own funds | Passports across all EU member states |
| Singapore PSA (DPT service) | MAS | Risk-based capital + auditor | Credible but selective; strong banking access |
| US BitLicense + MSB | NYDFS + FinCEN | USD 5,000 application fee + reserves | Access to the US market; demanding review |
| Offshore VASP | Local regulator | Lower; varies by jurisdiction | Faster and cheaper; harder for banking |
Sources: MiCA Annex IV; MAS DTSP and DPT guidelines; NYDFS Virtual Currency Business Licensing. Capital figures are jurisdiction minimums; regulators can require more.
File before you finish building. Licensing commonly takes six to eighteen months, far longer than a software deployment. Submitting the application early, with the business plan, capital evidence, and draft AML policies attached, lets the regulator review while your technology and compliance program come together in parallel.
"Founders ask me which jurisdiction is cheapest, but that is the wrong first question. The right one is where your customers and your banking partners are. An EU MiCA authorisation costs more and takes longer, yet it passports across the whole bloc and unlocks banking that an offshore VASP licence rarely will. We model the licence as a market-access decision, not a line item."
Dr. Marcus Hartmann, Senior Licensing Advisor
The Technology Stack
A centralized exchange has four technical pillars, and each one is a project in its own right. Get the architecture right and the platform scales; cut corners and it fails under load or, worse, loses customer funds. The four pillars are the matching engine, the wallet and custody system, the KYC and AML layer, and liquidity.
1. The matching engine
The matching engine is the heart of the exchange. It pairs buy and sell orders, almost always on a price-time priority basis, also called FIFO: the best price fills first, and where prices are equal, the oldest order fills next. Because latency is a competitive feature, matching engines are typically written in a fast language such as Go or Rust and must process orders deterministically at high throughput.
2. Wallet and custody
Custody is where exchanges most often fail their customers and their regulator. The industry standard is to hold the large majority of assets, typically 90 to 95 percent, in offline cold storage, keeping only a small operating float in hot wallets for withdrawals. Multi-signature or MPC key management, segregation of customer assets from company funds, and regular reconciliation are baseline expectations under MiCA, MAS, and most VASP regimes.
3. KYC, AML, and supporting infrastructure
Around the engine sits the rest of the stack: KYC onboarding and identity verification, transaction monitoring, a trading and wallet services layer often built in Node.js or Python, a transactional database such as PostgreSQL with Redis caching the live order book, and container orchestration on a cloud platform for horizontal scaling. This is the plumbing that turns a matching engine into a usable, compliant exchange.
Mapping the licence to your exchange model? Get a free 30-minute consultation. We will recommend a jurisdiction, size the capital, and lay out the build-versus-white-label decision for your launch.
Get Free Consultation →Build or White Label
This is the single biggest cost-and-speed decision in the project. A white-label exchange gives you a ready-made platform, the matching engine, wallets, admin panel, and basic KYC, branded as your own and live within weeks. A custom build gives you full control of the engine, custody design, and roadmap, at the cost of months and a much larger budget. Most regulated exchanges start white label to reach market, then migrate to custom infrastructure once volume justifies it.
Industry estimates put an entry-tier white-label deployment at roughly USD 8,000 to 30,000 with a two-to-four-week launch, scaling up to USD 250,000 or more for a feature-rich white-label build. A custom MVP typically runs USD 50,000 to 250,000 over four to nine months. Our overview of the white-label exchange route covers what a turnkey package includes and where its limits show. Layer licensing legal fees of USD 50,000 to 500,000 on top, and a realistic all-in minimum lands around USD 300,000 to 500,000.
| Factor | White Label | Custom Build |
|---|---|---|
| Time to launch | 2–4 weeks (entry tier) | 4–9 months |
| Indicative cost | USD 8,000–250,000+ | USD 50,000–250,000+ |
| Control of engine & custody | Limited; vendor-defined | Full |
| Customisation | Branding and config | Unlimited |
| Best for | Testing demand, fast market entry | Scale, differentiation, long-term roadmap |
Cost and timeline figures are industry and vendor estimates and vary widely by features, jurisdiction, and compliance scope.
Secure Banking and Liquidity
Two operational dependencies sink more exchange launches than any technical problem: fiat banking and liquidity. Neither is optional, and both must be arranged before you go live.
Fiat rails, the bank or payment-institution relationships that let customers deposit and withdraw money, are notoriously hard for crypto businesses to secure. Banks de-risk aggressively, and a credible licence in a respected jurisdiction is often the price of admission. This is one reason a MiCA authorisation can be worth its higher cost: it opens banking doors that an offshore VASP licence frequently cannot.
Liquidity is the other make-or-break. A brand-new exchange has empty order books, wide spreads, and poor execution, which drives traders straight back to established venues. New exchanges fix this by integrating liquidity aggregators and professional market makers through APIs, often connecting to larger venues, so the order book shows tight spreads and real depth from day one. Budget for liquidity as a recurring operating cost, not a one-off integration.
In our exchange-launch mandates across more than 60 jurisdictions, the failure point is almost never the matching engine. It is the licence stalling because the AML framework was treated as paperwork to bolt on at the end, or the launch slipping because no bank would open an account for an entity licensed in a jurisdiction it did not trust. We sequence those two risks first, before a line of exchange code is written.
We also see founders underestimate liquidity. A perfectly built platform with thin order books loses its first traders within days and rarely recovers their trust. The exchanges that launch cleanly are the ones that treated banking, liquidity, and the AML program as gating dependencies from the start, and ran the technology build to fit that timeline rather than the other way around.
Ongoing Exchange Compliance
Authorisation is the beginning of compliance, not the end. A licensed exchange runs a permanent program that the regulator can examine at any time, and weak compliance is the fastest route to losing the licence you worked months to obtain.
At the centre sits the AML and KYC framework: customer due diligence at onboarding, ongoing transaction monitoring, suspicious-activity reporting, and sanctions screening against watchlists. Most regimes require you to appoint an anti-money-laundering compliance officer, often called an MLRO, at management level, and the regulator will assess that person's fitness as part of authorisation. Our team implements this framework end to end as part of a licensing engagement.
On top of AML sits the FATF Travel Rule, Recommendation 16 applied to crypto, which requires you to collect and share sender and recipient identity data with the counterparty provider for transfers above the threshold. By 2025, 85 of 117 surveyed jurisdictions had passed Travel Rule legislation, and a working Travel Rule solution is now a baseline expectation in most licence applications. Add segregated, safeguarded custody with regular reconciliation, IT and cyber-security controls, and periodic regulatory reporting, and you have the standing compliance load of a live exchange.
The Launch Timeline
The five phases below describe the core sequence of an exchange launch. In practice they overlap, the licence application, the technology build, and the compliance framework all run in parallel, but the milestones below are consistent across jurisdictions.
Starting a Crypto Exchange: Common Questions
Sources & Official References
- ESMA: Markets in Crypto-Assets Regulation (MiCA) hub
- EUR-Lex: Regulation (EU) 2023/1114 (MiCA), incl. Annex IV own-funds tiers
- Latham & Watkins: MiCA Requirements for CASPs (tracker)
- MAS: Guidelines on Licensing for Digital Token Service Providers
- MAS: Guidelines on Provision of Digital Payment Token Services (PS-G02)
- NYDFS: Virtual Currency Business Licensing (BitLicense)
- FATF: Targeted Update on Implementation of the FATF Standards on Virtual Assets and VASPs (2025)