Payment facilitator vs payment processor: key differences for vertical software platforms

You start exploring the idea of adding embedded payments to your vertical software platform. Suddenly, everyone around you is throwing out terms like processor… payment facilitator… PayFacs – as if they’re interchangeable.
Meanwhile, your head is spinning. 

Here’s the thing. They’re not interchangeable. Choose the wrong model, and you might spend months building around infrastructure that was never the right fit for your platform. 

So let's clear it up. We'll walk through what payment processors, payment facilitators, and payment gateways actually do, where each one fits, and how to figure out which model makes the most sense for your platform. 

Because the first decision you make for your payments strategy has major potential to shape your fintech roadmap. 

Let’s dive into the definitions first. 

What is a payment processor?

A payment processor keeps a card payment moving. It passes transactional data between the merchant, card networks, and the issuing and acquiring banks so a payment can be authorized, settled, and completed securely.

Processing doesn't happen on its own. Before any of it starts, a merchant needs its own merchant account. That means underwriting with either the processor or the acquiring bank.
Each merchant goes through that process individually before it can start accepting payments.

What is a payment facilitator (PayFac)?

A payment facilitator (PayFac) is a registered entity that onboards sub-merchants under its own master merchant account. They own the entire payments infrastructure, including compliance, risk management, underwriting, chargebacks, and fraud monitoring. 

Unlike a payment processor, a payment facilitator does not usually connect directly to the card networks for authorization and settlement. Some PayFacs are also processors, which means they might connect directly to the card networks. But most payment facilitators partner with an established payment processor for this part.

Payment processor vs payment facilitator: The key differences

Here’s what this actually looks like in practice. 

When someone says "payment processor," they're usually not being technical about it. They mean the traditional payment processor business model. Your merchant applies for their own merchant account, gets underwritten individually by the processor or acquiring bank, and your platform sits on the outside of that relationship. 

When someone says "payment facilitator," that's probably not quite what you're picturing either. Odds are you don't want to become a registered PayFac yourself. What you actually want is someone else to handle the compliance and operational overhead while you deliver the best merchant experience. That's PayFac-as-a-Service (PFaaS). 

Here’s what both models mean for your vertical SaaS platform. 

Onboarding and underwriting

With a traditional payment processor, every merchant goes through its own underwriting process before it can accept payments. That's on them, and on the acquiring bank behind the processor.

With PFaaS, merchants are onboarded as sub-merchants under your payments provider's master merchant account. Underwriting still happens; it's just run through your partner instead of a separate acquiring relationship your merchant has to go set up on their own.

Risk and liability ownership

Under a traditional payment processor, risk sits mostly with the merchant and the acquiring bank. If a merchant's business goes sideways, that's a problem between them and their bank. 

With most PFaaS, your payments partner takes on underwriting risk and compliance responsibility for every sub-merchant on your platform. Either way, as a platform, you’re not taking on the risk here. 

Merchant relationship and data ownership

Under a traditional payment processing relationship (depending on who it is), the processor might own the merchant relationship. They're the ones your merchants call for support, and they're the ones holding the transaction-level data.

With PFaaS, you keep that relationship. Merchants are onboarded, supported, and managed inside your product. You get direct access to their transaction data. And your payments partner runs the show behind the scenes, but the relationship stays yours.

Pricing and revenue potential

A traditional payment processor that you partner with on a referral model typically pays out a fixed commission or a small share of processing revenue which is a rate you don't set and can't move.

PFaaS puts pricing in your hands. Instead of sending merchants elsewhere, you set your own rate and earn revenue from every transaction that runs through your platform.

That's why it's worth calculating your margin on payments volume before deciding which model makes the most sense for your platform. 

Which model is right for your platform?

So, there's no single right answer. The best model depends entirely on your platform, merchants, and what role you want payments to play in your business.

A traditional payment processor keeps implementation relatively simple, but it also means giving up much of the merchant relationship and long-term payments revenue.

PayFac-as-a-Service (PFaaS) provides you with many benefits of becoming a PayFac without requiring you to become a registered payment facilitator yourself. Instead, the PFaaS provider manages the underwriting, compliance, and risk behind the scenes while you deliver a fully embedded payments experience to your merchants.

That changes how payments contribute to your business. Rather than treating payments as a supporting feature with limited revenue potential, you can capture even more payments volume while owning the merchant relationship within your platform. Payments shouldn’t be treated as a bolt-on, it should be treated as the core of your product. 

There are vertical software platforms that haven't made that shift yet. And 70% of non-financial platforms still see payments as a utility instead of a revenue engine. But the question isn't just how you want to process payments. It's how much value you want payments to create for your platform.

The model behind the fastest-growing platforms

The vertical software platforms that are winning are not sending merchants to a third-party processor. They're embedding payments directly into the experience they already provide. That creates a smoother onboarding journey for merchants – keeping the merchant relationship inside the platform. And when embedded payments is done right, a platform will unlock more revenue and drive retention. 

More and more platforms understand why embedded payments should be part of their roadmap. PayFac-as-a-Service gives platforms a way to deliver a PayFac experience without taking on the burden of becoming a registered payment facilitator.

But success isn't just about choosing the right payments model. It's about having a go-to-market strategy for embedded payments that helps merchants understand the value, adopt the product, and keep using it.

That's exactly what Rainforest is built for. 

Thinking about embedding payments into your platform? 

‍

‍

Frequently asked questions about payment facilitators and payment processors

What is the difference between a payment processor and a payment facilitator?

A payment processor ensures the movement of card payments. It securely transfers transactional data between the merchant, card networks, and the issuing and acquiring banks. This way a payment can settle, authorize and complete it. Before any processing begins, a merchant needs its own merchant account. They then go through that process individually before accepting payments.  

A payment facilitator (PayFac) onboards businesses as sub-merchants under one master merchant account. A PayFac takes on responsibility such as the entire payments infrastructure, including compliance, risk management, underwriting, chargebacks, and fraud monitoring. 

However, a payment facilitator does not typically connect directly to the card networks for authorization and settlement. There are some PayFacs that are also processors and may connect directly to the card networks. Most payment facilitators partner with an established payment processor to get this done. 

‍Do I need to become a payment facilitator to monetize payments on my platform?

No. Becoming a registered payment facilitator isn't the only way to monetize payments on your platform. However, becoming a registered PayFac or using a PayFac-as-a-Service (PFaaS) provider gives you greater control over pricing, merchant relationships, and the share of the transaction revenue you can earn as volumes grow.

With PFaaS, a payments partner handles the underwriting, compliance, and risk management, allowing you to offer embedded digital payments without becoming a registered PayFac yourself.

Who owns chargeback and fraud liability under a PayFac model?

Merchants remain responsible for managing disputes relating to their own credit and debit card transactions, so chargeback management remains an important part of running their business. Modern payment platforms help reduce fraud with tools like 3D Secure and transaction monitoring, but no payment system can eliminate chargebacks entirely.

With a provider like Rainforest, the platform doesn't carry the financial risk if a merchant goes out of business and leaves behind customer disputes. Since Rainforest is responsible for merchant underwriting, we also absorb merchant credit losses, allowing vertical software platforms to focus on their product and customer support rather than payment operations.

Can a payment facilitator support PayPal, digital wallets, and other payment methods?

Yes. Most modern payment facilitators support a wide range of payment methods, including credit and debit cards, bank payments (ACH, wire transfers), and digital wallets such as Apple Pay, PayPal and Google Pay. The exact payment methods available depend on the payments provider.