Which state money transmitter licenses do you need when the value you move is a stablecoin?

Whether a stablecoin transfer requires a state money transmitter license depends on how each state defines money, monetary value or virtual currency in its money transmission statute, and on any guidance its regulator has published on top of that statute. As of mid-2026 there is no single federal answer: FinCEN registration is required for any money transmitter, but it does not substitute for a state licence, and states range from treating a dollar stablecoin exactly like a wire, to running a separate virtual currency licence, to publishing an exemption for specific models. A bank or MSB planning a stablecoin product across the US therefore needs a state-by-state map and a sequencing plan, not a single licence. This article explains how states classify stablecoin activity, what the Money Transmission Modernization Act changed, why New York stands apart, and how to order a rollout.

Why does federal MSB registration not settle the question?

FinCEN has treated administrators and exchangers of convertible virtual currency as money transmitters since its 2013 guidance, and its 2019 guidance confirmed that position for a range of business models. Registration with FinCEN on Form 107 is mandatory for any money transmitter, carries anti-money laundering programme, recordkeeping and suspicious activity reporting duties, and must be renewed every two years. It is a registration, not a licence, and confers no authority to transmit money in any state; the form itself asks the registrant to list the states in which it holds licences.

The GENIUS Act, signed on 18 July 2025, regulates who may issue a payment stablecoin and how it must be backed. It does not create a federal licence for transmitting stablecoins between customers. It settles the issuer's position, not the transmitter's. The practical control at this stage is a written legal memorandum, refreshed at least annually, that records the regulatory characterisation of each product flow: on-ramp, off-ramp, custody, transfer between customers and transfer to a third party. Every state analysis that follows starts from that memorandum.

How do states classify a stablecoin transfer under money transmission law?

Most state money transmission statutes are triggered by receiving money or monetary value for transmission. The question is whether a dollar-pegged stablecoin is monetary value received from one person for delivery to another. States have answered in a few ways, and the answer can shift with a new guidance letter, so the map must be dated.

• Some states read virtual currency into monetary value under the existing statute, either by amending the definition or by regulator guidance, so a firm that takes a customer's stablecoins to send to a third party needs the ordinary money transmitter licence.
• Some states run a dedicated virtual currency regime alongside or instead of the money transmitter licence, of which New York's BitLicense is the oldest and California's Digital Financial Assets Law, with its licensing requirement effective from July 2026 after a legislative deferral, is the most recent large example.
• Some states have published guidance or no-action letters stating that specific activities, for example acting only as a technology provider, or holding assets without transmitting them, fall outside the licence, and those letters are usually tied to the facts presented and should not be generalised.
• Some states have not addressed virtual currency in statute or guidance at all, and there the prudent reading is that a two-party transfer of a dollar-referenced token is transmission unless counsel can document a reason it is not.
• Montana has historically had no money transmitter licensing statute, which makes it the one state where the question does not arise in the usual form, although federal obligations still apply in full.

Two characterisation points recur in every state analysis. The first is custody: a firm that never takes control of the customer's stablecoins, because the customer signs from a self-hosted wallet, has a stronger argument that it is not receiving value for transmission, although several states now regulate control of a customer's keys directly. The second is the fiat leg: an on-ramp that accepts dollars and delivers USDC to the same customer is often treated differently from a flow that delivers value to a third party. The document an examiner wants is a flow diagram per product, marked at each step with who holds what and under which characterisation.

What did the Money Transmission Modernization Act change?

The Money Transmission Modernization Act is a model law drafted by the Conference of State Bank Supervisors and released in 2021 to replace a patchwork of state statutes with common definitions, common licensing standards, a uniform net worth and surety bond approach, and a coordinated examination framework. A substantial number of states have enacted it in whole or in part, though adoption is uneven and some states have modified the text, so a firm cannot assume uniformity without checking the enacted version in each state.

For a stablecoin business the model act matters in three ways. It aligns the core definitions of money and monetary value, which reduces the number of distinct characterisation arguments a firm must run. It supports the multistate licensing process run through the Nationwide Multistate Licensing System, under which a lead state coordinates the review of common application components, and the networked supervision programmes CSBS has promoted. And it standardises the permissible investments rules that decide what a licensee may hold against customer obligations, which is directly relevant to whether stablecoins themselves can count towards that requirement in a given state.

