Should our SaaS become a payment facilitator?

For most SaaS platforms, no. Full payment facilitator registration only starts to make economic sense above roughly $1B in sustained annual GMV — and even then it is genuinely required only when fund flows demand it: state money transmitter licenses, legacy systems that already require registration, or holding funds for more than 30 days. Registration typically costs $750K–$1.5M to set up plus $500K–$700K per year to operate. The Rainforest 2026 benchmarking study found only about 10% of vertical SaaS platforms are registered PayFacs, while 82% use PayFac-as-a-service or managed PayFac models.

Reviewed by Jane Podbelskaya · last reviewed 2026-07-28 · how we produce answers

The short answer

For most SaaS platforms, no. Full payment facilitator registration is an optional terminal state, not the natural endpoint of an embedded payments program. As of 2026, it only starts to make economic sense above roughly $1B in sustained annual GMV — the tier where registered PayFacs earn observed net take rates of 100–120+ bps — and even at that scale, most platforms consciously choose not to register.

This answer is about the yes/no registration decision itself. If you are weighing full registration against PayFac-as-a-service as operating models, see the companion answer: PayFac vs PayFac-as-a-service: which should a software company choose?

What full registration costs

Becoming a registered PayFac means registering directly with Visa and Mastercard, obtaining money transmitter licenses (MTLs) across required US states (cumulatively about $450K over three years), implementing PCI DSS Level 1 compliance ($200K+ per year), and operating as merchant of record for every sub-merchant. In effect, you are building a payments company inside your SaaS business.

The three cases where registration is genuinely required

The Payment Models chapter narrows the cases where full registration is genuinely required to three:

1. Your fund flows require money transmission licensing in specific states — for example, holding customer funds in escrow for extended periods (common in property management and legal-adjacent software), multi-party settlement structures (marketplaces), or certain payroll-adjacent flows (HR and workforce platforms).
2. Your legacy systems already require PayFac registration — typically the result of an earlier strategic decision that cannot be cleanly unwound.
3. You must hold money for more than 30 days as part of your core business model.

Outside these three circumstances, a managed PayFac arrangement with orchestration delivers equivalent end-state economics at materially lower overhead. The question “should we register?” often reduces to “does our product model require us to hold money long enough to require it?” For most SaaS platforms, the answer is no.

What the market is doing

The directional data points one way. Registered PayFacs’ share of North American ISV/SaaS programs contracted from 47% to 43% between March 2023 and early 2024, with roughly 6% annual attrition — platforms that registered and subsequently exited after the operational burden exceeded the economic benefit. The Rainforest 2026 benchmarking study, the first independent industry survey, found only about 10% of vertical SaaS platforms operate as registered PayFacs, while 82% use PayFac-as-a-service or managed PayFac models.

When becoming a PayFac is worth it

Registration is the right call for a minority of platforms — and for them it is genuinely the right call. If your GMV is measured in billions, your fund flows fall into one of the three cases above, and you have made a deliberate strategic decision to build a payments business — with the 8–20+ FTE organization, compliance program, and risk infrastructure that implies — full registration captures the most gross margin available on the spectrum, at 100–120+ bps net take rates. The point is not that registration is always wrong; it is that the burden of proof sits with the registration case.

How to decide

Start from your fund flows, not your ambitions: if they don’t require MTLs or 30+ day holds, model the managed alternatives first. The Payments Model Navigator walks through the decision systematically, and the Embedded Finance Self-Assessment locates your platform on the maturity spectrum. For the full five-stage framework behind this answer, read the Payment Models chapter of the guide, and compare providers across the managed tiers in the payments vendor directory.

FAQ

Sources

• Charge Forward, Definitive Guide to Embedded Payments — Payment Models chapter (2026)
• Rainforest, 2026 Vertical SaaS Embedded Payments Benchmarking Study (Q1 2026 fielding) (2026)
• Visa registered-PayFac program data (North American ISV/SaaS share, March 2023–early 2024) (2024)