Banking as a Service: How FinTechs Launch Without a Bank Licence

Banking as a service lets fintechs offer deposits, cards and payments under their own brand while a licensed sponsor bank carries the charter, the compliance and the risk.

2026-11-07 · 8 min read

Key takeaways

  • BaaS splits one banking product across three parties, and the licensed bank always remains the regulated entity
  • Deposit insurance covers the failure of the bank, not the failure of the fintech or the middleware sitting between them
  • Unit economics rest on interchange share, platform fees and deposit spread, all of which the fintech controls only partially
  • Sponsor bank selection is a compliance decision, a revenue decision and a concentration risk in one

What banking as a service actually means

Banking as a service (BaaS) is an operating model, not a product. A licensed institution exposes regulated capabilities — deposit accounts, card issuing, payment initiation, lending — through software interfaces, so that a non-bank company can distribute them under its own brand. The bank keeps the charter, the deposit insurance and the direct connection to the payment rails. The fintech keeps the customer, the interface and the product roadmap.

For a founder or product manager, BaaS reframes a familiar question. The alternative to partnering is authorisation: applying for a banking charter, or for the lighter licences described below, and building the compliance, capital and reporting machinery that comes with it. BaaS trades that multi-year, capital-heavy path for a commercial contract and an integration project. What it does not trade away is the regulation — it relocates it.

The three layers of a BaaS stack

The sponsor bank

The sponsor bank is the legal entity behind every account, card and loan in the programme. In the United States it holds a state or national charter and FDIC insurance; it is the institution the supervisor examines, not the fintech. Sponsor banks in this market tend to be smaller institutions with a taste for programme business, and their risk appetite, concentration limits and supervisory standing set the boundaries of everything built on top of them.

The platform and API layer

Between the bank and the brand sits the technology layer. Some providers are pure middleware; others own a charter and build modern interfaces directly on top of it. This layer typically supplies:

  • account and sub-ledger creation, with individual customer balances mapped to a pooled account held at the bank "for benefit of" (FBO) end users;
  • card issuing, tokenisation and programme management;
  • payment initiation across ACH, wires and instant rails — the mechanics of which are covered in our guide to payment rails;
  • identity verification (KYC, "know your customer"), business verification (KYB) and sanctions screening orchestration;
  • transaction monitoring, dispute and chargeback handling.

Middleware matters because core banking systems inside small banks are often decades old. The platform's job is to translate file feeds and batch processes into something a product team can call on demand.

The brand

The top layer is the consumer or business-facing application. From the customer's point of view the brand is the financial provider. In practice the account sits at the sponsor bank, and the brand is a service provider to that bank.

This layering is the same idea behind embedded finance APIs, applied to regulated banking products specifically.

Why fintechs choose BaaS over a charter

Three arguments dominate.

Time to market. A charter application runs through capital adequacy, governance, management fitness and a full anti-money-laundering programme before the first customer is onboarded. An API integration rarely does.

Cost. A sponsor bank already pays for the core system, the compliance function, the audit and the exam. The fintech pays for a share of the revenue instead of building the whole apparatus.

Focus. Teams that are good at distribution and user experience are usually not good at regulatory reporting. BaaS lets each side do what it does well.

The alternatives are worth knowing. In the EU, a company can seek an electronic money institution or payment institution authorisation instead of a full credit institution licence — a lighter regime tied to the E-Money Directive and the second Payment Services Directive, still requiring authorisation, own funds and supervision, but far narrower than banking. In the UK, an authorised bank can operate under a restricted licence while it builds out its systems, and many jurisdictions run regulatory sandboxes that let firms test with real customers under supervision. What is permitted in the US under a sponsor bank arrangement is not automatically available in the EU or the UK.

Who is legally responsible for what

The sponsor bank is the regulated entity. That is not a formality. Supervisors have been explicit that a bank cannot outsource responsibility for compliance to a fintech partner: three US banking agencies issued a joint statement on arrangements with third parties setting out expectations for third-party risk management, and warning that misleading statements about deposit insurance coverage are themselves a regulatory violation.

Deposit insurance is narrower than the marketing suggests

A BaaS account is usually insured on a pass-through basis: the end customer is covered as if they were a depositor of the bank, up to the standard limit, even though the funds sit in a pooled account. The FDIC's own guidance on pass-through coverage explains the mechanics, and the conditions are strict — the bank's records must disclose the depositor relationship, and individual beneficial owners must be identifiable.

