Payment Aggregator
What Is a Payment Aggregator? Definition and How It Works
Definition
A payment aggregator is an entity that pools multiple merchants under a single master merchant account with an acquiring bank, enabling sub-merchants to accept card payments without establishing their own direct acquiring relationships.
How it works
An aggregator holds a single merchant account with the acquirer and onboards individual businesses as sub-merchants under that account. Transactions from all sub-merchants are processed under the aggregator's merchant ID (MID), with the aggregator responsible for compliance, underwriting, and settlement to each sub-merchant.
The sub-merchant does not interact with the acquirer directly. The aggregator handles underwriting (assessing the business for fraud and chargeback risk), compliance (KYC/AML checks, scheme registration obligations), and settlement (receiving funds from the acquirer and distributing to sub-merchants after deducting fees).
Onboarding is the main commercial advantage for sub-merchants: aggregators can onboard a business in hours compared to weeks for direct acquiring. The aggregator absorbs the compliance and integration cost centrally, making payment acceptance accessible to businesses that would not qualify for or afford a direct acquiring relationship.
The trade-off is that the aggregator, not the sub-merchant, is the acquiring bank's client. All transactions appear to the acquirer under the aggregator's MID. This limits sub-merchant visibility at the scheme level, restricts the ability to negotiate custom MDR, and means that chargeback or fraud events across the sub-merchant base affect the aggregator's standing with its acquirer.
Why it matters
Aggregator pricing is typically blended and non-negotiable at low volume: aggregators set flat-rate pricing that bundles interchange, scheme fees, and margin. This is convenient for small merchants but does not scale cost-effectively; higher-volume merchants pay above-market effective MDR under blended aggregator pricing.
Chargeback liability is concentrated at the aggregator level: an aggregator is responsible for all chargebacks across its sub-merchant portfolio. Aggregators with poor sub-merchant underwriting face elevated chargeback ratios that can trigger scheme monitoring programs, and may terminate sub-merchant relationships if their chargeback contribution is disproportionate.
Sub-merchants have limited visibility and control: operating under an aggregator's MID means the sub-merchant has no direct acquirer relationship, no access to scheme-level data, and limited ability to negotiate terms. Moving to direct acquiring later requires a new integration and potentially losing stored card credentials.
Aggregators must comply with scheme registration requirements: Visa and Mastercard require aggregators to register as payment facilitators (PayFacs) and maintain specific compliance obligations for sub-merchant onboarding. Non-registered aggregators operating at scale face scheme fines and termination.
With PXP
PXP supports merchants operating as payment facilitators, providing the acquiring infrastructure and compliance framework needed to onboard sub-merchants. PXP's platform handles sub-merchant risk monitoring, settlement distribution, and scheme reporting obligations for merchants running PayFac models.
Frequently asked questions
What's the difference between a payment aggregator and a payment facilitator?
The terms are often used interchangeably, but in scheme terminology a payment facilitator (PayFac) is the formally registered entity that operates an aggregation model under Visa and Mastercard rules.
When should a merchant move from an aggregator to direct acquiring?
The inflection point is typically around $1-5M in annual card volume, where the cost difference between aggregator blended pricing and direct interchange-plus pricing becomes material. The move also makes sense when the merchant needs features not available under aggregation, custom routing, direct scheme access, or specific chargeback management capabilities.
What compliance obligations does an aggregator have for its sub-merchants?
Aggregators must conduct KYC checks on sub-merchants at onboarding, perform ongoing monitoring for suspicious transaction activity, maintain AML compliance, and report sub-merchants to card schemes in countries where scheme registration is required. Aggregators are liable for their sub-merchants' scheme rule violations, including chargeback ratio breaches.
Can sub-merchants under an aggregator be listed separately by card networks?
In some cases, yes. Visa's Merchant Registration Program and similar Mastercard requirements mandate that sub-merchants in certain high-risk categories be registered directly with the scheme, even when operating under an aggregator's MID. Registration requirements vary by merchant category code and transaction volume.
Revolutionize your business with PXP
Take complete control of your commerce and payments with one platform.
Get Started