Picture this: The product is built, the customers are interested, and the fintech has found a bank willing to provide the regulated financial services behind the platform.
Launch day is getting close. It’s time to order hors d’oeuvres.
Then someone asks a question that is considerably less exciting than the product demo: If a customer disputes a transaction on Monday morning, whose problem is it?
Or a more uncomfortable one: If the fintech fails, who has the records necessary to figure out where the customers’ money is?
Those questions get to the heart of banking as a service. The technology may make the financial product feel simple to the customer, but behind the screen are two organizations with different expertise, different responsibilities and, in many cases, different regulators.
The federal banking agencies sometimes describe arrangements involving banks and nonbank companies as “banking-as-a-service” or “embedded finance,” depending on the structure and parties involved. As highlighted by the principles in the Federal Reserve’s Joint Statement on Banks’ Arrangements with Third Parties to Deliver Bank Deposit Products and Services, an important consideration is whether the bank effectively understands and manages the risks created by the arrangement.
That makes a solid partnership agreement vital.
A fintech often brings the software expertise, the product development, and the ability to move quickly. A bank brings access to regulated financial infrastructure and the experience and discipline required to operate inside the banking system. Combining the two can make sense for deposit products, lending, payments, and other financial services.
But the agreement connecting them has to do considerably more than say, “You provide the technology; we’ll provide the bank.”
It needs to explain how the service will actually work when reality arrives.
1. Start With the Regulated Activity, Not the Org Chart
One attraction of banking as a service is that a fintech may be able to offer financial products through a bank rather than trying to recreate the bank’s regulatory position on its own.
That distinction can matter considerably in businesses such as payments and lending. Nonbank financial companies remain subject to state licensing regimes in many areas. The Conference of State Bank Supervisors’ Money Transmission Modernization Act is an ongoing effort to make state money-transmission requirements more uniform, but as of Sept. 2026, only 31 states had enacted the model law in full or in part.
Partnering with a bank, however, does not mean everybody gets to put “compliance” in somebody else’s column and move on.
Under the federal banking agencies’ Interagency Guidance on Third-Party Relationships: Risk Management, a banking organization remains responsible for conducting its activities in a safe and sound manner and in compliance with applicable law even when a third party performs part of the activity. The guidance specifically contemplates relationships with fintech companies.
So one of the first jobs of a bank-fintech agreement is to map the service in detail.
The parties may need to answer:
- Who establishes the customer relationship?
- Who performs onboarding and identity verification?
- Who makes lending or account decisions?
- Who processes transactions?
- Who provides required customer disclosures?
- Who responds to complaints and transaction disputes?
- Who maintains the authoritative customer and transaction records?
- Who oversees vendors performing pieces of those functions?
But a harder question follows each of those: Who is responsible for making sure it was done correctly?
A fintech might operate the interface where customers submit information while the bank retains responsibility for ensuring a particular banking requirement is satisfied. A service provider might conduct elements of customer identification, for example, while the bank still needs appropriate controls and procedures to monitor the third party’s performance. The FFIEC’s BSA/AML examination procedures for Customer Identification Programs (CIP) specifically instruct examiners to evaluate those controls when third parties perform CIP functions.
This is where fintech compliance becomes much more concrete than a policy manual. It becomes workflow design.
2. The Agreement Needs a Way to Change the Agreement
A normal supply contract can be impressively final.
Let’s say that you want 20,000 bricks. They need to be this large, this color, and delivered on this date. Once everyone agrees on the specifications and price, there may not be much reason to revisit the arrangement.
But brick orders rarely experience regulatory developments. Banking-as-a-service programs, on the other hand, do.
The product changes, customer volume grows, or the fintech adds a feature. Then a fraud pattern emerges, a new service provider enters the chain, a regulator changes its expectations, or a procedure that worked perfectly with 5,000 customers begins wheezing audibly at 500,000.
You get the picture.
Trying to put every operating detail permanently into the primary contract can create its own problem.
A better agreement establishes a way for the parties to change how the service operates without renegotiating the entire relationship every Tuesday.
That might include:
- A governance committee with representatives from both organizations
- Designated compliance, business, and technology contacts
- Escalation procedures when the parties disagree
- A jointly approved policy and procedure library
- A separate platform playbook describing how particular functions are performed
- A process for approving material changes to the program
This is especially relevant to fintech regulation right now.
In Sept. 2026, the Federal Reserve, FDIC, OCC and NCUA proposed new third-party risk-management guidance intended to replace existing guidance. The Federal Reserve’s announcement explained that the proposal reflects lessons learned from supervising third-party relationships, while the OCC’s description of the proposal emphasized a more risk-based approach to oversight.
Whether or not the final guidance looks exactly like the proposal, the larger lesson is difficult to miss: The regulatory framework surrounding fintech partnerships does not stand still.
The contract should not assume it will. This is one area where the agreement benefits from a little humility. The parties cannot predict everything that will happen over a five-year relationship.
They can decide in advance who gets in the room when it does.
3. “Who Owns the Customer?” Is Not a Simple Question
Customer information may become one of the most valuable assets created through a banking-as-a-service relationship.
It may also become one of the most complicated.
The bank and fintech can accumulate customer identification data, account information, transaction histories, marketing records, and other information as the program operates.
So who owns it?
Sometimes the answer is the bank…and sometimes the fintech. Often the reality is that the two businesses maintain distinct but overlapping sets of information with different access and use rights.
If you were looking for a simple, clear answer on that, the real world doesn’t provide one. Sorry.
The “Who owns the customer?” question is really shorthand for a much longer discussion:
- Which party owns or controls each database?
- What information can the other party access?
- Which system contains the official record when two records disagree?
- May either party use customer information for its own marketing?
- May information be shared with affiliates or service providers?
- What information may each party retain after termination?
- Who must maintain records for regulatory or legal purposes?
- What happens to data if one of the parties becomes insolvent?
Privacy law also limits how casually the parties can treat those answers.
The CFPB’s Regulation P, which governs privacy of consumer financial information, requires covered financial institutions to provide certain privacy notices and restricts some disclosures of nonpublic personal information to nonaffiliated third parties. It also limits certain reuse and redisclosure of that information.
The federal banking agencies’ third-party risk-management guidance separately recommends that contracts address data access, confidentiality, security, incident notification, and the return or destruction of information after termination.
The agreement, therefore, has to reconcile two facts:
- Customer information can be commercially valuable.
- Customer information is also regulated information.
Those facts occasionally run in opposition to each other.
This issue becomes particularly important in embedded finance, where the customer’s primary interaction may be with a nonbank brand even though a bank sits behind the financial product. The customer experience may make the program look like one seamless product. The legal and operational structure underneath it usually is not.
4. Compliance Obligations Need Names Attached to Them
It would make things easier if the agreement simply stated: “Both parties will comply with applicable law.”
Regulators, however, tend to expect more detail.
The laws that matter depend on the product, but a banking-as-a-service program may implicate rules covering deposits, lending, payments, anti-money laundering, sanctions, privacy and other areas.
For example, depending on the particular service:
- The CFPB’s Regulation E governs covered electronic fund transfers and includes requirements involving disclosures, consumer liability, and error resolution.
- The CFPB’s Regulation DD implements the Truth in Savings Act and governs disclosures for covered deposit accounts, including information about rates, fees, and account terms.
- The FFIEC BSA/AML Examination Manual makes clear that banks need appropriate controls when third parties perform certain customer-identification functions.
- OFAC’s Framework for Compliance Commitments recommends risk-based sanctions compliance programs built around management commitment, risk assessment, internal controls, testing, and training.
The agreement doesn’t necessarily need to reproduce the Code of Federal Regulations in miniature, but it does need to make the operating responsibilities clear.
If the fintech handles a customer complaint, when must the bank know about it? If one party performs sanctions screening, what evidence does the other receive? Who updates disclosures when a product changes? Who approves policy revisions? Who keeps the documentation showing the process actually occurred?
This is where fintech law stops being an abstract discussion about whether a rule applies and starts becoming a series of very ordinary operational questions: Who? When? Using what system? Who checks?
Banking regulation has a remarkable ability to turn four short questions into 30 pages of procedures.
5. The Compensation Formula Can Quietly Rewrite the Risk Model
A banking-as-a-service relationship also has to make economic sense.
Let’s be real. Banks are not generally volunteering their infrastructure for cultural enrichment, and fintechs aren’t developing technology as a charitable exercise.
Depending on the program, compensation could involve:
- Technology or platform fees
- Fees for services performed by the bank
- Referral or program fees where legally permissible
- Deposit or cost-of-funds economics
- Transaction-related revenue
- Interchange allocations
- Dedicated staffing or compliance expenses
- Costs charged by third-party technology providers
The contract needs to define the calculation well enough that both accounting departments can arrive at approximately the same number without legal counsel serving as an interpreter.
But precision is only half the issue because compensation changes behavior.
The federal banking agencies’ third-party risk-management guidance specifically cautions against performance measures or incentives that encourage imprudent behavior, including rewarding processing volume or speed without adequate consideration of accuracy, compliance requirements, or effects on customers.
That observation deserves attention when designing a bank-fintech compensation model.
If everyone earns substantially more whenever new accounts open faster, but nobody’s compensation changes when the compliance workload doubles, the contract has created an incentive. It may simply be the wrong one.
Economics and compliance should be designed together rather than negotiated by separate groups that meet for the first time at closing.
6. Write the Breakup Plan Before Anyone Wants to Break Up
Most commercial contracts contain termination provisions. Banking-as-a-service agreements may need an actual evacuation plan.
That difference becomes especially important when customer funds are involved.
Suppose the fintech goes bankrupt tomorrow. Can the bank independently identify every customer and balance? Can it access the transaction history? Could another provider take over the program? Who communicates with customers? How long would a transfer realistically take? What if the bank can no longer provide the service?
On the other hand, let’s suppose nothing catastrophic happens at all, and the parties simply decide three years from now that the relationship no longer works.
The agreement should already have considered:
- How long the transition period lasts
- Which services continue temporarily after termination
- Who provides transition assistance
- Who retains access to systems and records
- How customers are notified
- Who bears transition expenses
- How customer funds and active transactions are handled
- What happens if one party is unable — or legally prevented from being able — to cooperate
After the 2024 bankruptcy of Synapse Financial Technologies disrupted access to funds for customers whose money had been placed at banks through fintech arrangements, the FDIC reported that partner banks encountered significant difficulty obtaining, reviewing, and reconciling Synapse’s records.
That lesson extends beyond that one company.
A financial-services agreement should not assume the party responsible for helping with the transition will remain healthy, cooperative, and fully staffed at precisely the moment the transition is needed.
The Best Contract Still Cannot Fix the Wrong Partnership
At this point, a banking-as-a-service agreement can begin to sound less like a contract and more like a minor system of government.
There is a reason for this. The parties are combining technology, regulated financial activity, customer relationships, compliance processes, data, and money inside one operating model. The primary agreement may then sit above policies, procedures, service levels, vendor agreements, and a platform playbook.
But you can draft all of that carefully and still encounter something nobody anticipated.
Imagine that a new regulatory interpretation emerges, economics change, fraud increases, technology fails, or one party wants to launch a product that the other thinks creates too much risk.
No contract can eliminate the need for judgment, and that makes partner selection part of the legal strategy.
A good bank-fintech relationship needs parties willing to exchange information, identify problems, exercise some give-and-take, and adjust the program when regulations or economics change. The agreement should create the mechanisms that make those conversations possible.
For banks and fintechs, that may be the most important distinction between a conventional commercial contract and a banking-as-a-service agreement. The document is not only describing today’s deal; it’s establishing how the parties will make tomorrow’s decisions.
Before entering or revising a banking-as-a-service arrangement, trace five things from beginning to end:
- Regulated activity
- Compliance responsibility
- Customer data
- Economics
- Exit path
If one of those trails disappears into language saying the parties will “mutually agree later,” it deserves another look.
A fintech lawyer or financial services lawyer experienced with these arrangements can help translate the actual product into the agreement rather than starting with generic contractual language and hoping the operations happen to fit.
At Farley Law, we work with banks and fintech companies on financial-services relationships, regulatory issues, and the contracts behind them. We specialize in helping people understand complicated agreements, especially in this industry.


