Most teams treat licensing as a procurement problem. You find a lawyer, you assemble a binder, you wait for an approval, and then you go build the product you always wanted to build. That sequencing is backwards. A licence is a specification. It tells you, in enforceable detail, what your money flows must look like, where customer funds may sit, how fast you must prove they are intact, and who in the building is personally accountable when they are not.
This module is about reading a licence as an engineer reads a spec. We will stay in the licensing lane and leave the statutory machinery to module 1 and the EU and US perimeters to modules 2 and 3. The point here is narrower and more practical: once you hold a given licence, what does it force you to build?
Three licence shapes, three build envelopes
The licence type you obtain is really a choice about what you are allowed to do with customer money, and that choice dictates your architecture.
A US money transmitter moves funds from A to B. It does not get to hold a stored balance as its own product the way a deposit-taker does, and it must keep customer obligations matched by liquid assets it does not freely deploy.
An EU or UK electronic money institution (EMI) can issue e-money, meaning it can hold a persistent stored-value balance for a customer and let them spend it over time. That stored balance is the regulated object, and the rules cluster around protecting it.
A payment institution (PI) in the EU or UK executes payment services, such as initiating transfers or acquiring transactions, without issuing e-money. It carries lighter capital but a narrower permitted scope.
These are not interchangeable. Picking the EMI route because it sounds more capable means signing up to e-money safeguarding and a higher capital floor you may not need. Picking money transmitter licences because you are US-first means signing up to a state-by-state build that is closer to fifty integrations than one.
What the EMI and PI rules make you build
The EU sets a hard initial capital floor of EUR 350,000 for an EMI under Directive 2009/110/EC, against EUR 125,000, EUR 50,000, or EUR 20,000 for a PI depending on which payment services you run under PSD2. That is the entry ticket. The ongoing requirement is the part that touches your systems: an EMI must hold own funds of at least 2 percent of the average outstanding e-money it has issued. Your finance stack has to compute that figure continuously, not at year-end.
The heavier engineering obligation is safeguarding. Under the UK Electronic Money Regulations and Payment Services Regulations, you must protect relevant customer funds either by segregating them into a designated safeguarding account separate from your own money, or by covering them with a qualifying insurance policy or guarantee. The FCA reports the segregation method is used by more than 95 percent of firms, so assume you are building segregation.
Segregation is a daily operational system, not a bank account. The FCA's strengthened regime under Policy Statement PS25/12 takes effect on 7 May 2026 and requires affected firms to run mandatory daily reconciliations of safeguarded funds, submit monthly regulatory returns, and undergo annual safeguarding audits. So the licence does not just say "keep customer money separate." It forces you to build a reconciliation engine that proves, every single day, that the cash in your safeguarding accounts equals the e-money liability on your ledger, and to produce evidence an auditor and a regulator will inspect.
What US money transmission makes you build
US money transmission splits into two layers that people routinely conflate. FinCEN registration is a federal filing, FinCEN Form 107, that every money services business must complete within 180 days of starting. It triggers a full Bank Secrecy Act program: a written AML policy, currency transaction reports, suspicious activity reporting, and recordkeeping. Note that money transmitter status under FinCEN carries no activity threshold. Move funds as a business at all, and the BSA obligations attach.
But FinCEN registration does not authorize you to operate. State money transmitter licences do, and you need one in every state where you serve customers. Each state, increasingly aligned through the Money Transmission Modernization Act, sets its own minimum net worth, surety bond, and permissible-investments rules. Net worth floors commonly land between roughly $100,000 and $1 million; surety bonds run from tens of thousands of dollars up to $500,000 or more in stricter states.
The permissible investments rule is the one that reshapes treasury. You must hold liquid assets, typically cash, deposits, and highly rated securities, at least equal to your outstanding transmission obligations. That is balance-sheet plumbing: your treasury cannot chase yield with float, because the float is legally pledged to cover what you owe customers.
A worked example
Take a startup launching a multi-currency spending wallet for consumers, US and EU.
In the EU it wants users to hold a balance and spend over weeks, so it needs an EMI, not a PI. That decision alone commits it to EUR 350,000 initial capital, a 2 percent outstanding-e-money own-funds calculation wired into finance, a segregated safeguarding account per the EMRs, and a daily reconciliation plus monthly return and annual audit under the 2026 FCA regime if it operates in the UK. Engineering must therefore build a ledger that can produce a defensible e-money liability figure on demand, and an automated job that reconciles it against safeguarding balances nightly.
In the US the same wallet needs FinCEN registration plus state licences. If it launches in ten states, that is ten net-worth tests, ten bonds, and a treasury policy that keeps customer float in permissible investments across all of them. The product team wanted one wallet; the licence map says it is building one ledger with ten compliance overlays and a safeguarding-grade reconciliation system on the EU side.
None of this is optional decoration. Each line item is a thing your code, your accounts, or your hires must actually do.
The takeaway
Read the licence before you read your own roadmap. The licence type fixes your capital floor, the safeguarding or permissible-investments rule fixes how customer money sits and moves, and the reconciliation and reporting cadence fixes what your systems must prove and how often. Treat licensing as architecture and these constraints become design inputs you build around cleanly. Treat it as paperwork and you discover them as expensive retrofits the week before launch.