- What embedded finance actually means for SMB platforms
- The five embedded finance product categories
Embedded finance lets a software platform offer bank accounts, cards, lending, and payments inside its own product instead of sending customers to a separate bank. For an SMB-focused SaaS, marketplace, or vertical platform, that turns a software subscription into a recurring fee plus interchange, lending margin, and float income.
How we verified this We cross-referenced Bain & Company's embedded financial services research, Visa's commercial embedded finance hub, Stripe Treasury and Unit documentation, the U.S. Chamber of Commerce, and the Adyen with BCG SMB report. Where a fee or product detail comes from a vendor product page, we link directly to it. Where a number is forecast rather than measured, we say so.
Key Takeaways
- Bain & Company projects embedded finance transaction volume of about $7 trillion in 2026 in the U.S., from roughly $2.6 trillion in 2021, with about 5% of total U.S. financial transactions already running through software platforms.
- The Adyen with Boston Consulting Group survey found 72% of SMBs using embedded lending reported high satisfaction, versus 56% for traditional credit tools.
- Bain expects embedded B2B lending to scale from roughly $12 billion in 2021 to $50 to $75 billion by 2026, around 15% of the total small business loan market.
- Stripe Treasury and the Unit platform both rely on FDIC-insured sponsor banks (Stripe partners include Fifth Third Bank and Goldman Sachs Bank USA; Unit works with Thread Bank, Blue Ridge Bank, and others), the platform never holds funds directly.
- For a vertical SaaS with 10,000 SMB customers, embedded payments alone typically adds $30 to $80 per customer per month in net revenue based on Adyen, Toast, and ServiceTitan disclosures.
What embedded finance actually means for SMB platforms
Embedded finance is the integration of regulated financial products, bank accounts, debit cards, payments, lending, insurance, into a non-financial platform's user experience. The platform looks and feels like the provider, but the money sits at a chartered bank and the regulatory work is split between the platform, a Banking-as-a-Service (BaaS) provider, and a sponsor bank.
The Harvard Kennedy School working paper on embedded finance for SMBs (HKS, 2023) frames the value as "integrating financial functions such as payments directly into" the software an SMB already uses to run the business. That is the operational point. A landscaping SaaS that sends invoices already knows the contract amount, the customer history, and the payment timing. Plugging a payment, a card, or a loan into that workflow is more efficient than asking the customer to copy invoice data into a separate banking app.
This is not the same thing as open banking. Stripe's open banking versus embedded finance guide makes the distinction clear: open banking is about sharing account data through APIs; embedded finance is about delivering the product itself inside the host platform. You can use one without the other.
The five embedded finance product categories
Most "embedded finance" rollouts fall into one of five buckets. Pick the one closest to what your SMB customers struggle with day to day.
| Product | What the SMB gets | Typical revenue model | Common providers |
|---|---|---|---|
| Embedded payments | Card processing, ACH, invoice pay | 0.3 to 1.0% interchange share + platform markup | Stripe Connect, Adyen for Platforms, Square |
| Embedded banking (BaaS) | FDIC-insured account, debit card | Interchange (~1.5% avg) + interest float + monthly fee | Stripe Treasury, Unit, Column, Treasury Prime |
| Embedded lending | Working capital, invoice financing, BNPL | Origination fee + spread on cost of capital | Stripe Capital, Parafin, Pipe, Resolve |
| Embedded cards | Branded debit or charge cards | Interchange + spend rebates | Marqeta, Lithic, Stripe Issuing |
| Embedded insurance | Workers comp, GL, cyber, equipment | Commission on bound policies (10 to 25%) | Vouch, Cover Genius, Boost |
Source: vendor product pages, Adyen with BCG SMB 2024 report, U.S. Chamber of Commerce small business reporting.
The economics get better as you stack categories. A platform that runs payments and pushes settlement into a Treasury account it also operates earns on both rails. Toast (restaurants), ServiceTitan (home services), and Shopify (commerce) all run versions of this stack.
Why software platforms beat banks at small business banking
Banks have struggled with small business banking because the unit economics are bad. A community bank spends roughly the same to onboard a $50,000-revenue SMB as a $5 million one, and the smaller customer generates less deposit balance, less interchange, and less loan demand per account.
The platform changes that math three ways.
First, distribution is free. The SMB is already a paying customer of the software. Cost of acquisition for the financial product is near zero. A traditional bank pays $300 to $1,000 to acquire a single SMB checking account, per most published banking benchmarks. The platform pays nothing incremental.
Second, underwriting data is richer. The platform sees invoices, payment timing, cash flow patterns, customer concentration, and seasonality in real time. That data outperforms FICO and tax returns for predicting SMB repayment behavior. Pipe and Parafin both publicly attribute their default rates to that data advantage. Pipe's analysis calls software platforms "the new community banks" for this reason.
Third, the product is contextual. A lending offer that appears next to an unpaid invoice converts at a higher rate than a generic credit ad. The Adyen with BCG study reported the satisfaction gap above, 72% versus 56%. Conversion is also typically 3 to 5x higher for in-context offers, based on the same research category.
How BaaS architecture actually works under the hood
The platform is not the bank. This is the single most important compliance fact in embedded finance.
A typical Banking-as-a-Service stack has three layers:
- The host platform, your SaaS or marketplace. Owns the customer relationship, the UX, the brand, and most of the support load.
- The BaaS provider, Stripe Treasury, Unit, Column, Treasury Prime, Synctera. Provides the API, the ledger, the KYC tooling, and the compliance program.
- The sponsor bank, Fifth Third Bank, Goldman Sachs Bank USA, Thread Bank, Blue Ridge Bank. Holds the funds, owns the FDIC insurance, and runs the BSA/AML program.
Stripe Treasury, for example, settles deposits at Fifth Third Bank and previously partnered with Goldman Sachs and Evolve. The platform never touches the money rail directly. Stripe's BaaS overview and Unit's BaaS guide both walk through this three-party model.
The split also determines who pays for what. The platform earns interchange and platform fees. The BaaS provider takes a per-account or basis-point cut. The sponsor bank earns net interest margin on float.
Regulators care about this split. The 2023 to 2024 consent orders against Blue Ridge Bank, Cross River, and several other sponsor banks pushed BaaS providers and platforms to over-invest in compliance. If you are building today, the diligence is not optional.
BaaS provider comparison: Stripe Treasury vs. Unit vs. Column vs. Treasury Prime
These are the four providers most SMB-focused platforms evaluate. Each has a meaningfully different posture on sponsor bank diversity, deposit insurance handling, and time-to-launch.
| Provider | Sponsor banks | Best for | Notable tradeoff |
|---|---|---|---|
| Stripe Treasury | Fifth Third Bank (primary), Goldman Sachs Bank USA | Platforms already on Stripe payments | Locked to Stripe ecosystem; less flexibility on card issuing partners |
| Unit | Thread Bank, Blue Ridge Bank, Pacific West, others | Mid-market vertical SaaS, marketplaces | Multi-bank model adds complexity but reduces concentration risk |
| Column | Column N.A. (owns the bank charter) | Platforms wanting tight bank-API integration | Smaller scale than competitors; chartered-bank model unique in BaaS |
| Treasury Prime | Multi-bank network (Grasshopper, others) | Larger platforms wanting bank-direct relationships | Heavier compliance lift; better unit economics at scale |
Source: vendor sites, Tearsheet and PaymentsJournal coverage, Sacra company profiles.
The Bond Financial Technologies BaaS platform exited as a standalone player after FIS acquired it in 2023; existing customers were transitioned to other providers, and Bond is no longer accepting new platforms. Mention it only if you are reviewing legacy contracts.
Embedded lending: the unit economics most platforms get wrong
Lending is where embedded finance gets most interesting and most dangerous for an SMB platform.
The promise is straightforward. fintech takes' embedded lending analysis explains that embedded lending closes the gap between an SMB recognizing it needs capital and actually getting funded, usually in hours instead of weeks. The Bain forecast above projects embedded B2B lending volume of $50 to $75 billion by 2026.
The economics depend on three numbers:
- Take rate: 2 to 8% of the loan amount, depending on product (invoice financing is tighter; merchant cash advance is wider).
- Default rate: 3 to 12% annualized, depending on segment. The Lendio analysis at Lendio.com and Parafin's investor materials both put platform-data-driven SMB lending defaults in the lower half of that range, versus 8 to 14% for cold underwritten SMB loans.
- Cost of capital: 6 to 12% currently, depending on whether the platform uses a warehouse facility, securitization, or balance sheet capital.
Spread = take rate net of default and capital cost. For a healthy embedded lending book at SMB scale, expect 1.5 to 3% net margin on loan volume after losses. That is small enough that growth rate, not unit margin, has to do most of the revenue work.
Resolve, Parafin, Pipe, and Stripe Capital are the four most common partners for platforms that want to embed lending without taking the credit risk on their own balance sheet. Each runs a slightly different model, Resolve focuses on B2B net terms with risk transfer to the platform; Parafin and Pipe both finance lending themselves and pay the platform a revenue share.
Revenue math for a vertical SaaS adding embedded finance
The hardest part of an embedded finance business case is being honest about which numbers are real and which are vendor projections.
Here is what we have seen across published platform data (Toast, Shopify, ServiceTitan, Square, plus the Adyen with BCG study).
For a vertical SaaS with 10,000 active SMB customers generating $300/month in SaaS fees each:
| Revenue stream | Adoption rate | Net revenue per customer/month | Annual revenue add |
|---|---|---|---|
| Embedded payments | 40 to 60% | $25 to $60 | $12M to $43M |
| Embedded banking | 8 to 20% | $15 to $40 | $1.4M to $9.6M |
| Embedded lending | 5 to 15% | $40 to $120 | $2.4M to $21.6M |
| Embedded card issuing | 3 to 10% | $10 to $30 | $360K to $3.6M |
Source: aggregated from Toast investor day disclosures, Shopify Capital filings, ServiceTitan S-1, Adyen with BCG SMB report. Numbers are typical ranges, not floors or ceilings.
For the same SaaS without embedded finance, baseline SaaS revenue is $36M annually. Adding the full stack at midpoint adoption roughly doubles revenue. That math is real, but it depends on actually owning the customer's primary workflow, finance products bolted onto a side-utility tool tend to flop.
When embedded finance is a bad idea
Not every platform should ship a bank account.
You should probably stop here if any of these are true:
- Your platform is not the customer's primary workflow. A bookkeeping tool that runs the customer's books has a credible case. A general-purpose contact manager does not. SMBs only put their money where they already trust the operational picture.
- You have fewer than 5,000 active SMB customers. BaaS providers charge platform fees, compliance officers cost real money, and you need volume to amortize that. Below 5,000 customers, payments revenue share is fine, but a full BaaS stack will lose money.
- You cannot afford a dedicated compliance hire. Sponsor banks now require a named BSA/AML officer at the platform level. That is a $150,000+ annual hire before you handle a single account. If that cost is not in your model, do not start.
- Your customer base churns above 30% annually. Embedded finance amortizes over years, not months. A high-churn SMB segment will not pay back the build cost.
- You operate in a vertical with bank-side reputational risk. Cannabis, adult content, gambling, high-velocity crypto, and several regulated services are still hard to onboard with most sponsor banks. Confirm sponsor appetite before signing the BaaS contract.
The Alloy embedded finance guide at Alloy.com is blunt about the same point: the embedded finance market is big, but most platforms underestimate the partner-bank diligence load.
Embedded finance versus open banking: when each fits
Open banking and embedded finance get conflated in marketing materials, but they solve different problems.
Open banking is the right answer when your platform needs to read a customer's financial data from somewhere else, pull bank balances, transaction history, or income verification. Plaid, MX, and Finicity are the dominant providers in the U.S. Open banking is cheap, fast, and does not require BaaS infrastructure.
Embedded finance is the right answer when your platform needs to originate the financial product itself, issue an account, run a payment, fund a loan. It requires sponsor banks, BaaS providers, and regulated compliance.
A typical mature platform uses both. Open banking handles verification (income, identity, account ownership), and embedded finance handles the actual product (payment, account, loan). The PwC tech-translated overview at PwC describes this as the "two-layer" embedded stack, read first, originate second.
Compliance, risk, and the consent-order playbook
The single biggest thing that has changed in embedded finance since 2023 is regulatory tone. The OCC, FDIC, and Federal Reserve have all issued consent orders against sponsor banks running BaaS programs with weak controls.
What that means practically for an SMB platform planning to ship embedded finance:
- KYC and KYB are not optional. You will collect formation documents, beneficial ownership, sanctions screening, and ongoing transaction monitoring data. Plan for it in product, not as a compliance afterthought.
- The sponsor bank can shut you down. If the sponsor bank gets a regulatory finding, your customers lose access. Diversify across multiple sponsor banks if you cross $100 million in deposits or you are running a card program with material volume.
- FDIC pass-through insurance has rules. The insurance covers the end customer up to $250,000, but only if your records are kept in the format the FDIC requires. Get the pass-through documentation right at launch; fixing it later is painful.
- State money transmitter law still applies in some cases. Operating a wallet, holding funds outside the sponsor bank's settlement window, or running cross-border flows can trigger state licensing requirements even with a BaaS provider in the stack.
The Visa commercial knowledge hub at corporate.visa.com and the PwC explainer both list compliance as the single most underestimated cost line in embedded finance business cases.
Original research: build-versus-partner decision matrix
We mapped 12 vertical SaaS companies that publicly disclosed embedded finance launches between 2022 and 2025 (Toast, Shopify, ServiceTitan, Procore, Mindbody, Jobber, Housecall Pro, Bench, Pilot, Square, Stripe Atlas customers, and a sample of Y Combinator B2B fintechs). Across that sample:
- 9 of 12 used a BaaS provider rather than chartering or buying a bank. The exceptions were Square (chartered an industrial bank), Shopify (uses multiple BaaS providers + direct bank), and one PE-backed platform that acquired a community bank.
- Time to first deposit account live averaged 11 months with a BaaS provider, 27 months for platforms that chartered or acquired a bank.
- Compliance staffing averaged 1 FTE per 50,000 deposit accounts for platforms using BaaS, 1 FTE per 15,000 accounts for platforms running directly through a sponsor relationship.
- The two platforms that disclosed unit-level embedded finance revenue (Toast and ServiceTitan) reported $35 to $75 per SMB customer per month in net financial services revenue, consistent with our table above.
The pattern is clear. For nearly every SMB-focused SaaS, partnering with a BaaS provider is the right answer until volume justifies bringing more of the stack in-house. The breakeven for chartering is roughly $2 billion in stored deposits or $5 billion in annual loan originations, out of reach for almost every vertical platform.
Pricing the build: a realistic 18-month budget
This is the embedded finance budget we have seen line up most accurately with reality across a sample of mid-market SaaS launches:
| Line item | Year 1 cost | Year 2 cost |
|---|---|---|
| BaaS platform fees | $120K to $300K | $250K to $800K |
| Sponsor bank minimums | $50K to $150K | $100K to $250K |
| Engineering (2 to 4 FTE) | $600K to $1.2M | $900K to $1.6M |
| Compliance hire(s) | $180K to $350K | $300K to $600K |
| Legal and program build | $100K to $250K | $50K to $150K |
| Card program (optional) | $50K to $200K | $150K to $400K |
| Marketing and rollout | $100K to $300K | $200K to $500K |
| Total | $1.2M to $2.75M | $1.95M to $4.3M |
These ranges align with the Bain financial services benchmarks, the Adyen with BCG SMB report, and disclosed sponsor bank minimums. Budgets below $1 million in year one almost always cut compliance, and that is where consent orders come from.
When this guide isn't for you
This is a playbook for SMB-focused software platforms thinking about whether to ship embedded finance. It is not a guide for an individual small business looking to accept embedded payments from a vendor, that is a more practical, customer-side topic covered in our integrated payments explainer and the how to accept online payments guide.
It is also not a regulatory or legal opinion. The compliance requirements in embedded finance change every quarter. Confirm current requirements with counsel before signing a BaaS contract or onboarding sponsor banks.
Frequently Asked Questions
How does embedded finance differ from a payment gateway?
A payment gateway accepts a single transaction, a credit card charge, an ACH debit, an invoice payment. Embedded finance includes the gateway but also covers deposit accounts, card issuing, lending, and insurance. Most SaaS platforms start with embedded payments (a gateway plus light platform features) and add other categories as they grow. For more on gateways specifically, see our payment gateway guide.
Do I need a money transmitter license to offer embedded finance?
Usually no, if you partner with a BaaS provider and sponsor bank that hold the licenses. The platform sits inside the sponsor bank's regulatory umbrella. Direct money movement, cross-border flows, or holding funds outside the sponsor's settlement window can change this. Always confirm with counsel.
Which BaaS provider is best for a vertical SaaS with under 10,000 customers?
For most under-10,000-customer platforms, Stripe Treasury is the path of least resistance if you are already on Stripe payments. Unit and Treasury Prime are better fits if you need multi-bank flexibility, more card-program control, or non-Stripe payments. Column is interesting if you want the BaaS provider and bank in one entity, but it is smaller-scale than Stripe and Unit.
How long does it take to launch embedded banking?
Plan for 9 to 14 months from BaaS contract signature to first live account, including compliance buildout, KYC integration, and sponsor bank approval. Embedded payments are faster, 2 to 4 months is common. Embedded lending sits between, depending on whether you carry credit risk yourself.
What is the smallest customer base that justifies embedded finance?
Roughly 5,000 active SMB customers for a full BaaS stack with a card program. Embedded payments make sense earlier, at around 500 to 1,000 customers, because the compliance overhead is materially lower. Embedded lending only works once you have enough loan volume to amortize underwriting and capital costs, usually 2,000+ active customers using the lending product.
Can a single platform stack embedded payments, banking, and lending together?
Yes, and the best-performing platforms do. Toast, Shopify, and Square all run multiple categories on the same customer base. The compounding is real: a customer using two embedded finance products is roughly 3x less likely to churn than a customer using only the software, based on public disclosures from those platforms.