Most of the advice about embedded payments starts one step too late. It assumes you have already decided to monetize payments and just need to pick a provider or a model. The more useful question, and the one almost nobody with authority answers, comes before that: should your platform be doing this at all yet, and if so, where do you start.
A vertical SaaS platform is ready to monetize payments when three things are true: meaningful payment volume already flows through or alongside the product, merchants pay through your software rather than a separate system and you are willing to own at least the merchant experience. If those hold, the first move is almost always a referral or a managed model, not becoming a registered payment facilitator. If they do not, waiting is the right call, not a timid one.
Should your platform monetize payments at all?
Most vertical SaaS platforms sit on payment volume they are barely monetizing, so the instinct is to assume the answer is always yes. It is not. Monetizing payments well is a business line, not a feature, and it only pays off when the platform is actually ready for it. Three readiness signals matter more than anything else:
- Volume. Real money is flowing through the platform, not a trickle. Payments economics are a small percentage of volume, so you need enough volume for that percentage to matter.
- Merchant behavior. Your merchants already run payments through or alongside your product. If they use a completely separate processor and never touch payments inside your software, you have a distribution problem before you have a monetization one.
- Willingness to own it. Capturing more economics means owning more of the experience, and eventually some operational weight. If nobody on the team will own payments as a real line of the business, the economics will underperform no matter which model you pick.
Monetizing payments is a business line, not a feature. It only pays off when the platform is actually ready to run it as one.
How much payment volume do you need before it is worth it?
The honest answer is that it depends on the model, but there are rough floors. To make a referral or managed model worth the effort, you generally want to be in the tens of millions of dollars of annual payment volume or clearly heading there. Becoming your own registered payment facilitator is a different universe: that only starts to pay for its cost and burden at roughly two hundred million dollars a year or more, which is why almost no platform should start there. Below the floor, the effort of monetizing outweighs the return, and your energy is better spent growing the platform.
Which model should you start with?
Almost every platform that monetizes payments starts by owning less and grows into owning more. The realistic progression:
- Referral. You refer merchants to a processor and earn a residual. Lowest commitment, thinnest economics, someone else owns the risk. The right first move for most.
- Managed PayFac / PayFac-as-a-service. You own the experience, the pricing and most of the economics on a provider's registration, without carrying a full payfac build. This is where most serious platforms land.
- Full, registered PayFac. Rare. Even the largest platforms usually run on a provider's infrastructure rather than registering themselves. It only makes sense at high volume with real appetite for the operational load.
The ISV-vs-PayFac decision and how platforms actually make money from payments go deeper on each model. The mistake is skipping straight to "become a payfac" because it sounds like the ambitious move.
How do ISVs choose between a referral model and owning the economics?
It comes down to four factors, in order: your volume (is there enough for a bigger cut to matter), your operational readiness (will you carry underwriting, risk and support), how much control you want over the merchant experience, and the migration cost of changing models later, which almost everyone underprices. A platform with real volume and the will to own the experience should move up the models. A platform without either should stay on referral and not feel bad about it. If you are weighing a specific provider once you know the model, how to choose a provider covers that next step.
When is it NOT the right time?
This is the part vendors will never tell you, because every vendor's answer is "now, with us." It is genuinely not the right time when your volume is still thin, when nobody will own payments operationally or when your core product is not yet sticky enough that merchants would stay for the payments experience. Monetizing payments on a shaky product just adds a revenue line to a base that is still churning. Fix the base first, then come back to this.
What is the first step if you are ready?
If the readiness signals are there, the first step is not to pick a provider. It is to model what payments monetization is actually worth on your specific volume and merchant mix across the models, so the decision rests on your numbers rather than a vendor's pitch. That is the difference between bolting payments on as a feature and running it as a business line. If you want to work that math against your real numbers before you commit a roadmap to it, that is exactly the conversation worth having first.