Industry Payment Guides

Should Your Marketplace Become a Payment Facilitator?

PayFac vs. marketplace explained: how card network rules classify your platform, what a full PayFac costs, and when PayFac-as-a-service fits better.

Five colleagues meet at a wooden table in a bright office, a woman leading discussion beside a laptop showing charts

Photo: Pixabay

On this page 7 sections
  1. PayFac vs. Marketplace: How Visa and Mastercard Define Each
  2. Signs Your Platform Is Acting Like a PayFac Without Registering
  3. What It Costs to Become a Payment Facilitator
  4. PayFac-as-a-Service: The Middle Path
  5. Revenue Upside: Earning Margin on Processing
  6. A Decision Framework by GMV and Seller Count
  7. Next Steps for Choosing Your Payment Model

Key takeaways

  • Visa and Mastercard look at how money moves on your platform, not what you call yourself. Collecting buyer funds and paying sellers can put you in regulated territory.
  • A full PayFac needs a sponsor acquirer, network registration, a real underwriting and risk program, and the capital to absorb seller losses.
  • PayFac-as-a-service lets you embed payments and earn some revenue while a provider holds the registration and much of the compliance work.
  • Base the decision on processing volume, seller count, risk appetite and staffing. Confirm any structure with your acquirer and legal counsel before you build it.

Most online marketplaces reach the same point eventually. Payments are flowing through the platform, sellers want faster payouts, and someone asks whether the company should "become a PayFac." The PayFac vs. marketplace question matters because the card networks classify platforms by how money and responsibility move, not by what the founders call the business. This guide covers how Visa and Mastercard draw that line, the warning signs that a platform is operating outside the rules, what full registration actually requires, and when PayFac-as-a-service is the more practical choice.

This article is general information, not legal or compliance advice. Card network rules, acquirer policies and state money transmission laws change. Confirm your structure with your acquirer and qualified counsel.

PayFac vs. Marketplace: How Visa and Mastercard Define Each

Both Visa and Mastercard publish rules for payment facilitators and for marketplaces. The details differ by network and get revised, so read the current versions with your acquirer. The core distinction is consistent, though.

The Payment Facilitator Model

A payment facilitator is sponsored by an acquiring bank and registered with the card networks. It signs agreements with sub-merchants, the independent businesses that sell to their own customers, and processes card payments on their behalf.

Typical PayFac examples include booking software for salons, invoicing tools for contractors and ordering systems for restaurants. Each sub-merchant has its own customers and its own brand. The PayFac supplies the payment rails and is accountable to its sponsor for every sub-merchant it onboards.

The Marketplace Model

A marketplace brings buyers and many sellers together under the marketplace's own brand. The buyer shops on the marketplace, pays the marketplace, and usually sees the marketplace's name on the card statement. The marketplace then settles funds to the sellers.

Under network marketplace rules, the marketplace generally takes responsibility for disputes and refunds on its transactions and must be registered through its acquirer.

Quick Comparison

QuestionPayment FacilitatorMarketplace
Whose customer is the buyer?The sub-merchant'sThe marketplace's
Whose brand does the buyer shop under?Sub-merchant'sMarketplace's
Who usually handles disputes first?Sub-merchant, with PayFac liable if it can't payMarketplace
Who onboards sellers?PayFac, under sponsor oversightMarketplace, under acquirer oversight
Network registration required?YesYes, under marketplace rules

Neither model lets a platform quietly collect money for other businesses. Both are registered, sponsored arrangements.

Signs Your Platform Is Acting Like a PayFac Without Registering

Many platforms drift into facilitation without planning to. The early setup was simple: one merchant account in the company's name, with sellers paid by ACH every week. Here are the warning signs that the setup has outgrown that account:

  • Buyer funds land in your merchant account, and you pay sellers later. Your account was underwritten for your own business, not for dozens or thousands of other businesses.
  • Sellers sell to their own customers under their own names. That looks like sub-merchant activity, not a marketplace sale.
  • Nobody but you verifies the sellers. If your acquirer has never seen your seller list, it can't assess the risk it is carrying.
  • Seller categories don't match your MCC. A home-goods platform that starts hosting supplement or ticket sellers is processing outside what was approved. Our guide to policing marketplace prohibited items covers how listings create processor risk.
  • You net fees and refunds out of seller payouts by hand. Spreadsheet-driven payouts often mean the payment flow was never designed for multiple parties.

Processing payments for other businesses through your own account without the right registration can be treated as aggregation or transaction laundering. The usual result is an account termination and possibly a MATCH listing.

The fix is to tell your acquirer how the platform actually works and restructure. Splitting volume or relabeling sellers to avoid review is not a fix. If you hold buyer funds before paying sellers, also ask counsel whether state money transmission laws apply to you. Requirements and exemptions vary by state.

What It Costs to Become a Payment Facilitator

Registering as a full PayFac means building a small regulated payments company inside your marketplace. The direct fees are only part of the cost. Sponsor banks set their own requirements, and network registration fees apply. Get current figures from prospective sponsors rather than relying on published estimates.

