Home  /  Fintech Counsel
All practice areas →
Fintech Counsel

Fintech counsel for payments and lending startups.

Whether you need a license, how to structure if you do not, and the contracts and compliance program underneath.

Most fintech founders are quoted a licensing project before anyone has asked whether they need one. The first question is not how to get licensed. It is whether you are transmitting money, lending, or neither.

CounselRaphael Gil, Esq.
AdmittedNew York · Washington
EngagementScoped analysis or retainer
ConsultationFree initial call

The question that comes first

Money transmission is defined by what you do with funds, not by what you call your product.

Receiving money for transmission to a third party

The usual trigger. If funds arrive from one person and you are responsible for getting them to another, you are in the analysis whether or not you call it a transfer.

Holding customer balances or issuing stored value

A balance a customer can draw down later is a liability you owe them. Most states treat that as money transmission regardless of how the product is marketed.

Settling between parties and directing the flow of funds

Control matters more than custody. If you can decide where money goes while it is in motion, that is usually enough.

Routing a payment you never control

Passing instructions to a bank or processor that moves the money itself may fall outside the definition. May. It depends on the contracts and the account structure, not on the architecture diagram.

Collecting as the agent of a payee

Most states exempt a business collecting on behalf of a merchant it genuinely represents. The exemption is narrower than founders assume and turns on whether the payer's obligation is discharged when you receive the funds.

The analysis turns on specifics most founders have never been asked about: whose name is on the account, who bears the loss if funds go missing, who the customer’s contract is with, when title to the money passes, and whether you can direct funds while you are holding them. A clear answer here is worth more than anything else on this page. It decides whether you need a multi-state licensing program, a sponsor bank, a narrower product, or nothing at all.

Registration is not a license

Federal registration and state licensing are different obligations, and satisfying one does nothing for the other.

The federal registration is a filing

Registering with FinCEN as a money services business is a form you submit. It is not permission to operate, and nobody reviews your business before it takes effect.

State licenses are the permission, granted one state at a time

Each state regulator approves you separately, on its own timeline, against its own requirements. Founders routinely complete the federal registration, see it accepted, and believe they are authorised. They are not.

Minimum net worth is usually a formula, not a flat number

Most states now scale it against total assets, so the requirement grows with the business. Model your capital requirement at the volume you are forecasting, not the volume you have.

Surety bonds scale too

Bond amounts rise with transmission volume and with the number of states. Some states accept a deposit or letter of credit instead.

Permissible investments constrain what you may do with customer funds

States require licensees to hold eligible assets against outstanding obligations. This limits treasury strategy in ways that surprise finance teams late.

These are funding questions as much as legal ones

Capital requirements belong in the model before you raise, not after a regulator asks for an audited balance sheet.

The state landscape is converging, slowly

One analysis travels further than it used to. It still does not travel everywhere.

Most of the country has adopted a version of the model law

The Conference of State Bank Supervisors published the Money Transmission Modernization Act to harmonise definitions, exemptions and net worth across states, and the large majority of money transmission activity now happens in states that have adopted some form of it.

Adoption is not uniformity

States enacted different versions at different times with their own amendments, and interpretation already varies enough that CSBS opened a formal guidance-request process to deal with the divergence. A handful of states remain outside the model entirely.

Sequence matters more than coverage

Licensing every state at once is rarely the right first move. Where your customers actually are, which regulators move fastest, and which have requirements you cannot meet yet — that ordering is the difference between launching in a year and launching in three.

Some states will gate the product, not just the timeline

It is normal for a program to launch without a handful of states and add them later. It is better to plan that deliberately than to discover it during onboarding.

If you are lending

Lending brings a separate licensing regime and a separate structural decision underneath it.

Your own licenses, or origination through a partner bank

State lender licensing is the direct route. The bank partnership model is the common alternative, and it is the one that carries structural risk rather than administrative burden.

The bank partnership model works, and is under sustained pressure

A California court ruled in 2026 that the partner bank rather than the fintech was the true lender in a well-known program. That decision is on appeal and binds nobody, and several states have true-lender statutes that reach further than the theory it rejected.

Rate exportation is not available everywhere

Several states have opted out of federal rate exportation for state banks, which is why most programs carry a state-by-state matrix of different terms, different products, or no availability at all.

These arrangements are judged on substance

Who funds the loan and from whose account, who holds it at origination, who keeps economic interest in the receivable, who sets credit policy and who can override it. A program where the bank’s role is real survives scrutiny. One where it is nominal does not, however the agreement is drafted.

What this engagement covers

The work that determines how large and expensive a licensing project turns out to be.

The threshold analysis

Whether your product is money transmission, lending, both or neither — and what would have to change for the answer to change.

Structuring around a license where that is legitimate

Agent-of-payee and payment processor exemptions, sponsor bank arrangements, narrowing the product at launch. Not every route is open to every business, and some that are marketed heavily do not hold up.

Licensing strategy and sequencing

Which states, in what order, against where your customers are and what you can satisfy today.

The commercial stack

Sponsor bank and program agreements, payment processor and banking-as-a-service contracts, merchant and platform terms, customer agreements, and the flow-of-funds provisions that set your regulatory position as much as the licensing analysis does. See vendor and customer contracts and SaaS and licensing.

The compliance program underneath

A written anti-money-laundering program with a designated officer, customer identification, transaction monitoring, reporting and independent testing — the first thing both a regulator and a sponsor bank ask to see. See corporate compliance.

Diligence readiness

Sponsor banks, payment partners and investors all run regulatory diligence. Most early fintechs fail it on documentation rather than on substance. See strategic counsel.

What I do not do, and who does

You should be sceptical of a generalist who claims otherwise.

Not a fifty-state licensing filing shop

Preparing and prosecuting dozens of NMLS applications is specialist work done by people who do nothing else. When a program reaches that point I bring those lawyers in and manage them alongside you, which is the same approach taken with IP, tax and immigration counsel.

Not a substitute for a compliance hire

A written program is not a compliance function. At volume you need someone running it day to day; the program and the policies are what they run.

What I do instead

The analysis that tells you whether you need the program, the structure that sets its scope, the contracts that create your regulatory position, the compliance infrastructure, and the ongoing general counsel role as the company grows into it. That is the work that is usually missing.

When this is worth doing

Earlier than most founders think, and more narrowly.

Worth it: before the flow of funds is built

The expensive mistakes in this sector are made at the design stage, before anyone consults a lawyer. A flow of funds that creates an obligation nobody intended is cheap to fix in a design conversation and expensive to fix after launch.

Worth it: before signing the sponsor bank’s paper

Program agreements arrive on the bank’s form and set your economics, your compliance obligations and your exit terms at once.

Worth it: when the pitch deck and the code disagree

If the product description you are raising on does not match what the system actually does with money, that gap is a regulatory problem and a diligence problem at the same time.

Probably not yet: a full licensing program pre-revenue

If you are pre-product or pre-revenue, the right engagement is a scoped analysis and a structure, not a fifty-state plan.

Probably not yet: crypto-specific questions

Digital asset businesses face an overlapping but distinct regulatory posture. Ask before assuming this page covers your situation.

Companies that clear the threshold analysis and start building usually move to an ongoing arrangement rather than returning per question. That is the Fractional General Counsel model, and in a regulated business it tends to pay for itself earlier than it does elsewhere.

Building something that moves money?

A scoped conversation about whether your product needs a license is usually a short engagement, and it is the one that changes the budget most.