The idea of becoming a payment facilitator is appealing. More control over how merchants get onboarded. A bigger share of the economics. A seamless, white-labeled experience that makes payments feel like a native part of the product. For some ISVs, becoming a PayFac is the right move.
For others, it’s not. At least not yet.
The question worth asking is not “should we become a PayFac?” It is “do we have what it takes to run one?” Those are different questions, and conflating them is where many software vendors get into trouble.
This guide breaks down what becoming a PayFac actually requires, the signals that suggest an ISV is ready, and the path that makes more sense for software companies that want the benefits without the burden.
What Does It Mean to Become a PayFac?
A payment facilitator is a company that has been formally approved by the card networks, primarily Visa and Mastercard, to process payments on behalf of its own customers, called sub-merchants. When a software vendor becomes a registered PayFac, it takes on legal and financial responsibility for every merchant that processes through its platform.
That shift is significant. It means the ISV is no longer just a software company that offers payments. It is, in part, a payments company. The card networks hold it accountable the way they would hold a processor accountable. If a sub-merchant commits fraud, racks up chargebacks, or goes out of business mid-transaction, the PayFac is the one absorbing the exposure.
The upside is real: more control, better unit economics at scale, and a merchant experience that the software vendor owns end to end. The trade-off is that the infrastructure required to run a responsible PayFac operation is not trivial.
What Are the Real Costs of Becoming a Registered PayFac?
The costs that most software vendors underestimate typically fall into four categories.
Card Network Registration
Becoming a registered PayFac requires a formal application and approval from Visa and Mastercard. There are registration fees involved, and the process requires demonstrating that the organization has the operational controls to manage sub-merchant risk.
Merchant Underwriting Infrastructure
As a PayFac, the ISV is responsible for evaluating every merchant that wants to process payments through its platform. That means building or procuring an underwriting process, making approval decisions based on business type and risk profile, and monitoring those merchants on an ongoing basis. This typically requires dedicated staff, third-party tooling, or both.
Financial Reserves
PayFacs are generally required to maintain reserve funds to cover potential chargeback losses from their sub-merchant portfolio. The exact requirements vary by acquirer relationship and risk profile.
Compliance and Ongoing Monitoring
PCI compliance, KYC (Know Your Customer) and KYB (Know Your Business) verification for every merchant, AML monitoring, and ongoing adherence to card network rules all become the ISV’s responsibility. These obligations can compound over time as the merchant portfolio grows.
Becoming a PayFac is an organizational decision, not just a product one. The infrastructure required to do it responsibly is a long-term operational commitment.
What Are the Signs an ISV Is Ready to Become a PayFac?
For the right organization at the right stage, becoming a PayFac makes more strategic and financial sense. The indicators below suggest a company could be ready to take that step.
Processing volume has reached a scale where the fixed infrastructure costs justify themselves. The economics of becoming a PayFac improve significantly as volume grows, because the compliance and operational costs are largely fixed. For early-to-mid stage integrated software vendors, that crossover point often has not arrived yet.
The company has dedicated payments operations capacity. Running a PayFac operation requires people who understand underwriting, risk management, and regulatory compliance. ISVs that do not have this capability in-house, and are not prepared to build it, will find the ongoing requirements overwhelming.
Merchant experience control is a genuine competitive differentiator. If the ISV is in a vertical where owning every touchpoint of the merchant onboarding and payments experience creates meaningful competitive separation, the investment may be worthwhile.
Leadership has modeled the total cost of ownership. Not just the revenue upside, but the full picture: registration, reserves, compliance staffing, and ongoing operational overhead. Software vendors that have done this analysis with clear eyes and the numbers still work are in a different position than those who have only modeled the upside.
What Are the Signs the Timing Is Not Right Yet?
For ISVs that do not yet meet the readiness criteria above, the honest answer is that the full PayFac path is likely to create more friction than value.
Common signs the timing is premature:
- Processing volume is still early-stage, and the math does not clear the infrastructure cost.
- The compliance and risk management burden would fall on the core product team, pulling focus away from building the software.
- The ISV has not yet fully optimized revenue in the current embedded model.
- Leadership has modeled the upside but not the operational overhead.
None of this means the PayFac path is permanently off the table. It means the sequencing matters. An ISV that pushes toward PayFac registration before the operational foundation is in place is likely to find the experience expensive and distracting.
Is There a Path That Delivers the Benefits Without the Complexity?
This is where most ISVs find the real answer. The PayFac model is appealing because of what it produces: better payment margins, a seamless merchant onboarding experience, and more control over the economics. But those outcomes are not exclusive to software vendors that become registered PayFacs.
The right embedded payments partner can deliver the same results, including revenue share, a white-labeled merchant experience, and fast onboarding, without requiring the ISV to take on the liability structure, compliance burden, or operational overhead of PayFac registration. The distinction is who holds the risk and who manages the infrastructure. For most integrated software vendors, outsourcing that complexity to a specialized partner while retaining the revenue and experience benefits is the more rational path.
Celero Fusion is built specifically for this. Integrated software vendors that partner with Fusion get access to a full embedded payments model, including revenue share and a purpose-built merchant onboarding process, without becoming a payments company themselves. Fusion handles the PayFac complexity while the ISV stays focused on building its product and growing its merchant base.
Frequently Asked Questions
What is a PayFac and why do ISVs consider becoming one?
A payment facilitator (PayFac) is a company approved by the card networks to process payments on behalf of sub-merchants. Software vendors consider becoming a PayFac because it offers more control over the merchant experience and better payment economics at scale. However, it also requires taking on significant compliance obligations, liability exposure, and operational infrastructure.
What processing volume do ISVs typically need before becoming a PayFac makes sense?
The economics of becoming a registered PayFac improve as processing volume increases, because a larger base spreads the fixed compliance and operational costs. There is no universal threshold that applies to every ISV. The right answer depends on the specific business model, vertical, risk profile, and how much operational infrastructure the company is prepared to build and maintain. For most ISVs, the more useful exercise is modeling the full cost of PayFac registration against current and projected volume, rather than anchoring to a number that may not reflect their actual situation.
What is the difference between becoming a PayFac and using an embedded payments partner?
As a registered PayFac, the ISV takes on direct liability for its sub-merchants and is responsible for underwriting, compliance, reserves, and ongoing risk management. With an embedded payments partner, the processor handles that infrastructure while the software vendor earns revenue share and retains a branded, integrated merchant experience. For most ISVs, the embedded partner model delivers comparable economic benefits with significantly less operational complexity.
Can an ISV access PayFac-level economics without becoming a registered PayFac?
Yes. The right embedded payments partner offers revenue share structures that give integrated software vendors meaningful payment income without requiring PayFac registration. The ISV earns on every transaction its merchants process, retains a seamless merchant experience, and avoids the compliance and liability overhead of operating as a registered PayFac.
The Bottom Line
Becoming a PayFac is a real path, and for the right ISV, it can be the right one. It works best for companies with significant processing volume, dedicated payments and compliance capacity, and a clear strategic reason to own the entire merchant experience end to end.
For most software vendors, that point has not arrived yet. The more practical path is partnering with an embedded payments provider that delivers the same outcomes, revenue share, a branded merchant experience, and fast onboarding, without the liability, compliance burden, and operational lift of running a PayFac independently.
Celero Fusion is built for that path. ISVs get the economics and control they are looking for, backed by a team that handles the underwriting, compliance, and risk management so the ISV does not have to become a payments company to offer payments.
Both paths can get an integrated software vendor to a working payments feature. The question is what it costs to get there, and what it takes to maintain it once it is live.
Ready to find out what makes sense for your platform? Contact the Fusion team to start the conversation.