Requirements Your Sponsor Will Expect

  • A sponsor acquirer willing to back your platform, often with collateral or reserves sized to your risk.
  • Card network registration as a payment facilitator, renewed periodically.
  • PCI DSS compliance at a level matching your volume and how you handle card data, usually with formal assessments.
  • A written underwriting and risk policy that covers acceptable industries, approval criteria, transaction monitoring and termination procedures.
  • Financial liability for sub-merchant chargebacks, refunds and fraud when a seller can't or won't pay.
  • Sub-merchant agreements that meet sponsor and network requirements.
  • Tax reporting for payments made to sellers. See our guide on 1099-K filing for marketplace operators.

Sub-Merchant Registration and Onboarding

Sub-merchant registration is where most of the daily work happens. For every seller, a PayFac typically must:

  1. Collect business and owner identity information.
  2. Verify that information and screen it against sanctions lists and the MATCH list.
  3. Assign an accurate MCC that reflects what the seller actually sells.
  4. Record and report the sub-merchant as the sponsor requires.
  5. Monitor activity after approval and re-review sellers whose volume, products or dispute rates change.

Networks also set volume levels above which a sub-merchant may need a direct merchant agreement with the acquirer. Confirm the current thresholds with your sponsor. For a deeper look at verification, see seller KYC for marketplaces.

The Staffing Reality

FunctionWhat It Covers
Underwriting and riskSeller approvals, monitoring, holds, terminations
ComplianceNetwork rules, PCI DSS, sanctions screening, audits
Payments operationsReconciliation, settlement, payout exceptions
DisputesChargeback responses, seller recovery, negative balances
EngineeringOnboarding flows, ledgering, split logic, reporting
Finance and legalReserves, tax reporting, contracts, licensing questions

Small teams can combine some of these roles. None of them can be dropped, and they have to stay staffed through nights, weekends and holidays when fraud tends to appear.

PayFac-as-a-Service: The Middle Path

PayFac-as-a-service (PFaaS) lets a platform embed payments while a provider holds the PayFac registration. The marketplace keeps the seller experience inside its product. The provider handles the regulated core, including underwriting decisions, network registration and much of the compliance burden.

How the work and economics usually split:

Full PayFacPayFac-as-a-ServiceSeparate Merchant Accounts
Control of onboardingFullSharedMinimal
Liability for seller lossesYouMostly provider, terms varyEach seller
Processing revenueHighest potentialRevenue shareLittle or none
Upfront build and staffingHeavyModerateLight
Time to launchLongestShorterShortest

Ask these questions before you sign a PFaaS agreement:

  • Who makes the final call on approving, holding or terminating a seller?
  • How are revenue share and pricing changes handled over time?
  • Can you migrate your sellers if you later register as a full PayFac or switch providers?
  • How does the provider support splitting one checkout across multiple sellers?
  • Who covers a seller's negative balance after a refund or chargeback?

Revenue Upside: Earning Margin on Processing

The main appeal of becoming a PayFac is earning margin on processing instead of paying it away. Margin is what remains after interchange and network fees, and you control neither of those. Network fee changes, like those covered in our industry news coverage of card network fees, can affect your spread.

Illustrative example only: A platform processing $10 million a year that keeps 0.10 percentage point of net margin earns $10,000 before costs. At $100 million, the same margin is $100,000. The arithmetic scales quickly. Your costs don't shrink at the same rate:

  • Staff salaries for risk, compliance, operations and engineering
  • Assessments, audits and registration fees
  • Reserves that tie up working capital
  • Losses from sellers who disappear owing chargebacks. See who pays marketplace chargebacks.

Model your break-even with real sponsor quotes and realistic loss assumptions before you commit.

A Decision Framework by GMV and Seller Count

No volume figure automatically means you should register. Use the stages below as a starting point for choosing a marketplace payment model, then test your assumptions with your acquirer.

StageTypical SignalsLikely Fit
EarlyModest GMV, small seller base, product still changingMarketplace or PFaaS through an established provider
GrowthGMV climbing, steady seller onboarding, payouts becoming a selling pointPFaaS, with a review of the full PayFac economics
ScaleLarge, predictable GMV, many sellers, appetite for owning riskFull PayFac, if you can staff and capitalize it

Factors that should push you toward more caution:

  • Higher-risk seller categories. Regulated or dispute-prone products raise liability. A high-risk processing review belongs early in planning.
  • Thin margins. If pricing pressure leaves little spread, the revenue upside may not cover the cost of the program.
  • A small team. Registering before you can staff risk and compliance creates the exposure you were trying to manage.
  • Long fulfillment windows. Services delivered weeks after payment raise dispute risk and affect payout holds for new sellers.

Next Steps for Choosing Your Payment Model

Start by mapping your current payment flow: who the buyer pays, whose name appears on the statement, where funds sit and who answers a chargeback. Share that map with your acquirer and counsel before changing anything. Most platforms find that the right model is the one they can operate cleanly now, with room to grow into more control later.

MannyPay provides online payment processing, payment gateways and integrations and merchant accounts for low- and high-risk businesses. To talk through your platform's setup, request a free payment quote and a MannyPay specialist will respond within one business day.

About the author

MannyPay Editorial Team

Beyond the Swipe's editorial desk researches the publication's guides and news and cites its sources in every article. Articles reviewed by a named MannyPay editor carry that editor's byline.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading