Payment Facilitation as a Service, also called Managed PayFac, PayFac Lite, or Embedded PayFac, has become one of the fastest-growing models in embedded payments. The premise is simple: you get most of the economic benefits of being a Payment Facilitator without building the compliance and operational infrastructure yourself.
The model exists because there's a wide gap between the economics of ISV Referral (5-25 basis points) and the cost of becoming a full registered PayFac ($500K+ implementation, 12-18 months to launch, dedicated compliance staff). Most platforms fit somewhere in the middle, they've outgrown referral economics but can't justify the investment of full facilitation. PayFac-as-a-Service fills that gap.
How It Works
In a PayFac-as-a-Service arrangement, a registered Payment Facilitator, providers like Stripe Connect, Finix, Tilled, or Payrix, provides the infrastructure: sponsor bank relationships, card network registrations, compliance frameworks, settlement systems. You operate as a sub-facilitator or managed partner under their umbrella. Adyen for Platforms offers a similar outcome through a different architecture, combining processing and facilitation under one roof.
You handle merchant-facing operations: onboarding, pricing, first-line support, and in some cases, underwriting decisions within pre-approved parameters. The PFaaS provider handles the regulatory layer: network reporting, reserve calculations, compliance monitoring, and the relationship with the acquiring bank.
Merchants are boarded as your sub-merchants. You set the rate. You collect the spread between what you charge and what you pay the provider. The provider earns their margin from the processing cost you pay them, typically interchange plus 10 to 20 basis points, depending on volume and risk profile. Stripe Connect charges differently (a per-transaction platform fee of 0.25% + $0.25 on top of standard processing), while Finix and Tilled price on an interchange-plus model that can be more economical at scale.
The Economics
PFaaS economics sit between ISV Referral and full PayFac:
| Model | Net Take Rate | On $50M Volume |
|---|---|---|
| ISV Referral | 5-25 bps | $25K-$125K/yr |
| PayFac-as-a-Service | 25-70 bps | $125K-$350K/yr |
| Full PayFac | 50-100+ bps | $250K-$500K+/yr |
On $50 million in annual merchant volume, the difference between referral at 15 bps ($75K) and PFaaS at 50 bps ($250K) is $175K per year. That gap grows with every merchant you add.
Implementation costs for PFaaS typically range from $50K to $200K, depending on the provider, your integration complexity, and whether you need custom boarding flows or can use their standard tools. Stripe Connect sits at the lower end for time-to-market; Finix and Payrix offer more white-label control but longer integration timelines. Time to launch is 2 to 6 months, significantly faster than the 12-18 months for full registration.
What You're Taking On
PFaaS isn't a referral program with better economics. You're taking on real operational responsibility.
Merchant onboarding. You manage the boarding experience, collect merchant information, and in many cases make preliminary underwriting decisions. The PFaaS provider approves or flags merchants based on risk criteria, but the merchant experience is yours.
First-line support. When a merchant has a question about their deposit, a chargeback notification, or a rate inquiry, they come to you. You'll need internal tooling or access to the provider's dashboard to handle these.
Pricing management. You set merchant rates. This means you need to understand interchange economics well enough to price profitably across different card types and transaction patterns. Getting this wrong is the most common source of margin compression in PFaaS programs.
Chargeback response. You're the first responder for disputes. In most PFaaS arrangements, you have a window, typically 5-7 days, to respond to chargebacks before they default. This requires process and tooling.
What the Provider Handles
Card network registration and reporting. They maintain the PayFac registration with Visa, Mastercard, and other networks, and handle the quarterly and annual reporting requirements.
Sponsor bank relationship. The acquiring bank relationship, which is the legal foundation for the entire processing chain, belongs to the provider. This is the single most complex and expensive element of becoming a PayFac, and it's what you're outsourcing.
Compliance framework. PCI compliance, AML monitoring, OFAC screening, and suspicious activity reporting are handled by the provider's compliance infrastructure. You feed data into it; they manage the regulatory obligation.
Settlement and funding. The provider manages the settlement cycle, holds reserves where required, and distributes funds to merchants according to the agreed schedule.
Want to see the numbers for your platform?
The Margin Multiplier models your revenue under all four embedded payments approaches. Takes 60 seconds. No signup required. Or start a conversation about what this means for your specific situation.
When PFaaS Makes Sense
The model fits a specific profile:
- Annual merchant volume between $30M and $200M
- 150 to 1,000+ merchants processing
- At least one person (internal or contracted) who understands payment operations
- You've been in ISV Referral and the economics no longer justify the simplicity
- Full PayFac registration isn't justified by your volume or timeline
PFaaS does not make sense if your volume is under $20M, the operational overhead isn't worth the incremental revenue over referral. And if you're above $200M and growing fast, the economics of full PayFac registration likely justify the investment at that scale.
Managed PayFac vs. Full PayFac: The Real Difference
The question isn't which is better. It's which matches your scale and trajectory.
Full PayFac gives you maximum economics and maximum control. But it requires a sponsor bank relationship (which takes 6-12 months to secure), card network registration ($50K+ in fees), dedicated compliance staff, and ongoing regulatory obligations that don't scale down if your volume dips.
PFaaS gives you 60-80% of the economics at 20-30% of the cost and complexity. For most platforms between $30M and $200M in volume, that trade-off is correct.
The transition from PFaaS to full PayFac is possible but nontrivial. It typically involves migrating your merchant portfolio to a new processing infrastructure, securing your own sponsor bank, and building the compliance and reporting systems the PFaaS provider was handling. Plan for 12-18 months. For the broader decision framework on whether to make that move, see Should You Become a Payment Facilitator?
PayFac-as-a-Service vs Full PayFac vs ISV Referral: The Complete Comparison
The three models that capture embedded payments economics for vertical SaaS platforms each sit in a different place on the economics-vs-complexity curve. The right choice depends on volume, operational capacity, and strategic time horizon.
| Dimension | ISV Referral | PayFac-as-a-Service | Full PayFac |
|---|---|---|---|
| Net economics | 5-15 bps | 30-60 bps | 60-100+ bps |
| Implementation cost | Minimal (weeks) | $50K-$200K | $500K-$2M |
| Time to launch | 2-4 weeks | 3-6 months | 12-18 months |
| Annual operating cost | Minimal | $100K-$300K | $300K-$800K |
| Who registers with card networks | Processor | The PFaaS provider | The platform itself |
| Who owns the sponsor bank relationship | Processor | The PFaaS provider | The platform itself |
| Who sets merchant pricing | Processor | The platform | The platform |
| Right volume tier | Under $25M | $30M-$200M | $200M+ |
The midpoint matters most: PFaaS gives you control of pricing and the merchant relationship (which is where most of the strategic value sits) without the capital expenditure or regulatory burden of full registration. For platforms at $30M to $200M of processing volume, that combination of control plus capital efficiency is usually the right answer.
How Much Does PayFac-as-a-Service Cost?
PFaaS costs split into three buckets: one-time implementation, recurring operating, and the volume-scaling spread share to the provider. Each scales differently with platform size.
Implementation: $50K to $200K
Implementation is mostly engineering integration with the PFaaS provider's APIs. The scope includes the merchant boarding flow (API integration with the provider's KYC and underwriting endpoints), the processing flow (payment intent creation, settlement reconciliation), the reporting flow (transaction-level data sync to your internal systems), and webhook handling for chargebacks, disputes, and balance updates. Most providers also charge a one-time setup fee of $20K to $50K on top of the engineering cost. Integration complexity varies by provider: Stripe Connect is the fastest at 2 to 4 months, while Finix, Tilled, and Payrix typically take 4 to 6 months.
Annual operating cost: $100K to $300K
The largest recurring cost is merchant operations staff, typically 0.5 to 1.5 FTEs depending on merchant count and complexity. This covers boarding support, chargeback response, tier-1 merchant inquiries, and pricing management. At fully-loaded comp of $150K to $200K per FTE, that's $75K to $250K per year in headcount. Beyond staff, expect $20K to $50K per year for monitoring tools, fraud screening integrations, and ongoing API maintenance as the provider updates their platform.
Spread share to the provider: 5 to 15 basis points of volume
This is the structural cost that scales with the platform's growth. The PFaaS provider takes a portion of the net spread in exchange for handling the regulatory layer. On $50M of annual processing volume at a 10 bps provider share, that's $50K per year. On $200M, it's $200K. This doesn't appear on the operating budget as a line-item expense, but it's real economic leakage that compounds with volume.
For a worked example: a platform with $100M of annual processing volume that has PFaaS net economics of 45 bps would gross $450K per year from payments. Operating costs (one mid-level FTE, monitoring tools, integration maintenance) run $175K. Provider spread share at 10 bps runs $100K. Net contribution to the platform: $175K per year in Year 1, scaling with volume. For the full volume-tier breakdown, see How Much Do SaaS Platforms Actually Make From Payments?
Frequently Asked Questions
What is PayFac-as-a-Service?
PayFac-as-a-Service (PFaaS), also called Managed PayFac or PayFac Lite, is an arrangement where a registered Payment Facilitator provides the underlying infrastructure (card network registration, sponsor bank relationships, compliance framework, settlement) while a software platform operates as a sub-facilitator under their umbrella. The platform owns the merchant experience, sets pricing, and handles first-line support. The provider handles the regulatory layer. Net economics typically run 30 to 60 basis points, compared to 5 to 15 bps for ISV Referral and 60 to 100+ bps for Full PayFac registration.
How is PayFac-as-a-Service different from being a full Payment Facilitator?
A full Payment Facilitator is registered directly with Visa and Mastercard, owns the sponsor bank relationship, and carries direct responsibility for all card network reporting and compliance. PayFac-as-a-Service lets a platform operate under another PayFac's existing registration. The platform gets 60 to 80 percent of the economics (30 to 60 bps vs 60 to 100+ bps) at 10 to 20 percent of the cost ($50K to $200K implementation vs $500K to $2M) and timeline (3 to 6 months vs 12 to 18 months). For most platforms between $30M and $200M in annual processing volume, PFaaS is the right call.
How much does PayFac-as-a-Service cost?
Implementation typically runs $50K to $200K, mostly engineering integration with the provider's APIs. Time to launch is 3 to 6 months. Ongoing operating costs include 0.5 to 1.5 FTEs handling merchant operations ($75K to $250K loaded), plus $20K to $50K per year for monitoring tools and integration maintenance. The provider takes 5 to 15 basis points of net spread, which scales with volume: $25K to $75K per year on $50M of processing volume, $100K to $300K on $200M.
Who are the top PayFac-as-a-Service providers?
The leading PayFac-as-a-Service providers include Stripe Connect (the largest by volume, with the fastest implementation but a per-transaction platform fee model), Finix (white-label PayFac infrastructure with interchange-plus pricing), Tilled (PFaaS focused on vertical SaaS with revenue share economics), Payrix (acquired by Worldpay, deep integration with FIS), and Adyen for Platforms (combined processing and facilitation under one architecture). Pricing model, time to market, and vertical fit vary significantly between them, which is why the right choice depends on volume, vertical, and operational maturity.
When does it make sense to graduate from PayFac-as-a-Service to a full PayFac?
The financial case for graduating from PFaaS to Full PayFac strengthens at $200M+ in annual processing volume. The marginal economics of Full PayFac (typically 25 to 30 bps over PFaaS) need to clear the marginal operating cost (typically $300K to $500K per year for compliance and risk staff). At $200M of volume, that 25 bps captures $500K of additional revenue against $300K to $500K of additional cost. Below $200M, the case is marginal. Above $300M, it usually justifies itself.
Is PayFac-as-a-Service the same as Stripe Connect?
Stripe Connect is one implementation of the PayFac-as-a-Service model, but not the only one. Connect uses a per-transaction platform fee model (0.25 percent plus $0.25 on top of standard processing fees) and is optimized for fast time-to-market. Other PFaaS providers like Finix, Tilled, and Payrix offer interchange-plus pricing that can be more economical at scale, white-label control over the merchant experience, and longer integration timelines in exchange for that flexibility. Choosing between them depends on volume, vertical, branding requirements, and how much engineering capacity the platform can invest in the integration.
PFaaS is the right model when referral economics feel like leaving money on the table, but full PayFac feels like building a payments company instead of a software company.
If you're evaluating the transition from referral to PFaaS, start with the Margin Multiplier to model the revenue difference. If you want to think through the operational readiness and provider selection questions, that's what the advisory engagement is built for.
Related: ISV Referral vs. PayFac-as-a-Service: How to Choose, a side-by-side comparison of the two most common transition points.