---
title: "Payment Aggregator"
url: "https://mahouse.world/glossary/payment-aggregator"
type: "glossary term"
topic: "Payments infrastructure"
author: "Ihor Vlasov"
reviewed: "2026-09-20"
published: "2026-08-10"
---

# Payment Aggregator

A payment aggregator is a provider that accepts payments on behalf of many merchants under its own merchant account or licence and settles the money on to them, so that each merchant need not have an account of its own — the model of early PayPal, of marketplaces collecting for sellers, and of the emerging-market aggregators that give small merchants cards, wallets and transfers through one integration. The payment facilitator is its regulated, registered form.

**Also known as:** Aggregator, Payment aggregation, Merchant aggregator

## Key facts

- **Used at:** marketplaces and platforms collecting for sellers; small-merchant acceptance where individual merchant accounts are impractical; multi-method acceptance (cards, wallets, bank transfers, cash vouchers) in markets with fragmented payments
- **Binding:** the aggregator is the merchant of record to its acquirer and must hold the licences its activity requires — a payment institution or e-money licence in the EU and UK where it handles funds, money-transmitter licences in the US; the schemes require registration as a payment facilitator for card aggregation; several regulators (India's RBI, for one) have written specific aggregator rules
- **Typical economics:** a blended fee to merchants (2–3% plus a fixed amount), the aggregator paying the acquirer and method providers below it; settlement to merchants on the aggregator's own schedule, which funds a float
- **Typical risk:** the aggregator holds merchants' money between collection and payout, so its solvency and safeguarding are the merchants' exposure; and it bears its merchants' chargebacks and fraud to its acquirer
- **Parties:** the aggregator, its acquirer and method providers, its merchants, their customers, and the regulators of the funds it holds

## How a payment aggregator works in practice

An online marketplace lets 20,000 sellers list goods. Buyers pay the marketplace, not the seller: the marketplace has the merchant account, the buyer's card is charged under the marketplace's name, and the marketplace pays each seller its share, less commission, on a schedule. The sellers never touch a merchant account, an acquirer or PCI; the marketplace does all of it, and holds the money in between. That is aggregation, and it is why regulators care: the marketplace is handling other people's funds and needs a licence to do so, or an exemption (the EU's commercial-agent exemption is narrow and contested), and it must safeguard what it holds.

The scheme rules made this formal. Aggregating card payments for others is payment facilitation: the aggregator registers with the schemes, underwrites its sub-merchants, passes their identity in each transaction, and bears their chargebacks. In emerging markets the aggregator model went further — one integration for cards, mobile wallets, bank transfers and cash-payment vouchers — and became the dominant way small merchants accept anything; those aggregators are now licensed payment institutions with their own rules.

For an acquirer of an aggregator the questions are the licence, the safeguarding of merchant funds, the sub-merchant underwriting, and the acquirer agreement's change-of-control clause — the same as a facilitator's, plus whatever the local regulator has added.

## Example

A marketplace in Southeast Asia aggregates payments for 60,000 sellers: cards through a local acquirer, three mobile wallets, bank transfers and convenience-store cash codes, through one checkout. It charges sellers 2.8%, pays about 1.6% to the method providers, and holds seller funds for seven days before payout — a float averaging $18m. Its regulator's new payment-aggregator rules require a licence, a $2m capital minimum, safeguarding of seller funds in an escrow account with a bank, and settlement to sellers within a set period. Compliance costs $1.5m and the float's investment income ends. A strategic buyer, a regional payments group, values the licence at more than the float was worth and buys the marketplace's payments arm for $90m — the licence, the 60,000 sellers and the six integrations it would otherwise build.

## Common mistakes

- Aggregating payments for others without the licence the funds require, and relying on an exemption a regulator reads narrowly.
- Merchant funds commingled with the aggregator's own, so a failure takes the merchants down.
- Sub-merchant onboarding with no underwriting, so the aggregator carries chargebacks it never priced.
- Settlement schedules built to fund the aggregator's float rather than the merchants' cash flow.
- Confusing aggregator, facilitator, PSP and gateway in a contract, when the liability sits in exactly one place.

## Related terms

- [Payment Facilitator](https://mahouse.world/glossary/payment-facilitator.md)
- [Payment Service Provider](https://mahouse.world/glossary/payment-service-provider.md)
- [Merchant Account](https://mahouse.world/glossary/merchant-account.md)
- [Acquirer](https://mahouse.world/glossary/acquirer.md)
- [Payment Gateway](https://mahouse.world/glossary/payment-gateway.md)
- [Split Payment](https://mahouse.world/glossary/split-payment.md)

— Ihor Vlasov, M&A FinTech Expert. Last reviewed 2026-09-20. https://mahouse.world/authors/ihor-vlasov