PayFac vs. Payment Aggregator: Underwriting, Fees, Risk

A PayFac and a payment aggregator both let a business accept card payments without opening its own merchant account at an acquiring bank, but they draw the line between the processor and the merchant in different places. A payment facilitator registers with the card brands, gives each sub-merchant its own unique identifier, and takes on underwriting and compliance for every business on its platform. A payment aggregator pools every sub-merchant under one shared Merchant Identification Number and trades deeper review for fast, low-friction onboarding. That structural choice drives everything else: how fast you can start processing, who carries the loss when a chargeback hits, how much the arrangement costs to run, and how much control you have over the payment experience.

How the Aggregator Model Works

A payment aggregator bundles a large number of businesses under one shared MID. The aggregator is the merchant of record in the eyes of the acquiring bank. Individual businesses are sub-merchants operating under the aggregator’s credentials, and the bank sees a single high-volume entity rather than thousands of small accounts. Early Square and PayPal are the familiar examples: you sign up in minutes and start taking payments the same afternoon, without anyone at a bank reviewing your application.

The architecture is hub-and-spoke. The bank maintains one relationship with the aggregator, and the aggregator’s software distributes funds internally among its sub-merchants. That simplifies the bank’s workload, but it concentrates risk. If a sub-merchant racks up fraudulent chargebacks or disappears after issuing refunds, the aggregator owes the acquiring bank for the losses. The shared-MID structure is the aggregator’s greatest strength and its biggest vulnerability.

How the PayFac Model Works

A payment facilitator also operates under a master MID, but it creates an individual sub-merchant identifier for every business that joins its platform. Each sub-merchant has a distinct identity within the PayFac’s system, which allows more precise transaction tracking, dispute handling, and reporting. The PayFac must register with card networks like Visa and Mastercard through its sponsoring acquirer, and that registration carries fees and ongoing obligations.1Visa. Visa Core Rules and Visa Product and Service Rules

Mastercard charges an initial registration bundle fee of $5,200, which consolidates costs that were previously billed separately. Annual renewal fees apply on top of that. Combined with the infrastructure needed to manage individual sub-merchant accounts, the PayFac model is significantly more expensive to set up and maintain than a basic aggregation arrangement.

Software-as-a-service companies often choose this model because it lets them embed payment processing directly into their product. A property management platform, for example, can handle rent collection natively rather than sending landlords to a third-party checkout page. The PayFac controls the onboarding experience, sets pricing, manages payouts, and earns a share of transaction revenue on every payment its sub-merchants process. That revenue share is the economic engine that makes the compliance investment worthwhile.

Key Differences at a Glance

The terms get used interchangeably because a PayFac is technically a more sophisticated form of aggregation. The operational differences, though, are real:

  • Merchant identity. An aggregator processes all transactions under one shared MID. A PayFac assigns each sub-merchant a unique identifier that gives every business its own trackable presence in the card networks’ systems.
  • Onboarding depth. Aggregators prioritize speed, often approving merchants in minutes through automated screening. PayFacs run a more thorough underwriting process because they carry direct responsibility for each sub-merchant’s risk profile.
  • Fund control. A PayFac manages the entire flow of funds from customer payment through to merchant payout, including the timing and amount of each disbursement. An aggregator typically handles only the payment transaction itself.
  • Service scope. PayFacs usually offer a broader package that includes payment gateway integration, fraud tools, reporting dashboards, and dedicated support. Aggregators tend to provide a more standardized processing service.
  • Registration. A PayFac must formally register with each card brand through a sponsoring acquirer. An aggregator operates under its own acquiring relationship without the same card-brand registration requirements.

Plenty of companies have evolved from pure aggregators into something closer to a PayFac as they scaled. The line between the two is a spectrum, not a wall.

How Each Model Underwrites You

Both models have to collect identifying information. Federal anti-money-laundering rules under the Bank Secrecy Act, strengthened by the USA PATRIOT Act, require customer due diligence protocols that apply to any entity touching payment flows.2Financial Crimes Enforcement Network. USA PATRIOT Act At minimum, that means collecting Social Security numbers or government-issued IDs from business owners, along with an Employer Identification Number obtained through IRS Form SS-4.3Internal Revenue Service. About Form SS-4, Application for Employer Identification Number (EIN)

Aggregators lean on automation. Their systems scan applicant information against watchlists and credit databases in near-real-time, and approvals can happen within minutes. The trade-off is that the aggregator absorbs most of the risk by letting merchants onto the platform with little manual review. That math works when the typical sub-merchant is small and the tickets are low, but it means greater exposure when something goes sideways.

PayFac underwriting goes further. Visa requires payment facilitators to validate each prospective sub-merchant’s identity, confirm the business is legitimate, and check the Terminated Merchant File (MATCH) to see whether the applicant was previously dropped by another processor.4Visa. Payment Facilitator and Marketplace Risk Guide Higher-risk applicants may be asked for audited financial statements, recent tax returns, and documentation showing how the business operates. Based on that review, the PayFac may impose processing volume limits or require a rolling reserve, where a percentage of each transaction is held back as a buffer against future chargebacks.

Settlement, Fees, and Reserves

After a card transaction is authorized and captured, funds move from the cardholder’s issuing bank through the card network to the acquiring bank, then into the merchant’s account. Standard settlement runs on a T+1 or T+2 timeline, meaning money arrives one or two business days after the sale, and weekends and holidays push things out further. The funds pass through the Automated Clearing House network, which is subject to federal regulations governing electronic fund transfers.5Consumer Financial Protection Bureau. 12 CFR Part 1005 – Electronic Fund Transfers (Regulation E)

