Part 3 of 4: Sponsor Banks, BaaS, and Plugging Digital Assets into the Banking System

In Part 1 of this series, Fastest Route to Market: Money Transmission Licensing Roadmaps for FinTechs, we explained why most early-stage companies begin by assessing federal MSB registration and state money transmitter licensing when they plan to move, hold, or manage customer funds. Federal MSB registration may be relatively quick, but obtaining state money transmitter licenses is typically one of the slowest and most demanding paths discussed in this series. In Part 2, we showed how that baseline becomes more complex for digital asset businesses, where securities, commodities, and virtual currency-specific regimes layer onto the money transmission analysis as product features evolve.

Part 3 shifts the focus from licensing categories to infrastructure. Once a company has selected its regulatory approach, the practical question is how to connect that structure into the traditional payments system. Sponsor banks and banking-as-a-service (BaaS) arrangements are common tools for doing so. They can allow a digital asset or FinTech business to access core banking functions and payment rails without obtaining a bank charter or rebuilding the entire regulatory stack in-house. Used thoughtfully, they can accelerate launch and extend product capabilities. Used reflexively, they can create dependencies that are difficult to unwind and that effectively lock the company into a particular regulatory lane.

The throughline remains speed to market. The aim is to reach customers quickly while preserving flexibility for how the regulatory and infrastructure stack evolves over time.

The Sponsor Bank Model: Banking Functionality Without a Charter

A sponsor bank relationship allows a non-bank FinTech to provide a customer-facing experience for banking products offered through a chartered institution.[1] The bank is not merely a back-end provider and cannot be treated as a fully white-labeled institution from a regulatory or contractual perspective. It provides the regulated product, holds customer funds on its balance sheet, opens and maintains accounts (often through omnibus or for-benefit-of structures), and connects to payment systems such as ACH, Fedwire, RTP, and card networks.[2] It is subject to the full suite of banking supervision, including safety-and-soundness, consumer protection, and BSA/AML obligations.[3]

The FinTech may design the user experience, build the app or platform, and perform substantial operational and compliance functions under the bank’s oversight.[4] But the user relationship must reflect the bank’s role in the regulated product.[5] The customer will need contractual privity with the bank in some form often through pass-through terms in the FinTech’s agreements and, increasingly, through direct contractual terms between the customer and the bank.[6] The bank must be clearly identified in the applicable account agreements and disclosures, rather than treated as an invisible provider behind a fully white-labeled program.[7] From the regulator’s perspective, the bank remains responsible for ensuring that the overall program meets supervisory expectations.[8]

For digital asset businesses, this model fills specific gaps that the MSB and money transmitter framework does not address on its own. A wallet provider that wants users to fund balances with ACH transfers, a stablecoin platform that needs fiat reserves held in insured accounts, or a tokenization platform that settles trades in dollars all need a way into the banking system. A sponsor bank relationship provides that connection without requiring the company to apply for and operate under a full bank charter, which for most early-stage firms would be misaligned with capital, governance, and timing realities.

What Banking-as-a-Service Really Delivers

“Banking-as-a-service” is often used as a marketing term, but in practice it describes a particular way of packaging sponsor bank capabilities.[9] Instead of the FinTech negotiating and integrating directly with a single bank, a BaaS platform may sit in the middle and provide a standardized interface to one or more banks’ infrastructure.[10] The platform supplies APIs, operational tooling, and sometimes compliance support, while the underlying bank or banks provide the chartered status and access to payment rails.[11]

Despite the variations in branding, the core functions tend to look similar. A BaaS stack will typically include some form of account sponsorship, under which end users hold balances at the bank that are sub-accounted to the FinTech’s customers.[12] It will provide mechanisms to originate and receive payments, whether via ACH, wires, or card networks. And it will define how onboarding, sanctions screening, transaction monitoring, and dispute handling are allocated among the bank, the BaaS platform, and the FinTech.[13] The structure must also preserve the bank’s contractual relationship with the end user, whether through incorporated pass-through terms or direct agreements, because the banking product remains the bank’s regulated product.[14]

In the digital asset context, these capabilities often sit alongside on-chain functionality. A crypto platform might allow users to deposit fiat through an ACH pull to an account at the sponsor bank, convert that balance into stablecoins or other tokens, and later redeem back into dollars in the same account structure. A tokenized asset platform might settle trades in fiat that moves through sponsor bank accounts even though the assets themselves live on-chain. In each case, the BaaS arrangement is what makes the digital asset product usable in a world where customers still hold and spend dollars.

Regulatory Allocation: Layers, Not Substitution

A recurring misconception is that operating through a sponsor bank “covers” the FinTech’s regulatory obligations. The reality is more layered. The bank remains fully responsible for its own compliance obligations.[15] It must satisfy its primary regulators that the program meets expectations around BSA/AML, sanctions, consumer protection, and third-party risk management.[16] That is why sponsor bank agreements tend to include detailed requirements around policies, controls, reporting, audit rights, and the bank’s ability to approve or veto product changes.[17]

