Banking-as-a-Service in 2027: Providers, Costs and Business Models
In April 2024 a company most consumers had never heard of, Synapse, filed for bankruptcy. Thousands of people using fintech apps built on its technology could not reach their money while others tried to work out whose balance was whose. The apps looked like banks. Behind them was a chain of contracts, and one link had snapped.
That episode changed how serious buyers evaluate Banking-as-a-Service. The pitch used to be speed. Now the first question is who holds the ledger and what happens when something fails.
Banking-as-a-Service (BaaS) is an arrangement in which a licensed bank makes its core services, such as accounts, cards and payments, available through APIs so that non-bank companies can offer them under their own brand. This guide covers how it works, the main providers, what it costs, and the business models that make it pay.
Quick answer
Banking-as-a-Service lets a non-bank company offer accounts, cards and payments by connecting to a licensed bank through APIs, usually via a middleware provider. Pricing is mostly usage-based and rarely published: expect platform fees, per-account and per-transaction charges, and revenue sharing with the bank. The sponsor bank’s regulatory health is the main risk.
How does Banking-as-a-Service work?
In a typical BaaS setup, three parties are involved: a sponsor bank that holds the charter and the deposits, a middleware or BaaS platform that connects to the bank through APIs, and the fintech or brand that builds the customer experience. The customer sees only the brand.
The company launching the product does not need its own banking licence. It does need to run onboarding, customer support and many compliance processes, because the bank remains accountable to its regulator and passes the requirements down. Regulators have made clear that the bank cannot hand off responsibility along with the work.
Three structures dominate. Some providers act as middleware between a fintech and one or more partner banks. Some banks offer their own APIs directly, with no intermediary. Some large payments companies, such as Stripe, offer banking features on top of partner banks within a broader platform.
Who are the main Banking-as-a-Service providers?
In the United States, the leading BaaS names include Unit, Treasury Prime, Synctera, Column and Stripe Treasury. In Europe and the UK, providers include Solaris, Swan, Griffin and ClearBank. They differ in structure, in which banks sit behind them, and in how much compliance support they bundle.
| Provider | Model | Notable trait |
|---|---|---|
| Unit | Middleware with partner banks | All-in-one accounts, cards, lending components |
| Treasury Prime | Multi-bank network | Choice of bank partner; no single-bank lock-in |
| Synctera | Bank marketplace | Connects fintechs with community banks, compliance tooling |
| Column | Chartered bank with API | Direct bank relationship, no sponsor layer |
| Stripe Treasury | Embedded in payments platform | Banking features inside the Stripe stack |
Features and bank partners change often, so check each provider’s current offering. Treasury Prime has also moved toward selling software to banks directly, a reminder that vendor positioning shifts with the market.
Which model is best depends on your risk tolerance. Middleware with several partner banks gives you flexibility if one bank has problems. A direct bank API removes a layer, and with it a layer of failure, but ties you to one institution’s appetite for your business.
How much does Banking-as-a-Service cost?
Banking-as-a-Service pricing is mostly unpublished. Unit, Treasury Prime and Synctera all direct buyers to a sales conversation, and pricing is described as usage-based. Costs typically combine a platform or integration fee, per-account and per-transaction charges, minimum commitments, and a revenue share with the partner bank.
- Platform and integration fees: setup, API access, sandbox and support tiers.
- Per-account and per-transaction fees: charged for each account opened and each payment, card or transfer processed.
- Minimum commitments: a floor on monthly or annual spend, which hurts small programmes most.
- Revenue share: the split of interchange and interest income between the fintech, the provider and the bank.
- Compliance costs: program management, fraud tools, KYC and AML screening, and staff.
Some third-party guides quote annual cost ranges for different company sizes. Treat them cautiously, since they rarely show their method and contracts are negotiated. The more reliable way to compare is to ask each shortlisted provider for a written quote against the same scenario: your expected number of accounts, monthly transaction volume and card spend.
Do not forget the cost that is not on the invoice. Ledger reconciliation, dispute handling and regulatory reporting all take staff time, and the bank partner may audit you. Budget for a small compliance and operations team from the start.
How do BaaS business models make money?
A fintech on a BaaS platform earns mainly from card interchange, a share of deposit interest, and fees for premium features. Providers earn from platform and usage fees plus a share of the programme’s revenue, and sponsor banks earn from deposits and fees.
Interchange is the foundation for many consumer and small-business programmes, so the economics depend on card spending per account. A programme whose users hold balances but rarely spend can struggle. Deposit economics depend on interest rates and on how much of the spread the bank keeps.
Fintechs with a strong core product, such as accounting software or a payments platform, often treat BaaS as a way to deepen the relationship and cut payment costs, not as a standalone profit centre. That is a healthier framing than expecting banking features alone to carry the business.
What are the risks, and what happened to the sponsor banks?
The central risk in BaaS is sponsor-bank and middleware failure. Following the Synapse collapse, US regulators issued consent orders against several sponsor banks over weak oversight of fintech partners, and some banks were barred from taking on new programmes without regulatory approval.
Orders came from the FDIC, the Federal Reserve and the OCC against banks active in the fintech sector, including Evolve Bank & Trust, Blue Ridge Bank and Lineage Bank, according to published summaries. The details differ bank by bank, but the common theme was inadequate monitoring of third-party programmes, anti-money laundering weaknesses and poor records.
The practical takeaway is to diligence the bank, not just the platform. Find out which banks sit behind your provider, whether any are under a consent order, and how concentrated your programme is with one of them. Ask whether you receive a regular, independent reconciliation of customer balances against the bank’s records.
Who should not use Banking-as-a-Service?
Companies without the appetite or budget for ongoing compliance should not use BaaS. A BaaS programme is not a one-time integration; it comes with audits from the partner bank, regular reporting and permanent staffing for onboarding, disputes and fraud.
If your goal is simply to move money for customers, a payments provider that handles the regulated layer may serve you better and carry less risk. BaaS pays off when holding accounts or issuing cards is central to your product, and when you have the volume to justify the operating cost.
How should you choose a BaaS provider?
- Define your product: accounts, cards, payments, lending, or a mix, and the countries you will serve.
- List the providers that cover your geography and products, and note which sponsor banks stand behind each.
- Review each bank’s regulatory record and its appetite for your type of business.
- Ask for written pricing against your own volume scenario, including minimums and revenue share.
- Examine the ledger design: who holds the master record, how often it is reconciled, and what you can export.
- Negotiate exit and migration terms before signing, including data portability and a transition period.
A candid recommendation: if your product depends on holding customer funds, favour arrangements with more than one bank or a direct relationship with a bank you have diligenced yourself. Speed to launch matters less than the ability to survive a partner’s bad quarter.
Frequently asked questions
What is Banking-as-a-Service in simple terms?
Banking-as-a-Service lets a company that is not a bank offer banking features, such as accounts and debit cards, by connecting to a licensed bank through software interfaces. The bank holds the licence and the money, and the company designs the customer experience and runs onboarding and support.
Do I need a banking licence to use BaaS?
No. The partner bank provides the regulatory cover, including the charter and deposit insurance where applicable. You still need to run KYC and AML processes, follow marketing and complaints rules, and in some cases hold separate licences for activities like money transmission or lending.
How much does a BaaS platform cost?
Pricing is mostly unpublished and negotiated. Providers like Unit, Treasury Prime and Synctera describe usage-based models with platform fees, per-account and per-transaction charges and revenue sharing. Ask for written quotes against your own expected volume, and check for minimum monthly commitments.
What was the Synapse collapse?
Synapse was a US middleware company that filed for bankruptcy in April 2024. Its failure left customers of several fintech apps unable to access funds while balances were reconciled between the company and partner banks. It prompted tighter regulatory scrutiny of sponsor banks and fintech partnerships.
What is the difference between BaaS and embedded finance?
BaaS is the infrastructure that lets a bank’s services be accessed through APIs. Embedded finance is the customer-facing use of that infrastructure inside a non-financial product, such as a software platform offering business accounts. One is the supply side, and the other is the finished feature.
Related reading
- DORA for fintechs: an operational resilience checklist
- Cross-border payments in 2026: rails, costs and reform
- Buy now, pay later: business models, risks and regulation
This article is general information, not legal, financial or investment advice. Rules, prices and product features differ by country and change often, so check current details with a qualified adviser or the provider. See our disclaimer. Last reviewed November 2, 2026.
Published by The Funding Journal Editorial. Practical writing on fintech, crowdfunding, investment platforms, SaaS and AI, and the stories of founders who raised capital.
