Money Transmitter License — United States

A money transmitter license — an MTL — is a state-level license that allows a business to receive money or monetary value from one party and transmit it to another party, location, account, wallet, merchant, beneficiary, or institution.

It may become relevant if your business does any of the following:

• Receives funds from customers for transfer, or holds customer funds even temporarily
• Moves money between customers, merchants, businesses, wallets, or bank accounts
• Exchanges fiat currency, or converts fiat to crypto and crypto to fiat
• Offers remittance, bill payment, or payment facilitation services
• Operates payment kiosks, ATMs, wallets, or stored-value accounts
• Settles funds to third parties on behalf of users, or provides cross-border payments
• Operates a crypto exchange, stablecoin payment platform, or on/off-ramp

The key issue is not what you call your product. If money comes to you, through you, or under your control before reaching someone else, you are likely inside the money transmission perimeter.

The first question is simple: does your business receive, control, hold, convert, or transmit money or monetary value for someone else? If no, you may not need a license. If yes, you need a proper licensing analysis.

The second question is whether you are relying on an exemption. Banks, credit unions, certain payment processors, technology-only providers, software vendors, and authorised agents operating under a licensed principal may all be exempt. But exemptions are dangerous when assumed casually.

An exemption in one state may not apply in another. A "technology provider" exemption may fail if you control settlement. A "payment processor" exemption may fail if you hold funds or transmit outside a closed merchant relationship. A software-only argument may fail if your platform controls wallets, routing, approvals, custody, or settlement instructions.

The real test is operational. Who receives the funds? Who controls them? Who can stop, reverse, delay, approve, or redirect a transfer? Who has the customer relationship? Who is responsible if the money does not arrive? If the answer points back to your company, assume you need a formal strategy.

— opens the full-size image in a new tab

This is one of the most misunderstood points in US payments regulation. You do not apply for a single federal license that lets you operate across the United States. There are two layers.

The first is federal: if you are a money services business, you generally register with FinCEN as an MSB and maintain an AML/BSA compliance programme. That is registration and compliance — not a license.

The second is state-level licensing. Most states have their own requirements. Serving customers in multiple states may mean multiple licenses unless you operate under another compliant structure.

Many companies say "we are registered with FinCEN, so we are licensed." That is wrong. FinCEN registration does not give you permission to operate in California, New York, Texas, Florida, Illinois, or any other state that requires an MTL.

Before discussing applications, bonds, states, timelines, and fees, answer one question. This is what determines your path.

Being in the flow of funds means money moves through accounts, wallets, ledgers, or settlement structures your company controls or is legally responsible for. Your entity is visible in the transaction chain. Your customer contracts with you. Your compliance programme matters.

— opens the full-size image in a new tab

Not being in the flow means another licensed provider owns the regulated activity — they hold the funds, run KYC/KYB, approve customers, control settlement, and own the regulated relationship. You may provide the front end, but you are not the regulated money transmitter.

If you are in the flow of funds, you can build customer ownership, compliance track record, banking relationships, and long-term enterprise value. If you are not, you may launch faster but depend on someone else’s license, rules, limits, pricing, risk appetite, and roadmap.

This is why the fastest option is not always the best option.

The cleanest and most independent structure. Your company becomes the licensed entity, contracts directly with customers, holds the approvals, maintains its own compliance programme, builds its own banking relationships, and answers directly to state regulators.

It gives you maximum control: the customer relationship, settlement timing, compliance programme, product design, banking, state expansion, and a regulatory track record in your own name.

But it is expensive, slow, and operationally heavy. A full 50-state plus D.C. strategy can take 18 to 24 months pursued aggressively in parallel. A single state can take 3 to 12 months depending on the state, application completeness, control-person backgrounds, financial condition, documentation, bonds, and regulator review.

For companies needing nationwide coverage, direct licensing can easily become a seven-figure project before the business is fully operational.

Best suited to companies with serious funding, a long-term US strategy, meaningful volume, and a model where payments are core to revenue. Not usually the right first step for a startup testing the market.

