Payment Facilitator vs Payment Processor
Definition
A payment facilitator (PayFac) is a master merchant that onboards sub-merchants under its own MID, handling underwriting, compliance, and settlement. A payment processor routes transactions between merchants, card networks, and issuing banks. PayFacs use processors — they operate at different layers of the payment stack.
How It Works
A payment processor provides the technical infrastructure for authorizing and settling card transactions — routing data between the merchant's terminal or gateway, the card network (Visa, Mastercard), and the issuing bank. A payment facilitator sits above the processor, managing the merchant relationship layer: onboarding, KYC/KYB, pricing, compliance, and settlement to sub-merchants. In practice, PayFacs use processors — Stripe, for example, is both a PayFac and a processor.
Why ISVs Care
The question isn't which is better — it's which role your ISV plays. If your software helps other businesses accept payments, you're in the facilitation space and need PayFac or PFaaS capabilities. If your software just needs to charge customers directly (your own SaaS billing), a payment processor/gateway integration is sufficient. The answer determines your revenue model, compliance burden, and integration depth.
These two terms describe different roles in the payment ecosystem — and understanding the distinction is essential for ISVs choosing how to integrate payments.
Definitions
A payment facilitator (PayFac) is a master merchant that onboards other businesses as sub-merchants under its own merchant identification number. The PayFac handles underwriting, compliance, and settlement for its sub-merchants.
A payment processor routes payment transactions between merchants, card networks, and issuing banks. The processor handles the technical infrastructure for authorizing and settling transactions.
The Key Distinction for ISVs
The question isn’t “which is better” — it’s “which role does your ISV play?”
If your software helps other businesses accept payments, you’re in the facilitation space. You need PayFac or PayFac-as-a-Service capabilities.
If your software just needs to charge customers directly (your own SaaS billing), a payment processor/gateway integration is sufficient.
How They Work Together
In practice, PayFacs use payment processors. A PayFac handles the merchant relationship layer (onboarding, KYC, pricing) while the underlying processor handles the transaction routing and settlement infrastructure. Stripe, for example, is both — a PayFac and a processor.
For ISVs, the practical decision is: do you want to be a PayFac (or use PFaaS), or do you want to simply integrate a processor’s gateway? The answer depends on whether payment revenue and merchant experience are strategic priorities for your business.