The Embedded Finance Roadmap
From payments wedge to full financial operating system: the sequenced roadmap, the build-vs-buy-vs-partner framework, and the investor narrative that supports a 20–25% revenue-multiple premium.
22 min read
Beyond payments — the opportunity
The embedded payments market is mature and well-understood. The embedded finance market — which includes lending, banking, insurance, payroll, and cards in addition to payments — is still in its early innings, despite the enormous opportunity it represents.
Market size at a glance
• Embedded finance TAM (2024): approximately $185 billion in revenue (Adyen/BCG, 2024) — up 25% in two years.
• Embedded finance transaction value: ~$65 billion (2024) → projected ~$7.2 trillion by 2030 (CAGR ~32%).
• North America revenue opportunity: $500B+ by 2025 (Flagship Advisory Partners estimate).
• 80% of the market is currently untapped — less than 20% of addressable platforms have meaningfully actioned the opportunity.
• 40% of SMBs are interested in embedded financial services from their software platform.
• First-movers now make more than 50% of their revenue from embedded payments rather than software.
• Only 21% of platforms currently offer any embedded finance beyond payments — lending (36%), banking (27%), insurance (15%), wealth (14%).
Embedded lending — the fastest-growing segment
Embedded lending — merchant cash advances (MCAs), working capital loans, and BNPL — is the fastest-growing segment of embedded finance for software platforms. The reason is structural: payment data is the single best predictor of a small business’s ability to repay (see Chapter 8 for the underwriting advantage). Platforms that process payments for their merchants have an underwriting moat that no bank or independent lender can replicate.
Parafin, the embedded lending infrastructure provider, reports that platforms using payment data for underwriting see meaningfully lower default rates than traditional SMB lenders — with some platforms reporting 40–60% lower default rates. That advantage translates directly into higher approval rates, better pricing, and stronger merchant attachment.
Embedded insurance — high-margin, underserved
Insurance embedded within vertical software platforms is one of the most margin-rich opportunities in the stack. A platform serving field-services contractors can offer general liability and workers’ comp at the point of onboarding — the moment of highest intent and lowest friction. Commission rates of 10–20% on premiums, combined with the stickiness of insurance relationships, make this highly attractive. The key is vertical fit. Insurance demand is concentrated in verticals with liability exposure: field services, construction, healthcare, hospitality, childcare. Platforms in pure software or e-commerce verticals may find lower demand.
Embedded banking — the retention play
Business checking accounts and debit cards within your platform — what Shopify Balance has demonstrated at scale — are the ultimate retention product. When a merchant’s operating account lives inside your platform, their switching cost approaches prohibitive. They see their payment volume, their balance, and their working capital in one place. This is the vision of the “financial operating system for [vertical].” The BaaS ecosystem has matured significantly. Providers like Unit, Treasury Prime, and Helix by Q2 allow platforms to launch business banking products in weeks rather than years, without obtaining a bank charter.
Embedded payroll — the new embedded payments
Payroll may be the most underappreciated embedded finance opportunity of the next five years. For platforms in verticals with employee-intensive merchants — restaurants, retail, field services, healthcare — offering payroll within the platform creates a deep, recurring integration that is genuinely hard to replace. Toast Payroll has become a meaningful revenue and retention contributor. Homebase built payroll into its scheduling and HR platform. Check (the payroll infrastructure API) enables platforms to launch embedded payroll in 90 days. The per-employee-per-month (PEPM) revenue model is predictable and scales with your merchants’ growth — a natural complement to the GMV-based revenue from payments.
The embedded finance product stack
The table below maps the full embedded finance product stack — from the payments foundation to the advanced products — with revenue models, key infrastructure providers, and strategic notes for each layer.
| # | Product | Revenue Model | Key Players | Barrier |
|---|---|---|---|---|
| 1 | Payments (Foundation) | Take rate on TPV (0.3%–1.5% typical for PFaaS) | Stripe Connect, Adyen for Platforms, Nuvei, Fortis, Rainforest, Finix | Already done |
| 2 | Working Capital / MCAs (First Expansion) | 3%–8% of advance as factor fee | Square Loans, Toast Capital, Shopify Capital, Parafin, YouLend, Liberis | Low |
| 3 | Term Lending (Second Expansion) | Interest margin (3%–8% APR spread) | Funding Circle, Lendio, Lendflow, Kanmon | Medium |
| 4 | Insurance (Vertical-Dependent) | 10%–20% commission on premiums | Next Insurance, Pie Insurance, Boost, Cover Genius, Coterie | Low–Medium |
| 5 | Banking / BaaS (Third Expansion) | Interchange on debit, interest on deposits, fee income | Shopify Balance, Toast Banking, Unit, Treasury Prime, Mercury, Helix by Q2 | Medium |
| 6 | Payroll (Vertical-Dependent) | $2–$8 PEPM (per employee per month) | Toast Payroll, Gusto Embedded (Check), Homebase, Rippling | Medium–High |
| 7 | Cards (Expense / Fleet — Advanced) | Interchange (1.5%–3%), interest on revolving balances | Divvy/BILL, Brex, Ramp, Marqeta, Lithic, Stripe Issuing | High |
A critical principle: each product in the stack leverages the data and relationships built by the products below it. You can only underwrite working capital effectively if you have rich payment data. You can only launch banking successfully if you have established merchant trust through payments and lending. The sequence matters — do not skip layers. The Charge Forward Maturity Framework places each product at a specific stage, with the corresponding GMV band and operating model required to support it.
How to sequence your embedded finance roadmap
The most common mistake platforms make with embedded finance is trying to do too much at once. A focused, sequenced approach — one major product initiative per year — consistently outperforms the “launch everything simultaneously” strategy. The recommended sequence for most vertical SaaS platforms:
| Year | Focus | Key Actions | KPIs to Track | Milestone |
|---|---|---|---|---|
| Year 1 | Optimize Payments | Maximize attach rate • Implement IC+ pricing • Build payment data infrastructure • Identify top merchant segments | Effective take rate, payment attach rate, authorization rate | Payments contributing 40%+ of platform revenue |
| Year 2 | Launch Working Capital | Select lending partner • Integrate MCA/working capital • Launch to top 20% of merchants by TPV • Refine underwriting with payment data | Capital attach rate, advance volume, default rate | $1M–$5M in annual lending revenue |
| Year 3 | Add Insurance or Payroll | Survey merchants for product-market fit • Select vertical-appropriate product • Launch with partner • Iterate on attach rate | Insurance GWP, payroll PEPM, cross-product attach | 2+ embedded finance products with >20% merchant attach |
| Year 4+ | Banking, Cards, Full Ecosystem | Launch business checking • Consider card issuance • Build full financial operating system for your vertical | Deposits held, card GMV, full financial services revenue | Embedded finance represents 50%+ of total platform revenue |
Why each product builds on the last
• Payments generates transaction data and merchant trust.
• Working capital uses payment data for underwriting — higher approval rates, lower defaults, no additional data infrastructure required.
• Insurance and payroll leverage your merchant relationships and platform presence — merchants who trust you with payments will trust you with adjacent products.
• Banking builds on the full payment + lending + payroll relationship — when you are managing a merchant’s transactions, their loan, and their payroll, the business checking account is a natural extension.
• Cards close the loop — expense management, fleet cards, and corporate cards round out the financial operating system.
Timing adjustments by vertical
The four-year framework is a baseline. Vertical dynamics can accelerate or delay specific products:
• Restaurants: compress the timeline. Toast launched Capital and Payroll in years 2–3. High merchant density, strong payment data, employee intensity — all three embedded finance products are immediately relevant.
• Field services: insurance before payroll. Liability exposure is high, creating strong insurance demand. Launch insurance in Year 2 alongside or before working capital.
• Healthcare / wellness: working capital first, banking next. Payment data is rich, working capital demand is strong, and the regulatory environment favors embedded banking over insurance for most sub-verticals.
• Horizontal SaaS: slower cadence. Horizontal platforms lack the vertical-specific underwriting advantage and face more competition for merchant financial relationships. Working capital and banking are still viable, but the timeline may extend to 5–6 years.
Build vs. Buy vs. Partner
For each embedded finance product, you face the same fundamental question: build it yourself, acquire a company that has already built it, or partner with a specialized provider. The answer is almost always “Partner First” — at least initially. The framework:
| Product | Build | Buy / Acquire | Partner | Best Path |
|---|---|---|---|---|
| Payments | Full PayFac ($5M+ build) — only at $500M+ GMV | Acquire payment processor — rare, capital-intensive | PFaaS / Managed PayFac — right choice for ~95% of platforms | Partner |
| Working Capital / MCA | Build lending engine + obtain licenses — $2M+ | Acquire lending company — expensive, fast | Parafin, YouLend, Lendflow, Liberis — launch in weeks | Partner |
| Term Lending | Build + bank charter or state licenses — $3M+ | Acquire licensed lender | Bank partnership (sponsor bank) + lending SaaS | Partner |
| Insurance | Obtain MGA license + build underwriting — rare | Acquire MGA — vertical-specific opportunity | Insurance API platforms (Next, Pie, embedded MGAs) | Partner |
| Banking / BaaS | Charter or industrial bank license — $10M+ | Acquire community bank — complex, rare | BaaS providers (Unit, Treasury Prime, Helix by Q2) | Partner |
| Payroll | Build payroll engine + multi-state compliance — $5M+ | Acquire payroll company | Check, Gusto Embedded, Homebase | Partner |
| Cards | Card issuing program + compliance + Visa/MC program — $3M+ | Acquire card issuer — rare | Marqeta, Lithic, Stripe Issuing | Partner |
Why Partner First wins at startup stage
• Speed to market: partner integrations launch in weeks to months vs. 12–24 months for builds.
• Capital efficiency: the investment in building a lending engine or payroll platform is enormous — capital better deployed on product and go-to-market.
• Risk reduction: your first embedded finance product will teach you things about your merchant base you did not know — learn with a partner’s infrastructure before committing to a build.
• Optionality: partner first, build later if scale justifies it. The reverse path (build first, partner later) is expensive and rare.
When to consider building
Building becomes viable — and eventually necessary — when two conditions are met simultaneously:
• Your GMV or volume in the specific product category is large enough that the partner margin exceeds the annualized build cost.
• The product is core to your strategic differentiation — you cannot be the best restaurant financial OS if you are using generic restaurant payroll from a third party.
Rule of thumb: at 5x+ annual revenue from the product category, run the build-vs-continue-to-partner analysis formally. Below that threshold, the partner is almost always right.
Charge Forward Insight
The most common error in build-vs-buy-vs-partner is treating it as a one-time decision. The right answer evolves with your scale. The platforms that get this right run the framework annually, not once at the start. A working-capital partner that was perfect at $50M annual advance volume may be limiting at $300M — and that is when the build conversation deserves to be revisited. The Charge Forward Vendor Database tracks each major embedded finance infrastructure provider with their typical client size, geographic coverage, and vertical focus, which makes the annual re-evaluation tractable.
The infrastructure landscape
The embedded finance ecosystem has matured dramatically over the past five years. Where platforms once had few choices, today the market is rich with specialized infrastructure providers across every product category. The landscape below is drawn from “The 2026 Embedded Finance Landscape: 100 Companies Transforming a $7.2T Market.”
| Category | Key Companies | Count |
|---|---|---|
| Embedded Payments Platforms | Stripe, PayPal, Block, Adyen, Fiserv, FIS, Global Payments, J.P. Morgan Payments, Nuvei, Fortis, Rapyd, Airwallex, Checkout.com, WePay, BlueSnap | 25+ |
| Banking-as-a-Service (BaaS) | Unit, Treasury Prime, Synctera, Green Dot, Helix by Q2, Cross River Bank, Goldman Sachs Transaction Banking, Evolve Bank, Pathward, The Bancorp, Mambu, Thought Machine, Griffin, Pismo | 25+ |
| Embedded Lending & BNPL | Affirm, Klarna, Afterpay, YouLend, Lendflow, Parafin, Liberis, Wisetack, TreviPay, Kanmon, Pipe, Capchase, Outfund, FundThrough, Raistone | 20+ |
| Embedded Insurance | Next Insurance, Pie Insurance, Coterie, Vouch, Boost Insurance, Ascend, Sure, Branch, Cowbell Cyber | 10+ |
| Embedded Payroll | Gusto Embedded (Check), Toast Payroll, Homebase, Rippling, Justworks, Paylocity, Patriot Software | 10+ |
| Spend Management & Cards | Divvy/BILL, Brex, Ramp, Marqeta, Lithic, Stripe Issuing, Galileo, i2c, Deserve | 10+ |
The takeaway from this landscape: for every embedded finance product you want to offer, there are multiple infrastructure providers ready to power it. The “we can’t build that” objection is no longer valid. The question is which partner best fits your vertical, your merchant risk profile, and your commercial requirements.
Real-world roadmap examples
The most instructive way to understand the embedded finance roadmap is through the companies that have already walked it. Three examples stand out for their clarity and replicability.
Toast — The restaurant financial operating system
Toast began as a restaurant POS software company. The embedded finance journey:
• Years 1–2: Embedded payments — launched Toast Payments, integrated directly into POS workflow. Payments quickly became the dominant revenue source (roughly 85–87% of revenue is fintech-driven per Flagship Advisory data, representing approximately $5B in total FY2024 revenue).
• Years 3–4: Toast Capital — merchant cash advances underwritten by payment volume data. Restaurants have seasonal cash flow needs; payment data is the perfect underwriting input.
• Years 4–5: Toast Payroll — payroll for restaurant employees, deeply integrated with scheduling and tips management.
• Year 6+: Toast Insurance — business insurance for restaurant operators. Liability coverage, workers’ comp, tailored to the vertical.
Result: Toast is now the financial operating system for over 100,000 restaurant locations. Fintech revenues dominate. The payments wedge funded everything that followed.
Shopify — The merchant commerce platform
Shopify’s embedded finance journey is the most studied in the market:
• Years 1–3: Shopify Payments — launched integrated payments, dramatically simplifying the merchant experience. Became the dominant revenue driver.
• Years 4–5: Shopify Capital — merchant cash advances underwritten by Shopify payment data. Shopify has an information advantage over any bank.
• Year 6: Shopify Balance — business banking accounts and debit cards. The merchant’s operating account now lives inside Shopify.
• Year 7+: Shopify Credit — business credit card for Shopify merchants. Full spend management within the platform.
Shopify’s NRR has consistently exceeded 110% — a direct result of the stickiness created by multiproduct embedded finance.
Block / Square — The SMB financial platform
Block (formerly Square) has executed the most complete embedded finance playbook in the market:
• Payments: The POS reader and Square Payments — the original product.
• Square Loans: Working capital for Square merchants, underwritten by Square payment data. Over $10B disbursed since launch.
• Square Banking: Business checking accounts and debit cards for merchants.
• Square Payroll: Full payroll processing integrated with the Square ecosystem.
• Afterpay acquisition: BNPL for consumers — extending the financial services stack to the end consumer.
Block now processes hundreds of billions in payment volume annually. The financial services revenue built on that foundation is equally substantial.
The common thread
What Toast, Shopify, and Block share is not industry, not geography, and not founding team background. What they share is a deliberate, sequenced approach to building financial services on top of a payments foundation, using payment data as the underwriting and relationship advantage that no pure-play financial institution can replicate.
What your PE/VC investors want to see
Embedded finance is now a top-five diligence topic for private equity and venture investors evaluating vertical SaaS platforms. The question is no longer “do you have embedded payments?” — it is “what is your full embedded finance roadmap, and what evidence do you have that you can execute it?” The best investor narratives include:
| What Investors Want | What to Show | Investor Signal |
|---|---|---|
| Payment proof points | Demonstrated ability to sell, implement, and monetize financial products in your vertical. Attach rate, take rate trend, merchant retention delta. | Executes on fintech, not just software |
| TAM expansion per product | For each planned embedded finance product, size the addressable market: (merchant count) × (ARPU uplift per product). Show the ladder. | Multiple vectors of revenue growth |
| Unit economics at scale | Revenue per merchant today vs. at target penetration. What does the fully-loaded embedded finance platform look like at 1,000 vs. 10,000 merchants? | Scalable, not one-off |
| Data moat | Payment data creates underwriting advantages. Show that your default rates on lending would be structurally lower than market because of proprietary payment data (see Chapter 8). | Durable competitive advantage |
| Retention impact | William Blair data: SaaS platforms with embedded finance have 95% GRR vs. 93% for software-only. NRR of 111% vs. 105%. Quantify yours. | LTV expansion story |
| Valuation comparables | Multiproduct embedded finance platforms trade at ~12.7x EV/Revenue vs. 8.4x for software-only (William Blair, 2025). Position yourself on the right side of this table. | Premium multiple justification |
| Roadmap credibility | A sequenced, believable roadmap with partner commitments and realistic timelines is more credible than an aspirational slide. | Management team execution credibility |
The valuation premium is real
William Blair analyzed approximately 100 M&A transactions involving privately owned software companies in North America with enterprise values of $100M–$3B (2020–2025). The findings:
• Software-only platforms: 8.4x EV/Revenue, 23.2x EV/EBITDA.
• Software + Payments platforms: 9.7x EV/Revenue, 25.6x EV/EBITDA — a 15% premium.
• Multiproduct Embedded Finance platforms: 12.7x EV/Revenue, 28.1x EV/EBITDA — a 51% premium over software-only.
Only 10% of companies in William Blair’s dataset were multiproduct embedded finance platforms — creating significant scarcity value for those executing on the strategy. The window of differentiation is now. Windsor Drake’s Q1 2026 Vertical SaaS Valuation Report reaches similar conclusions: vertical category leaders trade at 8–12x revenue (with outliers to 14x) against a 6.7x public median, with embedded fintech contributing a 25–45% valuation lift.
Charge Forward Insight
Payments is the wedge. The real value creation comes from the financial services ecosystem you build on top of it. Platforms report significant incremental revenue from embedded lending alone, often in the millions annually, using payment data to underwrite loans with meaningfully lower default rates than traditional lenders due to the richness of payment data used for underwriting. That lower default rate means higher approval rates, better pricing, and stronger merchant adoption — a flywheel that compounds over time. The most important decision you can make today is not which lending partner to pick or which payroll API to integrate. It is the decision to treat your payment infrastructure as a strategic asset — to invest in the data architecture, the merchant relationships, and the internal expertise that makes every subsequent embedded finance product easier to launch and more valuable to your merchants. Platforms that make that decision in Year 1 look very different at Year 5 than those that treat payments as a revenue line item and nothing more. The difference is not just financial — it is strategic. The platform that is deeply embedded in its merchants’ financial operations is extraordinarily difficult to displace.
Getting started — your next steps
You now have the complete framework. The action sequence:
1. Assess where you are on the maturity curve. Use the Charge Forward Maturity Framework to identify your current stage and the right next move. If you don’t know your effective take rate, find out today.
2. Optimize your current payments (Chapters 5–6). Maximize attach rate, implement IC+ pricing, and clean up your revenue model before adding new products. A leaky bucket cannot be expanded.
3. Build your data strategy (Chapter 8). Ensure you are capturing the transaction-level data that will underwrite your first lending product. If your current processor doesn’t provide this data, add it to the migration trigger list.
4. Identify your first embedded finance product based on your vertical. Survey your top merchants on financial pain points. The answer is in their answers, not in a market report.
5. Select a partner and launch in 90 days. The right MCA, insurance, or payroll partner can be integrated and live within a quarter. Perfect is the enemy of good.
What’s next
Chapter 11 — “Benchmarks & Industry Data” — is the reference companion to everything in this Knowledge Hub. Every data point cited throughout Chapters 1–10 (attach rates by vertical, take rate ranges by model, embedded finance revenue estimates, valuation benchmarks) is consolidated, sourced, and kept current in the Benchmarks chapter. Use it alongside any chapter for current market context.
Chapter 12 — “AI & Agentic Payments” — looks at the next frontier: how AI agents will reshape payments authentication, fraud, optimization, and the merchant experience over the next 3–5 years. For platforms building today, Chapter 12 is the strategic argument for designing payment infrastructure that an AI agent can transact through, not just consume reports from.
To benchmark your platform’s embedded finance maturity, download the Charge Forward Embedded Payments Maturity Framework. To quantify the revenue runway from each next product, run the Charge Forward Payments Revenue Calculator.
SOURCES & REFERENCES
Flagship Advisory Partners — Beyond Payments: The $1T Embedded Finance Opportunity (2025); The Massive Embedded Finance Opportunity SaaS Platforms Cannot Afford to Miss (2025).
Adyen / BCG — Embedded Finance Report (2024). adyen.com/knowledge-hub/embedded-finance-report.
William Blair — How Embedded Finance Drives Enterprise Value and Increases Multiples for SaaS Platforms (September 2025).
Windsor Drake — Vertical SaaS Valuation Report, Q1 2026 (January 2026).
“The 2026 Embedded Finance Landscape: 100 Companies Transforming a $7.2T Market.”
Charge Forward Embedded Payments Benchmark Report (April 2026); see Chapter 11 for the full benchmark dataset.
Public Charge Forward tools referenced in this chapter: Maturity Framework, Payments Revenue Calculator, Vendor Database. All available at chargeforward.io/tools.
By Jane Podbelskaya · Updated