US MTL play: how payments companies can license up (without losing a year)
Why this matters
If you’re a scaling payments company, there are only two durable ways to access the US market at scale: (1) operate under a bank or licensed partner, or (2) become licensed yourself. Plenty of teams start with a sponsor-bank model to get moving, then pursue money transmitter licenses (MTLs) to control more of the product, economics, and roadmap. This post is a field guide to doing option (2) well – what “MTL-ready” really means, how to scope and sequence the work, and the red flags regulators and banks care about most.
First principles: what MTLs actually cover
At its core, “money transmission” is about receiving money or monetary value and transmitting it to another person or location. Each state defines it differently, which is why teams feel like they’re solving 50 puzzles at once. There’s real progress toward convergence—states are coordinating through the CSBS Model Money Transmission Modernization Act and the Nationwide Multistate Licensing System (NMLS) led programs, but harmonization isn’t complete yet.
You’ll also have federal obligations the day your activity makes you a money services business (MSB): register with FinCEN, implement a risk-based AML/BSA program, file SARs/CTRs as applicable, and maintain an agent list if you use authorized delegates.
Reality check: Many applications and ongoing filings run through NMLS, but each state remains the decision-maker on whether you need a license and what evidence they require. Expect common scaffolding with state-by-state wrinkles.
Decide with intent: license now, later, or not at all?
Before you build a licensing machine, pressure-test the business case:
Sponsor bank vs. MTLs. Bank programs (and some “agent-of-bank” structures) can keep you out of the licensing perimeter if structured carefully, but the bank’s risk appetite, program controls, and change queues become your constraints. Owning MTLs gives you more control but that comes along with examinations, surety bonds, permissible investment rules, change approvals, and capital/financial condition expectations.
Sequencing. Fintechs often take the sponsored bank approach first to get a foot-hold in the US market before getting directly licensed with their own MTLs. You will need to weight up the cost-benefit of operating under your own MTLs including considering where most of your customers are operating from. In most cases, New York and California are key states where you need to get an MTL to make it worthwhile to operate in the US under your own MTLs. MTLs in these states, particularly New York, can take more than one year to obtain, so you need to factor this approval timeframe into your US market entry sequencing approach.
Crypto angle. If you touch crypto, even with a sponsor bank arrangement, you may need separate state-based licenses depending on your flows and products. Some states, such as New York, are more strict than others in this regard, so make sure you plan accordingly when entering the US market. You should expect longer timeframes to get approvals for direct licenses as part of your US market entry plans.
What “MTL-ready” looks like (the substance regulators test)
Think of the application as a story that ties your customer promise to your ledger entries—and proves you can keep customer money safe through any weather. Expect to evidence:
Crystal-clear flow of funds
Who holds funds at each step; where are settlement and “for benefit of” accounts; who can debit what and when; how exceptions and reversals work.
How you prevent commingling; how you reconcile.
How you’ll handle insolvency events so customers get their money back.
Safeguarding economics
Surety bond (or alternatives) sized per state methods; coverage for historical and peak transmission volumes.
Permissible investments to cover outstanding obligations (e.g., cash, certain approved instruments). States lean on MTMA-derived standards, but details vary—codify how treasury will maintain coverage.
Financial condition & governance
Audited financials (or reviewed, depending on state), net worth thresholds, and access to liquidity.
Board/committee structures, independent compliance function, and management experience with BSA/operations risk.
BSA/AML program
Risk assessment tied to your products, corridors, and customers.
KYC/KYB and beneficial owner verification; sanctions screening and monitoring rules.
Independent testing and training, with evidence you actually fixed past findings.
Operational resilience & information security
Vendor/outsourcing framework; business continuity and disaster recovery with RTO/RPO targets; incident response playbooks.
Data security aligned to your bank/processor expectations and contractual audit rights.
Consumer/business clarity
If you’re B2B-only, say so—then show how sign-up gates and T&Cs prevent consumer leakage.
Marketing controls so claims are fair, clear, not misleading; no “we’re a bank” language or implied deposit insurance.
Authorized delegate/agent oversight (if applicable)
Onboarding, training, monitoring, and termination playbooks.
Agent list management (federal and state expectations differ; NMLS UAAR is common).
Build once, license many: the application machine
A high-functioning licensing program is equal parts content library and project discipline.
Core content library (single source of truth)
Business plan, target markets, and competitive positioning.
Detailed flow-of-funds diagrams (normal, edge, and failure states).
Compliance Management System: AML Policy, KYC/KYB SOPs, sanctions, fraud, complaints, audit.
Treasury & safeguarding policy with permissible investments and daily controls.
Vendor/outsourcing register, diligence, and exit plans.
Information security policy suite, SOC2/ISO evidence if available.
Financial model and liquidity plan; covenant trackers.
Project discipline
A unified licensing tracker with each state’s prerequisites, fingerprints, background checks for “control persons,” bond amounts, and publication requirements.
A weekly cadence with counsel, finance, compliance, and engineering to close gaps.
“First-10 states” package, “next-15” package, and “long tail” package to meter workload without duplicating effort.
Where to leverage convergence
Use the NMLS artifacts and the multistate MSB licensing program checklists wherever possible; they won’t eliminate differences, but they reduce rework and make your pack legible to reviewers across states.
Examinations and the life after licenses
Winning licenses isn’t the finish line. You’ll face routine examinations – often coordinated across states under One Company, One Exam (OC/OE) – and ongoing change approvals (e.g., control, business model, or product changes). Build your evidence with that future in mind: policies + proof (tickets, dashboards, reconciliations, training rosters).
What exam teams like to see
Reconciliation packs that tie to bank statements and ledgers, with exception tracking and aging.
Alerts → investigations → outcomes → SAR decisioning that can be sampled end-to-end.
Vendor performance/KRI dashboards and how issues trigger escalations.
A promotions review log showing who approved what, on what basis.
State-specific sharp edges (plan for them up front)
New York is different by design. Money transmission and virtual currency authorizations live on separate tracks (MTL vs. BitLicense/limited-purpose trust). If you do fiat only, you’ll likely “just” pursue MTL; if you touch crypto, plan for dual track or an alternative charter. Many filings run via NMLS, but NYDFS has bespoke expectations and deeper ongoing supervision.
Model law ≠ uniform law. The MTMA raises the floor and standardizes concepts (e.g., control, permissible investments), but adoption is uneven and states keep local flavors. Always confirm the statutory text and current guidance in your target states.
Agent networks. If your distribution uses authorized delegates, design the training, monitoring, and termination program before you apply; several states will ask how you manage agent risk and how you produce agent lists (NMLS UAAR helps).
Red flags that slow (or sink) MTL applications
“Trust us” safeguarding. Commingled operating and customer funds, unclear FBO structures, or hand-wavy coverage calculations.
Policy-only AML. A binder with no tuning, no QA, and no evidence of independent testing or SAR QA.
Ghost governance. A nominal compliance officer who can’t explain your monitoring rules, a board who never sees KRI/MI, or outsourced functions with no oversight.
Marketing drift. Websites or decks implying deposit insurance, bank status, guaranteed savings/yields, or universal “instant” payouts.
Crypto creep. Product roadmaps adding stablecoins or crypto settlement without revisiting your licensing posture, especially for NY.
A practical roadmap
Scope & design (2–4 weeks)
Confirm whether your current flows trigger money transmission in key states; identify any sponsor bank dependencies you’ll keep.
Decide your NY position (if relevant) and crypto posture.
Choose tranche one vs. parallel filing strategy.
Build the evidence (4–8 weeks)
Finalize funds-flow and treasury/safeguarding designs; lock daily recon and exception handling.
Finish AML/BSA artifacts: risk assessment, rules, procedures, training, and independent test plan.
Stand up vendor oversight and security artifacts.
Prep audited/reviewed financials and liquidity plan.
Apply via NMLS (rolling)
Populate company and control person records; order fingerprints/background checks; place surety bonds.
File tranche one, respond to checklist items and regulator follow-ups, then rinse and repeat for tranche two.
Operate like you’ll be examined tomorrow
Establish a compliance calendar; track KRIs (e.g., recon breaks, sanctions hits, fraud loss rates).
Keep an exam-ready binder and a change-log for any model adjustments.
Technology centric solutions
There are SaaS providers in the US market that offer tailored solutions to help fintechs apply for MTLs. One such SaaS provider is Brico. Brico’s solution helps fintechs automate new MTL applications across the 50 US states so you don’t have to manage 50 separate applications. Brico’s solution also facilitates ongoing compliance requirements needed to maintain each MTL including managing surety bond requirements, licence renewals and regulatory updates. Implementing a licensing solution via a SaaS provider like Brico can save fintechs seeking to expand into the US market time and money. Leveraging Brico for the administrative matters together with a specialised external counsel for the hard stuff is the optimal strategic approach for many fintechs.
Where a fintech legal consultant can help
Licensing strategy tied to economics. Not just “get all the licenses,” but which states first and why – based on customer concentration, payout corridors, and sponsor-bank constraints.
One coherent pack. Align the business plan, product disclosures, treasury mechanics, AML program, and vendor contracts so they tell the same story.
NMLS project management. Herding the documents, fingerprints, bonds, and state conversations while your team ships product.
Exam prep and feedback loops. Turning early regulator questions into program improvements, so your first multistate exam isn’t a fire drill.
Targeted local counsel. Narrow, high-leverage questions (e.g., unique state interpretations, statutory change, or consent order clean-up), not an army of billers.
The bottom line
MTLs are not just a badge, they’re a commitment to safeguarding, transparency, and operational discipline that can unlock better margins, more product control, and strategic independence. Treat licensing as a design exercise, not just a paperwork exercise. Build an application machine that reuses 90% of your content across states, stay honest about where you still need a bank partner or alternative authorization (especially in New York and anything crypto-adjacent), and operate like you’ll be examined next quarter.
Do that, and “licensed in X states” becomes not just a slide in your deck, but a competitive moat your customers and counterparties can trust.