Finance term
Banking-as-a-Service (BaaS)
Also known as: BaaS, embedded banking, embedded finance, BaaS platform
Definition
Banking-as-a-Service (BaaS) is the delivery of regulated banking capabilities — accounts, payments, cards, lending — through APIs by licensed banks to non-bank businesses (fintechs, brands, platforms) for embedding in their own products, subject to OCC supervisory guidance and CFPB Section 1033 data-portability rules.
Detailed explanation
Banking-as-a-Service is the infrastructure layer that powers embedded finance — when a non-bank company (a fintech, an e-commerce platform, a payroll provider, a SaaS company) offers banking products (deposit accounts, debit cards, payments, lending) directly within its own user experience without holding a banking license. The licensed bank (the 'BaaS bank' or 'sponsor bank') provides the regulated infrastructure and charter; the fintech or brand provides the customer experience.
Regulatory framework: BaaS arrangements are supervised through the sponsoring bank's primary federal regulator. The OCC issued guidance on third-party relationships in 2021 (OCC Bulletin 2021-25, occ.gov/news-issuances/bulletins/2021/bulletin-2021-25.html) and, jointly with the FDIC and Federal Reserve, published comprehensive Third-Party Risk Management guidance in June 2023 (occ.gov/news-issuances/bulletins/2023/bulletin-2023-17.html — Joint Guidance on Third-Party Relationships). This guidance requires BaaS banks to maintain direct oversight of fintech partners, conduct due diligence equivalent to what they'd apply to internal operations, and ensure consumer protections apply through the full delivery chain.
CFPB Section 1033 (Personal Financial Data Rights Rule, finalized October 2024 — consumerfinance.gov/rules-policy/final-rules/personal-financial-data-rights/) directly affects BaaS: it requires covered financial institutions (including BaaS banks and their fintech partners) to make consumer and small-business account data available in machine-readable, standard formats to authorized third parties. This creates data portability obligations that BaaS platforms must architect into their API designs.
For small businesses, BaaS is the mechanism behind neobanks (Mercury, Relay, Bluevine), embedded payroll banking (Gusto, Rippling), e-commerce banking (Shopify Balance), and fintech lending (Kabbage/American Express, Brex). The sponsor bank behind each product (often Thread Bank, Coastal Community Bank, Cross River Bank, Blue Ridge Bank) holds the FDIC-insured deposit charter and the OCC/state bank examination relationship, while the fintech brand manages the customer experience. FDIC insurance passes through to end customers (FDIC.gov/deposit/deposits/brokered.html covers pass-through insurance for deposit accounts held through intermediaries).
◈ Worked example
- A payroll SaaS company embeds BaaS-powered business checking accounts and debit cards: the SaaS company provides the UI, the sponsor bank (e.g., Thread Bank) holds the deposits, provides the Visa card BIN sponsorship, and processes ACH transfers. Customers see only the SaaS brand.
- A small business e-commerce platform offers 'instant payouts' to sellers: BaaS infrastructure enables the platform to push funds to sellers' accounts within minutes of a sale via FedNow or RTP, without the platform holding a payments license directly.
- OCC 2023 Third-Party Risk Guidance consequence: a BaaS bank that failed to conduct adequate due diligence on its fintech partners received a formal supervisory action in 2023–2024, forcing it to pause new BaaS partnerships and remediate risk-management gaps — illustrating that regulatory risk lives with the sponsor bank, not the fintech.
Common questions
The most-asked questions about Banking-as-a-Service (BaaS) — answered straightforwardly.
Are deposits in a BaaS-powered neobank FDIC-insured? +
Yes, provided the BaaS bank is FDIC-insured and the deposit is properly titled. FDIC pass-through insurance covers accounts held at insured depository institutions through intermediaries (brokers, fintechs) — the $250,000 per-depositor limit applies to the underlying bank, not each intermediary. Verify the sponsor bank name (disclosed in your account agreement) and confirm it is FDIC-insured at fdic.gov/bank/individual/failed/banklist.html or the FDIC BankFind tool.
What is the difference between a BaaS bank and a fintech? +
A BaaS bank holds a federal or state banking charter, is FDIC-insured, and is subject to OCC, Federal Reserve, or state bank examination. It is the regulated entity. A fintech BaaS partner (neobank, platform, SaaS company) is not a bank — it provides the technology and customer experience but relies on the sponsor bank for the regulated functions. Consumer protections (Reg E, Reg Z, TILA, ECOA) apply through the sponsor bank's obligations, which it contractually extends to the fintech relationship.
How does BaaS affect small business lending? +
BaaS platforms that hold small business deposit data can provide embedded lending products with faster underwriting — the lender sees real-time cash-flow data from the business's own embedded account, eliminating the bank-statement collection step. This is the model behind many fintech MCA and revenue-based financing products. CFPB Section 1033 data portability will accelerate this further by standardizing how deposit data flows between financial institutions for underwriting purposes.
Further reading
This glossary entry is educational content. ClearValue Lending is a business & personal financing platform — not a lender, broker, or financial advisor. Specific product terms vary by lender; verify with the lender or issuer before applying. See privacy policy.