How to Build a Money Transmitter or Remittance App in the US (2026): MTL, FinCEN MSB and Build Guide
AI Summary: Building a money transmitter or remittance app in the US involves more than creating a platform for sending and receiving money. Businesses must understand state-level Money Transmitter License (MTL) requirements, FinCEN MSB registration, AML compliance, and payment infrastructure. This guide explores the regulatory steps, essential app features, technology considerations, and development process to help businesses launch a secure and compliant money transfer solution in 2026. |
Moving money for other people is one of the most regulated things a US fintech can do. A remittance app, a P2P transfer feature, a payout platform or a stored-balance product can each make your company a money transmitter. That brings in federal registration, state licences in almost every state you serve, consumer protection rules for international transfers, and, since 2026, a federal excise tax on some cash-funded remittances.
This guide is for founders and product teams planning a US money transmitter or remittance app. It covers when your product counts as money transmission, the choice between a licensed partner and your own licences, the four layers of rules (federal, state, consumer and tax), a reference architecture, the integrations involved, and what drives cost and timeline. For licences across the US and India, start with our Fintech Licensing Requirements 2026 guide. For the product features of a transfer app, see our earlier post on how to build a money transfer app.
When your app is money transmission
Under FinCEN's rules, a money transmitter is a person that accepts currency, funds or other value that substitutes for currency from one person and transmits it to another location or person by any means. State laws use similar definitions. Products that usually fall in scope:
Product | Why it is likely money transmission |
International remittance app | Accepts funds from a sender and delivers them to a recipient abroad |
Domestic P2P transfers | Moves value between users |
Stored balance or wallet | Holds users' funds for later transfer or spending |
Payouts on behalf of others | Receives funds and pays them out to third parties, depending on structure |
Bill pay services | Accepts consumer funds to pay billers, depending on structure and state exemptions |
There are important edges. FinCEN's definition in 31 CFR 1010.100(ff)(5) excludes certain payment processors that facilitate purchases or bill payments through a clearance and settlement system under an agreement with the seller or creditor. Many states have agent-of-payee exemptions, but their scope varies. Card-acceptance models are covered in our PayFac guide. Get a legal opinion on your fund flow before you design the ledger.
Licence route: partner or your own licences?
Route | What you build | Who holds the licences | Time to launch | Best for |
Licensed partner (you as a programme manager or agent) | App, onboarding UX, pricing, customer support; partner runs regulated money movement | A licensed money transmitter or a bank partner | Faster: partner due diligence and integration | Startups proving demand in a corridor or use case |
Own licences, phased by state | Full stack: compliance, ledger, safeguarding, reporting | You: FinCEN MSB registration plus state MTLs | Long: state-by-state licensing | Companies whose core business is money movement |
Hybrid | Your own licences in key states, partner elsewhere | Split | Medium | Scaling companies moving off a partner |
The partner route is how most products start, and it shapes your architecture. The partner's compliance programme becomes yours by contract: its KYC rules, limits, monitoring and complaint handling. Our licence-as-a-service guide explains how these arrangements work and what to check in the contract.
The federal layer: FinCEN MSB
Registration
Money transmitters are money services businesses (MSBs) regardless of transaction size. FinCEN's MSB registration guidance and 31 CFR 1022.380 require:
Registration on FinCEN Form 107 within 180 days after the business is established
Renewal every two years
Re-registration after certain changes, such as in ownership or a large increase in agents
A list of agents, kept current and available to FinCEN
If you are only an agent of a licensed transmitter, check whether you need your own registration. FinCEN treats agents differently from principals.
Anti-money laundering programme
Every MSB must develop, implement and maintain an effective AML programme reasonably designed to stop it being used for money laundering or terrorist financing. In practice that means written policies, a designated compliance officer, training and independent testing. For software, it means:
Customer identification and verification at onboarding, with risk-based enhanced checks
Transaction monitoring for structuring, velocity, unusual corridors and mule patterns
Suspicious activity reports (SARs). MSBs must report suspicious transactions involving at least $2,000 under 31 CFR 1022.320. Build case management that supports investigation, decision and filing
Currency transaction reports for cash transactions over $10,000, if you accept cash
Funds transfer recordkeeping. Non-bank financial institutions must collect and keep specified information for transmittals of $3,000 or more under 31 CFR 1010.410
Sanctions
All US persons must comply with OFAC sanctions. Screen senders, recipients and counterparties against OFAC lists before funds move, re-screen when lists update, and log every match decision.
The state layer: money transmitter licences
Almost every state requires a money transmitter licence (MTL) to serve its residents, and each state regulator makes its own decision. Most use the Nationwide Multistate Licensing System (NMLS) for applications, renewals and reporting. Expect each state to look at:
Ownership and control persons, with background checks
Net worth, surety bonds and permissible investments to cover outstanding obligations
Your BSA/AML, cybersecurity and complaint policies
Financial statements and business plans
Ongoing reporting and examinations
The Conference of State Bank Supervisors' Money Transmission Modernization Act (MTMA) is a model law meant to standardise these requirements. CSBS's list of state enactments (8 October 2026) shows that a large number of states have adopted it in full or in part. Requirements still differ, especially for partial adopters. Build your compliance reporting so state-specific rules are configuration.
The consumer layer: CFPB remittance rule
If you send money from US consumers to recipients abroad in the normal course of business, the CFPB's remittance rule in Regulation E, Subpart B applies. A provider that made 500 or fewer remittance transfers in both the previous and current calendar years is not treated as doing so in the normal course of business. Once you pass that number, these rules turn into product features:
Requirement | What you build |
Pre-payment disclosure (amount, fees, taxes, exchange rate, amount received) | A quote screen with all required elements, before the sender pays |
Receipt after payment, including the date funds will be available and error and cancellation rights | A receipt screen, email or SMS with the required content |
Cancellation within 30 minutes of payment, with a full refund within three business days if the funds have not been picked up or deposited | A cancel button and a refund flow that works within those windows |
Error resolution: notices accepted up to 180 days after the disclosed availability date, investigation within 90 days, results within three business days of finishing | An error intake flow, case tracking and remedy handling |
The CFPB's small entity compliance guide explains each requirement in plain language and is worth giving to your product team.
The tax layer: remittance transfer excise tax
From 1 January 2026, a 1% federal excise tax applies to certain remittance transfers that the sender pays for with cash, a money order, a cashier's check or a similar physical instrument. The remittance transfer provider collects the tax and reports it to the IRS. The IRS announcement on the proposed regulations sets out the details. If you accept cash at agent locations, your quote, disclosure and reporting logic must handle the tax. Transfers funded from bank accounts or cards are treated differently, so tag each transfer's funding source accurately.
Reference architecture
Module | Responsibilities |
Onboarding and KYC | Identity verification, document checks, risk scoring, enhanced due diligence triggers |
Sanctions screening | Sender, recipient and counterparty screening, list updates, match review |
Quote and FX engine | Live rates, fees, taxes, quote expiry, disclosure generation |
Transfer state machine | Quoted, funded, screened, sent, paid out, cancelled, refunded, returned |
Ledger | Double-entry balances for customer funds, fees, FX positions, partner and bank accounts |
Funding connectors | ACH debits, debit cards, bank transfers, cash at agents |
Payout connectors | Bank deposit, mobile wallet and cash pickup partners per corridor |
Transaction monitoring | Rules and models for structuring, velocity, corridor risk; alert queues |
Case management | SAR investigation, decisioning and filing records |
Disclosures and receipts | Reg E pre-payment disclosures, receipts, cancellation and error notices, multilingual where required |
Complaints and error resolution | Intake, tracking, deadlines, remedies |
Regulatory reporting | State call reports via NMLS, FinCEN filings, tax reporting |
Safeguarding and reconciliation | Daily reconciliation of customer obligations against bank balances and permissible investments |
Keep the compliance modules independent of any one partner. If you start on a partner's licences and later get your own, you want to replace the partner connector, not rebuild monitoring and case management.
Key APIs and integrations
Identity and KYC: document and selfie verification, database checks, phone and email risk
Sanctions screening: OFAC and other list screening with ongoing monitoring
Bank account verification and ACH: to fund transfers from US bank accounts
Card processing: debit card funding, with attention to card network rules for money transfer
FX and payout networks: corridor partners for bank deposit, wallet and cash pickup. Our list of international money transfer APIs compares options
Banking partner APIs: for customer fund accounts and reconciliation
Case management and reporting tools: for SARs and regulator reporting
For cross-border specifics such as corridors, FX and settlement, see our guide to cross-border payments app development. Our post on US fintech compliance (KYC, KYB, AML, PCI) covers the controls in more depth.
Cost and timeline drivers
We do not quote fixed prices because scope varies widely. These are the factors that matter most:
Driver | Why it matters |
Route | Partner launch is an app and integration build; own licences add state-by-state applications, bonds, capital and exams |
Number of states | Each state adds application work, reporting and examination exposure |
Corridors and payout methods | Each corridor adds partners, FX handling and local rules |
Funding methods | ACH, cards and cash each carry different risk, cost and tax handling |
Compliance tooling | Monitoring, case management and screening are ongoing costs, not one-off builds |
Consumer rule scope | Reg E disclosures, cancellation and error resolution add flows and testing |
Audits and exams | Independent AML testing, state exams and partner audits need documentation and engineering time |
Build plan in phases
Get a legal view of your fund flow: money transmission, payment processor or agent-of-payee.
Choose the route: licensed partner, own licences or hybrid. Pick launch states and corridors.
Build onboarding, screening, quote and transfer flows with the ledger at the centre.
Add monitoring, case management, disclosures, cancellation and error resolution before launch.
Launch in a few corridors, measure loss and fraud rates, then expand.
Apply for your own licences when volume and economics justify it, and migrate state by state.
Build your money transmission app with Fintegration
Fintegration builds payment, lending and banking platforms for fintechs in the US and India. We can help you choose between partner and own-licence routes, design the transfer state machine, ledger, monitoring and Reg E flows, and integrate KYC, sanctions, ACH and payout partners. Talk to our team to scope your build.
FAQ
1. What is a money transmitter or remittance app?
A money transmitter app allows users to send, receive, and transfer money digitally, often across different states or countries.
2. Do I need a Money Transmitter License (MTL) to launch a remittance app in the US?
In most cases, yes. Businesses conducting money transmission must obtain the required state-level licenses unless an exemption applies.
3. What is the role of FinCEN MSB registration?
FinCEN requires businesses operating as Money Services Businesses (MSBs) to register and follow applicable AML compliance and reporting requirements.
4. What features should a US remittance app include?
Essential features include user onboarding, identity verification, money transfers, payment tracking, transaction history, fraud monitoring, and compliance checks.
5. How much does it cost to build a money transfer app in the US?
The cost depends on app complexity, payment integrations, licensing, security, and compliance requirements. Licensing and operational expenses should be budgeted separately.
