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 provides the infrastructure — sponsor bank relationships, card network registrations, compliance frameworks, settlement systems — and you operate as a sub-facilitator or managed partner under their umbrella.

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.

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. 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.

When PFaaS Makes Sense

The model fits a specific profile:

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.

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.