What Is a Payment Aggregator? Meaning, PG Difference & RBI Rules Explained
Highlights:
- Understand how payment aggregators handle and pool merchant funds, requiring RBI authorisation under the Payment and Settlement Systems Act
- Learn the key difference between payment aggregators and payment gateways in fund handling and merchant onboarding
- Discover RBI's net worth requirements: ₹15 crore at application, rising to ₹25 crore by Year 3
- Explore the three PA categories (PA-O, PA-P, PA-CB) and the September 2025 consolidated Master Directions framework
Introduction
You're setting up online payments for your business. One provider calls itself a "payment gateway," another a "payment aggregator." Both promise seamless transactions, but the terms sound interchangeable. Here's what actually separates them: payment aggregators handle your money directly, pooling funds before settling into your account. Gateways simply route transaction data without touching funds. This fundamental difference shapes everything from regulatory oversight to how quickly you receive payments. With 46 RBI-authorised online payment aggregators operating as of March 2025, understanding what they do and how they're regulated helps you choose the right payment infrastructure for your business.
What Is a Payment Aggregator?
A payment aggregator is a service provider that collects, pools, and transfers payments to merchants without requiring individual merchant bank accounts. Unlike traditional payment processors, aggregators handle funds directly—receiving customer payments into a master merchant account and then settling to your business account on a T+1 basis (the next business day after the transaction). This fund-handling capability requires RBI authorisation under the Payment and Settlement Systems Act, 2007.
Payment aggregators enable faster merchant onboarding; you can start accepting payments within hours, rather than spending weeks setting up dedicated merchant accounts with banks. They aggregate multiple merchants under one umbrella, distributing transaction processing infrastructure and compliance costs across their merchant base. For businesses, this means lower entry barriers to digital payments and simplified technical integration.
Payment Aggregator vs. Payment Gateway: Key Differences
| Aspect | Payment Aggregator | Payment Gateway |
|---|---|---|
| Fund Handling | Handles and pools merchant funds | Routes transaction data only; never touches funds |
| Merchant Account | Uses a shared master merchant account | Requires an individual merchant account with a bank |
| RBI Authorisation | Mandatory for non-bank entities | Not required (technology provider) |
| Onboarding Speed | Same-day to 48 hours | 1-2 weeks (bank account setup) |
| Typical Use Case | SMBs, startups, and D2C brands needing quick deployment | Enterprises with existing banking relationships |
The core distinction: aggregators physically receive customer payments before settling to you, creating regulatory obligations. Gateways act as pure technology conduits, passing transaction instructions between customer banks and your merchant account without intermediating funds.
Types of Payment Aggregators in India
RBI categorises payment aggregators into operational types:
By Business Model:
- Bank Payment Aggregators: Operated by existing banks using their banking licence—no separate RBI authorisation needed
- Third-Party Payment Aggregators: Non-bank entities requiring explicit RBI authorisation
By Transaction Channel (September 2025 Master Directions):
- PA-O (Online): E-commerce and digital transactions
- PA-P (Physical): Face-to-face, POS, offline payments
- PA-CB (Cross-Border): Import/export transaction handling
Each category requires separate authorisation. A PA-O licence doesn't permit offline payment aggregation—businesses must verify their provider's licence type matches their payment acceptance channels.
RBI Rules for Payment Aggregators
On September 15, 2025, RBI issued consolidated Master Directions replacing the fragmented 2020-2023 guidelines. Key requirements:
Capital Requirements:
- ₹15 crore minimum net worth at application
- ₹25 crore by the end of the third financial year after authorisation
- Ongoing maintenance of ₹25 crore thereafter
This capital threshold ensures only financially stable entities handle merchant funds, reducing the risk of settlement failures.
Compliance Mandates:
- PCI DSS compliance mandatory for card payment data protection
- Settlement timelines: Maximum T+1 (next business day) for fund transfer to merchant accounts
- Merchant KYC: Aggregators must verify merchant identity and business legitimacy before onboarding
For businesses, this means choosing an RBI-authorised aggregator guarantees regulatory compliance, standardised settlement timelines, and security frameworks—without implementing them yourself.
Choosing Payment Infrastructure for Your Business
Verify your provider's RBI authorisation status before onboarding. As of March 2025, 46 online payment aggregators held authorisation—up from 22 in March 2024, reflecting rapid regulatory progress.
Payment aggregators suit businesses needing rapid deployment without complex bank account setups. The master merchant account model handles compliance, security, and multi-payment method integration. Settlement cycles of T+1 ensure predictable cash flow—Monday's ₹2 lakh revenue reaches your account by Tuesday evening.
Understanding aggregator regulations helps you evaluate providers beyond features and pricing, ensuring your payment infrastructure meets RBI standards while supporting business growth.
Key Takeaways for Merchants
Payment aggregators fundamentally differ from gateways through direct fund handling, creating regulatory obligations but enabling faster merchant onboarding. RBI's September 2025 Master Directions establish clear capital requirements (₹15-25 crore net worth), PCI DSS compliance mandates, and standardised T+1 settlement timelines. With 46 authorised aggregators serving diverse business needs, verify your provider's RBI status and licence category to ensure compliance and reliable settlement cycles.
FAQs
1. What is the main difference between a payment aggregator and a payment gateway?
Payment aggregators handle and pool merchant funds requiring RBI authorisation, while payment gateways only provide technology to route payment data without touching funds. Aggregators enable faster merchant onboarding without individual bank accounts.
2. Do payment aggregators need an RBI licence in India?
Yes. Non-bank payment aggregators must obtain authorisation from the RBI under the Payment and Settlement Systems Act, 2007. Bank-operated aggregators use existing banking licences. As of March 2025, 46 online PAs have been authorised.
3. What is the minimum net worth required to become a payment aggregator?
₹15 crore at application to RBI, increasing to ₹25 crore by the end of the third financial year after authorisation, and maintained ongoing. This ensures financial stability for handling merchant funds.
4. What are the three types of payment aggregators regulated by RBI?
PA-O (Online) for e-commerce transactions, PA-P (Physical) for face-to-face/POS payments, and PA-CB (Cross-Border) for import/export transactions. Each requires separate authorisation based on transaction channels.
5. How quickly do payment aggregators settle funds to merchants?
RBI directions specify T+1 settlement (next business day after transaction date). This is faster than older T+2 or T+3 cycles, improving merchant cash flow predictability.
6. Is PCI DSS compliance mandatory for payment aggregators?
Yes. RBI Master Directions mandate payment aggregators to ensure PCI DSS compliance and review it during merchant onboarding. This protects card payment data for merchants and customers without merchants implementing standards themselves.