At the same time, the FinTech retains its own regulatory obligations. If it is registered as an MSB, it still must implement and maintain its own BSA/AML program, with a designated compliance officer, written policies, training, independent testing, and customer diligence and monitoring mechanics tailored to its activities.[18] If it holds state money transmitter licenses, it remains subject to state examinations, net worth and bonding requirements, and ongoing reporting.[19] If its digital asset activities implicate securities or commodities regimes, it may separately need to consider broker-dealer, ATS, exchange, FCM, or similar registrations, regardless of the presence of a bank partner.[20]

The resulting structure is one of overlapping oversight rather than substitution. The FinTech answers to its own regulators and to the sponsor bank, which in turn answers to bank supervisors. Misalignment between these layers is where many programs run into trouble. A customer onboarding flow that fits comfortably within the FinTech’s view of MSB expectations may nonetheless fall short of the sponsor bank’s CIP standards.[21] A new token or yield feature that the FinTech believes it can justify under securities or commodities analysis may be beyond the bank’s risk appetite. In those cases, the bank’s supervisory environment often dictates the outcome.

Speed to Market, But With Structural Dependency

Relative to pursuing a de novo charter or specialized bank license, sponsor bank and BaaS arrangements can offer a faster path to launch. The bank already has connectivity to payment systems, an established compliance framework, and a supervisory relationship.[22] The FinTech can focus on integrating APIs, aligning policies and procedures, and executing product and operational buildout. In many cases, the difference is measured in months versus years.

The cost of that speed is structural dependency. Because the bank owns the charter and provides the regulated product, it controls key aspects of the program.[23] It can impose constraints on eligible customer types, geographies, transaction sizes, and product features.[24] It can require the FinTech to modify onboarding flows, monitoring thresholds, disclosures, contractual terms, or communications in response to exam feedback that the FinTech may not see directly.[25] In the extreme, it can decide that a category of business such as a particular digital asset use case no longer fits within its risk appetite and move to wind down the program on a timeline that reflects regulatory and internal pressures rather than the FinTech’s commercial needs.[26]

For early-stage companies, that tradeoff is often acceptable. The alternative may be to remain pre-launch while pursuing licensing or chartering paths that stretch beyond investor and runway constraints. But as the business scales, the concentration risk inherent in relying on a single sponsor bank becomes harder to ignore. A payments or digital asset platform that has built its product, operations, and customer relationships tightly around one bank’s infrastructure may find that changing banks or moving to a different regulatory lane altogether is more complex and disruptive than anticipated.

Designing the Relationship With the Future in Mind

Because the structure of a sponsor bank or BaaS arrangement has long-term implications, it is worth making certain early design choices deliberately rather than by default. One is how the customer relationship is framed. The bank should be identified as the provider of the regulated account or payment product and must have contractual privity with the customer, whether through direct agreements or enforceable pass-through terms. The FinTech may remain the primary brand and customer-facing point of contact, but the program should not portray the bank as an invisible or fully white-labeled back-end provider. Clear agreements and disclosures should explain the parties’ respective roles, account ownership, complaint handling, and liability allocation.

Another choice is how systems of record are structured. If the bank or BaaS platform is the sole source of truth for balances and transactions, moving to a different bank or model later may require significant operational migration. If the FinTech maintains its own robust ledger and reporting infrastructure, with clear reconciliation processes, it may be better positioned to add additional bank relationships, change providers, or support a future transition to direct licensing or a chartered entity.

A third structural choice is the scope of services and responsibilities spelled out in the program agreement. Decisions about who performs KYC, who conducts sanctions screening and transaction monitoring, who handles fraud investigations and chargebacks, and how these functions are documented will all influence both day-to-day operations and how regulators view the division of labor. Thoughtful allocation can keep the program workable in the short term while leaving room to bring functions in-house as the company matures.

Viewed this way, the sponsor bank model is not just a commercial contract. It is a key part of the regulatory roadmap, and it should be evaluated alongside MSB, money transmitter, securities, and commodities considerations as part of an integrated strategy.

A Bridge to the Next Regulatory Lane

For many FinTech and digital asset startups, sponsor banks and BaaS platforms are best understood as a bridge rather than a destination. They provide a way to launch products, build a compliance track record, and demonstrate operational competency without first securing a bank charter or specialized license. They can coexist with MSB registration, state money transmitter licenses, and, where applicable, securities or commodities registrations, giving the company more than one regulatory pillar to lean on.

Over time, however, the balance may shift. As transaction volumes grow, as the product set expands, or as the company’s business model converges more explicitly on core banking functions, the limitations of a sponsor-bank-centric approach may become more pronounced. Economic constraints, product approval friction, and exposure to a single bank’s risk appetite can all become strategic issues in their own right.

