US Money Transmitter Licensing: How Payment Models Change the Analysis

Ask ten payments operators how to "get licensed to process payments in the US" and most will describe applying for a single credential — the way you'd apply for an EMI licence in the UK or a payment institution licence under PSD2. The US has no such thing. What it has is a federal registration that authorises you to operate nowhere, and a separate licensing layer administered independently by whichever states actually require it — with a set of exemptions that can remove the requirement entirely, but only on facts that have to be re-checked state by state. Operators who start from "what licence do I need" ask the wrong question. The right one is: does this specific flow of money, in this specific state, under this specific model, meet the statutory definition of money transmission — and if so, does an exemption apply.

Scope note. This is structural explanation of how the money-transmission trigger works and how it interacts with common payment models — not legal advice, and not a substitute for counsel qualified in the specific states involved. Four pages on this site already hold pieces of this picture, and this article is written to sit alongside them rather than duplicate them. The United States market page carries the factual profile — jurisdiction count, FinCEN-versus-state distinction, MTMA adoption pattern, timeline and cost ranges — and this piece does not restate those figures; treat that page as canonical for them. PSP vs PayFac operations reference owns who holds the merchant account, boards merchants, and carries chargeback risk across PSP, PayFac, acquirer, marketplace, and MoR models; this article picks up beneath that, at the licensing question for whichever model you choose. Merchant of record vs PSP owns the tax and commercial-liability decision; this piece is about when the underlying activity is money transmission regardless of that choice. Wallet funding and stored-value operations covers safeguarding mechanics globally with one paragraph on the US; this article is the fuller US money-transmission trigger for stored value specifically. One concept — the agent-of-payee exemption, arguably the single most consequential exemption a payment processor can rely on — has had zero coverage anywhere on this site until now.

The statutory trigger: what counts as "money transmission"

The federal definition is deliberately broad. "Money transmission services" means "the acceptance of currency, funds, or other value that substitutes for currency from one person and the transmission of currency, funds, or other value that substitutes for currency to another location or person by any means." FinCEN reads "another location" expansively — its own guidance gives the example of a virtual-currency exchanger crediting a customer's account with the equivalent of currency received, which counts as transmission to another location even without anything moving in a literal geographic sense. There is no minimum dollar threshold and no requirement that the transmission cross state lines. The test is about the shape of the transaction — value in from one party, value out to a different party or location — not its size or its label.

From that broad starting point, federal regulation carves out six categories of activity that don't make someone a money transmitter: providing the delivery or network infrastructure a transmitter uses; acting as a payment processor through a clearance and settlement system under agreement with the creditor or seller; operating a clearance and settlement system, or acting solely as an intermediary between BSA-regulated institutions; physically transporting currency as an armored-car-style business with no more than custodial interest; providing prepaid access; and accepting and transmitting funds only as an integral part of a sale of goods or services, rather than as a freestanding transfer. FinCEN is explicit that it reads these narrowly: it "interprets these exemptions strictly," and an activity that doesn't conform fully to one doesn't get to claim it. State law runs a parallel version of this same test, usually with its own exemption list that overlaps with — but does not exactly mirror — the federal one. Every question in the rest of this article is a variation on the same starting move: trace the actual flow of funds, and check it against both lists.

Federal registration and state licensing are separate, cumulative regimes

The single most consequential thing to get right early is that these are two different obligations, not two names for the same thing. Federal law requires "each money services business (whether or not licensed as a money services business by any State)" to register with FinCEN — the regulation's own phrasing makes clear that registration is independent of whatever a state requires. Registration is renewed every two years, and it functions as a gateway into the BSA/AML regime: a compliance program, recordkeeping, and suspicious-activity reporting. It carries no capital requirement, no bond, no examination regime of its own, and — critically — no grant of authority to hold or move customer money anywhere.

The actual permission to operate sits at the state level, in whichever states regulate money transmission, administered independently state by state. An operator that registers as an MSB and treats that as "the licence" has not, in fact, licensed anything. This is a recurring and expensive mistake, and it's exactly backward from how the two obligations relate: federal registration and state licensing are cumulative requirements that both apply, not alternative paths where satisfying one substitutes for the other.

NMLS and the Money Transmission Modernization Act

