When SaaS Should Rent Payments
Diving deeper into
Jareau Wadé, Chief Growth Officer at Finix, on building payments infrastructure for SaaS companies
There are many cases where you are going to be interested in the convenience, scalability, and flexibility of working with someone else's infrastructure.
Analyzed 3 sources
Reviewing context
The real threshold is not payment volume, it is whether a software company wants to own payments operations or rent them. Even large platforms often keep paying a markup because outsourced infrastructure lets them launch faster, avoid building underwriting, reconciliation, and dispute tooling themselves, and move between lighter and heavier payments models without migrating merchants or card tokens.
-
For a platform, payments are much harder than for a single merchant. One refund or chargeback can ripple across thousands of sub merchants, so Finix is selling the back office machinery, APIs, reporting, payouts, and compliance relief, not just card processing.
-
Vertical SaaS companies use this to delay becoming a full payment facilitator until it is strategically worth it. The old rule of thumb was around $50M to $100M in volume, but practice showed that speed and flexibility often matter more than squeezing every basis point.
-
This is why payments became such a large revenue lever for vertical software. ServiceTitan and Toast show the pattern, software wins the merchant relationship first, then layers in payments to raise take rate, bundle workflows, and increase retention.
The market is moving toward modular ownership. More software platforms will start on rented infrastructure, then selectively take on more economics and control as they scale, which favors providers that let customers switch models without rebuilding the whole payments stack.