Part 4 of this series will pick up at that inflection point. It will examine when it may make sense to move beyond a sponsor bank or BaaS model into a specialized charter or other bank-like structure, and how to plan that transition so that the company is not forced into a long-term regulatory lane that no longer matches its business. The objective, throughout, is to give founders a way to think about regulatory choices as a sequence of options rather than a one-time bet made at launch.

Thinking about your own licensing roadmap?

Every FinTech’s path to market turns on the specifics: your product structure, target states, projected transaction volume, and available runway. Contact us to schedule a licensing roadmap consultation and get a clear, sequenced picture of what your regulatory path looks like from Day One.

Taft’s FinTech Practice is composed of attorneys specializing in bankruptcy, banking, blockchain, cryptocurrencies, and digital assets, corporate, financial services, government investigations, intellectual property, litigation, public policy, securities, tax, technology, transactional, and regulatory issues that serve clients across the FinTech space.

This article is intended for general informational purposes only and does not constitute legal advice. Licensing requirements vary by jurisdiction and business model. Consult qualified legal counsel before making regulatory filing decisions.

---

[1] Office of the Comptroller of the Currency, Board of Governors of the Federal Reserve System & Federal Deposit Insurance Corp., Joint Statement on Banks’ Arrangements with Third Parties to Deliver Bank Deposit Products and Services (July 25, 2024), available at: https://www.occ.gov/news-issuances/bulletins/2024/bulletin-2024-20.html.

[2] Id.

[3] 12 U.S.C. § 1831p-1 (2022); 31 C.F.R. § 1020.210 (2025); 12 C.F.R. § 1005.7 (2025); 12 C.F.R. § 1030.4 (2025).

[4] Interagency Guidance on Third-Party Relationships: Risk Management, 88 Fed. Reg. 37,920 (June 9, 2023).

[5] Joint Statement on Banks’ Arrangements with Third Parties to Deliver Bank Deposit Products and Services, supra note 1.

[6] 12 C.F.R. § 1030.4(a)–(b) (2025); 12 C.F.R. § 1005.7(a)–(b) (2025).

[7] Interagency Guidance on Third-Party Relationships: Risk Management, supra at note 4.

[8] Joint Statement on Banks’ Arrangements with Third Parties to Deliver Bank Deposit Products and Services, supra note 1.

[9] Id.

[10] Interagency Guidance on Third-Party Relationships: Risk Management, supra at note 4.

[11] Joint Statement on Banks’ Arrangements with Third Parties to Deliver Bank Deposit Products and Services, supra note 1.

[12] 12 C.F.R. §§ 330.5, 330.7 (2025); Fed. Deposit Ins. Corp., Pass-Through Deposit Insurance Coverage (May 29, 2024), available at: https://www.fdic.gov/financial-institution-employees-guide-deposit-insurance/pass-through-deposit-insurance.

[13] Interagency Guidance on Third-Party Relationships: Risk Management, supra at note 4.

[14] Joint Statement on Banks’ Arrangements with Third Parties to Deliver Bank Deposit Products and Services, supra note 1.

[15] Joint Statement on Banks’ Arrangements with Third Parties to Deliver Bank Deposit Products and Services, supra note 1; Interagency Guidance on Third-Party Relationships: Risk Management, supra note 4.

[16] Joint Statement on Banks’ Arrangements with Third Parties to Deliver Bank Deposit Products and Services, supra note 1; Interagency Guidance on Third-Party Relationships: Risk Management, supra note 4.

[17] Joint Statement on Banks’ Arrangements with Third Parties to Deliver Bank Deposit Products and Services, supra note 1; Interagency Guidance on Third-Party Relationships: Risk Management, supra note 4.

[18] 31 C.F.R. § 1022.210 (2025).

[19] Conference of State Bank Supervisors, Model Money Transmission Modernization Act §§ 7.01–.05, 10.01–.02 (2023), available at: https://www.csbs.org/sites/default/files/2023-02/CSBS%20Money%20Transmission%20Modernization%20Act.pdf.

[20] 15 U.S.C. § 78o(a)(1) (2022); 17 C.F.R. § 242.300 (2025); 7 U.S.C. § 6d(a)(1) (2022); 15 U.S.C. § 78f (2022); 17 C.F.R. § 242.301(b)(1) (2025).

[21] 31 C.F.R. § 1020.220 (2025).

[22] Joint Statement on Banks’ Arrangements with Third Parties to Deliver Bank Deposit Products and Services, supra note 1; Interagency Guidance on Third-Party Relationships: Risk Management, supra note 4.

[23] Joint Statement on Banks’ Arrangements with Third Parties to Deliver Bank Deposit Products and Services, supra note 1; Interagency Guidance on Third-Party Relationships: Risk Management, supra note 4.

[24] Interagency Guidance on Third-Party Relationships: Risk Management, supra note 4.

[25] Id.

[26] Office of the Comptroller of the Currency, New, Modified, or Expanded Bank Products and Services, OCC Bulletin 2017-43 (Oct. 6, 2017), available at: https://www.occ.gov/news-issuances/bulletins/2017/bulletin-2017-43.html.