April 22, 2026
Payment Facilitator vs. Payment Processor: What's the Difference?
People use "payment facilitator" and "payment processor" interchangeably — and they shouldn't. They sit at different layers of the payments stack, they make money in different ways, and one depends on the other. If you're evaluating how to structure a payments business or choosing who to partner with, the distinction matters.
The short answer
A payment processor is the pipe: it routes transactions from the merchant's checkout to the card networks (Visa, Mastercard) to the issuing bank and back. Examples: Fiserv, TSYS, Worldpay, Elavon, Chase Merchant Services.
A Payment Facilitator (PayFac) is a front-office: it onboards sub-merchants under its own acquiring relationship and uses a processor behind the scenes to move the money. Examples: Stripe, Square, Toast, Shopify Payments.
Every PayFac sits on top of a processor. Not every processor partners with PayFacs.
What a payment processor does
A payment processor is the infrastructure layer of card-based payments. Its job:
- Receive an authorization request from a merchant's gateway
- Route it to the appropriate card network
- Receive the issuing bank's approve/decline decision
- Return the decision to the merchant
- Batch settle approved transactions daily
- Handle chargebacks and disputes
Processors are typically large financial-infrastructure companies with direct connectivity to Visa and Mastercard. They're certified by the networks and typically partnered with sponsor banks for acquiring.
What a Payment Facilitator does
A PayFac is a master merchant that onboards sub-merchants under its own acquiring relationship. Its job:
- Underwrite sub-merchants (make the accept / reject decision)
- Provision sub-merchant IDs under its master MID
- Handle the sub-merchant contract, billing, and support
- Route sub-merchant transactions through a processor
- Collect the discount rate from the sub-merchant
- Pay the processor and sponsor bank their share
- Keep the margin in between
The PayFac is the customer of the processor. The sub-merchant is the customer of the PayFac.
Side-by-side
| Dimension | Payment Processor | Payment Facilitator |
|---|---|---|
| What it is | Network / bank infrastructure | Master merchant with sub-merchants |
| Primary customers | Acquirers, ISOs, large merchants, PayFacs | Sub-merchants (small businesses, SaaS customers) |
| Revenue model | Per-transaction fees, network access fees | Discount rate on volume minus processor cost |
| Certification burden | Very high (directly network-certified) | High (registered with Visa / MC, sponsor bank) |
| Onboarding time for customers | Weeks–months (large customers) | Minutes–hours (sub-merchants) |
| Who holds the merchant contract | N/A (works through ISOs/PayFacs for small merchants) | The PayFac |
| Examples | Fiserv, TSYS, Worldpay, Elavon | Stripe, Square, Toast, Mindbody |
The money flow on a card-rail PayFac transaction
A customer pays $100 at a small business that uses Stripe:
- Customer enters card details on the business's Stripe-powered checkout
- Stripe (PayFac) sends the authorization to its processor (historically Fiserv, now in-house)
- Processor routes to Visa, Visa to the issuing bank, bank approves
- Response flows back to Stripe, Stripe confirms to the merchant
- Batch settlement that night. Stripe receives $100 from the processor (less interchange)
- Stripe takes 2.9% + $0.30 = $3.20 as the discount rate
- Stripe pays ~$1.50 to the processor + networks + issuing bank in interchange & assessments
- Stripe pays ~$0.10 to its sponsor bank
- Stripe nets ~$1.60 on the transaction
- Stripe deposits $96.80 into the sub-merchant's bank account on T+2
Where a self-hosted gateway fits
A self-hosted crypto gateway like PayRam collapses several of these layers. There's no processor (the blockchain is the processor). There's no sponsor bank (no acquiring relationship). There's no issuing bank (the customer pays from their own wallet). And there's no batch settlement — payments land in the merchant's cold wallet in seconds to minutes.
The PayRam operator plays a PayFac-like role (onboarding sub-merchants, running the master infrastructure) but without being dependent on any of the card-rail layers. The crypto PayFac explainer covers the full parallel.
Key takeaways
- A processor is infrastructure. A PayFac is a business model on top of that infrastructure.
- PayFacs exist because processors are too expensive and slow to onboard small merchants directly. The PayFac abstraction makes that possible.
- On crypto rails, the processor layer is the blockchain itself — which is why a self-hosted gateway can collapse the stack.
- If you're picking who to work with: partner with a processor when you're already a PayFac or have very large direct merchants. Partner with a PayFac (or be a PayFac) when you're onboarding many small merchants quickly.
