Payment Processor vs. Payment Facilitator: What’s the Difference and Which Is Right for You?
A payment processor handles the technical movement of funds between banks. A payment facilitator, or PayFac, lets multiple businesses accept payments under one master merchant account while managing onboarding, underwriting, and compliance on their behalf.
The choice affects how quickly you can start accepting payments, how much payment processing costs, how much control you have, and who owns compliance and risk. The right answer for your business depends on your transaction volume, business model, growth plans, and appetite for operational responsibility.
What Is a Payment Processor?
A payment processor is a third-party company that routes transaction data between a merchant, card networks, acquiring banks, and issuing banks so funds can move from a customer to a business.
When a customer pays by card, ACH, EFT, or digital wallet, the processor helps coordinate authorization, settlement, and funding. The processor may also provide a payment gateway, POS terminal, card reader, recurring billing tools, subscription management, and chargeback support.
Payment processor functions typically include:
Authenticating card or account details
Confirming that funds are available
Obtaining approval from the issuing bank and card network
Routing the transaction for settlement
Transferring funds to the merchant’s bank account
Under a traditional processor model, each business generally obtains its own dedicated merchant account. That application may involve financial documentation, credit checks, underwriting, and other paperwork, so approval can take several days to several weeks.
What Is a Payment Facilitator (PayFac)?
A payment facilitator is a company that onboards businesses as sub-merchants under its own master merchant account, allowing them to accept payments without establishing individual merchant accounts.
A PayFac maintains an agreement with an acquiring bank. Transactions settle through the PayFac’s account structure, and the PayFac then pays its sub-merchants. Most PayFacs do not connect directly to card networks; instead, they partner with an underlying payment processor for authorization and settlement. Some providers operate as both a payment facilitator and a payment processor.
PayFac responsibilities typically include:
Fast sub-merchant onboarding through KYC and KYB checks
Underwriting and merchant risk assessment
Fraud monitoring and transaction controls
Chargeback management
PCI DSS and other compliance programs
Reporting, reconciliation, and merchant support
For a business, the main benefit is convenience: it can often begin accepting payments in minutes or hours rather than waiting days or weeks for a dedicated merchant account.
Payment Processor vs. Payment Facilitator: Key Differences
Both models support payment acceptance, but they operate differently from the merchant’s perspective.
Dimension | Payment Processor | Payment Facilitator |
|---|---|---|
Merchant account | Each business establishes its own dedicated merchant account. | Businesses operate as sub-merchants under the PayFac’s master merchant account. |
Onboarding speed | Detailed application and credit checks; approval may take days to weeks. | Simplified, API-based onboarding; approval may take minutes to hours. |
Risk and compliance ownership | The business is responsible for its own merchant risk and PCI DSS obligations. | The PayFac manages underwriting, fraud controls, and much of the compliance framework. |
Bank relationship | The merchant has a direct contractual relationship with its processor and acquiring bank. | The PayFac maintains the primary acquiring relationship and typically relies on an underlying processor. |
Pricing structure | Interchange-plus pricing is more complex but can be less expensive at high volume. | Flat-rate pricing is easier to understand but may cost more as volume increases. |
Funding timeline | Funds may arrive by the end of the business day, depending on the agreement. | Funds may be staged through the PayFac and paid to sub-merchants in scheduled batches. |
Best for | Larger or high-volume businesses seeking control and pricing efficiency. | Startups, small businesses, SaaS platforms, and marketplaces seeking speed and simplicity. |
In practical terms, processors offer more control and potentially lower per-transaction costs at scale. PayFacs offer faster onboarding, simpler operations, and greater compliance offloading. A traditional processor may approve a merchant in several business days, while a PayFac may approve an eligible sub-merchant in minutes or hours.
How Each Model Handles Risk, Compliance, and Chargebacks
The biggest difference is not simply who moves the money; it is who assumes responsibility when something goes wrong.
Under a processor model, the merchant generally owns its own merchant account, PCI DSS compliance program, underwriting requirements, fraud controls, and chargeback exposure. The processor may provide tools and operational assistance, but the merchant remains responsible for meeting its obligations.
Under a PayFac model, responsibility is layered:
Financial liability: The PayFac is generally exposed to the acquiring bank for sub-merchant credit losses, chargebacks, fraud, and other payment-related risk under its agreement.
Operational dispute handling: The individual merchant may still need to collect evidence and respond to customer disputes. The PayFac can provide the workflow, deadlines, and support, but it does not necessarily write every response.
Fraud monitoring: The PayFac monitors transactions across its sub-merchants and may apply rules, reserves, limits, or settlement delays.
A PayFac also typically manages KYC and KYB checks, AML controls, underwriting, and merchant monitoring. Its PCI DSS certification may reduce the compliance burden for sub-merchants, although it does not eliminate every merchant obligation.
Understanding the Full Spectrum of Payment Models
The choice is not just processor or PayFac. There is a spectrum of payment models, each offering a different balance of control, revenue, cost, and risk.
Referral partner: A referral partner introduces merchants to a processor or acquiring provider and earns a commission. This is the simplest model, but it offers limited control over onboarding, the payment experience, and long-term revenue.
PayFac-as-a-Service (PFaaS): A payments partner handles much of the underwriting, compliance, risk management, and payment infrastructure. The software platform delivers an embedded payments experience and may retain the merchant relationship and a share of transaction revenue.
Registered PayFac: The company becomes a registered PayFac with the card networks, establishes a master merchant account, and assumes responsibility for its sub-merchants. Building this model can take 12–18 months and may require substantial investment in bank sponsorships, reserves, registration fees, compliance systems, risk operations, and technical infrastructure.
Direct processor relationship: The merchant works directly with a processor through its own dedicated merchant account. This provides greater control over pricing, payment flows, risk thresholds, and banking relationships, but requires more internal responsibility.
For many ISVs and SaaS platforms, PFaaS is the practical middle ground: it provides embedded payments and monetization opportunities without requiring the platform to build and operate a registered PayFac from the ground up.
Payment Processor vs. Payment Facilitator vs. Payment Gateway
A payment gateway is often confused with a payment processor or PayFac, but the gateway is primarily a technology layer. It captures, encrypts, and transmits payment data between a merchant’s website, application, or POS terminal and the payment system. It does not inherently own merchant onboarding, underwriting, risk, or compliance.
Entity | What It Does | Who Owns It |
|---|---|---|
Payment gateway | Captures, encrypts, and transmits payment data. | A processor, PayFac, or standalone technology provider. |
Payment processor | Routes transactions, obtains authorization, and settles funds between banks. | The merchant, through its own merchant account. |
Payment facilitator | Onboards sub-merchants, manages risk and compliance, and aggregates transactions under a master account. | The PayFac, while the merchant operates as a sub-merchant. |
A business can use all three layers at once. For example, a SaaS company might use a gateway to collect payment details, a processor to route transactions, and a PayFac or PFaaS provider to manage merchant onboarding and risk.
Merchant of Record vs. Payment Facilitator — What’s the Difference?
A merchant of record, or MoR, is the entity legally and financially responsible for a sale. That responsibility may include sales tax or VAT collection, refunds, transaction-related regulatory compliance, and the commercial terms of the customer’s purchase.
A payment facilitator has a different primary role. It simplifies payment acceptance by onboarding merchants under a master account and managing payment-related risk and compliance. A PayFac does not necessarily become the seller of record for every transaction.
An MoR goes further because it stands between the customer and the underlying seller as the legally recognized seller for the transaction. It may own the tax, refund, regulatory, and commercial obligations associated with the sale itself.
This distinction matters for SaaS platforms and marketplaces. A platform might use a PayFac model to embed payments while merchants remain responsible for their own sales. Alternatively, it may use an MoR model—sometimes alongside payment facilitation—to simplify global tax compliance, refunds, and cross-border selling.
Which Is Right for Your Business?
The best model depends on four practical variables.
Transaction volume: Low-volume businesses and newer companies may benefit from a PayFac’s flat-rate pricing and simpler setup. High-volume businesses often save more with interchange-plus pricing through a processor, especially when they can negotiate the markup and manage their own payment operations.
Time to market: Choose a PayFac when you need to launch payments quickly, often in minutes or hours. A processor may be a better fit when you have time for a detailed application, underwriting process, and account setup that could take days or weeks.
Control and customization: A processor gives the merchant more direct control over pricing, payment routing, risk thresholds, settlement, and customer experience. A PayFac is usually preferable when the business wants to offload much of the compliance and risk-management burden.
Revenue goals: For platforms, a referral or ISO model generally provides a fixed commission. PFaaS or a deeper embedded payments relationship may allow the platform to customize the experience, set rates within the agreement, and earn revenue from transactions.
An illustrative cost example
Suppose a PayFac charges 2.9% plus $0.30 per transaction. Assume a processor offers interchange-plus pricing equivalent to 2.05% plus $0.20 per transaction, but charges $1,500 per month in account, compliance, and operational costs.
For a $50 average transaction:
PayFac cost: $1.75 per transaction
Processor cost: $1.23 per transaction, plus fixed monthly costs
Estimated per-transaction savings with the processor: about $0.52
At those assumptions, the processor’s fixed costs would break even at roughly 2,900 transactions per month, or about $145,000 in monthly payment volume. This is only an illustration; actual interchange, processor markups, gateway fees, reserves, chargebacks, and contract terms vary.
Quick pick: Use a PayFac if you prioritize fast onboarding, simple pricing, and reduced compliance responsibility. Use a payment processor if you have substantial volume and need maximum control, customization, and long-term pricing efficiency.
Key Terms Glossary
Master merchant account: The primary merchant account a PayFac uses to process transactions for itself and its sub-merchants.
Sub-merchant: A business that accepts payments through a PayFac’s master merchant account.
Acquiring bank: The financial institution that enables merchants or PayFacs to accept card payments and receive settlement funds.
Issuing bank: The bank or financial institution that issued a customer’s payment card.
Card network: A payment network, such as Visa or Mastercard, that routes transaction information between issuers and acquirers.
Interchange fee: A fee transferred between the acquiring and issuing sides of a card transaction.
Underwriting: The process of evaluating a merchant’s business, financial profile, products, and risk before approving payment acceptance.
Chargeback: A transaction reversal initiated through a card issuer after a customer disputes a payment.
Rolling reserve: A portion of processed funds held temporarily to cover potential chargebacks, fraud, or other losses.
PCI DSS: The Payment Card Industry Data Security Standard for protecting cardholder data.
KYC/KYB: Know Your Customer and Know Your Business procedures used to verify identities and business information.
AML: Anti-money-laundering controls designed to detect and prevent illicit financial activity.
Merchant identification number (MID): A unique identifier associated with a merchant account for payment processing.
How Forte Supports Your Payment Strategy
Once you know which model fits your business, the next step is finding the right partner to execute it. CSG Forte supports payment processing, gateway services, merchant services, and embedded payment strategies across different business needs.
That flexibility matters when a company’s requirements change over time. A merchant may begin with gateway-based processing, move toward an acquired model, or choose an embedded payments approach that gives a software platform more control over the customer experience. CSG Forte’s partner options range from referral relationships to payment facilitation and embedded payments, helping organizations choose how much responsibility, revenue participation, and operational control they want to take on. Contact us today to learn how CSG Forte can help.
Payment Processor & PayFac FAQs
Can a company be both a payment processor and a payment facilitator?
Yes. Some large providers operate as both a payment processor and a payment facilitator. Stripe is a well-known example: it provides processing infrastructure while also onboarding businesses as sub-merchants under its platform.
How long does it take to get approved as a sub-merchant under a PayFac?
Approval is typically measured in minutes to hours for an eligible business, depending on the PayFac’s underwriting rules and risk controls. By comparison, obtaining a dedicated merchant account through a traditional processor may take several days or weeks.
What happens to my funds if my PayFac holds them?
A PayFac may stage transaction funds in its own account structure before paying sub-merchants, often in scheduled batches. It may also delay settlement, withhold funds, or apply a rolling reserve to manage risks such as chargebacks, fraud, or unusual transaction activity. These policies are important for businesses with tight cash-flow requirements.
Do I need to become a registered PayFac to monetize payments on my software platform?
No. A PFaaS arrangement can let a software platform offer an embedded payments experience and earn transaction revenue without building a registered PayFac operation. This can avoid the 12–18 month registration process, substantial buildout costs, and full sub-merchant risk liability associated with becoming a registered PayFac.
Is a payment facilitator a good fit for high-risk industries?
Not always. PayFacs typically apply strict eligibility rules and may decline or limit merchants in high-risk categories such as adult content, gambling, or some nutraceutical businesses. Companies in these industries may need a specialized processor or acquiring bank, a dedicated merchant account, and risk controls designed for their vertical.
What responsibilities does a Merchant of Record (MoR) assume?
A Merchant of Record (MoR) assumes legal and financial responsibility for processing a business’s transactions. Its responsibilities typically include handling payment processing, calculating and collecting applicable taxes, managing fraud screening, supporting refunds and chargebacks, maintaining payment security and regulatory compliance, and providing transaction records and reporting. Because the MoR appears as the seller in the transaction, it may also manage customer billing and payment-related obligations on the business’s behalf.