Crypto and Fiat Licenses: MSB, MTL, EMI and MiCA

Every founder building a crypto and fiat product hits the same wall in the first quarter: the licensing question. Can we legally move money? Do we need a money transmitter license? In how many places? The answers feel like a maze because the map spans regulators, countries, and activity types that rarely line up neatly.

This guide is the map. It explains the four licenses that matter most for moving crypto and fiat (a US money transmitter license, MSB registration, a European EMI, and MiCA), what each one actually authorizes, roughly what they cost and how long they take, and the faster path of leaning on a licensed partner. Nothing here is legal advice, and thresholds vary by market, so treat it as orientation and confirm the specifics with fintech counsel.

For the broader build, this pairs with our pillar guide on how to build a crypto and fiat payment platform, where licensing is one of five foundations.

What a money transmitter license is, and when you need one

A money transmitter license is a US state-level authorization to receive funds from one party and deliver them to another on that party’s behalf. You generally need one the moment you take custody of, convert, or transmit customer money inside a state that regulates the activity.

That last part is the trap. Licensing usually follows where your customers are, not where you are incorporated. Serve users in a state that requires an MTL, and you are on the hook there, regardless of your Delaware or offshore setup.

The practical test is control of funds. Ask three questions:

• Do you hold customer money at any point, even briefly in transit?
• Do you convert one form of value to another (fiat to stablecoin, for example)?
• Do you decide when and where funds move on the customer’s behalf?

Answer yes to any of these and you are likely inside money transmission somewhere. Answer no across the board (because users control their own funds in a non-custodial design and approve each movement) and the perimeter narrows significantly. This is why the custody decision drives the licensing conversation. If you have not settled it, read custodial vs non-custodial before you file anything.

MSB registration vs a money transmitter license: not the same thing

MSB registration and a money transmitter license are often confused, but they operate at different levels and neither replaces the other.

MSB (Money Services Business) registration is a federal filing with FinCEN. It is a one-time registration that anchors your anti-money-laundering obligations under the Bank Secrecy Act across the whole country. It does not, by itself, grant you the right to transmit money.

A money transmitter license is granted state by state. It is the actual permission to move funds, and it comes bundled with bonds, net-worth minimums, and examinations in each state that requires it. A nationwide US operation historically needs a license in nearly every state that has the regime.

	MSB registration (federal)	Money transmitter license (state)
Issued by	FinCEN (US Treasury)	Each state’s financial regulator
What it authorizes	AML/BSA registration	The right to transmit money in that state
Scope	Nationwide	One state per license
Grants the right to transmit?	No	Yes
Typical timeline	Days to weeks	Months per state
Ongoing burden	AML program, reporting	Bonds, net worth, exams, renewals

The takeaway: you can be a registered MSB and still not be allowed to transmit money in a given state without its license. Both layers matter.

The four licenses that matter for crypto and fiat

Moving crypto and fiat across borders touches several regimes at once. Here are the four you will meet most often, and what each authorizes.

US money transmitter license (state). The right to receive and send money within a state. This is the workhorse for US fiat movement and, in many states, for crypto activity too.

MSB registration (US federal). Your FinCEN anchor for AML obligations. Required alongside state licensing, not instead of it.

EMI (Electronic Money Institution, Europe). An authorization to issue electronic money and hold client funds, typically obtained in one European jurisdiction and passported across the bloc. It is the closest European analog to holding balances and issuing accounts.

MiCA (Markets in Crypto-Assets, EU). The EU framework that authorizes crypto-asset service providers and sets rules for stablecoin issuance. If you touch crypto in Europe, MiCA increasingly defines the perimeter.

Regime	Geography	Covers	Custody of client funds	Typical route
MSB	United States (federal)	AML registration	N/A	Direct filing
Money transmitter license	United States (per state)	Fiat and often crypto transmission	Yes	Direct or via partner
EMI	Europe (passportable)	E-money issuance, accounts	Yes	Direct or via partner
MiCA	European Union	Crypto-asset services, stablecoins	Depends on activity	Direct or via partner

A single global crypto-fiat product often needs coverage across all four. That does not mean you must hold all four yourself, which is the whole point of the next two sections.

What licensing costs and how long it takes

Getting fully licensed yourself is expensive and slow, which is precisely why most teams do not do it on day one. Exact figures vary by state and jurisdiction and change over time, so treat the ranges below as orientation to confirm, not quotes.

For a full US footprint, direct licensing commonly runs into the hundreds of thousands to low millions of dollars once you stack application fees, surety bonds, minimum net-worth requirements, legal work, and annual renewals. Surety bond sizes and net-worth minimums differ per state, and they compound as you add states.

On timing, licensing a nationwide US footprint yourself typically takes 12 to 24 months or more, because each state runs its own review. European EMI and MiCA authorizations are their own multi-month processes with their own capital requirements.

Path	Time to go live	Upfront cost profile	Control	Best when
Get licensed yourself	12 to 24+ months	High (bonds, net worth, legal)	Full	Licensing is your core moat
Operate under a partner	Weeks to a few months	Low to moderate (platform or revenue share)	Shared	You want to launch the product fast
Hybrid (partner now, license later)	Weeks, then grow	Staged	Grows over time	You plan to internalize as you scale

