Banking as a Service in 2026: Stack, BaaS TCO & Build Cost
Banking as a service lets a software product offer accounts, cards, and payments through a licensed bank's rails. Here's how the BaaS stack is wired, what you build vs buy, the compliance after Synapse, and the cost.

On this page

Banking as a service is the practice of a licensed bank exposing its regulated capabilities, accounts, payments, and card issuing, as APIs that a software product can consume without holding a charter of its own. You call an endpoint to open an account, another to issue a card, another to move money, and a stack of parties beneath you turns that call into a real transaction on the banking and card networks. The bank keeps the license. Your product keeps the customer. That split is why a payroll tool, a logistics platform, or a vertical SaaS product can hold balances and issue cards. You'll also see the model called BaaS banking, or just BaaS.
This guide is written from the builder's chair. It goes a level below the sales pitch, into the stack an engineer integrates against: the sponsor bank, the BIN sponsor, the provider middleware, the ledger, and the boundary where the provider stops and your code starts. It also covers what happens to your build when a provider fails, because one did in 2024.
The short version
- Banking as a service (BaaS) lets a non-bank software product offer accounts, cards, and payments by calling a licensed bank's APIs, while the sponsor bank holds the charter and the product keeps the customer relationship.
- The stack runs bottom to top: a sponsor bank holds the license, a BIN sponsor enables card issuance, a provider such as Unit or Solaris exposes the APIs, ledger, and compliance tooling, and your app sits on top consuming it.
- The provider gives you the regulated core (ledger, KYC engine, card issuing, and payment-rail access), while you build the user experience, a product sub-ledger, daily reconciliation, idempotent payment calls, and your own fraud rules.
- BaaS is the infrastructure, embedded finance is the user-facing experience built on top of it, and open banking is a separate consent-based data-sharing layer that sits beside both.
- The 2024 Synapse collapse froze customer funds when the provider's and the bank's ledgers disagreed, so independent reconciliation and knowing which licensed bank holds the money are now core engineering work. A July 2024 US interagency statement made the same point to banks.
- Cost has two sides: provider fees (a setup fee, a monthly minimum commonly quoted at roughly $5,000 to $15,000 or more and negotiated per program, per-account and per-rail pricing, and an interchange split) plus your own engineering. That build runs $135,000 to $285,000 in CEE at Idealogic's $75/hr, versus $297,000 to $627,000 at our $165/hr estimate for US agencies, for an immutable PostgreSQL sub-ledger, daily FBO reconciliation, KYC/KYB orchestration, and PCI DSS v4.0.1 card controls.
What banking as a service is, and where it sits in the stack
Banking as a service is a delivery model where a chartered bank packages its regulated functions, holding deposits, moving money across rails, issuing cards, as developer-facing APIs that non-bank software consumes. The defining property is the separation of license from product. The bank carries the regulatory weight: deposit insurance eligibility, the relationship with examiners, the obligations under banking law. The software product carries the experience: the screens, the onboarding, the support, the brand the customer trusts.
At the bottom of the stack is a licensed bank. Above it sits a BaaS provider, a technology company that translates the bank's slow, batch-oriented core banking software into clean modern APIs and adds the ledger and compliance tooling that the bank requires. On top of the provider sits your application, which never touches the bank's core directly. When a user taps a button in your product, the request travels down through the provider to the bank to the network, and the confirmation travels back up. The user sees one screen. Three or four regulated and unregulated parties did the work, each owning a precise slice of it. If you know which party owns which slice, your system can survive an audit and a provider failure. If you don't, it won't.
Banking as a service vs embedded finance vs open banking, in one minute
Banking as a service, embedded finance, and open banking describe different layers, and treating them as synonyms produces bad architecture. The one-line version: BaaS is the infrastructure, embedded finance is the experience built on it, and open banking is a data-sharing framework that sits beside both.
In practice the three stack on each other. You almost always sit on BaaS to ship embedded finance, and you might use open banking, governed in Europe by the Payment Services Directive 2 (PSD2, Directive (EU) 2015/2366), to read a customer's existing accounts or initiate account-to-account funding inside that flow. PSD2 still applies. Its successors, PSD3 and the Payment Services Regulation, have been agreed politically but aren't yet applicable. We unpack the embedded-finance layer in depth in our embedded finance guide; here we go a level down, into the infrastructure that powers it.
How a BaaS stack is wired: sponsor bank, BIN sponsor, provider, and your app
A BaaS stack is wired as a chain of responsibilities, each connected by an API boundary: a sponsor bank holds the license at the base, a BIN sponsor enables card issuance, a provider or middleware exposes the API layer and runs the ledger and compliance tooling, and your app sits on top consuming it all. Money and instructions flow down the chain. Confirmations and webhooks flow back up. A good build respects each boundary and doesn't reach across it.
Sponsor bank and BIN sponsor
The sponsor bank is the chartered institution that legally holds customer deposits, settles on payment rails, and answers to regulators. It's the only party in the chain that can hold the money. Card issuance brings in a second role, the BIN sponsor, the entity that owns the bank identification number range under a card network like Visa or Mastercard and lets cards be issued against it, while network rules require PCI DSS v4.0.1 compliance from anyone handling cardholder data. Sometimes the sponsor bank is also the BIN sponsor; sometimes they are separate, and that separation matters when you trace where a card program's risk really lives.
BaaS provider and your app
Above the bank sits the BaaS provider, the middleware that does the work your team would otherwise build from scratch. It exposes the APIs you call, runs the ledger that records every balance and movement, and operates the compliance tooling, the KYC engine, the screening, the reporting, that the bank requires of every program on its rails. On top sits your app: the product, the user experience, and the integration code that speaks to the provider. The cleaner you keep that top boundary, the easier it is to swap providers later or absorb a function in-house. The figure and table below lay out the four layers and the boundary between each.
What the provider gives you versus what you build on top
The split between provider and product is the most important architectural line in a BaaS build: the provider gives you the regulated core, and you build everything that makes the product yours. Almost nobody should write a bank core ledger of record, card-network processor, or identity-verification bureau from scratch, and fewer still should chase their own banking license early (the general trade-off is in our build vs buy software guide). What you do build is the experience, the product sub-ledger, and the integration logic. That's a substantial system in its own right.
On the provider side of the line sit the core ledger that tracks balances, the KYC and onboarding engine that verifies identity, card issuing that mints virtual and physical cards, and the connections to the payment rails that settle money (how those rails work is in our payment processing software guide). On your side sit the user interface, a product sub-ledger that maps the provider's accounts to your own users and internal logic, reconciliation that proves your records and the provider's agree, idempotent payment calls so a retried request never moves money twice, webhook handling that absorbs the asynchronous, out-of-order events the financial rails emit, and the fraud and limit rules specific to how your product is abused. The table below draws the line capability by capability.
The ledger and reconciliation problem
The ledger problem is the question of who holds the authoritative record of every customer's balance, and reconciliation is the daily discipline of proving every record agrees. In a BaaS build there are at least two ledgers in play: the provider's, which the sponsor bank settles against, and your own product sub-ledger, which maps those balances onto your users and your features. They must agree to the cent, every day. If they don't, money is going missing somewhere in the chain.
The structure underneath usually involves an FBO account, a "for benefit of" account the sponsor bank holds that pools customer funds, with the provider's ledger tracking each end user's share inside it. Your sub-ledger mirrors those shares. A reconciliation job compares the two and flags any drift the moment it appears, because drift that goes unnoticed is how a customer ends up unable to withdraw money that the system insists is there. Idempotency keys on every money movement keep a retried request from double-posting and corrupting the very records you are trying to reconcile. For orchestrating compensating payment sagas alongside scheduled cutoff jobs, see our Temporal vs Airflow engineering comparison.
This is where Synapse failed. When the provider filed for Chapter 11 in April 2024, its records and the partner banks' records didn't line up, and working out who was owed what became enormously difficult. End users of products built on the rails lost access to their funds while the ledgers were untangled. If you're building now, your reconciliation is what protects your users when a layer beneath you breaks, so give it the same rigor as the money movement itself. The Federal Deposit Insurance Corporation (FDIC) drew the same conclusion: in September 2024 it proposed that banks keep daily beneficial-owner records for the custodial accounts underlying these programs.
Choosing a banking as a service provider as an engineering decision
Pick a BaaS provider on engineering grounds first and commercial ones second, because it becomes load-bearing infrastructure you can't cheaply replace. A provider whose APIs are immature, whose webhooks drop events, or whose sponsor bank cannot support the product you need becomes a wall you hit a year in, after your money already flows through it. So evaluate on technical and structural questions.
Work through these in discovery:
- API and sandbox quality. Are the APIs documented, versioned, and stable, with a sandbox that behaves like production and webhooks you can test against? You will live inside this integration for years.
- Webhook reliability. Does the provider deliver events durably, with retries, signatures, and a way to replay missed events? Your ledger correctness depends on never silently losing one.
- Which banks the provider sponsors. Which licensed bank or banks stand behind the provider, and what does each one's program permit? The bank is the real boundary on what you can offer, and single-bank dependence is a concentration risk.
- License type. Does the provider rely on a sponsor bank, or does it hold its own banking or electronic-money (EMI) license governed in Europe by the EU Electronic Money Directive 2 (EMD2, Directive 2009/110/EC)? An EMI can safeguard funds and issue accounts and cards, but it can't take deposits, pay interest, or lend customer funds. Any credit it grants must be ancillary and funded from its own capital. That sets your product ceiling.
- Data portability and exit risk. Can you export your ledger, customer, and transaction data in a usable form, and how hard is it to move to another provider or bring a function in-house? Plan the exit before you sign.
Some examples make the categories concrete. In the US market, companies such as Unit, Treasury Prime, and Synctera operate as middleware that connects products to sponsor banks. In Europe, Solaris runs as a licensed institution itself, and ClearBank operates as a clearing bank with API access. Treat these as examples of how providers are structured. We aren't ranking or recommending them, and company status changes, so confirm each one's current license and bank partners before you shortlist it. The right choice depends on your product, your geography, and the licensed entity you're comfortable having behind your money.
The 2023-2024 banking as a service reckoning: what Synapse and the FDIC actions mean if you build now
Between 2023 and 2024, a provider failure and a coordinated regulatory response reset what "build on a provider" demands of you. The provider was Synapse. Its collapse in 2024 froze funds for end users of products built on its rails and showed how fragile the model gets when ledgers can't be independently verified and nobody clearly owns each responsibility.
US regulators answered directly. Building on the Interagency Guidance on Third-Party Relationships: Risk Management (FIL-29-2023), the Federal Reserve, the FDIC, and the OCC issued a joint statement on 25 July 2024 on arrangements between banks and third parties that deliver bank products and services, which is the bank-fintech setup BaaS runs on. The statement creates no new rules. It flags the risks in these partnerships, reminds banks of existing expectations on oversight, record-keeping, and the management of funds held for end users, and came with a request for information on the arrangements.
What does that change for a build? Provider due diligence stops being optional. You need to understand the provider's financial health, its bank relationships, and how it keeps its ledger, because its failure is now a modeled risk in your own system. Be precise about who owns compliance too: the regulators made clear that a bank can't outsource its responsibility for the program, even when a provider runs the tooling. And treat sponsor-bank concentration as a real exposure. A program riding on a single bank inherits that bank's regulatory troubles, and some banks tightened or exited their BaaS programs in this window. The model still works, with a higher bar. Products clear it when reconciliation and ownership are built in from the first commit.
The teams that survive a provider failure are the ones that treated their own ledger and reconciliation as the product, not as plumbing. When a layer beneath you breaks, your records are the only thing standing between your users and their money.
Who owns compliance, and the parts you cannot outsource
Compliance ownership in banking as a service is layered, and the most expensive mistake is assuming the provider absorbs all of it. The regulatory relationship belongs to the sponsor bank. The bank owns its obligations under the Bank Secrecy Act and anti-money-laundering law administered by FinCEN, and the interagency guidance from US regulators made explicit that a bank stays responsible for those obligations even when a third party operates the controls. The provider runs much of the tooling. You, the product, feed the controls and own the parts that touch your users directly.
Map it to the concrete controls. BSA, AML, and sanctions screening are the bank's regulatory duty, operated through the provider's engine, but they only work if your product collects the right data and integrates the screening into your flows. KYC and KYB, verifying individual and business identity, gate who can hold an account or a card, and while the provider supplies the engine, the onboarding experience and the data quality are yours to get right. We cover that build in detail in our KYC software guide. The parts you can't outsource are the ones bolted to your own product: accurate identity data at onboarding, correct surfacing of disclosures, your fraud and transaction-monitoring signals, and the reconciliation that proves the money is where your records say it is.
Operational resilience is the other half of compliance that builders underestimate, and in Europe it is now law. The EU Digital Operational Resilience Act (DORA, Regulation (EU) 2022/2554) sets requirements for how financial entities and their critical technology providers manage operational and cyber risk, alongside the European Banking Authority's outsourcing guidelines (EBA/GL/2019/02), which its new guidelines on third-party risk management will replace for non-ICT services. If your BaaS build touches the EU, your provider relationship falls inside the third-party dependency controls DORA and the EBA expect you to manage. Messaging standards like ISO 20022 add structured remittance and party data to the payment instructions moving through these rails, which matters once you are reconciling and reporting at volume.
What banking as a service costs to build on
Provider fees usually combine a setup fee, a monthly minimum commonly quoted at roughly $5,000 to $15,000 or more (negotiated per program), per-account and per-transaction charges, and an interchange split. Your own build runs $135,000 to $285,000 in Central and Eastern Europe at $75 per hour, per the tiers further down. Teams routinely conflate those two sides. Both scale with how much of the stack you take on, so a single number never holds for long. The provider side is a recurring bill tied to usage. The build side is engineering plus the standing cost of a compliance function, and that's the line most teams underestimate by the widest margin.
Provider fees
Expect a setup or platform fee to get a program live, per-account and per-transaction pricing as the recurring usage cost, often a monthly minimum that bites before you reach scale, and an interchange share, the cut of card-network fees a card program returns to you, which can offset cost as spend grows. Minimums and setup fees are what make the lightest tier still nontrivial for an early product. The table below breaks the components down by who charges and what drives each one.
BaaS is no longer experimental. Fortune Business Insights puts the 2025 global banking as a service market at about $22.7 billion, growing near 19% a year to 2034. Other firms publish different figures because they define BaaS differently, so read these as direction. What it means for a builder: provider economics are competitive, and the durable cost is operational.
Your build and compliance cost
Start at the lightest tier that delivers real value, prove the flow, and climb only when volume or strategy demands it. For the broader mechanics of pricing a build at this depth, see the worked ledger, KYC, and sponsor-minimum budgets in our fintech app development cost guide, or run a scoped discovery with the custom software development team. Platforms shipping this as a SaaS product tend to start small and grow into more of the stack as volume justifies it. The fintech practice is where we scope these programs end to end.
Sponsor bank vs BaaS middleware: 36-month cost comparison
Post-Synapse sponsor-bank examinations and the FDIC's proposed custodial deposit recordkeeping rule (12 CFR Part 375, which would require insured depository institutions to maintain daily beneficial-owner balances across transactional FBO accounts) have split the BaaS market into three infrastructure models.
Three infrastructure models
- Direct API-native sponsor banks (Column, Lead Bank, Cross River): Chartered banks that expose programmable ledger, ACH, wire, and card program APIs directly, with no unregulated middleware ledger between your product and the bank's core banking software. Column and Cross River document FedNow and RTP support; confirm Lead Bank's current rails and card program for your use case. You get wholesale rail pricing and institutional interchange and FBO yield splits. In exchange you engineer your own double-entry PostgreSQL sub-ledger, KYC/KYB waterfall, and daily FBO cutoff reconciliation.
- BaaS middleware and multi-bank networks (Treasury Prime, Unit): Treasury Prime routes across a multi-bank partner network to reduce single-sponsor concentration risk, while Unit bundles accounts, card issuing, and compliance dashboards on top of partner sponsor banks. Middleware shortens launch time. It also adds platform minimums commonly quoted at roughly $5,000 to $15,000 or more a month (negotiated per program), per-active-account tiers, and shared interchange and float margins.
- Turnkey embedded banking (Stripe Treasury + Stripe Issuing): The fastest route for US vertical SaaS platforms already running Stripe Connect, typically weeks rather than months, with availability subject to Stripe's approval (compared in depth in our embedded finance guide). You trade developer velocity for Stripe's service-level fees on issuing, payouts, and money movement, and for less room to negotiate card and deposit-yield economics once volume scales.
36-month TCO model
The model covers a commercial fintech or vertical SaaS program with 15,000 active customer FBO sub-accounts and $60,000,000/yr in gross payment and card volume (120,000 ACH/RTP transfers/yr, $24M/yr commercial debit/prepaid card spend, and 6,000 KYB/KYC onboardings/yr). Assumptions: engineering is priced at Idealogic's $75/hr CEE rate, with $165/hr as our estimate for US agencies. Provider and bank fees are illustrative model inputs, not published rate cards, because these prices are negotiated per program. Stripe publishes no per-account fee for holding a Treasury financial account, so check the Stripe column against Stripe's current pricing before relying on it.
In this model, before counting the illustrative $270,000 to $450,000 in 3-year interchange and FBO float upside, a direct sponsor-bank adapter with a double-entry PostgreSQL sub-ledger costs $428,400 less than the Stripe Treasury column and $97,800 less than BaaS middleware over 36 months. The Stripe gap rests on our fee assumptions, so rerun it with a real quote. The direct stack also leaves you holding the daily beneficial-owner records that sponsor-bank examiners ask for.
Custom ledger build tiers
Idealogic's 2026 BaaS sub-ledger and sponsor-bank engineering tiers compare senior CEE fintech squads at $75/hr, our blended rate, against $165/hr, our estimate of a blended US fintech agency rate. For context on regional cost differences, see Eurostat's labour cost levels (lc_lci_lev), which measure labour cost per hour worked and not agency billing rates.
Where BaaS fits: real build patterns and use cases
Banking as a service fits anywhere a software product wants to hold balances, move money, or issue cards without becoming a bank, and the patterns repeat across very different products. The common move is the same: a non-bank product adds a financial capability at the point where its users were already about to transact, and a licensed bank runs the money underneath through a provider. Four patterns cover most of what gets built.
Embedded accounts inside a SaaS product let a vertical platform give its business customers a real account to receive and hold funds, so the software becomes the place money lives and not just passes through. Marketplace payouts use the rails to pay thousands of independent sellers or contractors, often pairing a held balance with a debit card so recipients can spend earnings directly. Expense and corporate cards issue branded cards against a funded account, with spend controls and a sub-ledger tracking every authorization (we benchmark processor switches, real-time webhooks, and interchange splits in our Lithic vs Marqeta card issuing comparison). And a neobank MVP stacks accounts, cards, and payments into a single consumer product, which is the most ambitious pattern because it leans on nearly every part of the stack at once, pairing BaaS infrastructure with custom digital banking software.
We have built across this range. Fese is our clearest example of building on banking rails: a neobank that runs accounts, loan applications, and budgeting in one product, on banking infrastructure, with the licensed bank holding the charter while we built the product, the integration, and the controls. C-Bank is a mobile banking app we built, a focused consumer money product with instant payments, loans, and transaction reporting. In both, the division of labor was the one this whole guide describes. The sponsor bank held the license and the regulatory relationship. We built the experience, wired the integration, fed the controls, and owned the reconciliation. To be precise about scope: Idealogic builds the product and the integration, never the bank. When the work goes past a provider integration into custom core or back-office systems, that's banking software development, a different scope. The closer you map that boundary before you start, whether through payment gateway integration or a full banking program, the cleaner the build.

