A SaaS platform or marketplace may want sellers to start accepting payments as soon as they sign up. In a traditional acquiring model, however, each seller applies for a separate merchant account and is underwritten by an acquiring bank. That separation can slow onboarding and fragment the payment experience.
The payment facilitator model addresses this problem by allowing approved sub-merchants to accept payments under a sponsored structure. It can make embedded payment acceptance faster and more consistent, but it also changes who manages merchant due diligence, transaction monitoring, disputes and card-network compliance.
For platforms operating in India, one distinction is essential: a payment facilitator is a card-network model, while a payment aggregator is an RBI-regulated category. The terms may describe similar commercial outcomes, but they are not automatically interchangeable.
TL;DR
- A payment facilitator, or PayFac, enables approved sub-merchants to accept payments through its acquiring relationship instead of obtaining separate merchant accounts.
- The PayFac manages sub-merchant onboarding and monitoring, while the acquirer continues to sponsor and oversee the programme.
- Faster onboarding comes with substantial obligations around due diligence, fraud, disputes, reporting, reserves and card-network rules.
- In India, platforms should evaluate RBI-authorised payment aggregation and embedded-payment infrastructure rather than assume that a global PayFac label defines their regulatory position.
- Most SaaS platforms should compare building a sponsored programme with using an established payments partner before committing capital and compliance resources.
What Is a Payment Facilitator?
A payment facilitator (PayFac) is an entity registered within a card-network and acquiring-bank programme to onboard eligible businesses as sub-merchants. Instead of every sub-merchant establishing a direct acquiring relationship and receiving a standalone merchant account, the PayFac operates through a master or sponsored merchant relationship.
The model generally has four participants:
- Acquiring bank: Sponsors the PayFac, connects it to the card networks and supervises the programme.
- Payment facilitator: Performs sub-merchant onboarding, due diligence, monitoring and programme administration.
- Sub-merchant: Sells the product or service and accepts payments through the PayFac arrangement.
- Processor or gateway: Supplies the technology that securely authorises, routes and records transactions.
Visa describes the model as one in which an acquirer contracts with a payment facilitator to provide payment services to sponsored merchants. Its official Payment Facilitator Model overview also makes the acquirer’s continuing role clear: the PayFac does not eliminate sponsor-bank oversight.
This structure is useful for vertical SaaS companies, marketplaces and service platforms that want payments to feel native to their product. A platform can control the onboarding interface and payment journey while the underlying programme defines how sub-merchants are approved and monitored.
Also read: How SaaS businesses should evaluate a payment gateway
How Does the PayFac Model Work?
The exact flow varies by acquirer, network, market and business category, but a typical PayFac arrangement follows six stages.
1. The acquirer sponsors the PayFac
The PayFac enters into an agreement with an acquiring bank and is registered under the relevant card-network programme. The parties define permitted merchant categories, underwriting rules, transaction limits, reserves, reporting and loss-allocation terms.
2. The platform collects sub-merchant information
The prospective sub-merchant supplies business identity, ownership, bank-account and operating information. Digital workflows can reduce data-entry friction, but “instant onboarding” does not mean skipping verification. In India, platforms can use automated KYC and AML workflows to collect and check relevant information, subject to the applicable regulatory framework.
3. The PayFac underwrites the sub-merchant
The PayFac evaluates the merchant’s identity, business model, products, expected volumes, refund exposure and fraud risk. Low-risk applicants may receive a quick decision; higher-risk or incomplete applications need manual review. Activation speed therefore depends on the merchant profile and the programme’s risk policy.
4. The sub-merchant is added to the programme
Once approved, the business receives the identifiers required to process payments within the PayFac structure. Transactions must carry accurate sub-merchant data so the acquirer and card networks can identify the actual seller.
5. Payments are processed and settled
The gateway and processor send the transaction for authorisation through the acquirer and card network. Settlement then follows the agreed programme structure. Funds do not simply become the platform’s money: handling and onward settlement must follow the acquiring agreement and applicable safeguarding or escrow rules.
For a marketplace, split-payment infrastructure can calculate the platform commission and each vendor’s share without relying on spreadsheets or manual transfers.
6. Activity is monitored continuously
Onboarding is only the first risk decision. The PayFac monitors transaction velocity, fraud, disputes, refunds and changes in merchant behaviour. It may request additional information, delay settlement, create reserves or suspend a sub-merchant when programme rules allow.
What Does a Payment Facilitator Actually Own?
A PayFac does more than place a payment form inside a platform. Its operating responsibilities commonly include:
- sub-merchant due diligence and underwriting;
- sanctions, fraud and transaction monitoring;
- prohibited-business and merchant-category controls;
- card-network registration and reporting;
- dispute and chargeback operations;
- reserve and settlement-risk management;
- sub-merchant support, suspension and offboarding; and
- security obligations across the payment environment.
The acquirer still retains oversight and contractual responsibility to the network. Meanwhile, the sub-merchant remains responsible for genuine sales, accurate descriptions, fulfilment, refund policies and customer service. Liability is allocated by programme agreements; it is too broad to say that either the bank or the platform alone “owns all risk.”
Platforms should also verify payout accounts before releasing vendor funds. An API-based bank account verification process helps detect incorrect beneficiary details during onboarding.
Benefits of the PayFac Model
Faster, integrated onboarding
Eligible merchants can apply inside the platform rather than moving through a disconnected bank application. Pre-filled information, API verification and risk-based review can shorten the path to activation.
A consistent product experience
The platform can bring signup, checkout, transaction reporting, refunds and settlement visibility into one interface. That matters when payment acceptance is part of the software’s core workflow rather than an external add-on.
Better portfolio-level risk signals
A platform can detect patterns across its merchant base—for example, repeated bank accounts, linked devices or abnormal refund behaviour—that may be harder to spot in isolated applications.
New commercial options
Embedded payments may create additional revenue, improve retention or support a broader subscription plan. The commercial model must remain transparent and comply with the contracts and rules that apply to pricing and fee disclosure.
Automated vendor accounting
Configurable splits and settlement schedules reduce manual commission calculations. Cashfree’s Easy Split API overview explains how platforms can manage vendors, settlements, refunds and adjustments through an integrated flow.
Also read: How split payments help online marketplaces manage vendors
Costs and Risks Platforms Should Not Underestimate
The PayFac model shifts work into the platform or its programme partner. Before building it, estimate the full operating cost, not only the API effort.
| Area | What the platform must plan for |
|---|---|
| Compliance | Policies, audits, network reporting, merchant reviews and evidence retention |
| Risk | Fraud detection, reserves, settlement exposure and sub-merchant monitoring |
| Operations | Manual reviews, support, disputes, refunds, holds and offboarding |
| Engineering | Onboarding, payments, ledgers, webhooks, reconciliation and exception handling |
| Finance | Sponsor and processor fees, losses, reserve capital and operational headcount |
A common mistake is assuming that a faster application form equals faster approval for every merchant. Restricted categories, unusual ownership structures, elevated dispute risk or inconsistent documents will still require additional checks. Another mistake is treating the platform ledger as a reporting feature; it is critical infrastructure for explaining every movement of money.
Platforms designing this layer should map event-driven updates early. Cashfree’s webhook documentation shows how payment-status events can keep an internal order or ledger state aligned with the payment system.
Payment Facilitator vs Payment Processor
These terms describe different roles.
| Dimension | Payment facilitator | Payment processor |
|---|---|---|
| Primary role | Onboards and manages sub-merchants within a sponsored programme | Transmits and processes payment messages between participants |
| Merchant structure | Multiple sub-merchants under the PayFac arrangement | May process for merchants with their own acquiring relationships or for a PayFac programme |
| Underwriting | Performs defined sub-merchant due diligence under programme rules | Usually provides processing technology rather than serving as the merchant underwriter |
| Ongoing monitoring | Monitors sub-merchants and programme-level risk | Monitors transaction and system activity within its contracted role |
| Best fit | Platforms embedding payments for many businesses | Businesses or payment providers that need reliable transaction processing |
One company can perform more than one role, subject to its licences, registrations and contracts. Therefore, the correct question is not only “What does the provider call itself?” but “Which regulated and contractual functions does it perform in this market?”
PayFac vs Payment Gateway, ISO and Payment Aggregator
| Model | Main function | Key distinction |
|---|---|---|
| Payment gateway | Securely captures and transmits payment data | A technology layer; it does not automatically onboard merchants or hold funds |
| Payment processor | Processes authorisation, capture, clearing or settlement messages | Focuses on transaction processing rather than necessarily sponsoring sub-merchants |
| ISO | Markets or services merchant-acquiring solutions on behalf of an acquirer | Its authority and risk responsibility depend on its agreement and network registration |
| Payment facilitator | Onboards and manages sub-merchants through a sponsored card-acquiring programme | A card-network programme role with defined oversight and monitoring duties |
| Payment aggregator in India | Aggregates customer payments and settles them to merchants under RBI rules | A regulated Indian category with authorisation, merchant onboarding, escrow and governance requirements |
A payment gateway may be one component in any of these arrangements. It should not be used as a synonym for the entity managing merchants or settlement.
The India-specific distinction deserves special attention. A platform serving Indian merchants should assess the RBI authorisation and operating model of its payment partner, the movement of funds, merchant contracts and settlement controls. A US-style PayFac blueprint cannot simply be copied into India without adapting it to local regulation.
Also read: What is a payment aggregator, and how does it work?
Do You Need to Become a PayFac?
Use the following decision framework before choosing a model.
| Consider a direct or partner-led setup when… | Explore a PayFac-style programme when… |
|---|---|
| You accept payments only for your own business | You onboard many independent businesses that accept payments from their customers |
| Payments are useful but not central to the product | Embedded payment acceptance is central to activation, retention or revenue |
| You want a provider to manage most payment compliance operations | You can fund dedicated compliance, risk, finance and support capabilities |
| Your seller volume does not justify programme overhead | Your scale and economics can justify sponsorship, certification and continuing oversight |
| A standard gateway or platform integration meets the need | You require programme-level control over onboarding and merchant lifecycle |
Three questions usually clarify the decision:
- Who is the seller of record? The answer affects contracts, customer communication, tax and disputes.
- Who controls funds and settlement instructions? Map each account and ledger entry rather than relying on a high-level diagram.
- Who performs each compliance task? Assign onboarding, monitoring, sanctions screening, disputes, reporting and offboarding explicitly.
For many SaaS businesses, a partner-led embedded-payments setup offers a shorter route: payments remain native to the software while an established provider supplies the underlying regulated infrastructure.
How Cashfree Supports SaaS Platforms and Marketplaces
Cashfree Payments operates as an RBI-authorised payment aggregator in India—not as a generic substitute for every global PayFac programme. Its platform infrastructure helps SaaS products and marketplaces embed merchant onboarding and payments while working within the applicable Indian framework.
Relevant capabilities include:
- Merchant lifecycle APIs: Cashfree Platform APIs support merchant onboarding, account management and payment activation within a platform journey.
- Vendor verification: Easy Split vendor KYC helps marketplaces collect and submit required vendor information before settlements are enabled.
- Payment acceptance: The Payments API overview covers order creation, checkout, payment status and refunds.
- Split settlements: Platforms can define commissions and vendor shares, schedule settlements and account for refund adjustments.
- Payout operations: Cashfree Payouts supports programmatic transfers when a business needs a separate disbursement workflow.
- Branded experience: A white-label payment gateway can help eligible platforms maintain visual continuity across the payment journey.
The appropriate architecture depends on the platform’s business model, fund flow, merchant categories and regulatory obligations. Product capability does not remove the platform’s responsibility to use the service within its approved use case.
Conclusion
A payment facilitator is not simply a faster gateway. It is a sponsored operating model for onboarding and managing sub-merchants, with continuing responsibilities across underwriting, monitoring, disputes, settlement risk and card-network compliance.
For an Indian SaaS platform or marketplace, the practical objective is usually not to acquire the PayFac label. It is to create compliant, low-friction merchant onboarding and an embedded payment experience with clear ownership of every risk and operational task. Compare the build, partner and hybrid routes using the same criteria: activation time, regulatory fit, control, unit economics, loss exposure and long-term operating cost.
Build payments into your platform – not around it
Explore merchant onboarding, embedded payment acceptance and automated split settlements for your SaaS platform or marketplace.
Explore Embedded PaymentsFAQs
What does a payment facilitator do?
A payment facilitator onboards and manages approved sub-merchants within an acquiring-bank and card-network programme. It typically handles due diligence, transaction monitoring, reporting and first-line merchant operations under the sponsor’s oversight.
Is a payment facilitator the same as a payment gateway?
No. A gateway securely captures and transmits transaction data. A PayFac manages a sponsored sub-merchant programme. A PayFac may use a gateway as part of its technology stack.
Is a payment facilitator the same as a payment aggregator in India?
Not exactly. PayFac is generally a card-network programme term, while payment aggregator is a regulated category in India. Their services may overlap, but businesses should assess the provider’s actual RBI authorisation, network role, contracts and fund flow.
Does every sub-merchant receive its own merchant ID?
Sub-merchants receive identifiers that allow transactions to be attributed and reported correctly within the programme. The exact identifier structure depends on the acquirer, processor and card-network rules; it should not be described as an independent direct merchant account unless it is one.
How quickly can a PayFac onboard a sub-merchant?
Low-risk applicants with complete, verifiable information may be approved quickly. Higher-risk categories, complex ownership, missing documents or unusual transaction patterns can require manual review. No legitimate model guarantees instant approval for every merchant.
Who is responsible for chargebacks in a PayFac model?
The sub-merchant is responsible for the underlying customer transaction, while the PayFac usually manages the dispute process and has programme-level exposure to its acquirer. Final financial responsibility depends on the merchant, PayFac and acquiring agreements.
Can a SaaS company earn revenue from embedded payments?
Potentially. Commercial models may include platform fees or contracted revenue sharing. Pricing, disclosures and fee collection must comply with the applicable agreements and regulations; payment margin should be modelled after fraud, disputes, operations and reserve costs.
What should a platform evaluate in a PayFac or embedded-payments partner?
Evaluate regulatory status, sponsor relationships, supported merchant categories, onboarding controls, payment methods, split settlements, dispute tooling, reconciliation, API reliability, data portability and the contract’s allocation of losses and reserves.
