Our guides to Embedded Payments for SaaS Platforms and Platform Monetization explain why financial workflows can be an expansion path. Shopify and Mindbody illustrate differing business models, but the supplied revenue-share percentages were not checked against current primary filings and are not used here as universal payments benchmarks.
This deep dive is built specifically for SaaS founders, CFOs, and CROs who are either launching embedded payments for the first time or re-architecting an underperforming legacy integration. Here is the exact unit-economic math across operating models, ASC 606 gross-vs-net revenue recognition, pricing floors and ceilings, and go-to-market attach rate levers.
How Does Net Take Rate Compare Across the 4 Embedded Payment Models?
Gross Payment Volume (GPV) is not revenue. For planning, define net take rate as retained payment economics divided by GPV, expressed in basis points: 1 bp = 0.01%; net take rate (bps) = net retained payment revenue ÷ GPV × 10,000. Reconcile this operating metric to accounting revenue with your accountant.
The following table is an illustrative operating-model comparison, not an independent study or provider quote. Model actual underwriting allocation, merchant agreements, adoption, pricing, compliance and exit terms before choosing a structure.
| Operating Model | Typical Net Take Rate (bps) | Annual Net Revenue on $50M GPV | Annual Net Revenue on $200M GPV | Setup Cost & Time to Launch | Who Owns Underwriting, Compliance & Pricing Control? |
|---|---|---|---|---|---|
| 1. Referral / Legacy ISO | 5–15 bps | $25,000–$75,000 | $100,000–$300,000 | Near $0 / 1–2 weeks | Provider owns 100% of merchant contract, onboarding, and pricing; SaaS receives passive residual. |
| 2. Integrated / Fee-on-Top Markup | 10–30 bps | $50,000–$150,000 | $200,000–$600,000 | Low / 2–6 weeks (e.g., standard Stripe Connect) | Sub-merchant connects standard account; platform charges a small API application fee on top. |
| 3. PayFac-as-a-Service (PFaaS) | 50–150 bps assumed | $250,000–$750,000 | $1,000,000–$3,000,000 | Illustrative: 1–4 months; obtain a real quote | Contract-defined provider and sponsor responsibilities. A payment facilitator is not automatically the merchant of record; platform pricing and residual sharing are negotiated. |
| 4. Full Registered PayFac | 50–100+ bps | $250,000–$500,000+ (minus $100k+ fixed ops) | $1,000,000–$2,000,000+ | ~$500,000 setup + $100,000+/yr ongoing / 12–18 months | SaaS platform registers directly with networks/sponsor bank and assumes full PCI Level 1, underwriting, and fraud/chargeback liability. |
Illustrative economics: At an assumed $50M GPV, 10 bps yields $50,000 and 80 bps yields $400,000 before incremental costs: an 8× spread difference under those assumptions. The proposed $50M volume, $500,000 setup and $100,000 annual overhead figures are not registration requirements or quoted costs; obtain provider, sponsor and compliance estimates.
Gross vs. Net Revenue Recognition: How $100M in GPV Changes Your Board Deck
ASC 606 gross-versus-net presentation is not a discretionary election. Determine whether the entity controls the specified service before transfer and is principal or agent, then apply the required accounting treatment with qualified accountants. Rainforest’s numerical example illustrates presentation, not permission to select whichever makes a board deck look better.
Worked Accounting Comparison on $100,000,000 Annual GPV
Assume your vertical SaaS platform processes $100,000,000 in annual card volume, charges sub-merchants a 3.00% blended processing rate, incurs 2.00% in pass-through interchange and network assessments, and pays 0.30% (30 bps) in PFaaS provider buy-rate fees—leaving 0.70% (70 bps) as your net spread:
| Financial Line Item | Option A: Net Revenue Recognition (Residual Only) | Option B: Gross Revenue Recognition (Full Merchant Fee) | Variance & Investor Interpretation |
|---|---|---|---|
| Annual Gross Payment Volume (GPV) | $100,000,000 | $100,000,000 | Identical underlying transaction activity |
| Recognized Payments Revenue | $700,000 (0.70% net spread) | $3,000,000 (3.00% merchant fee) | Gross books 4.28x higher top-line revenue |
| Direct Cost of Revenue (Interchange + Provider) | ~$0 (netted prior to payout) | $2,300,000 (2.00% passthrough + 0.30% provider) | Gross records passthrough interchange as COGS |
| Net Payments Gross Profit ($) | $700,000 | $700,000 | Identical $700,000 cash gross profit |
| Reported Payments Gross Margin (%) | ~100.0% | 23.3% | Gross compresses blended company gross margin % |
Every SaaS CEO and CFO should align investors on Net Take Rate (70 bps) and Net Payments Gross Profit ($700,000) alongside top-line revenue so board members never mistake gross-recognized interchange pass-through for software margin compression.
How Do You Set Your Embedded Payments Price Floor and Price Ceiling?
Software sales teams routinely make the mistake of treating payment processing as a commodity price war—offering to "match or beat" whatever rate a prospective customer claims they pay their local bank. In reality, vertical SaaS platforms earn pricing power by embedding payments inside the core workflow (invoicing, scheduling, EHR, property management, or POS reconciliation).
1. Calculating Your Bottom-Up Price Floor
Per Rainforest Pay's Embedded Payments Pricing Benchmarks, your cost floor equals Estimated Pass-Through Costs (Interchange + Network Assessments) + Provider Buy-Rate + Target Platform Margin:
- Low-ticket in-person B2C:
1.60%–2.00%illustrative pass-through cost assumption - High-ticket in-person B2C:
1.80%–2.30%illustrative pass-through cost assumption - Low-ticket online B2C:
1.90%–2.30%illustrative pass-through cost assumption - High-ticket online B2C:
2.20%–2.60%illustrative pass-through cost assumption - Non-profit:
1.50%–1.90%illustrative pass-through cost assumption - B2B commercial cards:
2.40%–3.00%illustrative pass-through cost assumption
For example, a vertical SaaS platform serving healthcare clinics ($250 average ticket) with a 2.10% pass-through cost, 0.20% (20 bps) PFaaS provider fee, and a 0.50% (50 bps) net margin target has a minimum viable price floor of 2.80%.
2. Setting Your Top-Down Price Ceiling by Product Comprehensiveness
What sub-merchants will gladly pay depends on how deeply your software runs their business (Bridges / Rainforest Pricing Ceiling Analysis):
- Horizontal / Light Workflow Tool (standalone invoicing/billing): Supports 2.70%–3.00% all-in.
- Moderately Differentiated Vertical Workflow: Supports 2.90%–3.50% all-in.
- Comprehensive Vertical Operating System (all-in-one scheduling, CRM, billing, and customer portal—such as boutique fitness or field services): Illustratively model 3.20%–3.90%+, or Bundled Pricing where software subscription fees are folded directly into a unified processing rate.
- Separate ACH economics — model only: Test the example 0.50%–1.50% fee, $5–$10 cap, or flat $1.50–$3.00 fee against actual contracts and customer value. Include returns, fraud, settlement, support and compliance costs; ACH is not pure margin.
Why Merchant Attach Rate Is a 10x Bigger Lever Than Shaving 5 Basis Points
Treat merchant adoption as a measured distribution in your own eligible customer base. The following 20% and 60% attach rates are sensitivity scenarios—not industry medians or an independently verified study. Define the eligible population, active transacting window and GPV before comparing cohorts.
Look at the math on a vertical SaaS platform with 1,500 active software customers, each processing $15,000/month ($180,000/year) in addressable payment volume ($270M total addressable GPV):
- Stalled Launch (20% Attach Rate / $54M GPV at 65 bps net take rate): Generates $351,000/year in net payment profit. Negotiating 5 bps off your provider buy-rate adds just $27,000/year.
- 60% attach-rate scenario ($162M GPV at 65 bps): $1,053,000/year retained spread, $702,000 more than the 20% scenario, before incremental operations, support, losses, incentives and acquisition costs. It is not retained spread before operating costs.
The 5 Operator Rules That Drive Attach Rate Past 60%
- Assign a payments owner with executive sponsorship: Give one person responsibility for adoption, economics, merchant outcomes and provider accountability. A claimed 45-bps causal uplift was not independently established here; measure your own cohort results.
- Make On-Platform Payments the Default Workflow, Never an Opt-In Tab: Embed payment onboarding directly inside core product activation (so sending the first quote, booking, or invoice automatically provisions the sub-merchant account via KYC/KYB API) rather than hiding a "Connect a Processor" button in Settings.
- Align Sales Compensation to Payment Attach and GPV: If software Account Executives are paid 100% on SaaS seat ARR and 0% on payment attachment—or if they are allowed to waive payment spreads to close software deals—attach rates will stall. Structure AE and CSM comp with explicit spiffs or quota retirement on Activated Payment Volume within 30 days of onboarding, using clear rules similar to our guide on revenue share agreements structure, rates, and terms.
- Ensure Contract & Vault Portability Before You Sign a PFaaS Partner: When evaluating PFaaS providers (such as Rainforest, Finix, Adyen for Platforms, Stripe Connect, or Payrix), verify two contractual clauses upfront: (a) your revenue share is calculated on true net processing margin rather than a capped referral fee, and (b) you own the sub-merchant relationship and portable network token vault if you ever migrate providers.
- Prepare Your Platform for Agentic & Autonomous Checkout: As AI agents increasingly execute B2B procurement and consumer bookings inside vertical software, your embedded payment rails must also support programmatic agentic verification—the exact topic of our final article in this series, Agentic Checkout Trust: What Platforms and Merchants Must Build Before AI Agents Start Spending.
Related Rebar payments guidance
Use this playbook alongside embedded payments guide saas platforms, platform monetization beyond saas. Explore Rebar Payments advisory for a review of provider options and commercial trade-offs.
Common questions
What volume threshold does a SaaS platform need before becoming a full registered PayFac?
Hosted payment components can reduce exposure, but SAQ A is not automatic. All current payment-page, script-security and other eligibility criteria must be satisfied; confirm with your acquirer/QSA.
Should a vertical SaaS platform price embedded payments as Interchange-Plus (IC+) or Blended Flat Rate?
Illustrative planning guidance, not a universal benchmark or promised result: For most vertical SaaS platforms serving SMB and mid-market merchants, a blended rate (e.g., 2.95% + $0.30) or bundled software-plus-payments rate is superior to Interchange-Plus. Blended pricing is easier for sub-merchants to reconcile, avoids exposing your exact basis-point spread on every monthly statement, and allows the platform to retain margin gains from interchange optimization.
What is a good merchant attach rate for embedded payments in vertical SaaS?
Illustrative planning guidance, not a universal benchmark or promised result: While many early programs stall at 15% to 20% attachment when payments are sold as an optional add-on, top-quartile vertical SaaS platforms achieve 60% to 80%+ attachment by embedding sub-merchant onboarding directly into the default product workflow and tying sales compensation to payment activation.
Does choosing Gross vs. Net revenue recognition change how much profit we make on embedded payments?
Illustrative planning guidance, not a universal benchmark or promised result: No. Under ASC 606, whether you recognize gross merchant fees (with interchange and provider fees as COGS) or net residual spread, your bottom-line gross profit in dollars is identical. However, gross recognition increases reported top-line revenue by ~4x while lowering your reported gross margin percentage, so CFOs should in the modeled scenario report Net Take Rate and Net Payments Gross Profit alongside top-line figures.