Payment Aggregator
A company that bundles many small merchants under a single merchant account, simplifying onboarding but sharing risk exposure.
Key Takeaways
- A payment aggregator processes transactions for many merchants under a single master merchant account, eliminating the need for each business to establish its own relationship with an acquiring bank.
- Aggregators like Square, PayPal, and Stripe enable near-instant onboarding but introduce shared risk: account freezes, rolling reserves, and fund holds can affect sub-merchants without warning.
- Crypto payment aggregators apply the same bundling model to blockchain-based payments, offering lower fees and faster settlement while removing chargeback risk entirely.
What Is a Payment Aggregator?
A payment aggregator is a third-party payment service provider that processes transactions on behalf of multiple merchants under a single master merchant identification number (MID). Instead of each business applying for its own dedicated merchant account with an acquiring bank, the aggregator onboards businesses as "sub-merchants" under its own account. The aggregator handles the relationship with the acquiring bank, card networks, and payment processors on behalf of all its sub-merchants.
PayPal pioneered this model in the early 2000s, allowing anyone with an email address to accept payments without navigating the traditional underwriting process. Today, Square, Stripe, and other major platforms operate as aggregators (or the closely related payment facilitator model), collectively processing hundreds of billions of dollars in annual transaction volume. The global payment aggregator market was valued at approximately $6.96 billion in 2025, with projections reaching $24.65 billion by 2035.
How It Works
The core mechanism is simple: one master account, many sub-merchants. Here is the typical transaction flow:
- A customer initiates a payment at a sub-merchant's checkout
- Payment data flows through the aggregator's payment gateway
- The aggregator encrypts and tokenizes the card information
- The transaction is routed to the acquiring bank, which communicates with the card network (Visa or Mastercard)
- The issuing bank authorizes or declines the transaction
- Funds settle from the issuing bank to the acquiring bank, then to the aggregator, which distributes to the sub-merchant
The sub-merchant never interacts directly with the acquiring bank or card network. From the network's perspective, every transaction appears to come from the aggregator itself.
Onboarding and Underwriting
Traditional merchant accounts require extensive documentation: bank statements, financial records, business history. Manual underwriting can take days or weeks. Aggregators replace this with automated, algorithm-driven checks that screen against the MATCH List (Mastercard's terminated merchant database), run KYC/AML verification, and assess business model risk. A new sub-merchant can be processing payments within minutes.
Fee Structure
Aggregators typically charge flat, blended rates that bundle interchange fees, scheme fees, and processing margins into a single percentage. For example, Square charges around 2.6% + $0.10 per in-person transaction, while Stripe charges 2.9% + $0.30 per online card charge. This simplicity contrasts with the interchange-plus pricing that traditional merchant accounts offer, where the interchange rate (set by card networks) and a smaller processor markup (typically 0.15%–0.30% + $0.08) are itemized separately.
At lower transaction volumes (generally under $500,000 per year), the convenience of flat pricing outweighs the cost premium. At higher volumes, a dedicated merchant account with interchange-plus pricing is almost always cheaper.
Settlement Timelines
Funds typically reach the sub-merchant within one to three business days after a transaction. Square deposits next-business-day for weekday transactions. PayPal offers standard transfers in one to three business days or instant transfers for a 1.5% fee. These timelines are governed by the aggregator's own settlement cycle with its acquiring bank, not the individual merchant's relationship.
Payment Aggregator vs. Payment Facilitator
The terms "payment aggregator" and "payment facilitator" (payfac) are often used interchangeably, but there is a technical distinction. Around 2011, Visa and Mastercard formalized the payment facilitator model as an evolution of the aggregator concept. The key differences:
| Dimension | Aggregator | Payment Facilitator |
|---|---|---|
| Merchant ID | Single shared MID for all sub-merchants | Unique sub-merchant ID under the master MID |
| Card network registration | May not be formally registered | Must register with Visa/Mastercard through an acquirer |
| Underwriting | Minimal automated checks | More thorough KYC, MATCH, and OFAC screening |
| Service scope | Payment processing focused | Full lifecycle: gateway, fraud protection, reporting |
In practice, most major aggregators today (Square, Stripe, PayPal) operate as registered payment facilitators. The aggregator model was the predecessor; the payfac model is its regulated, formalized successor.
Payment Aggregator vs. Traditional Merchant Account
The traditional model uses Independent Sales Organizations (ISOs): there are roughly 3,500 ISOs across North America, each helping merchants establish their own dedicated merchant accounts. The tradeoffs are significant:
| Factor | Aggregator | Traditional Merchant Account |
|---|---|---|
| Approval time | Minutes to hours | Days to weeks |
| Documentation | Minimal identity verification | Bank statements, financials, business history |
| Pricing | Flat rate (2.6%–3.5% + fixed fee) | Interchange-plus (interchange + 0.15%–0.30%) |
| Account stability | Shared risk, potential freezes | Dedicated account, lower freeze risk |
| Control | Limited (no batch control, fixed terms) | Negotiable terms, batch timing control |
| Best for | SMBs, startups, low volume | Established businesses, high volume |
For a deeper look at how fees flow through the card payment ecosystem, see the research on merchant payment acceptance costs.
Use Cases
- Small and micro-merchants: a food truck or craft seller can accept card payments through Square without any bank relationship or credit check
- Marketplaces and platforms: services like Shopify use aggregator infrastructure to let thousands of independent sellers process payments through a single integration
- Seasonal and event-based businesses: a vendor at a weekend market can activate and deactivate payment processing without monthly fees or long-term contracts
- SaaS platforms with embedded finance: non-financial software companies embed payment processing by partnering with an aggregator, offering payments as a feature rather than building their own PSP infrastructure
- Cross-border sellers: aggregators handle multi-currency processing and international card acceptance, simplifying cross-border payments for merchants who lack the scale for direct acquiring relationships
Crypto Payment Aggregators
Crypto payment aggregators apply the same bundling model to blockchain-based payments. Services like BitPay and CoinGate onboard merchants under a shared infrastructure, convert cryptocurrency to fiat or stablecoins at the point of sale, and handle settlement.
The transaction flow mirrors traditional aggregation with key differences:
- Customer selects cryptocurrency payment at checkout
- The aggregator generates a unique payment address or invoice
- Customer sends crypto to that address
- The blockchain confirms the transaction
- The aggregator converts to the merchant's preferred currency (fiat or stablecoin)
- Merchant receives settlement, typically same-day
Crypto aggregators typically charge 0.5%–1% per transaction, compared to 2%–3.5% for card-based aggregators. Because blockchain transactions are irreversible, there is no chargeback mechanism: this eliminates friendly fraud for merchants but also removes a layer of consumer protection.
Stablecoin-based payments offer particularly fast settlement. Where card aggregators settle in one to three business days, stablecoin transactions on networks like Spark can settle in seconds with near-zero fees, making them attractive for merchants comparing payment rails.
Risks and Considerations
Account Freezes and Fund Holds
Because millions of sub-merchants share a single master account, the aggregator bears collective risk. Automated algorithms monitor for anomalies: sudden volume spikes, high chargeback rates, unusual transaction patterns, or flagged business categories. When triggered, freezes happen without warning and often without explanation until after the fact.
PayPal, for instance, can impose automatic 21-day holds on new accounts, and risk-based holds can last 21 to 180 days. This is the primary tradeoff of the aggregator model: the speed of onboarding comes with less account stability than a dedicated merchant account.
Rolling Reserves
Aggregators may withhold 5%–10% of transaction revenue for 90 to 180 days as a rolling reserve. This protects the aggregator and its acquiring bank from chargebacks, refunds, or sudden business closures. After the holding period, funds are released on a rolling basis. New merchants and higher-risk categories are more likely to face reserve requirements.
Chargeback Thresholds
Card networks flag merchants whose chargeback rate exceeds approximately 1% of transactions. For aggregators, this threshold applies at the master account level: a single bad actor among thousands of sub-merchants can put the entire portfolio at risk. Aggregators respond aggressively, sometimes terminating sub-merchants at chargeback rates well below 1% to protect the master account.
Regulatory Complexity
Payment aggregators must comply with PCI DSS requirements, including annual independent security audits and regular vulnerability scans. In the United States, aggregators that handle funds may also need federal registration with FinCEN and money transmitter licenses in up to 47 states. Crypto aggregators face additional complexity: in the EU, MiCA licensing is now required, and businesses like CoinGate have obtained both MiCA and Payment Institution licenses to operate.
Limited Control at Scale
Sub-merchants cannot negotiate pricing, control batch timing, or customize dispute handling. Terms are take-it-or-leave-it. As businesses grow, these limitations become more costly, and many eventually migrate to dedicated merchant accounts or register as their own payment facilitators for greater control and lower per-transaction costs.
This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.