SaaS Platforms Moving Upstack to PayFac
Jareau Wadé, Chief Growth Officer at Finix, on building payments infrastructure for SaaS companies
The jump from referral payments to PayFac models changes who owns the merchant relationship. In model one, the software company sends the merchant to a separate processor for signup, support, disputes, and settlement questions. In model two or three, the software company can keep onboarding, reporting, support, and payouts inside its own product, which makes payments feel built into the software instead of bolted on.
-
The practical change is visible in support workflows. Finix described Clubessential moving from a setup where clubs had to deal with a separate processor, to a PayFac setup where Clubessential could answer decline, dispute, and settlement questions itself because software and payments were delivered together.
-
That control also changes the economics. Finix framed the move up the stack as a way for software platforms to own more of payments margin, and pointed to platforms like Lightspeed using embedded payments to increase take rate and make payments a much larger share of total revenue.
-
The reason infrastructure providers like Finix matter is that becoming a PayFac adds underwriting, compliance, sub-merchant management, and payout operations. Finix built its product around handling those jobs through APIs and dashboards, so a SaaS company can act more like a mini processor without building the whole stack from scratch.
The market keeps moving toward software platforms owning payments because it improves both user experience and margin. As more vertical SaaS companies bundle onboarding, checkout, payouts, and support into one interface, payments will look less like a separate vendor choice and more like a built in product feature that deepens retention and expands revenue per customer.