SaaS Payments Built on Legacy Rails
Jareau Wadé, Chief Growth Officer at Finix, on building payments infrastructure for SaaS companies
The key point is that most fintech products are distribution and software layers, not rebuilt financial rails. A company like Finix can give a SaaS platform APIs for onboarding, payouts, reconciliation, and support workflows, but the actual regulated plumbing still runs through sponsor banks, processors, and card network memberships that were built years earlier. That is why the fastest way to launch fintech is usually to wrap modern software around old infrastructure, not replace it.
-
In payments, the hidden stack is concrete. The software company owns the merchant relationship and embeds checkout and reporting in its product, while firms like Fiserv, Worldpay, and sponsor banks such as Wells Fargo or Fifth Third handle network access, settlement, and sponsorship behind the scenes.
-
This pattern shows up well beyond acquiring. Banking-as-a-service providers, card issuers, and embedded finance platforms usually combine bank partners, ledger vendors, processors, and compliance layers, then expose that bundle through one API. The customer sees one app, but several legacy systems are doing the actual money movement.
-
The business implication is that control moves upward over time. Platforms like Clubessential and Lightspeed use infrastructure providers to start quickly, then pull more payments operations into their own product as volume grows, because owning the workflow improves support, raises take rate, and makes software stickier.
The market is heading toward more unbundling at the infrastructure layer and more bundling at the product layer. More software companies will look like fintech companies to users, while underneath they will still rely on specialized banks, processors, and compliance partners. The winners will be the platforms that own the customer workflow and the infrastructure providers that make that control easy to adopt step by step.