The United States is the largest fintech market in the world and the only one where the rulebook fragments fifty ways. For Australian, New Zealand and UK fintechs, US entry is usually the biggest prize on the roadmap — and the place where architecture shortcuts taken at home get exposed. Here’s the US map from a CTO’s chair.
Quick answer
Building fintech for the US market in 2026 means navigating a layered system: federal AML obligations through FinCEN, state-by-state money transmitter licensing (or a bank/BaaS partnership that carries it for you), consumer protection under the CFPB, and a payments landscape running ACH, RTP and FedNow simultaneously. The central architectural decision is the partnership model — who holds the licences and the accounts — because it dictates your compliance surface, your data obligations and much of your stack.
The US regulatory map
- FinCEN — the federal AML layer. Money services businesses register with FinCEN and carry Bank Secrecy Act obligations: KYC programs, transaction monitoring, suspicious activity reports. This is systems work, and US banking partners audit it hard.
- State money transmitter licensing — the famous US complication. Moving money as principal generally requires licences state by state, each with its own reporting, bonding and examination regime. Many fintechs avoid the full patchwork initially by operating through a licensed partner — which trades licensing burden for partner-dependency.
- CFPB — consumer financial protection, including the Section 1033 data-access rule that is shaping US open banking; treat implementation timelines as in flux and design consent and data-access capability rather than betting on a specific deadline.
- SEC / FINRA — the moment your product touches securities, investments or certain digital assets, a different and heavier regime applies.
- Bank partners and BaaS — most non-bank fintechs ride on partner banks, and US supervisors have sharply increased scrutiny of these arrangements in recent years. Expect your partner bank’s compliance requirements to function as de facto regulation — flowing directly into your onboarding, monitoring, reconciliation and reporting systems.
The payments landscape
- ACH — the workhorse: batch, cheap, ubiquitous, with same-day windows but not real-time
- RTP — The Clearing House’s real-time network, strong and growing among larger institutions
- FedNow — the Federal Reserve’s instant-payments service, expanding bank coverage year on year
- Cards and wires — scheme rules and PCI DSS on one side, Fedwire for high-value on the other
Unlike Australia (NPP) or the UK (Faster Payments), no single real-time rail covers the market — reachability depends on the receiving bank. US payment features need capability-aware routing: real-time where possible, ACH fallback where not, with the difference invisible to the user.
What this means for your architecture
- The partnership model is an architecture decision — direct licensing, BaaS platform or sponsor bank each produce different ledgers, data flows and audit surfaces; decide deliberately, not by default
- Multi-rail routing from day one — abstract the rails behind a payments core so ACH/RTP/FedNow selection is logic, not rewrite
- Compliance evidence to bank-partner standard — SOC 2 is commercial table stakes, and partner-bank audits reach into your monitoring, reconciliation and incident practices
- State-aware configuration — disclosures, fees and permissible activities can vary by state; platforms that treat the US as one jurisdiction accumulate exceptions fast
- Data protection by sector and state — GLBA obligations plus a growing patchwork of state privacy laws; classify and control data at the schema level, not the policy level
Entering the US from Australia, NZ or the UK
US expansion exposes every hidden assumption in a home-market platform: single-currency ledgers, hard-coded KYC rules, settlement-time assumptions, data-residency defaults. The fintechs that enter cleanly are the ones whose platforms were designed multi-jurisdiction early — the pattern in our overview of building fintech across Australia, New Zealand, the US and the UK. The commercial reality also differs: US banking partners effectively audit your engineering before they’ll work with you, so due-diligence readiness is a market-entry requirement, not a nice-to-have.
Working with a fractional CTO on US market entry
Founder Ken Armitt has 27 years across payments, fintech and enterprise technology, including NYSE-listed environments, and works with fintechs building for or expanding into the US. Typical engagements: partnership-model and architecture decisions, multi-rail payments design, bank-partner due-diligence readiness, and standing CTO leadership through market entry. See payments & fintech advisory, our fintech CTO New York page, and published pricing.
Frequently asked questions
Do we need fifty state licences to launch a fintech in the US?
Not necessarily — many fintechs launch through a licensed partner or BaaS arrangement that carries money-transmission licensing, then revisit direct licensing as volume grows. It’s a legal and commercial decision with major architecture consequences either way.
Should we build on ACH, RTP or FedNow?
All three, behind an abstraction. No single US rail gives full real-time coverage, so capability-aware routing with ACH fallback is the pattern that works.
What will a US bank partner examine before working with us?
Your AML systems, transaction monitoring, ledger and reconciliation discipline, security posture (SOC 2 at minimum), incident history and change management. It resembles technical due diligence — arrive prepared.
Is this legal advice?
No — it’s a technology leader’s view of what the US regime means for your build. Licensing strategy belongs with US counsel; we design and evidence the systems alongside them.