# What Is Embedded Finance? A Founder's Guide to Revenue Beyond Subscriptions > Embedded finance explained for SaaS founders. Layers, revenue models, partner types, and how to add financial features to your product without becoming a regulated entity. - **Author**: Ayush Agarwal - **Published**: 2026-05-03 - **Category**: Embedded Finance, SaaS, Payments - **URL**: https://dodopayments.com/blogs/what-is-embedded-finance --- Embedded finance is the practice of integrating financial services into non-financial products. A SaaS app that lets you accept customer payments. A vertical SaaS that issues your customers a debit card. A creator platform that holds your earnings until you withdraw them. Each is an example of embedded finance. The category got its name in the early 2020s, but the underlying idea is older. Apple Pay, Shopify Capital, and Uber's instant pay for drivers were embedded finance before anyone called it that. What changed is the toolchain: by 2026, almost any SaaS company can add financial features without becoming a bank or hiring a compliance team. This guide is the founder-friendly explanation of what embedded finance actually is, the layers you can integrate, the revenue models that work, and where to start. ## A Working Definition Embedded finance means delivering financial services through the user experience of a non-financial product. The user does not visit a bank's website or download a separate app. The financial feature appears inside the product they are already using. Three things are usually true: 1. **The non-financial product owns the user experience.** Branding, design, support flow, and customer relationship sit with the SaaS company. 2. **A regulated partner handles the regulated activity.** Holding deposits, issuing cards, processing payments, lending money. The partner has the licenses; the SaaS provides the distribution. 3. **The user usually doesn't know there's a partner.** They pay through the SaaS, get a card from the SaaS, hold a balance with the SaaS. The partner is invisible to them. > Embedded finance flips the traditional relationship. Banks have always controlled the user relationship. With embedded finance, the SaaS controls the relationship and the bank becomes infrastructure. That shift is worth trillions. > > - Ayush Agarwal, Co-founder & CPTO at Dodo Payments ## The Five Layers of Embedded Finance Most embedded finance programs map to one of five layers. Each layer requires different partners, different compliance posture, and unlocks different revenue. ```mermaid flowchart TD A[SaaS Product] --> B[Layer 1: Embedded Payments] A --> C[Layer 2: Embedded Payouts] A --> D[Layer 3: Embedded Treasury] A --> E[Layer 4: Embedded Lending] A --> F[Layer 5: Embedded Cards] B -->|Lowest complexity| G[Process customer payments] C --> H[Send money to your customers] D --> I[Hold customer balances] E --> J[Lend to your customers] F --> K[Issue branded cards] G --> L[Most common starting point] ``` ### Layer 1: Embedded Payments Customers pay through your application. Common in every SaaS, every checkout, every subscription. This is where embedded finance starts for most companies. Revenue: take rate (typically 0.5 to 2 percent) on every transaction. For a SaaS doing $1M annual transaction volume, that translates to $5K to $20K per year of pure embedded payments revenue, on top of the underlying product subscription. For a deeper look, see our [embedded payments for SaaS platforms guide](https://dodopayments.com/blogs/embedded-payments-saas-platforms). ### Layer 2: Embedded Payouts Send money out to your customers. Marketplaces (paying sellers), creator platforms (paying creators), gig economy apps (paying contractors), affiliate platforms (paying affiliates). All embedded payouts. Revenue: per-payout fee (typically $0.25 to $2 per payout), interest on the float (the time between when funds arrive and when they're paid out), and FX margin on cross-border payouts. ### Layer 3: Embedded Treasury Customers hold cash balances inside your app. Vertical SaaS for restaurants, contractors, freelancers, and small businesses commonly add treasury features so customers can keep their working capital inside the platform. Revenue: interchange on outgoing card spend from those balances (1.5 to 2.5 percent), interest on idle balances (which the partner bank shares with you), and account fees if you charge them. ### Layer 4: Embedded Lending Customers borrow against future revenue, accounts receivable, inventory, or general business needs. Common in commerce-adjacent SaaS, B2B fintech, and specialized vertical SaaS. Revenue: origination fee (1 to 3 percent of loan principal), ongoing take rate (0.5 to 2 percent), and FX/cross-border margin where applicable. Highest revenue per customer of any embedded finance layer. ### Layer 5: Embedded Cards Customers receive a branded debit or credit card from your platform. Spending on those cards generates interchange revenue. Common in expense management, vertical SaaS, and creator economy products. Revenue: interchange on every card swipe. Net of partner share, this typically nets 0.5 to 1.5 percent. At scale (when customers spend $5K+ per month on the card), this becomes a significant revenue stream. ## Why It Matters for SaaS The unit economics of embedded finance are dramatically better than typical SaaS. A $50/month SaaS subscription generates $600 ARR per customer. Adding embedded finance can 3 to 10x that number without proportionally increasing CAC, support costs, or feature investment. Three structural reasons it works: 1. **You already have the customer.** No incremental acquisition cost. 2. **You already understand their workflow.** Embedded financial features are easy to position because you know the pain. 3. **You already have integration leverage.** Customers don't compare alternatives because the financial feature is bundled with the product they already love. The companies that have built embedded finance well (Shopify, Toast, ServiceTitan, Mindbody) typically see 40 to 70 percent of their revenue come from embedded finance, up from 0 percent five years prior. ## What's Required: Partners and Compliance The compliance requirements scale with the layer. Layer 1 (payments) is the lightest. Layer 4 (lending) is the heaviest. For most SaaS companies, the path is: 1. **Pick a partner that holds the necessary license** (sponsor bank, payment processor, lending platform). 2. **Operate as a "program manager" or "platform" under the partner's license.** This carries lighter compliance requirements than holding your own license. 3. **Implement the partner's required policies** (KYC, transaction monitoring, marketing compliance, data security). The exception is if you want to take on the regulated activity yourself. Becoming a money transmitter, bank, or licensed lender takes 18 months to 5 years and costs millions of dollars. Don't do this until you've scaled embedded finance to the point where the unit economics justify it. For more on the compliance side, see our companion guides on [PCI compliance for SaaS](https://dodopayments.com/blogs/pci-compliance-checklist-saas), [PCI-DSS for digital business](https://dodopayments.com/blogs/pci-dss-compliance-digital-business), and our [embedded finance solutions for SaaS](https://dodopayments.com/blogs/embedded-finance-solutions-saas) deep dive. ## Real Embedded Finance Examples | Company | Embedded Finance Layer | Revenue Story | |---|---|---| | Shopify | Payments + Capital + Card | ~50% of revenue from embedded finance | | Toast | Payments + Lending + Treasury | Embedded finance is faster-growing than subscriptions | | Square | Payments + Treasury + Card + Lending | Embedded finance has been the moat since 2015 | | Lyft | Payouts + Card | Driver retention play that became revenue | | Patreon | Payments + Payouts | Take rate on creator earnings | | ServiceTitan | Payments + Lending | Embedded finance ARR exceeded SaaS ARR by 2024 | The pattern: companies that add embedded finance well end up with a financial services business that's larger than the SaaS that birthed it. ## How to Decide What to Embed Start with these questions: 1. **What's the natural financial transaction in your customer's workflow?** If you sell to restaurants and they take card payments from diners, payments is obvious. If you sell to contractors who get paid by clients, payouts is obvious. 2. **What's the customer's pain at the financial layer?** Slow payouts? High processing fees? No access to credit? The pain points map to layers. 3. **What's your customer's revenue size?** Each layer has minimum customer revenue thresholds for the math to work. Payments works at any size. Treasury, cards, and lending start to make sense above $5K to $50K of monthly customer revenue. 4. **What's your company's stage?** Pre-seed: focus on the product. Series A: layer 1. Series B+: consider layers 2-5. For more strategic context, see our companion piece on [what is embedded finance](https://dodopayments.com/blogs/what-is-embedded-finance) and our [SaaS expansion guide](https://dodopayments.com/blogs/scaling-global-saas-microsaas-expansion). ## Common Embedded Finance Mistakes Patterns that derail programs: - **Underestimating support load.** Financial features generate 3 to 5x more support tickets than software features. - **Treating compliance as a feature.** It's a continuous program with ongoing costs. - **Building before validating.** Add the simplest version of each layer first, validate adoption, then invest in the full feature set. - **Picking the wrong first layer.** Embedded lending before payments is like skipping the foundation of a house. - **Underpricing.** Most SaaS founders price embedded finance too cheap because they don't realize how valuable it is to customers. - **Ignoring fraud.** Embedded finance amplifies fraud surface. Plan for 0.5 to 2 percent of transaction volume in fraud losses. For more on fraud, see our [chargeback fraud prevention](https://dodopayments.com/blogs/chargeback-fraud-prevention) and [friendly fraud prevention](https://dodopayments.com/blogs/friendly-fraud-prevention) guides. > The biggest mistake I see is founders treating embedded finance as a product feature. It's a business line. It deserves its own roadmap, its own metrics, and its own go-to-market motion. Companies that treat it that way win. Companies that treat it as a side project lose. > > - Rishabh Goel, Co-founder & CEO at Dodo Payments ## When NOT to Embed Embedded finance isn't right for every SaaS. Skip it if: - **Your customer base is tiny.** Below 1,000 active customers, the per-customer revenue from embedded finance probably doesn't justify the complexity. - **Your product doesn't have a financial workflow.** A pure tool with no money flowing through it can't easily layer in financial services. - **Your runway is short.** Embedded finance takes 6 to 18 months to monetize meaningfully. If you need revenue in 90 days, focus on the core SaaS first. - **Your team can't take on the support load.** Financial features generate more tickets than software features. Staff for it. ## The Roadmap: From Zero to Embedded Finance For a typical SaaS company, here's the realistic timeline: | Month | Milestone | |---|---| | 1-2 | Add embedded payments (Layer 1) for customer purchases | | 3-6 | Validate take rate, customer adoption, support load | | 7-9 | Add payouts (Layer 2) if customer workflow includes outgoing money | | 10-12 | Validate, optimize, refine | | 13-18 | Consider treasury (Layer 3) for vertical SaaS, or cards (Layer 5) for spend management | | 19-24 | Consider lending (Layer 4) once you have transaction history to underwrite from | By month 24, embedded finance should be 10 to 30 percent of revenue. By year 5, it can be 50+ percent. ## How Dodo Payments Fits Embedded Finance Strategies Dodo Payments handles Layers 1 (Embedded Payments) and 2 (Embedded Payouts) natively for SaaS companies: - Embedded checkout (inline, overlay, raw API options) - Native subscription management with hybrid billing - [Payouts to your customers' bank accounts](https://docs.dodopayments.com/features/payouts/payout-structure) across 220+ countries - Multi-currency support with automatic localization - Full Merchant of Record coverage so tax compliance is handled automatically - Webhook events for every billing state change - Customer portal embedded in your app - Transparent pricing at 4% plus 40 cents per transaction For higher layers (treasury, lending, cards), Dodo Payments integrates with specialized partners. The payments and payouts foundation that those layers depend on is handled natively. For implementation walkthroughs, see the [integration guide](https://docs.dodopayments.com/developer-resources/integration-guide) and the [Dodo Payments SDKs documentation](https://docs.dodopayments.com/developer-resources/dodo-payments-sdks). ## FAQ ### What is embedded finance in simple terms? Embedded finance is when a non-financial product (like a SaaS app) integrates financial services (payments, payouts, lending, cards) directly into its user experience. The user doesn't go to a bank or fintech company; the financial feature appears inside the product they're already using. A regulated partner handles the licensing and compliance behind the scenes. ### What are the layers of embedded finance? The five common layers are: embedded payments (process customer purchases), embedded payouts (send money to customers), embedded treasury (hold customer balances), embedded lending (lend to customers), and embedded cards (issue branded debit or credit cards). Each layer adds revenue but also compliance overhead, so most companies start with payments and add layers as they scale. ### Do I need a banking license for embedded finance? In most cases, no. You partner with a regulated provider (sponsor bank, payment processor, lending platform) that holds the necessary licenses. You operate as a "program manager" under their license, which carries lighter compliance requirements. You only need your own license if you want to take on the regulated activity directly, which costs millions and takes years. ### How much revenue can embedded finance generate? Companies that build embedded finance well typically end up with 40 to 70 percent of their revenue from financial services, often exceeding their core SaaS revenue. Even at smaller scale, adding embedded payments alone can 2 to 5x revenue per customer compared to subscription-only models. ### Where should I start with embedded finance? Start with embedded payments (Layer 1). It has the lowest compliance burden, the broadest applicability, and the clearest revenue model. Validate that your customers actually adopt and pay for it before moving to higher layers like payouts, treasury, lending, or cards. ## The Takeaway Embedded finance is no longer a fintech concept. It's the natural extension of any SaaS product whose customers transact money. Payments, payouts, treasury, lending, and cards are all available to SaaS companies through partner relationships, without becoming a regulated bank. Start with payments. Validate the customer behavior. Add layers as customer needs and revenue justify the complexity. Pick partners that handle compliance for you so your team stays focused on product. If you're at the embedded payments and payouts stage today, [Dodo Payments](https://dodopayments.com) handles checkout, subscriptions, payouts, and full Merchant of Record coverage in one stack. See the [pricing page](https://dodopayments.com/pricing) and the [integration guide](https://docs.dodopayments.com/developer-resources/integration-guide). --- - [More Embedded Finance articles](https://dodopayments.com/blogs/category/embedded-finance) - [All articles](https://dodopayments.com/blogs)