Payment facilitator. PayFac. Managed PayFac. PayFac Lite. PayFac-as-a-Service. Sub-merchant. Master merchant. The terminology around payment facilitation is genuinely confusing, and it's confusing by design — because the companies defining these terms are the ones selling the services.

If you run product, finance, or partnerships at a software company and you're trying to figure out what payment facilitation actually means for your business, this is the plain-language version. No jargon ladders. No sales positioning disguised as education.

The Basic Concept

A Payment Facilitator is an entity registered with the card networks (Visa, Mastercard) that is authorized to board merchants under its own merchant identification number (MID) and process payments on their behalf.

In plain terms: instead of each of your merchants getting their own individual merchant account with a processor — which involves separate applications, separate underwriting, and separate agreements — a PayFac aggregates merchants under one umbrella. Your merchants become "sub-merchants" under the PayFac's master account.

This matters for software companies because it changes the economics. When a processor gives each of your merchants their own account, the processor owns the relationship and keeps most of the margin. When merchants are aggregated under a PayFac structure, the PayFac — which could be you, or a service you use — controls the pricing and keeps a larger share.

Why It Exists

Before the PayFac model, getting a merchant account was slow and painful. Every business that wanted to accept card payments had to apply individually, go through underwriting, wait days or weeks for approval, and sign a direct agreement with a processor. For a software platform trying to enable payments for hundreds or thousands of small businesses, this was a dealbreaker.

The PayFac model was created to solve this. By allowing one entity to aggregate merchants and take responsibility for their risk, the card networks enabled faster boarding, simpler onboarding, and a better merchant experience. Square was one of the first companies to popularize this model at scale — every small business swiping through a Square reader is a sub-merchant under Square's PayFac registration.

For vertical SaaS platforms, the PayFac model unlocked the ability to embed payments into their product and participate in the economics — not just connect merchants to a processor and collect a referral fee.

The Spectrum of Payment Facilitation

This is where the terminology gets muddy. "Payment facilitator" describes a spectrum of arrangements, not a single model. Here's how to think about it:

Full / Direct PayFac

You register directly with Visa and Mastercard as a Payment Facilitator. You get your own MID, you underwrite merchants yourself, you manage compliance and reporting to the card networks, and you handle settlement. You buy processing at wholesale rates from a sponsor bank and keep maximum margin.

This is the most control and the best economics — net margins of 50 to 100+ basis points on volume. It's also the most expensive and complex to set up: $500K to $2M+ in implementation, 12-18 months to launch, and ongoing compliance obligations that require dedicated staff.

Full PayFac makes sense at $100M+ in annual processing volume. Below that, the infrastructure cost outweighs the economic benefit.

Managed PayFac / PayFac-as-a-Service

A registered PayFac provides the infrastructure — sponsor bank relationships, card network registrations, compliance frameworks — and you operate as a partner under their umbrella. You handle merchant-facing operations (onboarding, pricing, first-line support) and they handle the regulatory layer.

You're not registered with the card networks yourself. But you set merchant rates, control the boarding experience, and keep the spread between what you charge and what you pay the provider. Net margins typically range from 25 to 70 basis points.

This model — sometimes called PayFac Lite — is the fastest-growing segment in embedded payments because it gives platforms PayFac-level economics without PayFac-level infrastructure requirements. Implementation costs range from $50K to $200K, and you can be live in 3-6 months.

ISV Referral (Not PayFac)

For comparison: in an ISV Referral arrangement, you're not a PayFac at all. You refer merchants to a processor, the processor boards and underwrites them, and you collect a residual — typically 5 to 25 basis points. You don't control pricing, you don't own the merchant relationship in payments terms, and your economics are a fraction of what a PayFac arrangement would produce.

Referral is the right starting point for many platforms, but it's important to understand that it is fundamentally different from payment facilitation — even though some processors blur the line in their marketing.

What a PayFac Is Responsible For

Whether you're a full PayFac or operating under a managed PayFac arrangement, someone is carrying these responsibilities. Understanding them helps you evaluate what you're taking on versus what your provider handles:

In a managed PayFac arrangement, the provider handles most of the compliance and regulatory reporting. You handle merchant onboarding, first-line support, and pricing. The split varies by provider, and understanding exactly who owns what is critical before you sign.

The Economics in Simple Terms

Here's why payment facilitation matters financially. On a $100 credit card transaction at a merchant rate of 2.75%:

The merchant pays $2.75. Interchange (paid to the card-issuing bank) might be $1.70. The card network takes about $0.02. Your processing cost (interchange + processor markup) might be $1.85. You keep the remaining $0.90.

That $0.90 on a single transaction doesn't sound transformative. But multiply it across $50 million in annual volume at roughly the same margin, and you're looking at $300,000 to $450,000 in annual net payments revenue. In an ISV Referral arrangement on the same volume, you'd earn $25,000 to $125,000.

The difference — $175,000 to $325,000 per year on $50M in volume — is why the PayFac model exists for software companies. And that gap widens every year as your volume grows.

Common Misconceptions

"We need to become a PayFac." Maybe. But for most platforms between $30M and $200M in volume, a managed PayFac arrangement gives you 60-80% of the economics at 20-30% of the complexity. Full registration is the end state, not the starting point.

"PayFac means we're a payments company now." No. It means you're monetizing the payments flowing through your platform. You're still a software company. The payments program is a revenue line, not a pivot.

"It's too complex for our team." A managed PayFac provider handles the regulatory complexity. Your operational addition is merchant onboarding, basic support, and chargeback response — which at most platforms translates to 0.5 to 1.5 FTEs depending on merchant count.

"We should wait until we have more volume." The threshold is lower than most teams assume. At $30-50M in annual volume with 150+ merchants, the economics of managed PayFac typically justify the move. The Margin Multiplier can show you the specific numbers for your volume.

Where to Go from Here

If you're trying to decide whether payment facilitation makes sense for your platform, start with two questions:

  1. What is your annual merchant payment volume? If you don't know, estimate it: merchant count times average monthly volume times 12.
  2. What are you earning on that volume today? If the answer is nothing, or a referral residual of 5-15 basis points, there is likely a significant revenue opportunity you're not capturing.
Payment facilitation isn't about becoming a payments company. It's about capturing the economics of the payments already flowing through your software.

The Margin Multiplier models your revenue across all four monetization approaches — ISV Referral, Enhanced Residuals, PayFac Lite, and Full PayFac — in about 60 seconds. Start there, then read our comparison of PayFac vs. ISO for the full decision framework.