A growing share of SaaS platforms have quietly stopped being just software. Toast doesn’t only run a restaurant’s point-of-sale — it lends the restaurant working capital. Shopify doesn’t only power a storefront — it originated $4.2 billion in merchant financing in 2025 alone. This is embedded finance: payments, lending, and banking features built directly into a SaaS product, rather than bolted on through a redirect to an outside bank.
The shift isn’t a side experiment anymore. It’s become one of the largest new revenue lines in software. The global embedded finance market grew from roughly $148 billion in 2025 to an estimated $197 billion in 2026, and Bain projects U.S. embedded transaction value will surpass $7 trillion by the end of this year, up from $2.6 trillion in 2021.
What “Embedded Finance” Actually Means
Embedded finance is the integration of a regulated financial product — a payment, a loan, a bank account, a card — directly inside a non-financial software platform, so the user never has to leave the app to access it. It generally splits into four categories:
- Embedded payments — accepting cards, ACH, or digital wallets without redirecting the user elsewhere.
- Embedded lending — working capital, lines of credit, or buy-now-pay-later offered at the exact moment a business or customer needs it.
- Embedded banking — branded deposit accounts, debit cards, and cash management issued by a SaaS platform rather than a traditional bank.
- Embedded insurance — point-of-sale coverage bundled into a purchase or transaction flow.
None of this requires the SaaS company to become a bank. Instead, it plugs into infrastructure — the same category of B2B revenue tooling increasingly gets built on top of — provided by API-first partners that handle the regulated parts underneath.
How the Stack Actually Fits Together
Every embedded finance product, no matter how simple it looks to the end user, sits on the same four-layer stack:
The SaaS platform owns the experience. The chartered bank at the bottom of the stack still owns the license — and, ultimately, the regulatory exposure.
Where SaaS Platforms Are Choosing Providers
| Function | Where SaaS Platforms Typically Go | What It Solves |
|---|---|---|
| Payment routing | Stripe, Adyen | Card, ACH, and digital wallet acceptance inside the product |
| Card issuing | Marqeta | Branded virtual or physical cards issued to end users |
| Banking infrastructure | Unit, Treasury Prime | Branded deposit accounts and cash management |
| SMB lending | Lendflow and multi-lender orchestration platforms | Working capital and credit lines matched to multiple funding sources |
Real-World Proof: This Isn’t Theoretical
Originated $4.2 billion in merchant financing in 2025, with gross loans receivable growing 43% year-over-year to $1.6 billion — evidence that embedded lending has moved well past the pilot stage.
Processes every card transaction across roughly 164,000 restaurant locations, giving it the transaction-level data to underwrite working capital loans between $5,000 and $300,000 using actual revenue history instead of a traditional credit score.
Has lent more than $22 billion cumulatively through its embedded lending products, with aggregate loss rates held below 3% — a track record that platforms with strong operational data can increasingly replicate.
The underwriting advantage is the real unlock here. A platform that already sees every transaction a merchant processes can price risk and adjust credit lines in near real time — something a traditional bank, working from quarterly financial statements, simply can’t match. It’s the same underlying dynamic that makes platform-native virtual economies, like Roblox’s DevEx payout system, feel instant compared to a traditional bank transfer: the platform already controls both sides of the ledger.
The Regulatory Reality Check
None of this comes free of risk, and the last two years have made that clear. Banking regulators — the OCC, the FDIC, and the Federal Reserve — have issued a growing string of consent orders against sponsor banks in bank-fintech partnerships, citing weak transaction monitoring, under-scaled BSA/AML compliance, and inadequate third-party oversight as programs scaled faster than their controls.
68% of embedded finance practitioners now name embedded lending as their top priority, ahead of payments processing at 59% — but that appetite is increasingly paired with due-diligence requirements that didn’t exist even two years ago. A sponsor relationship built on “trust and weekly reconciliation files” is not likely to survive a 2026 sponsor-bank diligence cycle.
Getting Started: A Practical Checklist for SaaS Founders
- Start with payments, not banking. Embedded payment acceptance has the lowest regulatory surface area and the fastest path to revenue — it’s the natural first step before lending or deposit products.
- Model the underwriting data you actually have. Embedded lending only works as a differentiator if your platform sees transaction-level data a traditional lender can’t — map that advantage before committing engineering time.
- Vet the sponsor bank, not just the API provider. Ask directly about the bank’s compliance program maturity and its history of regulatory actions before signing a BaaS contract.
- Build a continuity plan for the day the partnership ends. Assume any single sponsor-bank relationship could be terminated with limited notice, and have a documented fallback before you need one.
- Treat compliance as a product requirement, not a legal afterthought. The SaaS teams succeeding here — the same discipline that shows up in solid software development practices generally — build monitoring and reporting into the roadmap from day one rather than retrofitting it after a regulator asks.
The Bottom Line
Embedded finance has stopped being a “nice to have” feature for SaaS platforms and become a structural part of how the best vertical software companies monetize and retain customers. Less than a fifth of the addressable $185 billion opportunity has been captured so far, which means the platforms moving first — with the underwriting data and the compliance discipline to back it up — have a real window to build a durable advantage. The ones moving carelessly are the ones showing up in next year’s consent orders.