The numbers are why the agent model exists. For most products, the license is not the differentiator, so paying two years and seven figures to build it yourself is the wrong first move.

The faster path: leaning on a licensed partner

You do not always need to hold the licenses yourself. Operating as an agent of a licensed institution (often called MTL-as-a-service, a BIN sponsor arrangement for cards, or simply the agent model) lets you launch the product while a partner supplies the regulated permission underneath.

Here is the mechanism. The licensed partner holds the MTL, EMI, or crypto authorization. You build the user experience and the vertical logic. The regulated activity (transmitting funds, issuing e-money, issuing cards) legally happens under the partner’s license, with you acting as its agent. This is the same principle behind Banking-as-a-Service, applied specifically to the licensing layer.

The benefits are speed and cost: weeks instead of years, and no seven-figure bond-and-capital outlay before your first customer. The trade-offs are real too: you share control, you carry a revenue share or platform fee, and you inherit the partner’s market coverage. You also still run your own AML/KYC program and cooperate with the partner’s oversight.

A common pattern is hybrid. Launch on a partner’s licenses to prove the market, then internalize specific licenses later if and where scale justifies the cost. That sequencing keeps your compliance perimeter honest while your engineers ship the product, the same principle behind our 90-day plan to launch your fintech.

Ongoing obligations you sign up for either way

A live license, whether yours or your partner’s, is not a one-time hurdle. It is a permanent operating discipline. Whoever holds it must run a continuous compliance program, and even as an agent you carry a meaningful share.

The recurring obligations include:

• A written AML/KYC program with a named compliance officer and documented risk assessment.
• Bank Secrecy Act reporting, including suspicious activity reports (SARs) and currency transaction reports (CTRs) at the applicable thresholds.
• Transaction monitoring and sanctions screening on onboarding and on every transfer.
• Independent AML audits at a regular cadence.
• Maintaining surety bonds and minimum net worth where the license requires it.
• Periodic state examinations and responding to regulator requests.

Two of these deserve extra attention for crypto-fiat products. First, your KYC and AML program is the backbone that examiners will test hardest. Second, cross-border and crypto transfers pull in the travel rule, which requires originator and beneficiary data to travel with qualifying transfers between regulated institutions. Both are far cheaper to build into the flow from the start than to retrofit under an exam deadline.

Reading licensing signals in an API

Licensing is not only a legal artifact; it shows up in how a compliant platform behaves. A well-designed API surfaces the compliance perimeter directly, so your engineers can see it, not just your lawyers. A transfer request against regulated rails, for example, typically carries the KYC status of both parties, screening results, and travel-rule fields, and it fails cleanly when the perimeter is not satisfied.

Here is an illustrative response to a cross-border transfer request, showing how compliance state rides alongside the money movement:

{
  "id": "txn_9f8c2a41",
  "status": "pending_compliance",
  "amount": { "value": "2500.00", "currency": "USD" },
  "rail": "cross_border_stablecoin",
  "compliance": {
    "sender_kyc": "verified",
    "recipient_kyc": "verified",
    "sanctions_screen": "clear",
    "travel_rule": {
      "required": true,
      "originator_attached": true,
      "beneficiary_attached": true
    }
  },
  "hold_reason": "awaiting_beneficiary_institution_ack",
  "idempotency_key": "req_2026_06_16_abc123"
}

Notice what the shape tells you. The transfer is held, not silently dropped, because a compliance step is still open. The travel-rule data is explicit. The idempotency key means a retried request will not double-send. These are the fingerprints of infrastructure built with the license in mind, rather than compliance stapled on afterward.

How to map your own licensing perimeter

Before you talk to any provider or regulator, draw your own perimeter. It comes down to three questions, and the answers determine everything else.

1. Who controls the funds? Custodial means you are likely inside money transmission. Non-custodial narrows the perimeter, because users hold and approve their own money.
2. Where are your customers? Licensing follows the customer’s location. List every market on day one, because each adds a regime.
3. What activities do you perform? Transmitting, converting, issuing e-money, and issuing crypto-asset services each map to different licenses.

With those answers you can decide, per market and per activity, whether to license directly, ride a partner, or defer that market entirely. Get this map from counsel before you scale, not after, because retrofitting a license perimeter is the most expensive kind of rework there is.

Where Tokelia fits

Tokelia is the infrastructure for programmable money: virtual accounts, unified crypto-and-fiat rails, card issuing, cross-border payments, and stablecoins, behind one API, with a non-custodial architecture and compliance built into the base stack. Money services are provided by Tokelia LLC, a Delaware company registered as a Money Services Business with FinCEN, with regulated banking delivered by licensed institutions. That combination lets you launch under your own brand while the licensed, hard-to-change parts sit underneath, so your team can focus on the product instead of a two-year licensing project.

If you are mapping your own licensing perimeter, the fastest way to pressure-test it is to walk a real flow with our team. Talk to us and we will help you see which regulated parts can ride on partner licenses and which, if any, you need to hold yourself.