Choosing Your Embedded Payments Model
Five stages, one decision framework, and the operator playbook for picking the right point on the spectrum.
22 min read
A spectrum, with five stages
Embedded payments stopped being a binary choice few years ago. Today, the operating-model landscape is a range of options across various roles, responsibilities, and risks. UBS Question 6.0 (May 2026) frames it identically: “the industry is migrating more toward something in between the two extremes, a model where the software company is able to enjoy many of the benefits of becoming a full-fledged PayFac (in terms of control over pricing, experience, etc.) but without the same degree of regulatory, compliance, etc. upkeep required.”
The middle is where this guide focuses, because that is where most platforms will land — for years, sometimes permanently. We identify five operational stages across the spectrum. Each has a GMV sweet spot, a take-rate range, a team profile, and a graduation trigger.
Treat the five stages as a trajectory to plan for, not a menu to choose from. Pick the right stage for today, but architect your data model, vendor contracts, and team structure so the next transition is clean. The single most expensive mistake highlighted in this chapter is signing vendor contracts that cannot be migrated cleanly when the platform graduates — re-integration costs at the next stage routinely dwarf the savings from optimizing the current contract.
The five stages at a glance
| Stage | GMV Band | Net Take Rate | Annual Pmt Revenue | Margin | Team Evolution |
|---|---|---|---|---|---|
| 1 — PSP Referral | $0–$10M | 0–20 bps | $0–$20K | 90%+ | Partner manager (part-time) |
| 2 — Light PFaaS | $10M–$50M | 20–40 bps | $20K–$200K | 80–90% | Product Manager + part-time eng |
| 3 — Full PFaaS / Managed PayFac | $50M–$500M | 40–80 bps | $200K–$4M | 70–80% | Payments PM + 1–2 eng |
| 4 — Managed PayFac + Orchestration | $250M–$1B | 65–90 bps | $1.6M–$9M | 60–75% | Head of Payments (3–8 FTEs) |
| 5 — Full Registered PayFac (Optional) | $1B+ | 100–120+ bps | $10M+ | Varies | Full Payments Org (8–20+ FTEs) |
The five stages in detail
Stage 1: PSP Referral
You refer your customers to a payment processor — Stripe, Square, Paysafe, PayPal — and earn a referral fee or residual on transactions they process. You are not the merchant of record. You bear no compliance, underwriting, or chargeback liability. Your customers leave your platform’s UI to onboard with the processor.
How it works: sign a referral or ISO partner agreement. Co-market or embed a referral link in your platform. The processor handles all merchant onboarding, KYC, underwriting, and support. You receive a monthly residual or one-time bounty. Square pays approximately $1,000 per qualifying referral that reaches $250K+ annual processing volume.
Take rate, in concrete terms: at 20 bps, a platform processing $10M of customer volume earns $20,000 per year. The economics are modest. The operational footprint is essentially nothing.
Key providers: Stripe Connect Standard, Square Referral Program, Paysafe ISV Partner Program, PayPal Marketing Solutions for partners. PayPal’s referral terms favor verticals with high cross-border activity given its native multi-currency support.
UI / UX trade-off — links vs. truly white-label. Stage 1 is the only stage where the merchant onboarding flow is owned by the processor, not the platform. That is the meaningful UX trade-off, not the take rate. If your customers are willing to leave your product to set up payments with a third party, Stage 1 is acceptable. If they expect a continuous in-product experience, you have already outgrown Stage 1 even at low GMV.
Team: minimal. A partner manager owns the relationship. No dedicated engineering unless building referral-tracking infrastructure.
Time to launch: 4–8 weeks. The constraint is legal review, not engineering.
When to graduate: GMV approaches $10M; referral revenue reaches $50–150K/year; customers ask for an embedded in-app payment experience; a competitor launches native payments.
Stage 2: Light PFaaS / Revenue-Share Integration
You integrate a white-label gateway or light PFaaS provider under your brand and earn a revenue share on processed volume. The provider handles network connections and compliance; you own the merchant relationship and checkout experience. This is the entry point to embedded payments without full PFaaS complexity.
You integrate via API with a gateway provider — NMI offers connections to 125+ processors; Stripe Connect Custom provides platform application fees. Customers onboard within your platform or via a lightly branded flow. You earn the spread above the provider’s buy rate, typically 20–40 bps net. Engineering investment is materially lighter than full PFaaS — typically one engineer for one to two months.
Key providers: NMI, Stripe Connect Custom, WePay/Chase for Platforms, Adyen Lite.
Team: one engineer for one to two months of integration. One product manager owning the payments roadmap. No dedicated compliance FTEs — the provider handles network compliance.
Time to launch: 6–10 weeks from signed vendor contract to first live transaction.
When to graduate: GMV crosses $50M. This is the inflection point — Full PFaaS delivers a 4–5x revenue uplift over the referral and light models. At $50M GMV, the spread between 20 bps ($100K/year) and 80–90 bps ($400–450K/year) more than justifies the additional engineering investment.
Stage 3: Full PFaaS / Managed PayFac
A PFaaS vendor — Rainforest, Tilled, Finix, Payabli, Forward, Infinicept Launchpay — provides the full PayFac infrastructure (underwriting, KYC, compliance, risk management, settlement) fully under your brand. This is the dominant model for vertical SaaS at scale: Rainforest 2026 confirms 82% of vertical SaaS platforms now operate at this stage or its Stage 4 evolution. The market uses “PFaaS” and “Managed PayFac” almost interchangeably at this tier; the meaningful nuances surface as you move up the GMV curve.
You integrate the vendor’s APIs (typically 3–6 months of engineering work). Customers complete KYC and merchant onboarding natively within your platform. The vendor approves them as sub-merchants under your master merchant account. Transactions are processed, settled, and reported within your product. You earn the spread between your customer-facing pricing and the vendor’s buy rate. Rainforest is purpose-built for vertical SaaS; Payabli has gained traction in infrastructure-heavy verticals; Finix offers the cleanest documented PFaaS-to-Full-PayFac graduation path.
Key providers: Rainforest (purpose-built for vertical SaaS, US, expanding into Canada), Tilled, Finix (PFaaS tier), Payrix, Payabli, Forward, Infinicept Launchpay.
Team: one to two engineers for three to six months of integration. One product manager owning the payments roadmap. One customer success resource trained on payment onboarding. No compliance or risk FTEs — the vendor bears those obligations.
Time to launch: three to nine months from signed vendor contract to first live transaction.
When to graduate: GMV exceeds $250M; payment revenue rivals or exceeds subscription revenue; vendor fee economics are measurably worse than direct acquirer pricing at your volume; or you need deeper underwriting control to support adjacent fintech products (lending, card issuance). At $10M monthly processing, the math is approximately $57,500 in net revenue under Full PFaaS vs. $5,000–$8,000 under referral — a 700–1,000% improvement on identical volume.
Stage 4: Managed PayFac + Payment Orchestration
You operate with a direct acquirer relationship and negotiated buy-rate pricing — moving beyond the standard PFaaS tier into a more mature, negotiated arrangement. Payment orchestration (multi-provider routing, redundancy, authorization-rate optimization) becomes a priority at this scale. Payment revenue typically rivals subscription revenue.
You negotiate buy-rate pricing directly with an acquirer-backed provider, pushing net take rates to 65–80 bps. You layer a payment orchestration tier on top for multi-provider routing, fallback, and authorization-rate optimization. FIS acquired Payrix in February 2022; Payrix subsequently became part of Worldpay following the FIS/Worldpay separation. Worldpay/Payrix Pro now processes approximately 75% of all Mastercard PayFac volume. Adyen for Platforms processed approximately €27B in platform volume in H1 2025.
Key providers: Worldpay/Payrix Pro, Finix (mid-market tier), Adyen for Platforms.
Team: 3–8 dedicated payments FTEs — payments product manager, risk analyst / underwriter, compliance officer, 2–3 backend engineers, customer support specialist. Legal counsel with payments experience for acquirer negotiations.
Time to launch: 9–18 months from decision to full transition, including vendor negotiations (3–6 months) and internal build of underwriting workflows and risk monitoring.
When to graduate (and whether to): GMV exceeds $1B and the PFaaS fee (10–20 bps) has become materially expensive at volume. Full PayFac registration only makes clear economic sense above ~$1B GMV — and even then, many large platforms are consciously choosing not to register. Stage 4 is the optimal terminal state for the majority of platforms above $250M.
Stage 5: Full Registered PayFac (Optional)
You register directly with Visa and Mastercard as a Payment Facilitator. You hold money transmission licenses (MTLs) in all required states. You maintain your own risk models, underwriting infrastructure, and compliance program. Complete economic control — and full regulatory responsibility. We mark this stage “Optional” because, as the Rainforest 2026 framework and UBS Q6.0 both make explicit, even at this scale most platforms do not need to register. The Rainforest data shows only 10% of vertical SaaS platforms surveyed are full Registered PayFacs.
You apply for PayFac registration with Visa and Mastercard. You obtain MTLs across required US states (cumulative ~$450K over three years). You implement PCI DSS Level 1 compliance ($200K+/year). You operate as the merchant of record for all sub-merchants. Total three-year all-in cost: $750K–$1.5M setup plus $500K–$700K/year ongoing.
Key providers: Adyen for Platforms (enterprise), Stripe (custom registered), Finix Open, Infinicept (clearest PFaaS-to-PayFac advisory and tooling pathway in market).
Team: 8–20+ FTEs dedicated to payments — Head of Payments, Chief Compliance Officer, Risk Director, underwriting analysts, fraud operations, payments engineers (4–6), legal counsel, bank relationship managers, customer support. This is, effectively, building a payments company inside your SaaS business.
Time to launch: 2+ years from decision to full operational status. Network registration: 3–6 months. MTL acquisition: 18–36 months for full 50-state coverage. PCI DSS Level 1: 6–12 months.
When this is the right answer: when your fund flows require money transmission licensing in specific states; when legacy systems already require PayFac registration; or when you must hold customer funds for more than 30 days (Rainforest, Vertex 2026). Outside those three circumstances — and absent a deliberate strategic decision to build a payments business — Stage 4 is the better answer for most platforms.
⚠ The Trap
Thinking Stage 5 is the inevitable destination. The conventional wisdom from 2018–2022 said any platform above $250M GMV should be evaluating full registration. That narrative has materially softened. Visa-registered PayFac counts among North American ISV/SaaS contracted from 47% to 43% between March 2023 and early 2024, with annual attrition of approximately 6%. The Rainforest 2026 study confirms only 10% of vertical SaaS platforms are Registered PayFacs vs. 82% on Managed PayFac/PFaaS. The Vertex/Rainforest conference 2026 panel — featuring operators from Toast, Clio, and Mews — described embedded payments as a “spectrum across roles, responsibilities, and risks” with most platforms landing between the extremes. Both Finix and Infinicept now explicitly market “start and stay at PFaaS” positioning, although both can help platforms get full PayFac registration. Some practitioners describe a modest re-acceleration in PayFac enablement work; we read this as continued sophistication of the middle tier (Stage 4 orchestration), not a return to “register everything.”
PFaaS vs. Managed PayFac: when the distinction matters
The market uses “PFaaS” and “Managed PayFac” almost interchangeably. At the operational level, the distinction matters less than vendors suggest. Both keep the provider as the registered PayFac. Both give you a branded merchant experience. Both let you capture the spread above a buy rate.
The meaningful nuance shows up as your GMV grows. Managed PayFac is the more mature, negotiated version of PFaaS — higher control, shared risk exposure, direct buy-rate negotiation. Crossing into Managed PayFac is what happens between Stage 3 and Stage 4 in the framework above. It is less a contract change than a posture change: you stop accepting standard PFaaS terms and start treating your vendor as a negotiation counterparty.
Practical guidance: below $100M GMV, treat the two terms as equivalent. Focus on choosing the right vendor. Once you cross $100M and your vendor relationship is established, start negotiating directly on buy rates. That is what effectively moves you into Managed PayFac territory, regardless of how the contract is labeled.
The revenue economics: why model selection compounds
The single most compelling argument for investing in embedded payments infrastructure is the revenue differential between models on identical transaction volume. The table below shows net revenue at $100M annual GMV across the four primary approaches.
| Model | Net Take Rate | Annual Revenue on $100M GMV | Three-Year Revenue |
|---|---|---|---|
| PSP Referral | 10–20 bps | $100K–$200K | $300K–$600K |
| Light PFaaS | 20–40 bps | $200K–$400K | $600K–$1.2M |
| Full PFaaS / Managed PayFac | 60–80 bps | $600K–$800K | $1.8M–$2.4M |
| Managed PayFac + Orchestration | 75–90 bps | $750K–$900K | $2.25M–$2.7M |
Take rates by vertical, not just by model
Rainforest’s 2026 Vertical SaaS Embedded Payments Benchmarking Study (the first independent industry survey) reports meaningful variation in achieved take rates by vertical. The variation can dwarf the differences between models for platforms that benchmark inappropriately.
| Vertical | Avg. Net Take Rate | Drivers |
|---|---|---|
| Consumer / community | ~90 bps+ | High card mix, higher interchange categories, smaller average ticket |
| Services / healthcare | ~80 bps | Mixed card / ACH, mid-range ticket size |
| B2B / institutional | ~70 bps | ACH-heavy mix; larger average ticket suppresses bps |
The $10M monthly processing example
A platform processing $10M per month through Full PFaaS earns approximately $57,500 per month in net revenue. The same volume on a referral arrangement earns $5,000–$8,000. That is a 700–1,000% improvement on identical transaction volume — same merchant base, same checkout experience. The only thing that changed is who captured the economics.
At $10M monthly ($120M annually), a platform staying on referral is forgoing approximately $545,000–$570,000 per year. Compounded over three years, that is $1.6–1.7M in foregone revenue — enough to fund the entire PFaaS integration multiple times over.
Charge Forward Insight
The most common pattern we see in advisory work: platforms either move to PFaaS too late (foregoing hundreds of thousands of revenue above $50M GMV) or go for full PayFac registration when managed models would serve them better at a fraction of the cost. The Rainforest 2026 data confirms what we see operationally — 82% of vertical SaaS platforms land on Managed PayFac/PFaaS for a reason. Companies that get this right think of embedded payments as a multi-year strategic trajectory, not a one-time vendor selection. They plan their data architecture, vendor contracts, and team structure with the next model transition in mind — even if that transition is two to three years away. Every vendor contract you sign today should be reviewed against the question: “does this give us a clean path to the next stage?” Re-integration costs at the next stage routinely dwarf the savings from optimizing the current contract.
When Full PayFac is genuinely necessary
Full Registered PayFac is now an optional terminal state, not an aspirational endpoint. The Vertex/Rainforest 2026 panel narrowed the cases where full registration is genuinely required to three.
1. The platform has fund flows that require money transmission licensing in specific states. Examples: holding customer funds in escrow for extended periods, multi-party settlement structures, certain payroll-adjacent flows.
2. The platform’s legacy systems already require registration as a PayFac (typically the result of an earlier strategic decision that cannot be cleanly unwound).
3. The platform must hold money for more than 30 days as part of its core business model.
Outside these three circumstances, Stage 4 (Managed PayFac + Orchestration) delivers equivalent end-state economics at materially lower overhead. The corollary: the question “should we register?” often reduces to “does our product model require us to hold money long enough to require it?” For most SaaS platforms, the answer is no.
Where the market is heading in 2026
The directional data published since late 2024 tells one consistent story.
Software-led acquiring continues taking share
UBS Global Research “The Question 6.0” (May 4, 2026) projects software platforms’ share of US merchant acquiring revenue at ~35% in 2025 → ~45% by 2030 (the updated authoritative figure, replacing the earlier “33%/2024 → >45%/2029” from Q5.0). UBS also discloses a NEW figure in Q6.0: software platforms’ share of US SMB acquiring REVENUE will grow from ~47% in 2025 to ~60% in 2030; the corresponding VOLUME share is ~70% (2025) → ~84% (2030). BCG and Adyen put the SaaS share of SME acquiring revenues at 36% in 2024, projected to expand to 45% by 2028. McKinsey’s 2025 Merchant Acquiring Survey reports 90% of US SMEs now use an ISV as their primary POS or payments solution — up from ~50% in 2022. The structural shift is well underway, not theoretical.
PFaaS is the fastest-growing operating model — and Rainforest data confirms it
The PFaaS market was valued at $6.9B in 2024 and is projected to reach over $35B by 2033 — approximately 18% compound annual growth, roughly 3x the overall payments industry growth rate. PFaaS is taking share from both the referral/ISO model below it and the full PayFac model above it. Rainforest 2026 confirms the operational reality: 82% of vertical SaaS platforms in the sample operate as Managed PayFac / PFaaS; only 10% are Registered PayFacs; the remaining ~8% are on referral or other models. Mastercard’s February 2025 PayFac-as-a-Service white paper (with Cardstream) characterized PFaaS as “not just a trend but a fundamental shift in how payments are being distributed.” The Rainforest survey data is the first independent empirical confirmation of that characterization.
Full PayFac registrations remain in mild contraction
North American ISV/SaaS PayFac registrations contracted from 47% to 43% of all registered PayFacs between March 2023 and early 2024. Approximately 6% annual attrition reflects platforms that registered and subsequently exited after operational burden exceeded economic benefit. The 2024 data has not been refreshed publicly through 2026, and while we hear about mild resurgence in PayFac registrations, the directional narrative — that platforms above $100M GMV are increasingly opting against registration — remains consistent in operator interviews and conference panels through Q2 2026.
Take rates are RISING, not falling
Rainforest 2026 documents a finding that overturns conventional wisdom: 60% of vertical SaaS platforms reported take-rate INCREASES over the last two years. 1% reported a decrease. 39% reported no change. The “race to the bottom” narrative in vertical SaaS embedded payments is empirically wrong. Toast, Shopify, and Square have all publicly raised back-book or front-book pricing in 2025–2026; the UBS Q6.0 SMB survey (September 2025) found ~50% of merchants expect pricing increases over the next 12 months. The pricing-power story in embedded payments is consistent with the broader software-pricing dynamic of 2024–2026.
Valuation premium concentrates on platforms, not vendors
SaaS platforms with embedded finance offerings trade at a 23% revenue-multiple premium and a 19% EBITDA-multiple premium versus peers without (William Blair, September 2025). Vertical SaaS category leaders trade at 8–12x revenue with outliers reaching 14x against a 6.7x public median, with embedded fintech contributing a 25–45% valuation lift (Windsor Drake Q1 2026). The investor implication is operationally significant: the model-selection decision is not a back-office vendor question. It is a top-of-house strategic decision that materially affects the multiple the market will pay for the entire business.
The decision framework
Five questions structure the decision. Answer them honestly; the answers shape everything else. Charge Forward’s Payment Model Fit Navigator walks through these systematically and produces a stage recommendation. The questions matter more than the tool.
1. What is your current and projected annual GMV?
The $50M threshold is the primary decision trigger. Below $10M: PSP Referral. $10–50M: Light PFaaS or build toward the $50M inflection. Above $50M: Full PFaaS becomes financially compelling. Above $250M: evaluate Managed PayFac + Orchestration. Above $1B: Full PayFac is possible but not required. Build your forecast from actual customer transaction data, not TAM.
2. How much engineering capacity can you realistically commit?
Full PFaaS requires one to two engineers for three to six months — sustainable for almost any funded platform. Managed PayFac requires three to five engineers for nine months or more. Full PayFac requires a dedicated engineering organization. If engineering is constrained, start one stage lower than your GMV alone would suggest, and plan the next transition.
3. How important is branded merchant experience to your product?
PFaaS, Managed PayFac, and Full PayFac all deliver fully branded experiences. Referral does not. If your product is a premium brand or operates in a trust-sensitive vertical (healthcare, legal, professional services), branded payments are not a nice-to-have. They are a product-quality requirement.
4. Is payments strategic or supplementary to your business?
If payments is supplementary — offered as a convenience but not core to your value proposition — Light PFaaS may be the appropriate permanent state. If payments is strategic — a meaningful revenue line, a retention driver, a data source for adjacent products — you should be planning for Stage 3 or Stage 4 and investing accordingly. The honest answer to this question is the most important one in the framework. Many platforms answer “strategic” because it sounds more ambitious, then under-invest.
5. What is your three- to five-year payments trajectory?
Plan for graduation, not just today. The platforms that maximize embedded payments revenue treat their current model as a stage, not a destination. Even if you are at Stage 2 today, your vendor contract, data architecture, and API integrations should be chosen with Stage 3 in mind. Vendor lock-in is real; the cost of re-integration when you graduate is consistently underestimated.
A self-assessment version of these questions runs in the Charge Forward Embedded Payments Fit Assessment.
The graduation path
Most successful vertical SaaS platforms follow a predictable progression. The triggers below are derived from public-company disclosures, vendor data, and Charge Forward advisory engagements. Most platforms stop at Stage 3 or Stage 4. Full PayFac is not the inevitable destination — it is an optional endpoint for a minority of platforms that have made a deliberate strategic decision to build a payments business.
Stage 1 → Stage 2
Triggers: GMV crosses $10–15M; referral revenue reaches $30–75K/year; customers request in-app payment experience; competitor launches native payments. Move when the first two triggers are present together.
Stage 2 → Stage 3
Triggers: GMV approaches $50M; the 4–5x revenue improvement of full PFaaS becomes financially compelling; customers request more deeply embedded workflows; you have engineering capacity for a 3–6 month build. The $50M threshold is the cleanest trigger; do not delay materially past it.
Stage 3 → Stage 4
Triggers: GMV exceeds $250M; vendor fees become material; you need direct buy-rate negotiation; payment revenue rivals subscription revenue. Approximately 90% of platforms remain at Stage 3 permanently — this is a valid terminal state.
Stage 4 → Stage 5 (Optional)
Triggers: GMV exceeds $1B; PFaaS fee (10–20 bps) is material at volume; the platform’s product model requires money-transmission licensing or extended fund-holding (per the three Rainforest conditions). Many platforms above $1B GMV stay at Stage 4 indefinitely. Stage 4 is the optimal state for most platforms above $250M.
Common mistakes
Five patterns recur in advisory work. Each is costly to unwind, which is the whole reason to flag them up front.
Mistake 1: Jumping to Full PayFac too early
The “everyone should be a PayFac” era is over. Rainforest 2026 confirms only 10% of vertical SaaS platforms are full Registered PayFacs. Full PayFac registrations are in mild contraction; annual attrition is approximately 6%. Platforms that register before they have the team, the compliance infrastructure, and the GMV to justify it consistently regret the decision. The operational burden — fraud exposure, MTL maintenance, PCI Level 1, underwriting staffing — is not proportional to the revenue improvement over a well-executed Stage 4 arrangement at most scales.
Mistake 2: Staying on referral past $50M GMV
A platform at $75M GMV on a referral model earns approximately $150K/year in payment revenue. On Full PFaaS, that same volume would generate $450–675K/year — a difference of $300–525K annually. Over three years, staying on referral past the $50M threshold costs $900K–$1.5M in foregone revenue. Payback period on a Full PFaaS integration is typically 18–24 months. The math is not subtle. The blocker is almost always organizational inertia, not economics.
Mistake 3: Failing to negotiate at $100M+ GMV
Once your GMV exceeds $100M, you have meaningful leverage with PFaaS vendors. Platforms that don’t recognize this — and continue accepting standard PFaaS terms — leave 10–20 bps on the table. At $250M GMV, 15 bps is $375K/year. Learn the distinction between PFaaS and Managed PayFac, understand your leverage, and negotiate accordingly.
Mistake 4: Ignoring orchestration and optimization at $250M+ GMV
Single-provider risk is real. Authorization-rate optimization at scale is real. Platforms above $250M GMV that process through a single provider are leaving authorization-rate improvements on the table (typically 1–3 percentage points), creating concentration risk, and missing the opportunity to negotiate leverage across multiple providers. Multi-provider routing should be on your roadmap by $250M.
Mistake 5: Choosing on headline take rate alone
The five-year operational cost of a model includes team size, compliance overhead, legal costs, and the opportunity cost of engineering time. A model that looks superior on headline take rate may have a higher total cost of ownership when these factors are included. Always model the full P&L, not just the revenue side. Charge Forward’s Payments Revenue Calculator handles this calculation; running it on your specific volume and vertical surfaces the distortion if there is one.
Charge Forward Insight
The most expensive mistake is not on the list above. It is treating model selection as a one-time decision rather than a sequenced trajectory. Platforms that win at embedded payments think about Stage 3 architecture decisions while operating at Stage 2 — vendor contracts that allow buy-rate renegotiation, data pipelines that capture interchange-level granularity, team plans that pre-load Payments Manager hires before GMV demands them. Re-architecting between stages is where most of the cost lives. The platforms that minimize re-architecting read the framework forward, not just for their current state.
What’s Next
Chapter 3 — “The PFaaS & Vendor Deep Dive” — provides detailed vendor comparison your team needs once the model decision is made. We cover Stripe Connect, Adyen for Platforms, Worldpay/Payrix Pro, Stax Connect, Finix, Rainforest, Tilled, Payabli, Forward, and Infinicept. The chapter is anchored on the Charge Forward Vendor Database — the live tool we use with advisory clients to score vendors against platform-specific requirements.
SOURCES & REFERENCES
UBS Global Research, Tim Chiodo: “The Question 6.0” (May 4, 2026 — canonical; replaces Q5.0); “Vertical SaaS & Embedded Finance: Takeaways from Vertex hosted by Rainforest” (April 15, 2026); “Toast: FinTech Net Take Rate Analysis & Core Payments Framework” (December 17, 2025); UBS Evidence Lab SMB Payments Survey (September 2025, N=200 US SMBs).
Rainforest, “2026 Vertical SaaS Embedded Payments Benchmarking Study” (Q1 2026 fielded; May 2026 release).
McKinsey & Company, “Global Payments in 2024” (October 2024); “Decoding ISV Maturity: A Global Playbook for Payments Growth” (January 8, 2026, N=1,500+ US SMEs).
Mastercard / Cardstream, “PayFac-as-a-Service: A Fundamental Shift in How Payments Are Distributed” (February 2025).
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); BCG / Adyen, “Moving Embedded Finance from Promise to Practice” (September 2025).
Public partner-program documentation: Stripe Connect, Square, Paysafe, PayPal, NMI, WePay/Chase, Adyen for Platforms, Rainforest, Tilled, Finix, Payabli, Worldpay for Platforms (Payrix), Forward, Infinicept Launchpay.
Public Charge Forward tools referenced in this chapter: Embedded Payments Maturity Framework, Payment Model Fit Navigator, Embedded Payments Fit Assessment, Payments Revenue Calculator, Vendor Database. All available at chargeforward.io/tools.
By Jane Podbelskaya · Updated