Because licensing is state-by-state, the practical filing mechanics run through the Nationwide Multistate Licensing System (NMLS) — the shared electronic system state regulators use for licence applications, change-of-control filings, surety bonds, reporting, background and credit checks, and coordinated examinations, wherever a given state has built its process around it. The Money Transmission Modernization Act (MTMA), a model law published by the Conference of State Bank Supervisors, is the harmonisation effort behind that coordination: a single uniform text that states can adopt to align their definitions, their exemption list — including an agent-of-payee provision — their prudential formulas for net worth, bonding, and permissible investments, their change-of-control process, and their expectations for multistate examination cooperation.

What the MTMA does not standardize is the actual dollar figures each state ends up with. The model text supplies default formulas — a net worth requirement, a bond calculation, a permissible-investments rule — but a state adopting the act is free to set its own numbers when it enacts the statute, and different states do. Treat the MTMA as harmonising the shape of state money-transmission law — definitions, exemption categories, licensing process, supervisory cooperation — not as producing one identical dollar amount everywhere it's adopted. Which states have adopted it, and how completely, keeps changing as legislatures act; check the current statute in the specific state rather than assuming last year's adoption count still holds.

Money transmission vs merchant acquiring

Processing card payments on behalf of a merchant is the clearest case of an activity that generally sits outside money transmission, and it's worth being precise about why, because the reasoning is what breaks down under other models. Two independent exemptions do the work. Federally, funds accepted and transmitted only as an integral part of a specific sale — rather than as a value transfer in their own right — fall outside the money-transmitter definition. At the state level, the CSBS model law exempts "an operator of a payment system" providing processing, clearing, or settlement services "in connection with wire transfers, credit card transactions, debit card transactions, stored-value transactions, [and] automated clearing house transfers" between persons who are themselves licensed or exempt. A merchant acquirer running card-network transactions for a merchant, settling through the card networks, is the paradigm case both provisions were written to cover.

The reasoning breaks down the moment an entity stops merely routing the proceeds of a specific, identifiable sale and starts itself holding, pooling, or redirecting money on behalf of a portfolio of unrelated payees. That's the fact pattern that pulls payment facilitators, marketplaces, and stored-value products into scrutiny even though plain card acceptance usually escapes it — the money stops being integral to one transaction and starts being a balance the operator itself controls. It's also worth noting that federally insured depository institutions are themselves generally exempt from state money-transmitter licensing under the same model framework, which is a large part of why so much of this market runs through bank-partner structures rather than direct non-bank licensing — covered further below.

The agent-of-payee exemption — and why it isn't universal

This is the exemption most likely to change an operator's licensing conclusion, and it has a clean legal theory behind it. If a payee — a merchant or creditor — properly appoints an agent to collect payment on its behalf, receipt of the funds by that agent is treated in law as receipt by the payee itself. The payor's obligation is discharged the moment the agent receives payment. Because the money is never, in the statute's terms, genuinely "in transmission" between two separate parties — it has already reached its destination in the eyes of the law — the agent doesn't need a money transmitter licence for that specific activity.

The CSBS model law's version of the exemption sets three conditions: a written agreement between payee and agent directing the agent to collect and process payments on the payee's behalf; the payee holding the agent out publicly as accepting payment for it; and payment being treated as received by the payee the instant the agent receives it, extinguishing the payor's obligation, with no risk of loss to the payor if the agent later fails to remit. This is the theoretical basis a meaningful share of payment processors and bill-collection intermediaries rely on to operate without a state MTL.

Be careful here. This exemption is not a federal rule and it does not exist uniformly. Whether a given state has enacted an equivalent provision — and on what exact conditions — is a state-by-state question that has to be re-checked every time, not assumed to travel on the strength of having confirmed it once elsewhere. California is a useful worked example of how much the details can diverge even where the core concept exists: its Department of Financial Protection and Innovation finalized its own agent-of-a-payee rule built on the same receipt-equals-discharge principle, but the final rule explicitly excludes open-loop stored-value transactions from the exemption's scope, reasoning that stored value issued without an identified payee has no immediate delivery obligation the exemption's logic depends on. Law-firm commentary on that rulemaking is blunt about the implication: interpretations of state-specific agent-of-a-payee exemptions can diverge even where states follow a similar template, and a compliance strategy still needs a state-by-state approach. Never present this exemption to a business team as a solved, portable fact. Confirm the specific state's statute, on the specific facts, every time.