What the model act does not do is settle the virtual currency question by itself. Its virtual currency treatment has been layered in state by state, and some enacting states have paired it with separate digital asset provisions. The operational instruction is to maintain, per state, three fields: whether the MTMA is enacted, whether the enacted text addresses virtual currency, and the citation for the state's position. That table is the spine of the licensing file.

A licence map that is not dated is not a map. Regulators change guidance by letter, and the letter that made your model exempt last year may have been superseded by the one that made it licensable this year.

Why is New York's BitLicense the outlier?

New York adopted 23 NYCRR Part 200 in 2015, creating a licence for virtual currency business activity that sits alongside the state's money transmitter licence rather than inside it. A firm that transmits stablecoins for New York residents typically needs the BitLicense, or a limited purpose trust charter from the New York State Department of Financial Services, and may also need the money transmitter licence for fiat legs. The application is substantial, review has historically taken well over a year for many applicants, and ongoing obligations include capital requirements set by the superintendent, cybersecurity rules and prior approval for material changes.

NYDFS also maintains its own view on which tokens a licensee may list or use. Its greenlisting framework allows licensees to use coins on the published list without further approval, while other coins require a coin-listing policy approved by the department. For a stablecoin settlement product this is a design constraint: the asset menu for New York customers must be reconciled with the greenlist and the licensee's approved policy, and a change to the menu is a change-control event with a regulator on the distribution list. Most multi-state plans therefore treat New York as a separate workstream with its own timeline, budget and product configuration, and block New York addresses until that workstream completes.

How should a multi-state rollout be sequenced?

The sequence is a function of three inputs: where the customers are, how long each licence takes, and which states cooperate through the multistate process. A workable method is to score every state on customer demand, licence lead time and complexity, then group states into waves. Wave one is the set of states that cover the largest share of demand and can be applied for together through NMLS with a lead state, typically states that have enacted the model act and treat stablecoins under the ordinary licence. Wave two is the states with separate virtual currency regimes and long lead times, of which New York and California are the usual members. Wave three is the long tail, some of which may never justify the licence cost.

Before wave one is filed, the product must be built to enforce the map. Customer address verification at KYB and KYC feeds a jurisdiction rule: licensed states pass, states with a documented exemption pass with the exemption reference logged, and everything else is hard-blocked at onboarding. The same rule must run at transaction time, because a customer that moves office moves jurisdiction. Beneficiary geography matters less, since the licence generally follows the customer from whom value is received, but counsel should confirm that reading per state.

The supporting file contains a dated jurisdiction table, the flow diagrams with characterisation at each step, the legal memoranda for exempt states, the surety bond and net worth calculations per state, and the NMLS application record. Examiners and bank partners ask for that file in that order. Firms that assemble it after the first application are rebuilding work they could have done once.

What does a bank partner or platform provider look for in your licensing position?

A bank providing accounts to a stablecoin MSB, or a settlement platform onboarding it, will ask for the jurisdiction table, the FinCEN registration confirmation, each state licence number, the exemption memoranda and evidence that the product enforces the map. It will also ask how a customer in a pending state is handled, and the acceptable answer is that the customer is not onboarded until the licence issues, or that the firm operates under a documented agency or sponsorship arrangement with a licensed principal where the state permits that structure.

Some states allow an authorised delegate to operate under a licensee's licence, which lets a new entrant start in a state under a partner's licence while its own application proceeds. It requires a written agreement, supervision by the principal, and the principal carrying the customer obligations. It is a bridge, not a destination, and the plan should date the firm's own licence in each such state.

Where StableNet fits

StableNet, built by SpendTheBits, is a cross border B2B payment and settlement platform for banks, credit unions, licensed money service businesses, exchange houses and remittance fintechs. It does not replace a licence, but it is built for institutions that hold them. KYB and KYC onboarding capture and verify the customer address that drives a jurisdiction rule, and the compliance workbench records each onboarding decision with the reference to the licence or exemption relied on, in a tamper evident audit trail an examiner can read. Settlement runs in regulated stablecoins such as USDC and USDT on public blockchains with customers keeping custody, the fact many state characterisations turn on, and every transfer carries ISO 20022 pacs.008 data tracked by UETR so the licensing file's flow diagrams match production messages. The three commercial models, B2B, B2B2B and B2B2C, map to the principal and delegate structures states recognise. SpendTheBits is a Bank of Canada registered payment service provider and a named finalist in the Swift Hackathon 2026 Technical Challenge.