This is where the model broke publicly. The failure of Synapse, a middleware provider connecting banks and fintechs, left consumer funds frozen for months because balances could not be reconciled; American Banker has reported a shortfall of roughly USD 65 million to USD 95 million in customer money. The lesson is precise: insurance protects against the failure of a bank, not the failure of a fintech or a technology intermediary. The FDIC's account of the episode makes the same point, and in September 2024 the agency proposed a recordkeeping rule for custodial deposit accounts with transactional features. As proposed, the rule would require banks to hold records identifying each beneficial owner and their balance, to have direct, continuous access to third-party records even if the provider fails, and to obtain an annual independent validation. Whether and in what form the proposal is finalised remains uncertain, so many programmes are being designed with its stricter recordkeeping standard in mind.

How the money works

BaaS revenue comes from four places: fees charged to the fintech, a share of card interchange, a share of the interest earned on deposits, and a share of any credit product. Interchange is explained in detail in our piece on card interchange fees.

Layer What it contributes How it earns Main exposure
Sponsor bank Charter, FDIC insurance, rails, ledger Deposit spread, programme fees, interchange share Supervisory action, concentration risk
Platform / API layer Interfaces, orchestration, card programme management Subscription, per-account fees, per-transaction fees, interchange share Thin margins until scale, client failure
Fintech brand Customers, product, experience Interchange share, account and subscription fees, deposit yield share Fraud first-loss, compliance cost, sponsor dependence

Pricing is negotiated contract by contract and, per the ABA Banking Journal's overview of BaaS partnerships, hybrid structures blending interchange, fixed fees and net interest margin sharing are increasingly common.

Two structural features shape returns. First, in the US debit interchange is capped by regulation for the largest banks while smaller institutions are exempt — the same ABA piece notes how the USD 10 billion asset threshold drives revenue sharing — which is why sponsor bank selection is a revenue decision as much as a compliance one. Second, the deposit spread only became a meaningful revenue line when rates rose, and it falls again when they do. Commercial market-size estimates for the sector vary widely between research houses and rest on differing definitions, so they are best treated as directional rather than as hard figures.

Risks and costs

  • Reconciliation risk. If the bank cannot tie every end-user balance to a pooled account, funds can be frozen. This is operational risk, and the fintech carries the reputational version of it whatever the contract says.
  • Regulatory spillover. When a sponsor bank receives an enforcement action or supervisory criticism, new requirements flow downstream to every programme it hosts. Those requirements arrive as contract amendments, and the cost lands on the fintech.
  • Concentration. A single sponsor bank relationship becomes a single point of failure for the product, the deposits and the roadmap.
  • Interchange dependence. Many consumer propositions only work because of the small-bank interchange exemption. Legislative or regulatory change to that carve-out would reprice the whole model.
  • Costs absent from the price sheet. Identity verification, transaction monitoring, fraud losses on a first-loss basis, reserve capital, programme management and support staffing are usually borne by the fintech, not the platform.
  • Portability. Migrating accounts, card programmes and payment identifiers between providers is slow and expensive. Exit rights, data formats and change-of-control clauses deserve as much negotiation as pricing.
  • Rate sensitivity. Deposit yield sharing shrinks when policy rates fall, and end users frequently receive little of it regardless.
  • Credit risk. Where the programme includes lending, credit losses sit somewhere in the stack. Establish exactly where before launch.
  • Disclosure risk. Overstating deposit insurance coverage is a regulatory violation, not a marketing slip.

A practical checklist for evaluating a BaaS partner

  • What is the sponsor bank's supervisory record, and are there open enforcement actions?
  • Who maintains the beneficial-owner ledger, and how is reconciliation evidenced to the bank daily?
  • Is the account titling structured to support pass-through insurance, and who confirms it?
  • What are the concentration limits, velocity caps and prohibited use cases?
  • Which costs are excluded from the quoted pricing, and what triggers a repricing?
  • What are the migration, termination and change-of-control rights?
  • Who owns the customer relationship contractually, and who controls pricing changes to the end user?
  • What dispute, fraud and outage service levels apply, and what are the remedies?

Bottom line

Banking as a service lets a fintech ship regulated products quickly by borrowing a bank's licence, systems and regulatory standing. The trade is explicit: less capital and time up front, less control afterwards. Deposit insurance protects against the failure of the bank, not the failure of the technology in the middle — a distinction that the Synapse episode made expensive for everyone involved, and one that proposed recordkeeping rules would harden further. Founders should model the full cost stack rather than the price sheet, treat sponsor bank selection as a revenue and resilience decision, and negotiate exit rights before launch, not after. For the routing layer that often sits alongside a BaaS stack, see our guide to payment orchestration. Nothing here is a recommendation of any provider or bank.

This article is for information and education only. It is not investment advice and does not take into account your personal situation. Read the full disclaimer.

Follow the shortlist

Following payments, banking and market-infrastructure change? Our global ETF and stock research watchlist is tracked daily. Premium members get the full list, the reasoning behind every entry and updates when entries change.

See premium access

Information and education only, not investment advice.

Related