Custody and control: the fact pattern every test above is actually asking

Strip away the labels and every test in this article — the federal money-transmission definition, the payment-processor exemption, the agent-of-payee doctrine, the crypto wallet framework below — is asking a version of the same factual question: who ever holds or directs the customer's money, for how long, and under what authority. Agent-of-payee turns on whether receipt by the agent legally discharges the payor's obligation — that is, whether the agent has real authority to receive on the payee's behalf, with no risk of loss sitting with the payor in between. FinCEN's crypto-wallet framework asks the same question in a different vocabulary: who owns the value, where is it stored, does the owner interact directly with the underlying payment system, and does the intermediary have independent control over the value even if it's contractually bound to follow the owner's instructions. The payment-processor exemption asks whether the entity's agreement runs to the seller or creditor receiving the funds — not just the buyer — and whether the clearing mechanism is a genuine bank-to-bank settlement system rather than a freestanding transfer product built on top of one.

The practical exercise for an operator is to draw the actual flow of funds and, at every hop, ask three things: whose money is this, legally, at this instant; who has the power to redirect it; and is it earmarked for a specific identified counterparty from the moment it's received, or could the operator itself choose to send it somewhere else. The more hops where the answer is "ours to direct," the closer the flow sits to money transmission, regardless of what the product is called on the pitch deck.

How payment models change the analysis

The underlying test doesn't change model to model. What changes is where custody actually sits, which changes the answer.

PayFac / sub-merchant under a licensed acquirer. A sub-merchant's own transactions ride the acquirer's card-network rails under the same operator-of-a-payment-system logic covered above. The facilitator itself is a different question: because it holds a master merchant account and directs settlement across many unrelated sub-merchants, it sits structurally closer to the custody fact pattern than any single merchant does. Whether a specific facilitator needs its own MTL is exactly the state-by-state, agent-of-payee-adjacent analysis above — not a settled "PayFacs never need one" rule, and not a settled "PayFacs always need one" rule either.

Marketplace and platform payouts. A marketplace holding seller balances before paying them out is functionally performing money transmission unless a specific exemption covers it or the platform is operating through a provider that already holds the licence. This is why the major PayFac-as-a-service platforms disclose their own money transmitter licences across relevant states — the platform inherits that coverage by contracting for the role rather than performing it on unlicensed infrastructure.

Merchant of record. An MoR's defining feature — becoming the identified legal seller for its own sales — keeps its own transactions inside the same receipt-equals-discharge logic the agent-of-payee doctrine is built on. But an MoR handling funds across many underlying sellers, not just its own inventory, is generally itself a licensed money transmitter for that activity. "We're a merchant of record" is not, by itself, a licensing exemption.

Stored value and wallets. The "is stored value covered" answer moves both by state and over time, which is the specific reason this deserves its own check rather than an assumption carried over from a prior analysis. California's carve-out of open-loop stored value from its agent-of-payee exemption is one example of how narrowly a state can draw this even where the general exemption exists.

Payouts and disbursements. Gig-worker earnings access, marketplace seller payouts, and claims disbursements all turn on the same custody question as everything above: whoever originates the payout and controls its timing and amount is the party transmitting it. Where that party is a sponsor bank or a licensed money-transmitter partner under contract, the platform distributing the product can operate without holding its own licence — provided the contract actually places the obligation, and the funds flow, with the licensed party.

Crypto on/off-ramps. At a structural level, FinCEN's guidance sorts participants into exchangers and administrators — both generally money transmitters — versus users obtaining virtual currency to spend on their own behalf, who are not. Hosted wallets, where the provider retains independent control over the value even while contractually bound to the owner's instructions, are treated as account-based money transmission. Unhosted, single-signature wallet software generally is not, where the value is the owner's own property and the owner interacts with the underlying network directly. An on/off-ramp that takes custody of customer funds mid-conversion is functioning as an exchanger under this framework and needs the full federal-plus-state analysis above; a non-custodial swap interface sits closer to the unhosted-wallet side. This is a structural map only — the newer federal stablecoin-issuer framework under the GENIUS Act is a separate track, covered on the US market page, and isn't restated here.

Sponsor banks and BaaS: licensing the obligation to someone else

