Guide to Licensing for Crypto Payment Enterprises: U.S. MSB and State MTL Applications

It is not a matter of scale, but whether the business activities have fallen within the scope of state law regulation.

Introduction

Projects engaged in crypto payments almost invariably register as Money Services Businesses (MSBs) in the United States at an early stage. However, once a project gains traction, it will inevitably confront a question:Is holding only an MSB registration legally sustainable?This question cannot be answered based on "industry sentiment"; it must be addressed by returning to the regulatory structure itself.

 

First, let us clarify a common misconception: MSB registration and state Money Transmitter Licenses (MTLs) do not constitute a "tiered upgrade relationship."

Many projects mistakenly interpret MSB registration and state MTLs as "basic" and "premium" versions, respectively. This is a typical misunderstanding.MSB（Money Services Business）An MSB is an anti-money laundering (AML) registration system regulated at the federal level by the Financial Crimes Enforcement Network (FinCEN). Its core focus is on:

• Whether Know Your Customer (KYC), AML, and sanctions screening obligations are fulfilled;
• Whether there are compliance risks such as money laundering or terrorist financing.

A state Money Transmitter License (MTL)is a financial license at the state level, addressing more fundamental questions:

• Whether you are qualified to engage in "money transmission" activities within that state;
• Whether you may legally contact, control, or transfer funds belonging to others.

To summarize the difference in one sentence:MSB regulation concerns whether the funds are "clean," while MTL regulation concerns whether you are "authorized to handle these funds."The two operate in different regulatory dimensions, and there is no legal logic whereby an MSB registration can supersede or cover the requirements of an MTL.

 

Why many projects can operate initially with only an MSB registration

is not due to regulatory leniency, but becausethe business model deliberately avoids triggering points under state laws. In projects we have assisted, common early-stage compliance structures include:

• Not directly serving natural persons in the United States;
• Not providing fiat currency on-ramps or off-ramps, processing only crypto assets;
• Not maintaining fiat currency balances for customers within the platform;
• Not directly holding or controlling customer funds;
• Ensuring that funds are always processed through third-party licensed channels or custodians.

Under these premises, projects typicallydo not constitute "money transmission" as defined under state laws, and therefore, an MSB registration combined with internal controls is feasible on a provisional basis. However, it must be emphasized that:This is not an "exemption," but rather a status of "not yet triggered."

 

The core question: What exactly are the triggering standards for a state MTL?

From a practical legal perspective, determining whether a state MTL is requirednever depends on whether you label yourself a "payment platform", but rather on your legal position within the fund flow chain. A highly operational standard for determination is:Whether you "transmit, control, or possess fiat currency or its equivalents belonging to others" in the course of your business.

In light of regulatory interpretations across various states, the following activities are highly likely to be deemed "money transmission":

• Directly providing fiat currency payment and collection services to users in the United States;
• Maintaining disposable fiat currency balances within platform accounts;
• Treating stablecoins as "currency or monetary substitutes";
• Funds entering your account first, before being transferred out upon your instruction;
• The platform having decision-making authority over the path, timing, or recipients of fund flows.

Once the above elements form a combination,relying solely on an MSB registration becomes legally very weak.

 

Which crypto payment scenarios practically cannot avoid state MTL requirements?

Based on our experience in handling projects, for the following business models, we typically advise project founders to:Seriously evaluate the need for a state MTL, rather than adopting a "launch first, comply later" approach.

• Crypto payments or exchanges targeting retail users in the United States;
• Integrated platforms for fiat currency ↔ stablecoin conversions;
• Issuance or use of U.S.-based crypto cards or virtual cards;
• Customer funds being "booked" or held within the platform's system;
• Integrated structures combining payments, wallets, and account systems.

The underlying logic is quite straightforward:The more your operations resemble a "quasi-bank" or "quasi-payment institution," the less likely state regulators will treat you merely as a technical intermediary.

 

Why many projects delay obtaining an MTL despite being aware of the risks

The reasons are not complex; they stem from cost and practical constraints. The actual barriers to obtaining a state MTL include: separate applications for each state (there is no "single license valid nationwide"); high surety bond amounts; ongoing capital and liquidity requirements; local compliance officers, audits, and annual filings; and the possibility of state regulatory examinations at any time. Therefore, many projects opt for a phased strategy: structuring their business to delay triggering events as much as possible, outsourcing "fund-handling" functions to licensed institutions, and treating the MTL as a mid-to-late stage capability-building goal. However, one must remain clear-headed about one point:Regulatory scrutiny often precedes your "completion of preparations."

 

A highly useful self-assessment question in practice

When conducting risk assessments for projects, I often ask the following question:If a state regulator were to send an inquiry letter today, could you clearly answer: "We do not contact, control, or transmit customer funds"?If you cannot affirmatively answer this question yourself, then the discussion is no longer about "whether to obtain an MTL," but rather "when you will be deemed to be operating without a license."

 

A more realistic compliance path: Not an either-or choice, but a phased design

A mature U.S. compliance path usually does not involve immediately applying for comprehensive MTLs upon obtaining an MSB registration. Instead, it starts with an MSB registration, designs the business model to avoid falling within the scope of state law regulation as much as possible, gradually builds internal control, risk management, and compliance capabilities, clearly identifies which business lines constitute "money transmission," and applies for MTLs state-by-state, business-line-by-business-line, and in a phased manner. From a legal perspective,a state MTL is not a "barrier to entry for startups," but rather an "indicator of business maturity."

 

Conclusion

I do not recommend that all crypto payment projects rush to obtain state MTLs at the outset. That would be neither realistic nor necessarily required. However, I also advise against assuming that:"We will only ever need an MSB registration."

An MSB registration is the foundation of compliance, while an MTL is the load-bearing structure. When you need it is not a result of subjective choice, but depends on whether your business has already entered the scope of state law regulation. If you have begun to seriously grapple with this question, it usually means—your project is no longer in the "early experimental stage."。