8 min read
Payment Aggregator vs. Payment Facilitator: Same Thing or Not?
Payment aggregator vs. payment facilitator: why the terms overlap, where they actually differ (merchant IDs, registration, regulation), how aggregators compare with processors and PSPs, and which one you're really using.

Quick answer: In card-network terms, a payment facilitator (payfac) is a specific, registered kind of payment aggregator. Both let many businesses accept cards under one master merchant account instead of each getting its own. "Aggregator" is the older, broader word for that model. "Payment facilitator" is the formal role Visa and Mastercard created with registration, sponsor-bank oversight and sub-merchant rules attached. In everyday use the two words mean nearly the same thing. The exception is regulated markets like India, where "payment aggregator" is a licensed category with rules of its own.
Most articles on this topic draw a sharp line between the two and then disagree with each other about where it goes. Some say aggregators give every merchant a shared ID and payfacs give each one a sub-ID. Others say a payfac is a type of aggregator. Stripe's own explainer takes the second view. The reason for the confusion is historical, and once you see it the distinction becomes easy.
Why two words exist for one model
Before about 2010, card networks didn't love the idea of one company processing for thousands of small businesses under a single account. PayPal did it anyway, and so did a handful of others, and the industry called them aggregators. They were tolerated more than formally recognized. Merchants underneath them were barely visible to the acquiring bank.
Then Square and Stripe made the model mainstream. Visa and Mastercard responded by writing formal rules: register as a payment facilitator through a sponsoring acquirer, identify every sub-merchant, monitor them, and move the big ones to their own accounts. The payfac was born out of the aggregator, with paperwork.
So when someone asks whether an aggregator and a payfac are different, the honest answer is yes on paper and mostly no in practice. Stripe, Square and PayPal get called both, and both labels are right.
Payment aggregator vs. payment facilitator at a glance
| Payment aggregator (broad term) | Payment facilitator (network role) | |
|---|---|---|
| Core idea | Many businesses process under one master account | Same |
| Formal card-network status | Not a defined role on its own | Registered with Visa/Mastercard via a sponsor acquirer |
| Sub-merchant identification | Varies; older setups were loose | Each sub-merchant identified and reported |
| Underwriting | Light, done by the aggregator | Done by the payfac under network and sponsor rules |
| Size limits | Not defined | Large sub-merchants must get a direct agreement (historically around $1M annual Visa volume) |
| Regulation | In some countries (e.g. India) a licensed category | Card-network rules plus local money-transmission law |
| Examples | PayPal, Stripe, Square, Razorpay | Stripe, Square, Shopify Payments, Adyen for Platforms |
Where the real differences show up
Merchant IDs come first, because that's what most comparison articles focus on. Under a formal payfac program, each sub-merchant gets its own identifier under the payfac's master account. That's why your Stripe charges show your business name on the customer's statement. Loose aggregator setups historically reported all merchants under the aggregator's single identity, which is why PayPal statement lines still start with "PAYPAL *" before a shortened merchant name. Today the gap has mostly closed, since network rules push everyone toward identifying sub-merchants.
Registration is the second. A payfac has a sponsor bank and a registration with each card network, along with obligations like KYC, transaction monitoring and annual reviews. We list them in our guide to payment facilitator compliance requirements. "Aggregator" as a word carries no such obligations.
Regulation is the third, and it varies by country. In India, the Reserve Bank of India licenses "payment aggregators" as a distinct category, with capital requirements and rules on how merchant funds are held. A company describing itself as a payment aggregator in India is making a specific regulatory claim. In the US or UK, the same phrase is usually just marketing language for a payfac.
Payment aggregator vs. payment processor

This one's easier. The processor is the technical plumbing that routes authorizations and settlements between the merchant's side and the card networks. An aggregator (or payfac) is a business model built on top of a processor that gets merchants accepting payments without their own merchant accounts.
Stripe is an aggregator that runs its own processing in many markets. A small payfac might use Fiserv or Worldpay as its processor and never touch the network messages itself. If you signed up online and took a payment the same day, you're with an aggregator. If you went through underwriting and received your own merchant ID, you have a direct processing relationship. Our payfac vs. payment processor guide maps the full stack.
Payment aggregator vs. payment service provider
"PSP" is the broadest term of the three. It covers any company that helps businesses take payments, whether it gives you your own merchant account or puts you under an aggregated one. Adyen is a PSP that offers direct merchant accounts to enterprises and a payfac-style product to platforms. Stripe is a PSP that aggregates most of its users.
Every aggregator is a PSP. Not every PSP is an aggregator. None of them make you any less the legal seller, which is the gap a merchant of record fills (see merchant of record vs. payment service provider).
Which are you actually using?

Two questions settle it. Did you get your own merchant ID after the bank reviewed your financials? Then you're on a direct account, probably through an ISO. Did you sign up and start selling the same day? Then you're a sub-merchant under an aggregator, and in the US or Europe that aggregator is almost certainly a registered payfac.
For a business under a few hundred thousand dollars a year in card volume, the aggregated model is usually the right one, and the label doesn't matter. The trade-offs show up later. Payouts can be held, accounts can be closed quickly, and flat pricing gets expensive at volume. Those are the same trade-offs whether the provider calls itself an aggregator or a facilitator.
Frequently Asked Questions
Is a payment aggregator the same as a payment facilitator?
Mostly. Both let many businesses accept payments under one master merchant account. "Payment facilitator" is the formal card-network role with registration and sponsor-bank oversight. "Payment aggregator" is the older, broader term, though in some countries, such as India, it's a regulated licence of its own.
Is a payfac a type of aggregator?
Yes. A payfac is a formalized aggregator. It is registered with Visa and Mastercard through a sponsoring acquirer and has to identify, underwrite and monitor every sub-merchant under its master account.
Is Stripe a payment aggregator or a payment facilitator?
Both terms apply. For most users, Stripe operates as a registered payment facilitator. Businesses are sub-merchants under its account rather than holding their own merchant IDs, which also fits the general definition of an aggregator.
What is the difference between a payment aggregator and a payment processor?
A processor is the technical layer that routes transactions between merchants and the card networks. An aggregator is a business model on top of processing that lets businesses take payments without their own merchant accounts. Some companies, like Stripe, do both.
What is the difference between a payment aggregator and a payment service provider?
A payment service provider is any company that helps businesses accept payments. An aggregator is a PSP that puts merchants under one shared master account. Some PSPs, like Adyen, offer both direct merchant accounts and an aggregated model.
Do payment aggregators handle sales tax or VAT?
No. Aggregators and payfacs process payments, but the business stays the legal seller and remains responsible for sales tax and VAT. A merchant of record is the model that takes on tax and legal-seller liability.
The bottom line
Use "payfac" when you mean the network-registered role and "aggregator" for the general model, and don't lose sleep over the overlap. What matters more is whether you need someone to carry the tax and compliance side of selling as well. If you sell software or digital products across borders, Comecero acts as your merchant of record for verified customers, after review, or runs billing on top of the processor you already use.




















