Banking-as-a-Service in 2026: The Ultimate Guide
A 2026 deep dive into Banking-as-a-Service: architecture, real-world use cases (Uber, Shopify, Apple, Klarna), PSD3 and Section 1033 regulation, economics, and how to launch your own embedded banking product.
What is Banking-as-a-Service?
Banking-as-a-Service (BaaS) is the model where a licensed bank exposes its regulated capabilities (accounts, cards, payments, lending, KYC, compliance) through APIs, so non-bank businesses can embed them inside their own products. The licensed entity carries the regulatory burden, the BaaS provider runs the orchestration layer, and the brand builds the customer experience. The result is a branded financial product shipped in weeks instead of years.
BaaS is how Uber pays its drivers same-day, how Shopify funds its merchants, how Apple lets you split a purchase into four, and how Klarna underwrites a basket at checkout. Most of the finance you touch every day is now running on some variant of a BaaS stack.
API-first
Accounts, ledger, cards, payments and KYC exposed as REST and webhooks. Integrate once, ship fast.
Licensed back-end
A bank or EMI in the background holds the license, the deposits and the regulator relationship.
Your brand up front
The end customer sees your product, your UX, your logo. The bank is invisible.
The category is huge and still accelerating. Embedded finance is projected to generate roughly $320 billion in revenue by 2026, with BNPL alone adding $576 billion in transactions. Nearly every SaaS, marketplace and consumer-tech company is asking "should we add financial products?". BaaS is the infrastructure that makes the answer yes.
Let's discuss your project and see how we can launch your digital banking product together
Request demoBaaS vs open banking vs embedded finance
These three terms are mixed up constantly, including in investor decks. They describe different things.
| Concept | What it is | Who benefits first | Regulatory anchor |
|---|---|---|---|
| Banking-as-a-Service | A bank rents out its regulated rails to non-banks via APIs. Non-banks build the product. | Non-bank brands that want to own the customer relationship with accounts, cards or lending. | Banking license or EMI of the provider |
| Open banking | Banks expose customer-consented data and payment initiation to third parties through standardised APIs. | Aggregators, PFM apps, account-to-account payment providers. | PSD2 in the EU, CMA Open Banking in the UK, Section 1033 in the US |
| Embedded finance | The user experience of consuming financial products inside a non-financial product. The outcome, not the plumbing. | The end customer and the distributing brand. | Depends on product (BaaS license, insurance, broker-dealer, etc.) |
A clean way to think about it: embedded finance is the what the user sees, BaaS is how you build it, open banking is how you read data and initiate payments on accounts that already exist elsewhere. A single product often uses all three.
How BaaS actually works
Every BaaS deployment has the same four moving parts. Knowing them tells you where your customer data lives, who is accountable when something breaks, and where the unit economics leak.
Brand
Your app, your users, your brand. Owns distribution, UX and the commercial relationship.
BaaS platform
APIs, ledger, KYC orchestration, card program, dispute handling, admin console.
Licensed entity
The bank or EMI that holds the license, the deposits and the regulator relationship.
Payment rails
ACH, SEPA, SEPA Instant, FasterPayments, SWIFT, Visa, Mastercard, FedNow.
On a real transaction, the flow is: your user taps a button in your app, your backend calls the BaaS API, the BaaS platform writes to its ledger and instructs the licensed entity, the bank moves money on the payment rail, a webhook flows back, and your UI updates. All of this typically finishes in under a second. The complexity is hidden behind a single SDK.
The 2026 BaaS and embedded finance market
The 2026 picture is less about "does BaaS work" (obvious yes) and more about three tensions. Who holds the license: middleware with sponsor banks, or BaaS providers with their own charters. Which vertical wins: horizontal platforms like Unit, Solaris and Swan, or vertical specialists for property, payroll or healthcare. Which rail: card interchange, net interest margin on loans, or platform fees. The teams that get these three right are the ones printing money. The rest are a feature no one asked for.
Real-world BaaS use cases
The clearest way to understand BaaS is to look at products you already use every week. Each of these is powered by some combination of a BaaS provider, a sponsor bank and a payment rail.
Uber Pro Card for drivers
Uber partnered with Evolve Bank & Trust and Branch to issue a debit Mastercard that pays drivers same-day after each trip and offers cashback on fuel. Drivers get a payroll card, Uber gets retention.
Shopify Capital and Balance
Shopify offers merchants cash advances based on sales history and a bank account (Shopify Balance) with a debit card, directly inside the merchant dashboard. No forms, no branch visit.
Apple Pay Later and Card
Apple lets users split a purchase into four interest-free instalments inside Apple Wallet, and the Apple Card runs on Goldman Sachs. Embedded lending and embedded banking inside a phone.
Klarna BNPL at checkout
A merchant plugs in Klarna, the shopper pays in four. Klarna underwrites, the merchant gets paid up front, the shopper gets frictionless credit.
Gusto payroll cards
US payroll platform Gusto lets employees get paid into a branded "Gusto Wallet" account before payday, backed by a BaaS partner.
Freelancer accounts
Lili (US) and Kontist (DE) ship freelancer-focused accounts with automatic tax set-aside, both built on top of BaaS partners rather than their own charter.
Who benefits from BaaS
BaaS is rarely a zero-sum trade. All three sides of the triangle win if the model is set up well.
Licensed banks
- New distribution channel without marketing spend
- Deposit growth without branch network
- Fee income plus revenue share on interchange
- Defensive moat against digital-only competitors
Non-bank brands
- Ship a financial product in weeks, not years
- Skip the 3-5 year banking license process
- New revenue streams (interchange, lending, FX)
- Higher retention: finance lives inside the product
End customers
- Finance where they already are (no new app)
- Faster payouts, same-day settlement
- Relevant products: a driver card, a merchant loan
- Lower fees thanks to cost structure
The regulatory picture in 2026
BaaS grew up faster than regulators could keep up. Between 2023 and 2025, consent orders against Cross River, Evolve, Choice and Blue Ridge in the US, plus BaFin measures against Solaris in Germany, forced a reset. By 2026 the ground rules are clearer, which is good news for anyone building a serious product.
- PSD3 and PSR in the EU. The EU reached political agreement on PSD3 and the Payment Services Regulation in late 2024 and early 2025. Implementation targets land around 2026. Expect tighter rules on fraud, strong customer authentication, and an expansion of open banking beyond current accounts into investments and pensions.
- CFPB Section 1033 in the US. The consumer financial data rights rule was finalised in late 2024 and is phasing in through 2026. Customers can port account data to competitors. BaaS providers must expose standardised endpoints.
- Reconciliation is now non-negotiable. Every transaction must reconcile to a single source of truth at the partner bank. When ledgers diverge, FDIC pass-through insurance can fail. This is what cost Synapse's customers their money in 2024.
- Reputation risk is off the table. The FDIC and OCC adopted a joint final rule in April 2026 prohibiting adverse action against banks based on reputation risk. That reopens appetite for crypto, cannabis-adjacent and politically sensitive verticals.
The practical takeaway: compliance is now a product feature, not a checkbox. The BaaS providers that invested in reconciliation, transaction monitoring and open-banking endpoints during the 2023-2025 reset are winning deals that used to go to the cheapest API.
How to launch a BaaS-powered product
There are three honest paths, each with different economics.
| Path | Time to launch | Capital needed | Best fit |
|---|---|---|---|
| Own banking license | 3-5 years | €20M+ plus regulatory capital | Well-funded incumbents targeting primary-account status and lending. |
| BaaS partnership | 3-6 months | €0.5-3M | Fintechs with a clear vertical (creators, gig workers, SME, healthcare, property). |
| White-label platform (e.g. Crassula) | 6-12 weeks to MVP | Low six figures | Teams that want a branded product without rebuilding ledger, KYC and card program from scratch. |
The middle and third paths are what most teams pick. Crassula sits on the orchestration layer: ready-made ledger, KYC, card program, IBAN provisioning, payments routing and admin back office. You plug into your own licensed entity or pick one of our BaaS partners (Solaris, Swan, ClearBank, Unit, Railsr, Currencycloud) and ship a branded product in weeks.
Where BaaS goes next
Three directions are visible in analyst reports and in the roadmaps of the leaders:
- Vertical BaaS wins. Generic all-in-one platforms still have a place, but the fastest growth is in providers specialised in one industry (healthcare, property, payroll, creators) or one product (cards, FX, treasury).
- Middleware becomes bank. Griffin, Column and Solaris already hold charters. More will follow, which simplifies the contract, removes tri-party risk, and changes the competitive dynamic for anyone still building on sponsor-bank middleware.
- AI-native operations. Support, fraud, underwriting and onboarding are already majority-AI at leading BaaS platforms. This drops cost-to-serve toward 10% of traditional bank levels by 2028.
Every incumbent bank will eventually operate like a BaaS provider, whether they call it that or not. The only question is whether your brand is on the distribution side of that shift or on the legacy side.
FAQ
Banking-as-a-Service is when a licensed bank lets a non-bank brand use its regulated capabilities (accounts, cards, payments, lending, KYC) through APIs. The non-bank builds the product and keeps the customer relationship. The bank carries the licence and the regulator relationship. It is why so many apps now come with a debit card, a savings account or a BNPL option.
No. Open banking is about banks exposing customer-consented data and payment initiation to third parties under PSD2, PSD3 and Section 1033. BaaS is about a bank renting out its full regulated capabilities so someone else can build a banking product. A single product often uses both: open banking to read existing accounts, BaaS to open a new one.
Embedded finance is the user-visible outcome: a loan inside a shopping app, a card inside a rideshare app, an account inside a SaaS dashboard. BaaS is the underlying plumbing that makes embedded finance possible. Embedded finance is what the user sees; BaaS is what the engineers wire up.
By region: Unit, Marqeta, Galileo, Treasury Prime, Synctera and Stripe Treasury in the US; Griffin, ClearBank and Railsr in the UK; Solaris, Swan, Treezor and Intergiro in the EU. Vertical specialists (Modern Treasury for treasury, Currencycloud for FX) matter for focused use cases. See our BaaS providers comparison for the full breakdown.
Uber pays drivers same-day into a Mastercard via Evolve Bank & Trust. Shopify offers merchants cash advances and a bank account inside the Shopify dashboard. Apple Pay Later splits purchases into four instalments. Klarna runs BNPL at checkout. Lili (US) and Kontist (DE) offer freelancer accounts. All of these are BaaS-powered.
Usually no. The BaaS provider or its sponsor bank carries the license. You still need your own AML program, onboarding policies, and in the EU you often register as an agent of the provider. If you plan to lend from your own balance sheet or hold deposits directly, you will eventually need your own license.
Three to twelve weeks for a well-scoped program. Complex verticals (lending, crypto, cross-border) can stretch to three to six months. Getting your own banking license takes three to five years and tens of millions in capital, so BaaS is the obvious default for most teams.
Crassula is the orchestration and product layer. We provide the ledger, KYC orchestration, card program management, IBAN provisioning, payments routing and admin back office. You plug in your own licensed entity or one of our partner BaaS providers, and ship a branded product in weeks. The stack stays modular so you can swap a partner later without a rewrite.
