What is a Payment Facilitator (PayFac)? How It Works

How the PayFac Model Simplifies Payment Acceptance for Businesses

For decades, accepting credit card payments was a clunky process for small businesses. Before a company could process card transactions, it usually needed to apply for a merchant account through an acquiring bank or processor, often with the help of an Independent Sales Organization (ISO). Approval would take days or weeks, and onboarding typically involved paperwork, underwriting reviews, and hardware setup before a business could start taking payments.

That all changed during the fintech boom of the 2010s. Companies like Stripe, Square, and Shopify popularized the payment facilitator (PayFac) model, which allowed businesses to onboard under a master merchant account instead of opening their own merchant account from scratch. That led to faster approvals, easier integrations, and a much simpler way for businesses to start accepting payments online or at the point of sale.

In this guide, we’ll break down how the PayFac model works, the responsibilities PayFacs take on behind the scenes, and the downsides businesses should understand before choosing a provider. We’ll also look at Slash, a business banking platform that helps companies centralize payouts and cash flow across the payment tools they already use, including PayFacs like Square and Shopify Payments.¹ At the same time, Slash also comes with its own native payment processor and SDK for building custom gateways. While Slash functions as a merchant of record rather than a PayFac, those looking for a facilitator in particular can still take advantage of what Slash has to offer.

See the ROI behind your spend

Use this calculator to understand impact, then manage and track it all in Slash.

ROI Calculator

What is a Payment Facilitator?

A payment facilitator is a company that lets businesses accept card payments without setting up their own merchant account. Instead of each business going through the slow process of getting approved by a bank, the PayFac holds one master merchant account and lets thousands of smaller businesses operate underneath it as sub-merchants.

A traditional merchant account is a specialized bank account that lets a business accept credit and debit card payments. It’s not actually a standard business account; instead, a merchant account is more like the holding bay that keeps your revenue before they’re transferred to your main checking or savings account.

Traditional (standalone) PayFac like Stripe, Square, and PayPal run payments as their core business and serve businesses directly. Software PayFac are vertical SaaS platforms (Toast for restaurants, Mindbody for fitness studios, Shopify for e-commerce) that embed payments into the software a business already uses. Marketplace PayFac like Etsy, Airbnb, and Uber sit between buyers and sellers, collecting funds from one side and paying out the other. All three are technically payment facilitators, but the experience for the business on the receiving end is quite different.

How Does a Payment Facilitator Work?

The PayFac isn’t the card network, the issuing bank, or even the underlying payment processor. Rather, it acts as a wrapper for those infrastructure pieces, offering a simpler product businesses can plug into. Here’s what PayFacs typically handle and where they sit in the payment processing stack:

Merchant onboarding and activation: Payfacs replace the traditional bank application with an automated signup, usually through a short form covering business details, ownership, and a bank account for deposits. Underwriting, KYC checks, and compliance reviews still happen in the background, and higher-risk industries or cross-region activity can trigger additional verification since the PayFac carries the risk for everything flowing through its sub-merchants.
Payment processing and transaction flow: When a customer pays, the transaction routes through the PayFac's infrastructure to the card networks and the customer's issuing bank for authorization. The business just sees an approved or declined result in its dashboard, and refunds, disputes, and chargebacks flow back through the same channels.
Master merchant account structure: Sub-merchants process payments under the PayFac’s broader acquiring relationship rather than maintaining their own. This is what makes fast onboarding possible, and it's also why the PayFac monitors activity across its sub-merchants and can pause an account if patterns look risky.
Payout and settlement: After transactions clear, the PayFac aggregates the funds and deposits them into a business's linked bank account, typically within one to two business days. Processing fees are netted out before deposit, and most PayFacs let businesses choose daily, weekly, or on-demand payout schedules.

Benefits of Payment Facilitators

When evaluating the benefits of a PayFac, the most useful comparison is against traditional merchant account setups. Historically, businesses accepted card payments by working directly with acquiring banks or through Independent Sales Organizations (ISOs) that helped establish and manage merchant accounts. The advantages below are largely tied to that shift away from direct merchant account relationships and toward a more embedded, software-driven payments model:

Faster merchant onboarding

Opening a traditional merchant account with a bank means filling out an application, going through underwriting, and waiting days or weeks for approval before you can accept card payments. A PayFac handles that approval process in the background as part of signup, so you can typically start taking payments much sooner. The actual timelines depend on your business type and the provider's risk review.

Simplified payment management

Processing, payouts, reporting, refunds, and disputes generally live on a single dashboard instead of being stretched across separate tools. For small businesses without a dedicated finance team, that consolidation can seriously cut down on the time spent managing daily payment operations. The specific features vary from one PayFac to another.

Embedded payment tools

Many PayFacs are built into software you're already using to run your business. For example, Shopify handles payments inside your store, Toast handles them inside your restaurant's POS system, and Square handles them inside your scheduling and inventory tools. Your payments live alongside the rest of your operation instead of being a separate system you have to log into.

Potential monetization opportunities

If your business runs a platform that other businesses sell through (a marketplace, a booking system, a vertical software product), payments can become a revenue stream rather than just a cost. Instead of routing your sellers' transactions through an outside processor and paying full fees, you can use a PayFac arrangement to take a cut of the processing revenue on the volume flowing through your platform.

Payment Facilitators vs. Payment Processors: How Are They Different?

Payment facilitators and payment processors tend to get conflated because businesses often interact with both through the same platform. In many cases, a PayFac is layered on top of a processor’s infrastructure, so a business may think it’s simply using a processor when it’s actually operating under a PayFac model.