CTO and Co-founder at Idealogic. Directing engineering, systems architecture, security, and full-stack delivery across web, mobile, and blockchain.
Frequently asked questions
Banking as a service (BaaS banking, or just BaaS) means a licensed bank exposes its regulated capabilities, such as accounts, payments, and card issuing, as APIs that a software product can consume. The product calls those APIs to open accounts and move money. The bank holds the license and the regulatory relationship underneath.
Usually no. Most BaaS providers are technology companies that sit between a licensed sponsor bank and the software products building on the rails. The provider runs the API layer, the ledger, and compliance tooling, but the deposit license and the supervisory relationship belong to the partner bank. A few providers hold their own banking or electronic-money license, which changes the risk profile, so what always matters is which licensed entity stands behind the money.
BaaS is the infrastructure and embedded finance is the experience built on top of it. BaaS is the API layer that exposes a licensed bank's accounts, cards, and rails. Embedded finance is what a software product delivers to its users by consuming those APIs, such as a checkout that lends or a marketplace that pays sellers. See our embedded finance guide for that layer in depth.
You pay twice: provider fees and your own build. Provider fees combine a setup fee, a monthly minimum commonly quoted at roughly $5,000 to $15,000 or more (negotiated per program), per-account and per-rail charges, and an interchange split. On the build side, a production BaaS sub-ledger, daily FBO reconciliation pipeline, KYC/KYB orchestration, and PCI DSS v4.0.1 card issuing layer costs $135,000 to $285,000 in Central and Eastern Europe at Idealogic's $75 per hour, versus $297,000 to $627,000 at our $165 per hour estimate for US fintech agencies.
It can be. The Synapse failure in 2024 showed how it goes wrong: the provider's ledger and the banks' records disagreed, and end users lost access to their funds. So treat provider due diligence, independent reconciliation, and knowing which licensed bank holds the money as core engineering work. US regulators followed with a July 2024 interagency statement on bank-fintech arrangements that reminds banks of their oversight duties, and the FDIC proposed daily recordkeeping rules for custodial accounts that September.
The provider gives you the regulated core: a ledger, a KYC engine, card issuing, and access to payment rails through a sponsor bank. You build the user experience, a product sub-ledger, reconciliation against the provider, idempotent payment calls, webhook handling, and your own fraud and limit rules. Those are the parts an audit and your users will judge.
An FBO (For Benefit Of) account is a custodial omnibus deposit account held at the chartered sponsor bank on behalf of your end users. Because multiple customers' funds sit inside one pooled bank account, your platform and the BaaS middleware must maintain a real-time double-entry sub-ledger and reconcile it daily against the bank's core cutoff files so every cent is attributable to a specific customer.
A BaaS middleware provider gets you live faster because it bundles the ledger, KYC orchestration, and card issuing behind one set of developer APIs, which suits initial product validation. Integrating directly with a chartered sponsor bank or an EU Electronic Money Institution (EMI) removes middleware revenue share and operational failure points, but requires you to build and audit your own sub-ledger, compliance engine, and reconciliation pipeline.
Column, Lead Bank, and Cross River are chartered banks that expose programmable APIs directly, without an unregulated middleware ledger in between. Column and Cross River document FedNow and RTP support; confirm Lead Bank's current rails and card program for your use case. Unit and Treasury Prime run BaaS middleware and multi-bank networks that speed up onboarding in exchange for monthly platform minimums and shared interchange. Stripe Treasury wraps partner banks for US platforms already on Connect, with service-level fees and less room to negotiate economics at scale.
In our illustrative model (15,000 active sub-accounts, $60,000,000 in annual payment and card volume), 36-month gross program cost comes to roughly $1,081,200 on Stripe Treasury plus Issuing, $750,600 on Unit or Treasury Prime middleware with shadow reconciliation, and $652,800 on a direct API sponsor bank such as Column or Lead Bank with a custom CEE-built PostgreSQL sub-ledger ($210,000 build included). The direct stack is also modeled to retain $270,000 to $450,000 more than the Stripe baseline in 3-year interchange and FBO deposit yield. Provider fees are assumptions, not published rate cards, so rerun the model with your own quotes.
More from the journal

Paddle vs Lemon Squeezy in 2026: MoR Fees, Stripe & TCO
Paddle vs Lemon Squeezy and Stripe Managed Payments in 2026, compared on fees and 36-month TCO: stacked international and subscription surcharges, merchant of record liability, B2B Net-30 invoicing, PG17 entitlement guards, and the math for a $6M/yr SaaS.

Finix vs Stripe Connect in 2026: PayFac, IC++ & Split TCO
Engineering and 36-month TCO teardown of Finix vs Stripe Connect vs Payrix and Adyen for Platforms in 2026: PayFac-as-a-Service, Interchange++ spreads, PostgreSQL 17 split sub-ledgers, and $108M GMV math.

Anrok vs Avalara in 2026: SaaS Sales Tax, VAT & Stripe Tax
Engineering and 36-month TCO teardown of Anrok vs Avalara vs Stripe Tax in 2026: SaaS and AI token taxability, HRIS physical nexus, EU VIES reverse charge, PostgreSQL tax ledgers, and $18M ARR math.