Most teams building a payments feature reach for the wrong question first. They ask "which license do we need?" before asking the only question that actually gates the architecture: does our money ever touch a regulated activity, and if so, whose money is it and for how long?
Get that wrong and you either over-build (months chasing licenses you do not need) or under-build (operating unlicensed, which is a criminal exposure in most US states). This lesson maps the regimes and, more usefully, the off-ramps that let real products avoid licensing entirely. Renting someone else's license is the next lesson; here we decide whether you need one at all.
The core test: do you control customer funds?
Licensing almost always triggers on one fact: you take possession or control of money that belongs to someone else, on its way to a third party. If funds pass through an account you control, or you direct where they settle, you are likely transmitting. If you only instruct a regulated party that holds the funds, you usually are not.
This is why "we just facilitate payments" is not a defense. The regulator looks at the flow of funds, not your marketing. Trace every dollar from payer to final recipient and mark each point where it sits in an account you can reach. Those are your trigger points.
The US: a federal registration plus a 49-state patchwork
There are two distinct US obligations, and people conflate them constantly.
Federal: FinCEN MSB registration
Any money services business must register with FinCEN as an MSB by filing Form 107, which is a registration, not a license. It is free, must be filed within 180 days of establishing the business, and renews every two years. As of December 2025 roughly 29,000 MSBs were registered. Registration is cheap and fast and gives you nothing except an AML obligation. It does not authorize you to transmit money.
State: the actual money transmitter license
The license that matters is granted state by state. A money transmitter license (MTL) is required in 49 states to move money on behalf of others; Montana is the lone holdout with no general money-transmitter licensing regime. Each state sets its own bond, capital, and net-worth requirements, and fees and surety bonds range from a few hundred dollars to well over $100,000 per state, with California's bond reaching into the hundreds of thousands at scale.
The Conference of State Bank Supervisors has pushed the Money Transmission Modernization Act to harmonize definitions. By the end of 2025, roughly 31 states had adopted it in whole or in part, and CSBS reports those states cover about 99 percent of reported money transmission activity. The MTMA reduces variance but does not create a single national license. Licensing a full US footprint still takes most firms many months and runs into the millions in legal, bond, and compliance cost.
The exemptions that change everything
Most products that "feel like payments" avoid MTLs through one of two structures.
Agent of the payee
If you collect money on behalf of a merchant under a written agreement, and payment to you legally counts as payment to the merchant, many states treat you as the payee's agent rather than a transmitter. Marketplaces like ride-hailing and short-term rentals run on this. The catch: only about half the states recognize the exemption, and the terms differ. California and Washington have versions; Florida and Arizona do not. CSBS maintains an agent-of-the-payee exemption map worth checking before you assume coverage.
The conditions are strict. There must be a written agreement directing you to collect on the payee's behalf, the payee must hold you out publicly as accepting payment for it, and receipt by you must legally discharge the buyer's obligation to the payee.
Operate through a sponsor or BIN-sponsor bank
If a chartered bank or a licensed transmitter holds the funds and you only build the interface and instruct movements, the license sits with them. This is the dominant model for embedded finance and most fintech "wallets." You stay off the regulated flow of funds by never controlling it. That is the rent-a-license path covered next.
Europe: EMI vs PI, a cleaner two-tier model
The EU and UK regimes are more legible than the US because the categories are statutory.
A payment institution (PI) can move money but cannot hold a stored balance for customers. An electronic money institution (EMI) can do everything a PI does and also issue and store e-money, meaning it can hold a customer balance over time. That single distinction (can you park value in a wallet) decides which you need.
Capital reflects it. Under the EU framework, an EMI needs at least €350,000 initial capital; a PI offering only money remittance needs as little as €20,000, tiered up by service. The UK runs the same shape under the Payment Services Regulations 2017 and the Electronic Money Regulations 2011, using its own labels: Authorised Payment Institution and Authorised Electronic Money Institution.
The UK also offers a lighter "small" tier. A small EMI is available where average outstanding e-money stays under €5 million and monthly payment transactions stay under €3 million, with only £20,000 initial capital. Cross either threshold and you must upgrade to full authorization within 30 days. It is a genuine on-ramp, but you build the upgrade into the plan from day one.
A worked example
Say we are building a US SaaS product that lets gyms collect membership dues and pay their freelance trainers.
Collecting dues from members and remitting to the gym: if we sign an agent-of-the-payee agreement with each gym, hold ourselves out as collecting on its behalf, and structure receipt to discharge the member's obligation, we can lean on the exemption in the states that recognize it. In Florida or Arizona, where it does not exist, that flow needs a license or a sponsor bank.
Paying out to trainers is the harder leg. Money is leaving the gym and going to a third party we selected; that looks like transmission almost everywhere. The clean answer is to route payouts through a sponsor bank or a licensed payouts provider that holds the funds, so we never control them. We file the FinCEN MSB registration regardless, because we touch the money flow, and we keep the AML program live.
The takeaway
Decide the question of control before you decide anything else. If you never hold or direct customer funds, you can often build the whole product on someone else's license and skip the multi-year licensing slog. If you must hold funds, in the US the work is the 49-state patchwork on top of FinCEN registration; in Europe it is the clean PI-versus-EMI choice, set by whether you store a balance. Map the flow of funds, mark every point you control money, and let those points, not the product label, tell you which regime you are in.