The path most serious companies should examine first. A licensed money transmitter acts as principal; your company operates under their license coverage, subject to their supervision, compliance requirements, reporting standards, transaction limits, and risk controls.

A proper authorised agent model is not the same as being a superficial API reseller. You can maintain a branded customer relationship, remain visible in the flow, operate your own business model under the principal’s oversight, build a compliance track record, and run approved KYC/KYB processes.

The timeline is measured in weeks rather than years — typically 3 to 8 weeks depending on the principal, your documentation, ownership structure, compliance programme, use case, target states, corridors, and risk profile. Setup may fall in the low five figures, plus capital adequacy expectations, revenue share, platform fees, and ongoing supervision.

The trade-off is that you are not fully independent. The principal is liable for your conduct, so they will vet you, monitor you, audit you, restrict you when needed, and terminate you if your programme creates unacceptable risk. That is not a weakness — that is the structure.

For many fintechs, remittance companies, crypto-fiat operators, and foreign MSBs entering the US, this is the most practical first serious step. It gives you market entry without pretending compliance is optional.

The fastest path: an API, embedded payments provider, BaaS provider, or licensed infrastructure partner where you are not in the flow of funds. Useful for testing a concept, adding payments as a non-core feature, or validating demand.

But the limitations are significant. The licensed provider usually owns the regulated customer relationship, performs KYC, approves customers, controls monitoring and settlement, and decides which geographies, corridors, currencies, and use cases are allowed. They can change pricing, restrict functionality, or exit a product line.

The biggest problem appears later. When you outgrow the API model, you may need to rebuild customer onboarding, compliance data, contracts, settlement flows, monitoring, banking relationships, and operating model.

Fast launch can become expensive migration.

There is no single cost. It depends on how many states you need, whether you apply directly or operate under a principal, your volume, business model, financial condition, ownership structure, crypto exposure, customer type, foreign ownership, and compliance readiness.

A single-state license may cost tens of thousands of dollars once legal, filing, documentation, compliance, audited financials, and bond costs are included. A multi-state strategy can cost hundreds of thousands. A full national strategy can reach seven figures.

Cost categories usually include state application fees, NMLS fees, legal and consulting fees, compliance programme development, AML/BSA policies, audited financials, surety bond premiums, minimum net worth, background checks, permissible investment controls, AML software, compliance staffing, renewals, examinations, and ongoing regulatory updates.

The direct application fee is rarely the real cost. The real cost is building a credible regulated operating company. If your margins cannot support compliance, the problem is not the regulator — it is the model.

An API or white-label setup can sometimes go live in 1 to 4 weeks, assuming the provider accepts your use case. An authorised agent structure may take 3 to 8 weeks once the right principal is identified and documentation is in order. A single state license can take 3 to 12 months. A broad multi-state programme can take 12 to 24 months or longer, especially where New York, California, or Massachusetts are involved.

Timelines also depend on the quality of your application. Incomplete filings, unclear flow of funds, weak compliance documents, thin capitalisation, foreign ownership questions, crypto exposure, or inconsistent business plans all slow the process.

A clean application is not just a form. It is a regulatory narrative — who you are, what you do, how money moves, who your customers are, how you manage risk, how you protect customer funds, and why the regulator should trust your company.

Even though there is no federal license, federal obligations still apply. A money services business may need to register with FinCEN, maintain an AML/BSA programme, monitor transactions, file suspicious activity reports, and keep records.

A basic federal programme generally includes:

• FinCEN MSB registration and written AML/BSA policies and procedures
• A designated compliance officer and customer identification procedures
• Customer due diligence and enhanced due diligence
• Transaction monitoring and suspicious activity reporting
• Recordkeeping, training, and independent review or audit
• Sanctions screening, escalation procedures, and management oversight

Federal compliance is not optional because you are small, nor because you operate through a partner. As an authorised agent, the principal will require policies, controls, reporting, training, and audit readiness — your activity sits inside their licensed perimeter.

This is where US money transmission becomes difficult. Each state has its own regulator, statute, definitions, exemptions, filing process, bond requirement, net worth standard, reporting requirement, renewal cycle, and examination posture.

