A customer pays ₹1,000 on your website.
The payment is authorised in seconds. But before that ₹1,000 becomes money available to your business, several different entities can be involved: the gateway, acquiring bank, card network or UPI system, issuer—and, in many setups, a payment aggregator.
The easiest way to understand a payment aggregator is to follow what happens to that payment after the customer clicks Pay.
The payment is authorised in seconds. But before that ₹1,000 becomes money available to your business, several different entities can be involved: the gateway, acquiring bank, card network or UPI system, issuer—and, in many setups, a payment aggregator.
The easiest way to understand a payment aggregator is to follow what happens to that payment after the customer clicks Pay.
TL;DR
- A payment aggregator (PA) enables merchants to accept customer payments through one or more payment channels and subsequently settles the collected funds to merchants.
- Under RBI's 2025 framework, the main categories are PA-Online, PA-Physical and PA-Cross Border.
- A payment gateway provides technology for routing a payment transaction; a payment aggregator is involved in aggregation and settlement of merchant funds.
- When choosing a PA, check RBI authorisation, payment coverage, settlement, fraud controls, reconciliation and whether you need domestic, physical or cross-border acceptance.
What happens after a customer clicks Pay?
Take a typical online card transaction.
1. The customer chooses a payment method
The checkout may offer cards, UPI, net banking, wallets or other supported methods.
2. Payment information is routed
The gateway or payment technology securely sends the transaction into the relevant processing route.
3. The transaction is authorised
For a card payment, the issuer decides whether to approve or decline the transaction. For UPI, the payment follows the applicable UPI flow.
4. The payment aggregator handles the merchant collection flow
RBI's current framework defines a PA around aggregating customer payments to merchants through one or more payment channels and subsequently settling the collected funds to those merchants.
5. The merchant receives settlement
The PA settles eligible funds to the merchant according to the applicable settlement arrangement.
So the aggregator is not simply a checkout page or a piece of routing software. It sits in the collection-and-settlement layer of the merchant payment flow.
Payment aggregator vs payment gateway
The two terms are often used interchangeably, but they describe different functions.
| Payment aggregator | Payment gateway | |
|---|---|---|
| Primary role | Aggregates customer payments and settles merchants | Routes/facilitates transaction information |
| Handles merchant funds | Yes, as part of the aggregation/settlement model | Typically no |
| Merchant onboarding | Part of the PA's regulated responsibilities | Not inherently the same function |
| RBI PA authorisation | Applicable to non-bank PAs under the PA framework | A pure gateway is a technology layer |
A single payment company may provide both gateway technology and aggregation services, which is why the distinction can become blurred commercially.
The three payment aggregator categories that matter in 2026
RBI consolidated payment-aggregator regulation in the Reserve Bank of India (Regulation of Payment Aggregators) Directions, 2025.
The framework recognises different PA models based on how and where payments are collected.
PA-Online
PA-Online, or PA-O, covers online/e-commerce payment aggregation where the customer and payment instrument are not physically present together at the point of transaction.
Think ecommerce checkout, online subscriptions or digital-service payments.
PA-Physical
PA-Physical, or PA-P, covers face-to-face or proximity payment aggregation.
This is relevant to in-person merchant acceptance where the payment device and instrument are physically present in proximity.
PA-Cross Border
PA-Cross Border, or PA-CB, handles eligible cross-border payment aggregation for merchant transactions under the applicable FEMA framework.
It can cover inward collections into India and, where authorised, outward flows.
This is a much more useful classification than treating "banks" and "third-party providers" as two competing product types.
Do payment aggregators need RBI authorisation?
For non-bank entities carrying on payment-aggregator business, RBI authorisation is a core regulatory requirement.
The 2025 Directions also cover areas including:
- merchant due diligence
- governance and risk management
- dispute management
- fraud and security controls
- escrow/collection-account operations
- merchant settlement
Banks providing PA services are treated differently under the authorisation framework, so merchants should verify the actual regulatory status and category of the provider they plan to use.
Why does merchant onboarding take more than an API key?
A PA is not only integrating your checkout.
It must understand who the merchant is and what business it is collecting money for.
That is why onboarding can involve:
- business identity and KYC
- bank-account verification
- website/app checks
- nature of products or services
- prohibited/restricted-business screening
- beneficial-owner or authorised-signatory information where applicable
This due diligence protects the payment ecosystem and is part of the PA's regulatory responsibility.
What should a business compare before choosing a PA?
1. Which payment flows do you actually need?
Domestic online, physical acceptance, international payments—or a combination?
2. Which payment methods matter?
Check the cards, UPI, wallets, bank methods and international methods your customers actually use.
3. How are funds settled?
Compare settlement timelines, reporting and visibility rather than assuming every PA settles in "1–3 days".
4. What happens when payments fail?
For online and international cards, routing, authentication, issuer messaging and fraud controls can materially affect success rates.
5. Can finance reconcile the money?
Look for transaction IDs, settlement reports, refunds, fee visibility and payment-status tracking.
6. Is the provider authorised for the flow?
A domestic PA authorisation should not automatically be treated as permission to handle cross-border aggregation.
Where PayGlocal fits
PayGlocal currently holds RBI authorisation as:
- Payment Aggregator – Online (PA-O)
- Payment Aggregator – Cross Border – Inward & Outward (PA-CB-I&O)
Its RBI authorisation certificate is No. 250/2025.
For domestic online payments, that allows PayGlocal to operate within the PA-O framework. For international business flows, its PA-CB authorisation supports cross-border inward and outward payment aggregation.
PayGlocal's cross-border stack also includes international cards, alternate payment methods, recurring payments and Multi-Currency Accounts for local collection.