The alternative to building a state-by-state MTL portfolio is to route the custody and transmission role to a partner who already holds the licence or charter, rather than performing that role on the operator's own infrastructure. A sponsor bank, or a licensed BaaS platform standing on top of one, carries the regulatory obligation while the operator distributes the product under its own brand — the mechanics, the technical stack this requires, and the concentration risk it creates are covered in full in embedded finance for operators and, for the card-issuing-specific version of the same trade, in card issuing and BIN sponsorship program management; this article doesn't re-run either. The trade-off in one line: no licensing build and faster time to market, against your program's continuity now depending on the partner's regulatory standing, and a partner exiting the relationship — a recurring event in this market — forcing migration on the partner's timeline, not yours.

What holding a licence actually costs, operationally

Once the analysis concludes a state MTL is genuinely required, the licence is not a one-time application fee — it's a standing operating obligation. The CSBS model law's own default structure illustrates the categories, though each adopting state sets its own dollar figures on enactment, so treat what follows as the mechanism, not a universal number to plan against. Net worth: a minimum tangible net worth that scales with total assets — the model's own default is the greater of $100,000 or a tiered percentage of assets, rising in the early tiers and tapering as the balance sheet grows. Surety bond: sized to the licensee's actual in-state transmission liability, calculated on a trailing average, with a floor and — in the model's default text — a cap. Permissible investments: assets whose market value must equal or exceed all outstanding money-transmission obligations at all times, and which are held in trust for customers even when commingled with the licensee's other assets — a customer's claim on those assets sits ahead of a general creditor's in the event of failure. Supervision: commissioners can examine a licensee on-site or off-site, jointly with other states or federal agencies, and can accept another state's examination as their own — the licensee typically pays for its own exam. Change of control: acquiring control of a licensee requires the commissioner's prior written approval, an investigation of the acquirer's financial condition and fitness, and a defined decision clock. Reporting: standing obligations spanning periodic condition reports, audited financials, and disclosure of specified triggering events, layered on top of ordinary BSA reporting. None of this disappears once the licence is granted — it's the operating tail that follows the decision, and it needs to be modelled as such before the application goes in, not discovered afterward.

Why "getting a US PSP licence" is the wrong framing

There is no such thing, and that's not a technicality — it's the single most important reframe an operator can carry into this analysis. There is no federal payment-institution charter a non-bank can obtain the way an EMI licence works in the UK or the EU. The federal layer is a registration — a BSA/AML compliance gateway that puts an operator on FinCEN's radar and obligates it to run a compliance program, nothing more. The actual authority to hold and move customer money is a state-by-state licence, granted or exempted jurisdiction by jurisdiction, under a test that starts from the same broad statutory trigger everywhere but resolves differently depending on which exemptions a given state has actually enacted and on what conditions. "What licence do I need" is never a single answer. The working question is: for this specific flow of funds, in this specific state, under this specific model, does an exemption apply — and if not, what does that state's licence actually require. That's the question this article is built to leave an operator equipped to ask.

Common mistakes

Treating FinCEN MSB registration as the licence. It's federal registration, not a state licence, and doesn't substitute for one. Both obligations apply, independently.

Assuming an exemption confirmed in one state travels to the next. Agent-of-payee, payment-processor, and similar exemptions are enacted (or not) state by state, on different conditions. Re-confirm every time, on the specific facts.

Treating a business model — PayFac, MoR, wallet provider — as itself an exemption category. None of those labels remove the licensing question; the underlying custody fact pattern is what gets tested, and it varies by model and by state.

Assuming a state's old position on stored value still holds. Coverage genuinely expands over time and by state; don't carry forward an answer that hasn't been re-checked against the current statute.

Underestimating the ongoing cost of a licence once granted. Net worth, bond, permissible investments, examinations, and change-of-control approval are recurring obligations, not a one-time application cost — model them as such before applying.

What to read next

• The United States market page — the factual profile this article deliberately doesn't restate: jurisdiction count, timelines, and cost ranges.
• PSP vs PayFac operations reference — who holds the merchant account and carries risk across each model, beneath which this article's licensing layer sits.
• Merchant of record vs PSP — when to switch — the tax and commercial-liability decision this article deliberately keeps separate from the licensing question.
• Wallet funding, float, and stored-value operations — global safeguarding mechanics behind stored-value products, of which this article's US trigger is one piece.
• Embedded finance for operators and card issuing and BIN sponsorship program management — the sponsor-bank and BaaS alternative to holding your own licence portfolio.