Skip to main content
Alliance Legal ExpertsClear law. Practical next steps.

Pathway 02

Banking, Payments & Fintech

How U.S. federal and state law treats payment products, lending features, bank partnerships, open banking, and digital assets.

There is no single U.S. fintech statute. A payment or lending product picks up obligations from a patchwork of federal regulators — the CFPB, FinCEN, the banking agencies, sometimes the SEC or CFTC — layered over fifty state licensing regimes. The result: two products that look identical to a user can carry completely different legal duties.

These guides are built around the questions examiners and bank partners actually ask: who touches the funds, who owns the customer relationship, what the fee really is, and which written agreement says so. Start with the guide that matches your product's mechanics, not its marketing label.

Foundational guide

If you read one thing here

Banking, Payments & Fintech

Embedded Finance Agreements: Which Company Owns the Compliance Risk?

When a software company adds accounts, cards, or lending through a partner bank, the contract says who does the compliance work — but regulators decide who answers for it. The two are not the same.

7 min

What changes the answer here?

  • Flow of funds — who holds, receives, or transmits customer money and when
  • Whether a fee is structured (and disclosed) as credit, a tip, or a service charge
  • The states where customers live, since licensing is state-by-state
  • What your bank partnership agreement actually allocates, in writing
  • Federal rulemaking still in motion — several regimes here are mid-transition

Partnership & infrastructure

Who owns compliance when a bank and a fintech share a product.

Product classification

Whether the product is money transmission, credit, or something else.

Digital assets

The federal stablecoin framework and what still varies.

Where this pathway connects

Questions here often lead into these areas next.