During settlement the processor subtracts its fees before disbursing the rest. The fees vary with card type, risk category, and processing model. For debit card transactions, Regulation II caps interchange fees for covered issuers at $0.21 plus 0.05% of the transaction value, with an additional $0.01 fraud-prevention adjustment if the issuer qualifies.6Federal Reserve Board. Regulation II (Debit Card Interchange Fees and Routing) – Average Debit Card Interchange Fee by Payment Card Network Credit card interchange has no federal cap and runs significantly higher, often between 1.5% and 2.5% plus a per-transaction fee depending on the card brand and transaction category. Merchants pay a bundled “merchant discount” to their processor that includes interchange, card network fees, and the processor’s own markup.

For merchants flagged as higher risk, the processor may hold a portion of funds in a reserve account for 90 to 180 days to cover chargebacks or refunds that surface later. Reserves are more common with PayFacs, which have sub-merchant-level visibility to impose them selectively, than with basic aggregators that manage risk at the pool level.

Chargebacks and Why Isolation Matters

Card networks actively monitor chargeback and fraud ratios, and both aggregators and PayFacs face consequences when their merchants cross certain lines. Visa consolidated its monitoring programs into a single framework called the Visa Acquirer Monitoring Program, effective June 2025. As of April 2026, a merchant is flagged as “excessive” in the United States when its VAMP ratio reaches 1.5% or higher with at least 1,500 combined fraud and dispute events per month.7Visa. Visa Acquirer Monitoring Program Fact Sheet 2025 The ratio combines fraud reports and disputes relative to settled transactions, so a merchant with high volume but normal disputes won’t trigger the program.

Crossing the thresholds brings escalating fines against the acquirer, mandatory remediation plans, and eventually termination. A terminated merchant lands on the MATCH list maintained by Mastercard, where the record stays for five years. Being on MATCH doesn’t legally bar you from processing cards, but as a practical matter most acquirers and processors will decline your application on sight. This is where the PayFac model offers a structural advantage. Because each sub-merchant has its own identifier, a PayFac can isolate and terminate a problem merchant without disrupting the rest of its portfolio. An aggregator working from a shared MID has less granular control, and one bad actor’s chargebacks can affect the entire pool’s standing with the card network.

Regulatory and PCI Obligations

Both models sit in a space where federal anti-money-laundering rules intersect with state money transmitter laws. FinCEN has outlined four conditions a company must meet to qualify for the “payment processor” exemption and avoid being classified as a money services business: it must facilitate the purchase of goods or services, operate through clearance and settlement systems limited to BSA-regulated financial institutions, act under a formal agreement, and have that agreement with the seller or creditor receiving the funds.8FinCEN. Application of Money Services Business Regulations to a Company Acting as an Independent Sales Organization and Payment Processor Most PayFacs and aggregators that stick to card-based payments meet those conditions. The risk arises when a platform starts disbursing funds outside normal card settlement channels, such as sending payouts via checks or money orders; the exemption falls away and state money transmitter licensing can come into play.

Regardless of the exemption, both models must maintain BSA/AML compliance programs: written policies approved by the board, a designated compliance officer, ongoing employee training, independent testing, and risk-based customer due diligence procedures.9FFIEC BSA/AML InfoBase. Assessing the BSA/AML Compliance Program PayFacs shoulder that burden more directly because they onboard and underwrite sub-merchants themselves. An aggregator typically relies on its sponsoring bank’s compliance infrastructure, which lightens the aggregator’s obligations but gives it less control over how quickly merchants get approved or flagged.

Both models must also comply with the Payment Card Industry Data Security Standard. Most sub-merchants under either model never touch raw card data; the processor stores sensitive payment information using tokenization, which replaces actual card numbers with randomly generated digital tokens. That shifts the heaviest PCI burden onto the aggregator or PayFac. One catch for merchants: those tokens are specific to the processor’s system. If you switch providers, you may need to re-collect card information from customers or negotiate a data migration, which can disrupt recurring billing and subscriptions. Non-compliance with PCI DSS can result in card-brand fines typically ranging from $5,000 to $100,000 per month depending on the compliance level and how long the violation persists.

Which Model Fits Your Business

The aggregator model works best for businesses that need to start accepting payments immediately with minimal setup. A small retailer, a sole proprietor selling online, or a seasonal vendor at farmers’ markets can be processing in minutes without financial statements, compliance officers, or registration fees. The trade-off is less control over your payment experience and potentially higher per-transaction fees, because the aggregator prices in the risk of its undifferentiated merchant pool.

The PayFac model is built for platforms, not individual merchants. A SaaS company that wants payments embedded in its product, or a marketplace that pays out to hundreds of sellers, gets control over onboarding, pricing, fund flows, and the user experience, plus a share of revenue on every transaction its sub-merchants process. The flip side is real compliance work: card brand registration, KYC screening, chargeback management, and ongoing monitoring of the entire merchant portfolio. Building or buying the infrastructure to run a PayFac operation typically requires a meaningful upfront investment in technology and compliance staff.

Some businesses land in the middle, starting with an aggregator while volumes are low and migrating to a PayFac arrangement as they grow and the processing revenue justifies the compliance overhead. The right choice turns on your volume, your appetite for regulatory complexity, and whether controlling the payment experience is a competitive advantage or just an operational headache.