What Is a Payment Aggregator
Definition
A payment aggregator is a service provider that processes transactions for multiple merchants under a single master merchant account, rather than requiring each merchant to establish their own merchant account with an acquiring bank. Payment aggregators bundle (aggregate) many merchants' transactions together.
How It Works
The aggregator holds one master merchant identification number (MID) with an acquiring bank. When a new merchant wants to accept payments, the aggregator onboards them as a sub-merchant under this master MID — no separate bank application required. All transactions from all sub-merchants route through the aggregator's infrastructure. The aggregator handles settlement, splitting funds to individual merchants after deducting fees.
Why ISVs Care
Payment aggregator is often used interchangeably with payment facilitator (PayFac), though there are technical distinctions. ISVs evaluating embedded payments need to understand this model because it's the foundation of platforms like Stripe, Square, and PayPal — and it's the model that PFaaS providers enable ISVs to replicate within their own software.
Payment aggregator describes a company that groups multiple merchants under a single merchant account, letting them accept card payments without individual merchant applications.
Payment Aggregator vs. Payment Facilitator
These terms are closely related and often used interchangeably, but there’s a distinction:
- Payment aggregator is the broader, older term — any entity that processes transactions for multiple businesses under one MID
- Payment facilitator (PayFac) is the specific card network designation (Visa and Mastercard formalized the PayFac rules in 2011) with defined responsibilities for KYC, monitoring, and settlement
In practice, every PayFac is a payment aggregator, but not every aggregator is a registered PayFac. Some aggregators operate under legacy structures that predate the formal PayFac designation.
For ISVs, the practical takeaway is the same: both models let you onboard merchants quickly under a shared account.
How Payment Aggregation Works
The Traditional Model (Without Aggregation)
- Merchant applies for a merchant account with an acquiring bank
- Bank performs underwriting (credit check, business verification, risk assessment)
- Bank issues a unique MID to the merchant
- Merchant integrates a payment terminal or gateway
- Timeline: 3-14 business days
The Aggregator Model
- Merchant signs up through the aggregator’s platform (often an ISV’s software)
- Aggregator runs automated KYC/KYB checks
- Merchant is activated as a sub-merchant under the aggregator’s master MID
- Merchant starts processing immediately through the aggregator’s infrastructure
- Timeline: Minutes to hours
The speed difference is what makes aggregation essential for ISVs. Modern software users expect to be live in minutes — not waiting days for a bank to approve a merchant application.
Well-Known Payment Aggregators
| Aggregator | Type | ISV Relevance |
|---|---|---|
| Stripe | Registered PayFac | Stripe Connect enables ISV payment facilitation |
| Square | Registered PayFac | Primarily direct-to-merchant, limited ISV tools |
| PayPal | Registered PayFac | PayPal Commerce Platform for marketplaces |
| Adyen | Registered PayFac | Adyen for Platforms targets enterprise ISVs |
| Finix | PFaaS Provider | Enables ISVs to act as aggregators |
| Payrix | PFaaS Provider | ISV-focused aggregation infrastructure |
Why ISVs Use the Aggregator Model
Merchant Experience
Aggregation removes the biggest friction point in payment onboarding — the merchant account application. ISVs that offer instant payment activation see higher adoption rates for their embedded payment features.
Revenue Model
Under the aggregator model, the ISV (or its PFaaS partner) controls pricing. The aggregator charges merchants a processing rate (e.g., 2.9% + $0.30) and keeps the spread between that rate and the underlying interchange + network fees. This spread is the ISV’s payment revenue.
Compliance Trade-off
The aggregator takes on responsibility for its sub-merchants’ behavior. This includes:
- Monitoring for fraudulent transactions
- Managing chargebacks and disputes
- Ensuring sub-merchants comply with card network rules
- Maintaining PCI DSS compliance for the entire platform
For ISVs using PFaaS, the PFaaS provider handles most of this compliance burden — but the ISV still has responsibilities around merchant communication and first-line support.
Aggregation Limits and Scaling
Card networks impose volume and risk thresholds on aggregators:
- Transaction monitoring: Aggregators must flag sub-merchants that exceed certain volume thresholds for enhanced due diligence
- High-risk merchants: Aggregators cannot onboard merchants in prohibited categories (gambling, adult content, etc. — varies by card network and acquirer)
- Volume limits: Some acquiring banks set volume caps per sub-merchant, requiring merchants above certain thresholds to obtain their own MID
ISVs should understand these limits because they affect which merchants your platform can serve and how your payment feature scales.
The Bottom Line for ISVs
Payment aggregation is the mechanism that makes embedded payments possible. Whether you call it aggregation or payment facilitation, the model is the same: your software becomes the merchant onboarding and payment acceptance channel, and you earn revenue on every transaction that flows through it.