Most companies should not start by asking how to get all 50 states. They should ask where their customers are, where volume will come from, which states matter commercially, which are high-risk or slow, which can be deferred, which can be accessed through an agent model, which require direct licensing, and which create crypto-specific issues.

Alphabetical licensing is not strategy. State strategy must follow revenue, risk, timing, and regulatory burden.

New York is one of the most demanding jurisdictions. Where virtual currency is involved, the BitLicense regime may also apply — and a BitLicense does not automatically replace other licenses required under New York law, including money transmission where fiat is involved.

California matters especially for digital asset businesses. Its Digital Financial Assets Law creates a licensing and supervisory framework for many crypto-related activities involving California residents, and should be analysed early.

Montana is unusual in having historically not required a state-level money transmitter license. That does not eliminate federal MSB obligations, and it does not solve requirements in other states.

You cannot assume one regulator’s position applies nationally.

Crypto does not remove licensing risk. In many cases it increases it. Exchanges, fiat ramps, stablecoin payment platforms, custodial wallets, crypto remittance services, kiosk networks, and digital asset settlement businesses may all be treated as money transmitters.

The key questions: do you accept value from one person and transmit it to another? Do you exchange fiat and crypto? Do you custody customer assets? Can you move, freeze, approve, or block transactions? Do you control private keys or wallet infrastructure? Do you settle value to third parties? Do you serve US customers, and residents of states with crypto licensing regimes?

"We are just software" is not enough. If the business controls value, custody, settlement, routing, or transmission, regulators will look through the label and analyse the function. Do the analysis before building, raising, launching, or onboarding.

A direct application is not an administrative filing. A serious one usually requires corporate formation documents, ownership and control person information, a business plan, a flow of funds explanation, financial statements, audited financials where required, minimum net worth evidence, a surety bond, bank account information, permissible investment policies, an AML/BSA programme, KYC/KYB procedures, a transaction monitoring plan, consumer disclosures, complaint handling, information security policies, background checks, management biographies, regulatory history disclosures, and NMLS or state-specific filings.

The application must tell a coherent story. The regulator needs to understand what you do, who you serve, how funds move, how customers are protected, how risk is managed, who controls the business, and whether the company has the capacity to comply.

Weak applications create delays. Inconsistent ones create suspicion. Overly broad ones create unnecessary burden. Understated ones create enforcement risk. A good strategy is not more paperwork — it is the right regulatory story.

The most common mistakes are predictable:

• Registering with FinCEN and assuming they are licensed
• Launching before completing state analysis
• Calling themselves a software company when they are actually controlling funds
• Assuming their payment processor exemption applies everywhere
• Using a white-label provider without understanding customer ownership
• Entering an API model and later discovering they cannot migrate customer data
• Underestimating surety bonds and net worth requirements
• Applying to too many states too early
• Avoiding New York and California without understanding commercial impact
• Pursuing direct licensing when an agent structure would have been faster
• Using an agent structure without negotiating operational control
• Building first and asking licensing questions later

The worst mistake is not choosing the wrong path. The worst mistake is choosing a path unconsciously.

This page is for serious operators — fintech founders entering the US market, remittance companies needing a legal pathway, foreign MSBs wanting US access, crypto companies building fiat rails, payment companies that need to understand licensing before launching, investors performing diligence, and compliance officers who need a practical framework.

It is not for people looking for shortcuts, loopholes, template answers, or assurances that licensing probably does not apply.

Be prepared to discuss your actual business model. You should be able to explain:

• What product you offer, and who your customers are
• Which states you serve or plan to serve
• How money moves — who receives funds, who holds them, who controls settlement
• Who performs KYC/KYB, and whether crypto is involved
• Whether funds cross borders, and your expected monthly volume
• Your launch timeline, available capital, and current legal structure
• Your existing banking or payment partners, and your long-term US strategy

If you cannot explain your flow of funds, that is the first problem to solve. If you can, we can help you determine whether you need your own licenses, an authorised agent structure, or an API path.