PayFac vs PayFac-as-a-service: which should a software company choose?
Most software companies should choose PayFac-as-a-service, not full payment facilitator registration. PayFac-as-a-service captures the large majority of the payments economics and control while a provider carries the compliance, underwriting, and risk load. As of 2026, full PayFac registration only starts to pay off at roughly $1B+ in sustained annual GMV — and even then only when fund flows genuinely require it — because running a registered PayFac program typically costs $750K–$1.5M to set up and $500K–$700K per year to operate.
Reviewed by Jane Podbelskaya · last reviewed 2026-07-24 · how we produce answers
The default answer
For the large majority of software platforms, PayFac-as-a-service (PFaaS) is the right model. It captures most of the payments margin and the branded experience of being a payment facilitator, without you having to register with the card networks or build a compliance and risk organization.
Full PayFac registration is a real option — but it is a scale decision, not a starting point.
What each model keeps and costs
| Model | You keep | You own | Best when |
|---|---|---|---|
| Referral | Least economics | Almost nothing | Validating demand; earliest stage |
| PayFac-as-a-service | Most economics | Experience & some ops | Scaling platforms that want margin + control without the burden |
| Full PayFac | Most gross margin | Compliance, underwriting, risk, sponsor bank | High, sustained volume that justifies the cost and risk |
Where full PayFac starts to pay off — and what it costs
As of 2026, full registration is an option worth modelling at roughly $1B+ in sustained annual GMV — the tier where registered PayFacs earn observed net take rates of 100–120+ bps. Even at that scale it is genuinely required only when fund flows demand it: when you need money transmitter licenses, when legacy systems already require registration, or when you must hold funds for 30+ days.
The cost side is what most platforms underestimate. Running a registered PayFac program means network registration with Visa and Mastercard, money transmitter licenses across required US states (cumulatively about $450K over three years), PCI DSS Level 1 compliance ($200K+ per year), and operating as merchant of record for every sub-merchant. All-in, that typically comes to $750K–$1.5M in setup costs plus $500K–$700K per year ongoing — before counting the risk, underwriting, and compliance headcount to run it.
The market has voted accordingly: 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, and the Rainforest 2026 benchmarking study found only about 10% of vertical SaaS platforms operate as registered PayFacs while 82% use PFaaS or managed PayFac models.
When full PayFac is not worth it
Below roughly $1B in annual GMV, the operational burden is not proportional to the revenue improvement over a well-executed managed PayFac arrangement — a meaningful share of the platforms that registered anyway later exited after the burden exceeded the benefit. If your fund flows don’t require registration, the burden of proof sits with the registration case, not against it.
How to decide
Two questions settle most cases: how much volume do you have (and will you sustain)? and how much operational and regulatory burden do you want to own? If volume is high and you can staff risk and compliance, model full PayFac. Otherwise PFaaS almost always wins on risk-adjusted return.
Compare specific providers in the vendor directory, see the economics on the embedded payments hub, and read how we stay neutral in our methodology.
FAQ
What is the difference in one sentence?
A full PayFac registers with card networks and owns compliance, underwriting, and risk; PayFac-as-a-service gives you most of the economics and merchant experience while a provider owns that burden for you.
When does full PayFac make sense?
At roughly $1B+ in sustained annual GMV, and typically only when fund flows require money transmitter licenses or holding funds for 30+ days. Below that, the incremental margin rarely outweighs the cost of compliance staff, risk operations, sponsor-bank relationships, and ongoing audits.
Where does the referral model fit?
Referral is the lightest option and the fastest to launch, but keeps the least economics. It suits early platforms validating demand before investing in deeper integration.
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)