Ask whether a product "is money transmission" and you will get a debate. Ask instead: at any moment between the payer and the payee, does our company receive value that belongs to someone else, with an obligation to move it onward or give it back? That question has a factual answer, and it is the one regulators start with.
The analysis has two independent layers. Federally, a business that qualifies as a money transmitter is a money services business that must register with FinCEN and run an anti-money-laundering program. Separately, nearly every U.S. state licenses money transmission under its own statute, with its own definitions, exemptions, and penalties. Clearing one layer says nothing about the other — and no single state's rule describes the country.
Map the flow before touching a statute
Every serious analysis starts with a diagram, not a memo. For each payment the product handles, trace the dollar from origin to destination and annotate each hop.
- Where does the money start? Payer's bank account, card, wallet balance, payroll file.
- What accounts does it pass through? Name the legal owner of every account in the chain — your entity, a bank "for benefit of" customers, a processor's settlement account, the payee directly.
- Who can move it at each hop? Signing authority, API control, and instruction rights matter more than account titles.
- How long does it rest anywhere? Instant pass-through, overnight settlement, and stored balances raise different questions — stored value that customers can hold and later redeem is its own category in many statutes.
- What happens on failure? Returns, refunds, and insolvency scenarios reveal who actually bears the obligation to the customer — which is the heart of the transmission question.
Practical step: Version-control the funds-flow diagram like code. Products drift — a new payout rail, a faster settlement option, a balance feature — and a flow that was clean at launch can become licensable after a product iteration nobody flagged to counsel.
The federal layer: FinCEN and MSB status
Under the Bank Secrecy Act framework, "money transmission services" means the acceptance of currency, funds, or other value that substitutes for currency from one person and the transmission of it to another location or person by any means — the definition sits in 31 C.F.R. § 1010.100. A person providing those services is generally a money services business required to register with FinCEN within the regulatory deadline after starting operations, renew periodically, maintain an AML program, and file required reports.
Registration is not a license and involves no substantive approval — but skipping it is serious. Operating an unregistered money transmitting business can violate 31 U.S.C. § 5330, and a parallel criminal statute reaches businesses that fail to register federally or that operate without required state licenses. FinCEN's rules also contain limited carve-outs — including one for certain payment processors — discussed below.
The state layer: licensing, and why it is the harder problem
State money-transmitter statutes are licensing regimes: application, background checks, net worth and bonding requirements, permissible investments rules, examinations, and reporting. Definitions vary — receiving money for transmission, selling stored value, and issuing payment instruments are typical covered activities, but the wording and exemptions differ state to state. The Conference of State Bank Supervisors coordinates multistate licensing and examination efforts, and its Money Transmission Modernization Act model law — adopted in some form by a substantial number of states in recent years — has narrowed, but not eliminated, the differences.
Because licensing is entity- and state-specific, the practical work product is a matrix: each state, the covered activity implicated by your flow, the exemption relied on if any, and the citation. Where the product runs on a bank partnership, that matrix should line up with the program agreement's allocation of roles — our companion article on who owns compliance risk in embedded finance agreements covers why the contract and the license analysis have to be built together.
The exemptions everyone reaches for — and their limits
| Position | Core idea | Where it fails |
|---|---|---|
| Agent of the payee | Receiving funds as the payee's contractual agent means payment to you is payment to the payee, so nothing is "transmitted" | Not recognized everywhere, and recognized versions have conditions (written agency agreement, goods/services context). Fails when the agency is paper-thin or funds flow to parties beyond the appointing payee. |
| Payment processor | FinCEN's carve-out for entities processing payments through clearance and settlement systems under agreements with creditors or sellers | The federal conditions are specific — including operating through regulated clearing systems and serving the seller side, not consumers generally. And it is a federal carve-out; states have their own, different rules. |
| Bank service provider | The bank holds and moves all funds; the company only provides technology and instructions | Fails when the company can unilaterally direct funds, holds them in its own accounts even briefly, or the operational flow departs from the documented one. |
| Closed-loop value | Balances redeemable only with the issuer for its own goods or services fall outside many statutes | Fails the moment value becomes transferable to other users or redeemable in cash beyond statutory limits. |
Watch out: An exemption memo written for one state gets quietly generalized to fifty in decks and diligence answers. Treat every exemption as jurisdiction-specific until a state-by-state review says otherwise — acquirers and bank partners will test exactly this in diligence.
Product patterns that should trigger a fresh look
Certain features are reliable signals that the analysis needs to be run or rerun: adding stored balances or wallets to a previously pass-through product; payouts to third parties who are not your direct customers; marketplace splits where you hold sellers' shares before settlement; cross-border remittance legs; payroll or benefits disbursement where wage funds rest with you — a live issue for the products covered in our earned wage access guide; and any handling of convertible virtual currency, where both FinCEN guidance and updated state statutes apply and where our digital-asset compliance checklist picks up the thread.
Quick answers
Our bank partner holds all the money. Are we automatically fine?
Not automatically. The model helps only if it is true in operation: the accounts are bank-owned, your company cannot take possession or unilaterally redirect funds, and the contracts document the bank's control. Regulators and examiners look through labels to actual authority. If your engineering team can move customer money with an API call unconstrained by the bank, the paper story may not hold.
Is FinCEN registration a substitute for state licenses?
No. They are independent obligations serving different purposes. FinCEN registration is a federal anti-money-laundering measure with no approval process; state licenses are consumer-protection and solvency regimes requiring applications and ongoing supervision. A business can need both, either, or neither, and the criminal statute on unlicensed money transmitting reaches state-license failures as well as federal registration failures.
How long does multistate licensing realistically take?
Timelines vary by state and applicant, and multistate coordination programs have shortened some paths, so treat any specific figure as stale on arrival. The dependable planning facts: applications require substantial financial disclosures, control-person vetting, and bonding; states move at different speeds; and phased launches — starting in states where you are licensed or exempt — are the common bridge strategy.
Does receiving money in cryptocurrency change the analysis?
It adds analysis rather than replacing it. FinCEN has long treated acceptance and transmission of convertible virtual currency as money transmission for BSA purposes, and states differ — some apply existing statutes, some enacted digital-asset-specific regimes, and some have published exemptive guidance. The funds-flow mapping method is identical; the statutory overlay is broader and moving faster.
A working plan
Draw the flow of funds with account owners and control rights labeled, and make product, engineering, and finance sign off that the diagram is real. Run the federal MSB question against the current FinCEN definitions, then commission the state-by-state matrix before launch commitments are made, prioritizing the states where your customers actually are. Revisit both whenever the product changes how money moves or rests. And read the analysis alongside its neighbors — the contract-allocation questions in bank partnership agreements and the rest of the Banking, Payments & Fintech pathway — because licensing is one panel of a larger compliance picture, not the whole frame.