The core difference is that payment processors handle the technical movement of transactions, while PayFacs manage the merchant relationship built around that infrastructure. Here’s how the two differ in practice:

Payment facilitator

Merchant onboarding: Handles onboarding under its master merchant account, allowing businesses to activate card payment acceptance quickly.
Ownership of the merchant account: Allows businesses operate as sub-merchants underneath the PayFac’s acquiring relationship instead of establishing their own direct merchant account.
Compliance responsibilities: Takes on much of the onboarding, KYC, underwriting, and ongoing compliance management associated with its sub-merchants.
Transaction oversight: Monitors merchants for fraud, chargebacks, and suspicious activity; can pause or terminate accounts if risk thresholds are exceeded.

Payment processor

Transaction infrastructure: Connects transactions between merchants, card networks, issuing banks, and acquiring banks for authorization and settlement.
Payment routing: Handles the technical transmission of payment data and ensures transactions move through the correct banking and card network channels.
Authorization and settlement: Manages the systems that approve, decline, clear, and settle card transactions behind the scenes.
Network connectivity and security: Maintains connections to card networks and banking partners while supporting encryption, tokenization, and other payment security standards.

Operational Responsibilities of a Full PayFac

Becoming a full PayFac means taking on the operating burden behind a payments platform, not just adding card acceptance to your product. You become responsible for the businesses processing underneath you, including how they’re approved, monitored, supported, paid out, and kept within card network and sponsor bank rules. Here’s a snapshot of some of the requirements for operating a full PayFac:

Onboarding and compliance oversight: You would need systems to verify each merchant, review ownership details, screen restricted business types, and decide who can process on your platform. That review doesn’t stop at signup – PayFacs are expected to monitor merchants over time and respond when activity changes.
Sponsor bank and network requirements: A full PayFac works under an acquiring bank and follows card network rules. That can mean registration, reporting, audits, documentation, and ongoing reviews from the bank or networks.
Fraud and disputes: You also would need processes for fraud monitoring, chargebacks, refunds, suspicious activity, and merchant support. As volume grows, this usually requires dedicated risk and operations teams.
Payouts, reserves, and treasury coordination: You control when merchants get paid, how fees are deducted, and whether funds need to be delayed or held. You may also need reserves to cover chargebacks, fraud losses, or merchant failures.
Data security and PCI DSS compliance: A PayFac has to manage payment data securely and ensure the right PCI controls are in place across its platform and merchant base.
Reporting and ongoing maintenance: All this work continues after launch. PayFacs need to track merchant activity, update policies as rules change, maintain records, and keep sponsor banks informed about risk across the portfolio.

How Slash Supports Modern Payment Workflows

If you opt to use a PayFac like Square or Shopify Payments, you can use Slash’s business banking platform in tandem to manage your cash, outgoing payments, invoices, and a lot more. Maybe, though, you haven’t yet set up your checkout flow and you’re looking for any type of payment processor. As a managed merchant of record (MoR) solution, Slash’s processor works a bit differently.

Eligible users can use our payment processor in two ways: adding card payments to your invoices and building Slash into your existing checkout with the Slash SDK and Payment Elements. Either way, because Slash is an MoR, we take some of the liability of selling as a merchant, such as fraud prevention and payment compliance, off of your hands. Users are still in charge of remitting their own taxes, but most MoR responsibilities are covered.

Whether you use Slash as a processor or financial platform, we allow you to do a lot with your money. Businesses can accept invoice payments in crypto, on-ramp into stablecoins like USDC and USDT to pay suppliers, and connect Slash to the rest of their financial stack through the Slash API.⁴ Slash also supports a broader set of financial workflows that extend beyond basic payment acceptance and settlement, with features like:

Working capital financing: Access short-term financing with flexible 30-, 60-, or 90-day repayment terms to help bridge cash flow gaps.⁵
High-yield treasury: Earn up to 4.01% annualized yield on idle funds with money market investments from BlackRock and Morgan Stanley, managed directly within your Slash account.⁶
Accounting & ERP integrations: Sync transaction data with QuickBooks Online, Xero, NetSuite, or Sage Intacct to streamline reconciliation, reporting, and month-end close.
Multi-entity support: Slash offers multi-entity account management tools without separate logins, allowing businesses to track spending, manage accounts, and download statements across all subsidiaries in one place.
Business banking: FDIC-insured business checking, protected up to $150M through Column N.A.'s insured cash sweep network.²

Apply in less than 10 minutes today

Join the 10,000+ businesses already using Slash.

Frequently Asked Questions

Can a business become its own payment facilitator?

Yes, but becoming a full PayFac requires significantly more operational infrastructure than simply integrating payment acceptance into a product. Businesses typically need sponsor bank relationships, compliance programs, fraud monitoring systems, payout operations, and dedicated risk and support teams before they can operate a PayFac model at scale.

What types of companies typically use PayFac models?

PayFac models are commonly used by software platforms that want to embed payments directly into their product experience. Examples include e-commerce platforms, vertical SaaS companies, online marketplaces, booking platforms, and POS providers that want merchants to onboard and begin accepting payments without leaving the platform.

Do PayFacs work for international payments?

Some PayFacs support international payment acceptance and cross-border payouts, but capabilities vary widely by provider. Businesses should evaluate supported countries, settlement currencies, payout timing, local compliance requirements, and FX fees before relying on a PayFac for global payment operations.