Every time a customer taps “Pay Now” on an e-commerce site, transfers money via a fintech app, or settles a bill through a QR code — a Payment Aggregator (PA) is silently working in the background. Yet despite processing billions of rupees daily, the PA business remains one of the least understood segments in India’s financial services ecosystem, even among seasoned NBFC professionals.

This article demystifies the PA business — who they are, how they make money, and what it takes to build one. Payment Aggregators (PAs) represent an emerging opportunity for NBFCs to capture a share of India’s booming digital payments market, which is projected to exceed $10 trillion in transaction volume by 2026.

1. What Exactly is a Payment Aggregator?

A Payment Aggregator is a regulated intermediary that sits between merchants (businesses accepting payments) and the banking/payment network. Unlike a payment gateway — which is purely a technology pipe — a PA actually holds a nodal/escrow account, collects funds from customers on behalf of merchants, and settles those funds to merchant accounts. A Payment Aggregator is essentially a merchant onboarding and payment processing platform that enables businesses (especially SMEs and online merchants) to accept multiple payment modes—cards, UPI, wallets, net banking—through a single integration.

Simple way to think about it:

Merchant + PA + Bank = Customer paying ₹500 online → ₹500 collected by PA in escrow → ₹497 settled to merchant (PA retains ₹3 as processing fee).

The RBI, recognising the systemic importance of PAs, brought them under a formal licensing framework under the Payment and Settlement Systems Act, 2007, with detailed guidance consolidated in the Master Direction on Regulation of Payment Aggregators, 2025. Prior to these Directions, PA business used to be regulated by the Guidelines on Regulation of Payment Aggregators and Payment Gateways, 2020. This shift transformed PA from a lightly regulated tech business into a proper regulated financial intermediary — opening it as a credible business opportunity for well-capitalised entities, including NBFCs. Under erstwhile Guidelines, payment gateways (PG) business used to be governed by the said regulatory framework; however, under the revised directions, PGs remain outside the direct regulatory purview of the RBI as they do not handle funds and function purely as technology service providers enabling payment aggregation.

Payment Aggregator (PA) Transaction Flow:

Customer → Merchant Checkout → Payment Aggregator → Acquiring Bank → Issuing Bank → Authorization (✓/✗) → PA Escrow Account → Settlement → Merchant Account

2. Core Business Model: How PAs Actually Make Money

PAs act as intermediaries, pooling thousands of merchants under one “master account” with banks, then routing payments via UPI, cards, wallets, or net banking—eliminating the need for each merchant to negotiate separate bank deals. Revenue flows from:

1. Transaction Fees: A small percentage charged (0.5%-2%) on every, scaling massively with volume—top PAs handle billions daily.
2. Setup/Subscription Fees: One-time onboarding fees plus monthly dashboards for analytics
3. Value-Adds: Premium features like instant settlements, Payment analytics, fraud management tool

3. The Business Case: Why PAs Are Worth Serious Attention

The business economics of a scaled PA are compelling:

1. High operating leverage: Technology infrastructure is a largely fixed cost. Incremental volume flows almost directly to EBITDA.
2. Low credit risk: PAs do not lend in their core model; they process and settle. The balance sheet risk is settlement float, not credit.
3. Regulatory barrier to entry: The RBI licence requirement has effectively reduced the number of new entrants, protecting incumbents and serious new applicants.

4. How to Become a PA: The Business Essentials

While full procedural details are covered under RBI’s Master Directions, from a pure business standpoint, these are the key checkpoints typically evaluated by the RBI while granting authorisation:

1. Net Worth: RBI requires a minimum net worth of ₹15 crore at the time of application, rising to ₹25 crore by the end of the third financial year. This is a genuine capital commitment, not a token amount.
2. Technology Infrastructure: The PA must build or procure a robust payment switch, reconciliation engine, fraud and risk management system, and merchant dashboard.
3. Banking Relationships: A nodal/escrow account arrangement with a scheduled commercial bank is mandatory. Banking partnerships for acquiring card payments and UPI sponsorship are operationally critical.
4. Merchant Onboarding & KYC: RBI mandates risk-based merchant due diligence. Building a scalable, compliant merchant onboarding workflow is a key operational differentiator.
5. Go-To-Market Strategy: The PA market is competitive. New entrants must identify a niche — a specific merchant vertical (healthcare, education, B2B), geography, or product (e.g., credit-at-POS) — rather than attempting to compete head-on with Razorpay.

5. Challenges and Difficulties

1. Revenue Compression: Zero MDR on UPI significantly erodes the core transaction-based revenue stream.
2. Technology Complexity: Payments infrastructure requires continuous investment, not a one-time setup cost.
3. Market Competition: Dominated by well-funded incumbents, making differentiation and scale challenging.
4. Operational Risk: Exposure to fraud, chargebacks, and escrow management adds ongoing risk pressure.
5. Regulatory Overhead: Dynamic RBI guidelines necessitate constant monitoring and operational adjustments.
6. Path to Profitability: Achieving scale economics typically requires a long gestation period of 3–4 years.

6. PA vs. PG vs. TPAP: Clearing the Confusion

Payment Aggregators (PAs), Payment Gateways (PGs), and Third-Party Application Providers (TPAPs) play distinct roles in the payments ecosystem, though often confused. The confusion arises because companies like Google Pay, Razorpay or PhonePe operate in more than one of these roles simultaneously — but the underlying functions, risks, and regulatory obligations remain entirely distinct.

A Payment Gateway is purely a technology pipe; it encrypts and routes payment data between a merchant and a bank but never touches the money and therefore does not require RBI authorisation/license.

A Payment Aggregator is a licensed financial intermediary that actually collects customer funds into an escrow account and settles them to the merchant — it moves money, not just data- and is required to obtain license/authorisation from the RBI.

A TPAP (like PhonePe or Google Pay) is a consumer-facing UPI application built on NPCI’s rails; it provides the interface for initiating a transaction but holds no funds, with actual settlement happening bank-to-bank through a sponsor PSP bank and operates under NPCI approval rather than requiring a separate RBI authorisation like a PA.

7. The NBFC Opportunity: A Unique Strategic Fit

The Payment Aggregator model is not merely a payments business but a strategic enabler of deeper financial integration within the digital economy. For NBFCs, it presents a unique opportunity to move closer to the cash flows of their customers, unlocking real-time insights, improving credit decisioning, and creating new fee-based revenue streams. While the business itself operates on thin margins and demands strong technology and risk capabilities, its true value lies in its ability to anchor a broader ecosystem of embedded finance. PAs are not just a feature. For the right player, they are a platform.