What Is PayFac as a Service
Definition
PayFac-as-a-Service (PFaaS) is a model where a third-party provider gives ISVs the capabilities of a payment facilitator — merchant onboarding, underwriting, settlement splitting, and compliance — without requiring the ISV to register as a PayFac with card networks or maintain a sponsoring bank relationship.
How It Works
The PFaaS provider holds the PayFac registration and acquiring bank relationship. The ISV integrates the provider's APIs to offer embedded payments, branding the merchant onboarding and checkout experience as its own. The provider handles KYC/KYB, risk monitoring, PCI compliance, and fund settlement behind the scenes. The ISV earns a revenue share on each transaction — typically 20-50 basis points — while the PFaaS provider keeps the rest of the spread.
Why ISVs Care
PFaaS is the fastest path for ISVs to monetize payments without the $500K-$2M+ investment and 6-12 month timeline of full PayFac registration. It lets ISVs offer instant merchant onboarding, earn meaningful payment revenue, and own the branded payment experience — all without building compliance infrastructure or taking on full chargeback liability.
PayFac-as-a-Service gives ISVs the economic benefits and user experience of being a payment facilitator without the regulatory burden, capital requirements, and compliance infrastructure of full PayFac registration.
The Problem PFaaS Solves
Full PayFac registration requires:
- $500K-$2M+ in setup costs (legal, compliance, technology)
- 6-12 months to register with card networks and establish a sponsoring bank relationship
- Ongoing investment of $200K-$500K annually for compliance, risk management, and a dedicated payments team
- Full liability for sub-merchant fraud, chargebacks, and regulatory violations
Most ISVs — especially those under $100M in aggregate processing volume — can’t justify this investment. But they still want the benefits: fast merchant onboarding, payment revenue, and a branded experience.
PFaaS bridges this gap.
How PayFac-as-a-Service Works
The Technical Flow
- ISV integrates PFaaS APIs — Merchant onboarding, checkout, reporting, and settlement endpoints
- Merchant applies through ISV’s interface — The experience looks and feels like the ISV’s product
- PFaaS provider runs KYC/KYB — Identity verification, business validation, risk assessment (usually in minutes)
- Merchant starts processing — Transactions route through the PFaaS provider’s infrastructure
- Funds settle — The PFaaS provider handles settlement splitting, sending the merchant their funds and the ISV its revenue share
What the PFaaS Provider Handles
- Card network registration and sponsoring bank relationship
- KYC/KYB verification and ongoing monitoring
- PCI DSS Level 1 compliance
- Chargeback management and fraud detection
- Settlement and fund disbursement
- Regulatory reporting
What the ISV Controls
- Merchant-facing onboarding UX
- Checkout and payment interface design
- Pricing to merchants (within the PFaaS provider’s guidelines)
- Merchant relationship and support
- Reporting and analytics dashboards
Leading PFaaS Providers
| Provider | Typical ISV Revenue Share | Key Differentiator |
|---|---|---|
| Finix | 20-40 bps | API-first, modern infrastructure |
| Payrix | 25-50 bps | Vertical-focused, strong analytics |
| Tilled | 25-45 bps | Transparent pricing, ISV-centric |
| Stripe Connect | 15-35 bps | Largest ecosystem, marketplace features |
| WePay (JPMorgan) | 20-40 bps | Bank-backed, enterprise-grade |
Revenue share varies based on the ISV’s aggregate volume, average transaction size, and negotiation.
PFaaS Economics for ISVs
The math is compelling even at lower margins than full PayFac:
Example: SaaS ISV with 2,000 merchants, $25K average monthly processing each
- Aggregate monthly volume: $50M
- ISV revenue at 30 bps: $150,000/month ($1.8M/year)
- PFaaS provider fee (included in processing cost to merchant): Covered in the merchant’s rate
This $1.8M in annual payment revenue comes on top of SaaS subscription revenue — from the same customer base, with no additional acquisition cost.
When to Choose PFaaS vs. Full PayFac
Choose PFaaS when:
- Aggregate processing volume is under $100M annually
- You want embedded payments live in weeks, not months
- You don’t have (or want) a dedicated payments compliance team
- Shared liability is acceptable
- 20-50 bps revenue share meets your business model needs
Consider full PayFac when:
- You process $100M+ annually and the volume is growing
- Payment revenue is a primary business line, not a feature
- You want 60-100+ bps per transaction
- You can invest in compliance and risk management infrastructure
- You need complete control over underwriting and merchant policies
Common PFaaS Misconceptions
“PFaaS is just a fancy referral program.” No — PFaaS gives ISVs control over the merchant experience, branded onboarding, and meaningful revenue share. Referral programs offer none of these.
“All PFaaS providers are the same.” They differ significantly in API design, onboarding speed, supported payment methods, vertical expertise, and revenue-sharing models. The right provider depends on your ISV’s specific needs.
“You can easily switch PFaaS providers later.” Switching involves re-integrating APIs, migrating merchant data, and potentially re-onboarding merchants. Choose carefully upfront — this is a long-term partnership.