Every vertical SaaS platform eventually has to decide how it runs payments, and the decision almost always gets framed as build versus buy versus partner. It is a useful frame because it forces the real tradeoff into the open: how much of the payment economics you want to capture, against how much of the operation you are willing to own to capture it. More of one means more of the other. There is no path that gives you full economics and zero responsibility.
This is the orientation map. It lays out the three paths, what each earns, what each costs you to run, and how to think about which one fits your platform right now. It is deliberately the high-altitude version. Each path has a deeper piece underneath it, linked as we go, for when you have narrowed to one.
The three paths, mapped to the real models
Build, buy and partner are a clean way to say three things the payments industry names less clearly. Here is the mapping, so the frame connects to the actual models you will hear from processors.
Partner: the ISV referral model.
You refer your merchants to a processor and earn a residual on the volume they process. The processor signs the merchant, underwrites, owns the relationship and runs the operation. You capture roughly 5 to 15 basis points of volume. Lowest economics, lowest burden, fastest to stand up. This is where almost every platform starts, and for many it is the right place to stay.
Buy: PayFac-as-a-Service, also called managed PayFac.
You run your own payment facilitator program, but on a provider's infrastructure. They own PCI scope, the sponsor-bank relationship and the underwriting rails. You own pricing, merchant experience and a much larger share of the spread, roughly 30 to 60 basis points, without building the program from scratch. This is the sweet spot for most vertical SaaS platforms above a real volume threshold.
Build: the full, registered payment facilitator.
You become your own PayFac: register with the card networks, secure a sponsor bank, stand up underwriting, compliance, risk and settlement, and run the whole program. You capture 80 to 120 basis points or more, and you take on a compliance and risk operation that needs real headcount and capital. A small number of very high-volume platforms belong here. Most that think they do are better served buying.
The same four-model language shows up across our other pieces, with the ISV referral path sometimes split into a basic referral and an enhanced-residual variant. The build, buy, partner frame collapses that into the decision that actually matters: who owns the program.
The tradeoff in one line
Every step toward more economics is a step toward more operational responsibility. The right path is the furthest one your platform can actually staff and stomach, not the one with the biggest take rate on the slide.
The single most common mistake is reading the basis-point numbers as the whole story. The 80 to 120 of a full PayFac looks like eight times the 5 to 15 of a referral, and on a spreadsheet at today's volume it can be. But the higher number carries underwriting losses, PCI program cost, support load, capital tied up in reserves and a team you have to hire. The number that matters is what you net after the full cost of running the program, which is why the honest comparison is always net margin at your real volume, not the rate anyone quotes you. For the full picture of how those economics work, see how SaaS companies make money from payments, and to put rough numbers against your own volume, the Margin Multiplier sizes it in two minutes.
How to choose for your stage
The right path is a function of four things: processed volume, vertical, operational appetite and where you are in your lifecycle. They tend to point the same direction.
Lower volume and a light operational appetite point to partnering. The economics of building or buying do not clear the cost of the operation until you have enough volume to spread it over, and below that line the referral model keeps you out of a program you are not ready to run. Meaningful and growing volume, plus a willingness to own the merchant experience, point to buying a managed PayFac program, which is where most platforms maximize net margin without taking on a risk operation. Very large volume, a specific product or risk need a provider cannot serve, and a genuine appetite to run compliance and risk in-house point to building.
The deeper decision between the entry path and the managed path is the one most platforms actually wrestle with, and it has its own piece: PayFac vs ISV for vertical SaaS walks through the comparison with the volume thresholds and the migration math. If you are weighing the full build, should you become a payment facilitator is the honest version of that question. And once you have settled on buying, PFaaS provider strengths and weaknesses is how you read the providers without getting sold.
It is a path, not a one-time pick
The last thing to hold onto is that this is rarely a permanent choice. Partnering, buying and building are stages on a path far more often than they are a fork you take once. The common arc is to start by partnering, move to a managed program as volume justifies the better economics, and in a few cases eventually build. The mistake is treating the first decision as final and never re-running it. The model that was correct at 50 merchants is often wrong at 500, and the gap between the model you are on and the model you should be on is exactly where six figures of annual margin quietly goes missing.
So which path is right for you? The honest answer is that it depends, on your volume, your vertical, your merchant mix and what your team can actually run. The frame is the same one any platform can use. Which path you can staff and stomach today, and when you should move to the next one, is the part that only resolves against your real numbers. If you are making this decision right now, that is the conversation worth having before you commit. Reach out and we will work through yours.