Payment Aggregator vs Payment Gateway: Key Differences
TL;DR - Summary
- What is a payment aggregator? - A payment aggregator lets businesses accept payments through a single platform and typically manages merchant onboarding, payment processing, and settlement.
- What is a payment gateway? - A payment gateway securely transmits payment information between the merchant and the payment infrastructure and returns the transaction's approval or decline.
- What is the difference between a payment aggregator and a payment gateway? - A payment aggregator manages payment collection and settlement, while a payment gateway primarily handles the secure transmission of payment data.
- How does the RBI regulate payment aggregators and gateways? - The RBI authorises and regulates payment aggregators that handle funds, while payment gateways that only provide technology and do not handle funds fall outside the Payment Aggregator Directions.
- Which one does a business need? - The choice depends on the business's transaction volume, banking setup, payment requirements, and need for operational control. For international payments, businesses should also check whether the provider supports and is authorised for the specific cross-border transaction.
What Is a Payment Aggregator?
A payment aggregator is a payment service provider that allows businesses to accept different types of digital payments through a single platform. Instead of setting up separate arrangements for cards, UPI, net banking, and wallets, a merchant can connect these payment options through one integration.
The aggregator typically manages much of the payment process, including:
- Merchant Onboarding and KYC: Verifies the business and completes the required checks before payments can be accepted.
- Payment Processing: Routes each transaction to the appropriate bank, card network, or UPI infrastructure.
- Risk Management: Applies fraud and transaction-monitoring controls as part of payment processing.
- Fund Settlement: Receives and processes the collected funds before transferring the merchant's share to its designated bank account according to the applicable settlement cycle.
This model reduces the need for merchants to establish separate payment relationships with multiple banks and payment networks. Common cross-border payment aggregators in India include Razorpay, PayU, and Cashfree Payments, while Stripe provides comparable payment aggregation and processing services in many international markets.
What Is a Payment Gateway?
A payment gateway is the technology that securely carries payment information between a merchant's checkout and the financial institutions involved in approving a transaction. It handles the exchange of payment data and the authorisation response. The actual movement of funds takes place through the banking and payment network.
When a customer makes a payment, the gateway:
- Encrypts the payment information before transmitting it.
- Sends the transaction details through the relevant acquiring bank and card network.
- Receives the approval or decline from the customer's issuing bank.
- Passes the result back to the merchant's website or application.
Payment Gateway vs Payment Aggregator
A traditional gateway model generally involves the merchant maintaining a direct merchant relationship with an acquiring bank. The acquiring bank may assess the business during onboarding and determine applicable commercial terms.
This arrangement can give larger merchants greater control over their acquiring relationship and, depending on the setup and transaction volumes, more scope to negotiate pricing.
A standalone gateway is primarily a payment-data transmission layer. It is not necessarily responsible for combining multiple processors, automatically switching failed transactions to another provider, or consolidating payment data from different sources. Those capabilities may be offered separately by other payment infrastructure providers.
Who Is Involved in a Gateway Transaction?
Three key parties involved in a gateway transaction are:
- Acquiring Bank: Processes card payments for the merchant.
- Issuing Bank: Provides the customer's card and decides whether to approve the transaction.
- Card Network: Connects the issuing and acquiring sides of the card transaction, such as Visa or Mastercard.
Examples of gateway technology and bank-operated gateways include Mastercard Payment Gateway Services (MPGS), HDFC Bank, ICICI Bank, and Axis Bank.
In India, the term payment gateway is often used broadly for online payment services. However, it is useful to distinguish between a payment aggregator arrangement and a gateway used with a merchant's acquiring relationship, because the responsibilities for onboarding, payment processing, and settlement can differ between the two.
Related: 2D vs 3D payment gateway.
Payment Aggregator vs Payment Gateway: What Are the Key Differences?
The main difference is who manages the payment relationship and operational responsibilities. A payment aggregator brings merchant onboarding, payment processing, and settlement into one provider, while a payment gateway primarily provides the technology for securely transmitting payment information between the merchant and the payment network.
| Dimension | Payment Aggregator | Payment Gateway |
|---|---|---|
| Primary role | Processes payments and manages settlement for merchants | Transfers payment information securely between the merchant and payment infrastructure |
| Merchant account required | Generally no separate acquiring relationship is required from the merchant | Traditionally used with the merchant's own acquiring relationship |
| Fund handling / settlement | Manages the collection and settlement process | Does not itself hold the merchant's funds |
| Bank relationship | Maintains the acquiring relationships used to process merchant payments | Merchant has a direct relationship with the acquiring bank in the traditional model |
| Regulatory responsibility | Key payment and settlement obligations sit with the regulated aggregator | Responsibilities are distributed between the merchant, gateway, and acquiring bank |
| Best suited for | Businesses seeking a simpler setup and faster onboarding | Businesses that want greater control over their acquiring relationship and commercial terms |
How the Two Models Handle a Payment
The movement of money and payment information differs between the two arrangements:
Payment aggregator
Gateway with a direct acquiring relationship
The aggregator generally takes care of merchant onboarding and required checks, whereas a direct acquiring arrangement can involve more extensive onboarding and underwriting between the merchant and its acquiring bank.
Aggregators may also provide services such as fraud monitoring, payment analytics, recurring billing, reporting, and automated settlement alongside payment processing.
The convenience comes with some dependency. If an aggregator changes its policies, delays settlement, or takes compliance action on an account, merchants using its infrastructure can be affected. A direct gateway arrangement gives the business more control over its banking relationship, but also places more operational responsibility on the business.
The distinction can become blurred because some providers, including PayU and PhonePe, offer multiple payment infrastructure capabilities. The terms may therefore be used interchangeably in everyday conversations even though the underlying models are different.
Let’s consider a Bengaluru-based UX freelancer receiving a $3,000 payment from a US client. Here is how it may look:
- Gateway-Led Arrangement: If the freelancer has a direct merchant and acquiring relationship, the gateway primarily facilitates the payment-data exchange. The freelancer's bank and acquiring arrangements handle the relevant settlement and currency conversion.
- Aggregator Arrangement: The freelancer onboards with the aggregator, which manages the payment flow and settlement under its infrastructure. This can reduce the number of separate banking and payment relationships the freelancer needs to manage.
The aggregator model can therefore be simpler for smaller businesses, while a direct gateway arrangement may provide greater control where transaction volumes justify the additional setup and operational responsibility.
The key difference is who takes care of the payment process. With an aggregator, one provider usually handles onboarding, processing and settlement for you. With a gateway, the business holds a more direct relationship with its acquiring bank.
How Does RBI Regulate Payment Aggregators and Gateways in India?
The RBI regulates payment aggregators through authorisation, capital, escrow, KYC, security, and reporting requirements. Payment gateways are treated differently because they provide payment technology without handling funds and are outside the scope of the RBI's 2025 PA Directions, although the framework recommends that they follow specified baseline technology and security practices.
Licensing and Capital Requirements
- Non-Bank PAs: A non-bank entity must obtain RBI authorisation to operate as a Payment Aggregator. Banks can undertake PA activities under their existing banking framework without separate PA authorisation.
- Net Worth: An entity seeking PA authorisation must have at least ₹15 crore in net worth when applying and reach ₹25 crore by the end of its third financial year after authorisation. The applicable minimum must then be maintained on an ongoing basis.
Fund Handling and Escrow
- Escrow Accounts: Non-bank PAs must keep merchant funds in a separate escrow account with a scheduled commercial bank. PA-CB transactions use designated inward or outward collection accounts, as applicable.
- Settlement: Merchant settlement timelines must be clearly specified in the agreement between the PA and merchant and must be fair and transparent. The RBI framework also sets requirements for how escrow funds can be credited and debited.
Security and Data Protection
- Payment Data: PAs must follow RBI requirements for storing payment-system data in India.
- Security Controls: PAs must maintain information-security, fraud-prevention, and risk-management systems, including applicable PCI-DSS and PCI-SSF requirements.
- Audits: PAs must undergo an annual system audit, including a cybersecurity audit, conducted by CERT-In-empanelled auditors. The framework also sets broader technology and security controls.
Merchant Onboarding and KYC
- Merchant Due Diligence: PAs must conduct customer due diligence under the RBI's KYC framework and carry out background and antecedent checks on merchants.
- FIU-IND Registration: Non-bank PAs must register with the Financial Intelligence Unit-India (FIU-IND) and meet the applicable reporting requirements under the KYC/AML framework.
Payment gateways therefore have a different regulatory position from payment aggregators. The RBI's 2025 Directions define a PG as a technology provider that facilitates payment processing without handling funds, and specifically state that PGs do not fall within the scope of those PA Directions. However, the Directions recommend that PGs adopt the prescribed baseline technology-related recommendations.
Payment Aggregator or Payment Gateway: Which One Does Your Business Need?
The choice depends on your transaction volume, internal capabilities, banking setup, and payment requirements. For Indian businesses, the decision also changes if you receive money from overseas and need appropriate cross-border settlement and remittance documentation.
- Early-Stage or Lower-Volume Businesses: A payment aggregator is usually simpler to set up because one provider can handle onboarding, payment processing, and settlement without requiring the business to establish separate acquiring relationships.
- High-Volume Businesses: A direct gateway paired with an acquiring bank can provide greater control over the banking relationship and potentially better commercial terms when transaction volumes justify negotiation. This model also requires more technical and operational involvement.
- Businesses Using Multiple Payment Providers: Companies managing several gateways, international payments, or high-volume recurring transactions may benefit from a payment orchestration layer that coordinates multiple payment connections. This is generally more relevant to mature payment operations.
What About Indian Businesses Receiving International Payments?
For Indian exporters and freelancers, the more important question is whether the chosen provider can support the specific type of overseas payment they receive.
Before selecting a payment gateway provider, check:
- Whether it supports foreign inward remittances in the currencies and payment methods your customers use.
- Whether it is authorised to provide the relevant cross-border payment service in India.
- What FIRA, FIRS, e-FIRA, FIRC, or other remittance documentation it provides for your transaction.
- How it handles currency conversion and settlement into your Indian bank account.
- Whether the documentation and transaction records support your applicable GST, FEMA, banking, and export requirements.
A domestic payment aggregator may be perfectly suitable for collecting INR payments from Indian customers but may not provide the same capabilities for international receipts. Therefore, Indian exporters should evaluate the specific cross-border product, rather than assuming that every service offered by a payment provider has the same functionality.
Is GPay a payment aggregator?
No. Google Pay is primarily a consumer-facing UPI payment application that enables users to make and receive payments through UPI. It is not itself a payment aggregator that onboards merchants, handles pooled merchant funds, and settles them under the payment-aggregator framework.
Is Paytm a payment aggregator or payment gateway?
Is Razorpay a payment aggregator?
Is UPI a payment aggregator?
Can a payment gateway work without a payment aggregator?
Which is better for receiving international payments in India?
