Skip to content

Payment Aggregator vs Third-Party PA: Key Differences

18 August 20251 min read
BANKING & FINANCEPaymentAggregator vsThird-Party PA:Key Differences18 August 2025safalsetu.com

Why in the news

IRCTC’s wholly-owned arm moved towards fintech; the platform now uses several outside aggregators plus its own gateway, iPay.

Key facts

  • PA: enables merchants to accept cards, UPI and wallets; holds customer money in a nodal/escrow account and pays merchants later.
  • Needs RBI authorisation under the Payment and Settlement Systems Act, 2007.
  • Third-Party PA: supplies technology linking merchants to banks or gateways, never touching funds.
  • No separate PA licence, yet RBI outsourcing and IT-security norms bind it.

Comparison

PointPAThird-Party PA
FundsCollects and settlesNone handled
RBI authorisationMandatoryNot required
Escrow accountMust keepNot applicable
ExamplesRazorpay, PayU, BillDeskJuspay (tech layer), Pine Labs as API only

Exam angle

  • Law: PSS Act, 2007.
  • Deciding test: handling of funds.

Test yourself

1. Under which law must a Payment Aggregator obtain RBI authorisation?

The notes cite the PSS Act, 2007.

2. What distinguishes a Third-Party Payment Aggregator from a Payment Aggregator?

A third-party PA only provides technology infrastructure.

3. Which IRCTC arm got RBI's in-principle approval to operate as a Payment Aggregator?

IRCTC Payments Limited received the approval.