Skip to main content

PROTAX INSIGHTS

Payment Gateway Integration Compliance: RBI and GST Requirements

Complete guide to payment gateway compliance in India: RBI Master Directions 2020, PA/PG registration, merchant KYC, 18% GST, data localisation, PCI-DSS, escrow norms for FY 2026-27.

Payment Gateway Integration Compliance: RBI and GST Requirements

Running an online business in India means touching the payments infrastructure every day, yet the regulatory framework governing that infrastructure remains poorly understood outside specialist fintech circles. Payment gateway compliance in India spans two distinct regulatory domains: RBI's oversight of payment system operations under the Payment and Settlement Systems Act, 2007, and GST obligations under the CGST Act, 2017 for the services that gateways and aggregators supply. Get either wrong and the consequences range from suspension of your payment processing rights to penalty proceedings under two separate statutes simultaneously.

This guide is written for three audiences: founders building fintech or e-commerce businesses who must choose and integrate the right payment partner; compliance teams at payment companies tracking what changed in the 2024 RBI updates; and businesses of any size that need to understand what their PA or PG is supposed to be doing on their behalf. Every factual claim is referenced to its governing statute, RBI circular, or GST council notification.

  • Payment Aggregators (PAs) that hold and settle funds require prior authorisation from RBI under the PSS Act, 2007; Payment Gateways (PGs) that only route technically do not
  • Minimum net worth for PA authorisation is ₹25 crore, with ongoing maintenance obligation (RBI Master Directions 2020, updated January 2024)
  • All payment data related to India transactions must be stored only in India (RBI circular DPSS.CO.PD No.1810/02.14.008/2017-18)
  • PA/PG services attract 18% GST under SAC 998433; merchants can claim ITC on these fees
  • Raw card numbers (PAN) cannot be stored by merchants or PGs; card-on-file tokenisation is mandatory from 1 October 2022
  • PAs are reporting entities under PMLA 2002 and must file STRs with FIU-IND for suspicious transactions

The Regulatory Architecture: Two Frameworks, One Ecosystem

Before diving into specifics, it helps to understand that payment gateway compliance in India sits at the intersection of two independent regulatory regimes that must both be satisfied simultaneously.

The first is the Reserve Bank of India (RBI) framework, anchored on the Payment and Settlement Systems (PSS) Act, 2007. This Act gives RBI the power to authorise, regulate, and supervise payment systems in India. Sections 4 and 7 of the PSS Act require entities operating payment systems to obtain prior authorisation from RBI. The detailed operational rules for payment aggregators and gateways are set out in the Master Directions on Payment Aggregators and Payment Gateways, first published on 17 March 2020 and significantly updated in January 2024 to add cross-border requirements and tighten merchant due diligence norms.

The second is the GST framework under the Central Goods and Services Tax Act, 2017 (CGST Act) and the Integrated Goods and Services Tax Act, 2017 (IGST Act). Payment services are classified as financial services and fall under the GST net. The rate, the classification, the place of supply, and the invoicing obligations all arise from these two Acts and the GST Council's rate notifications.

The core legal instruments governing payment gateway compliance in India are: Payment and Settlement Systems Act, 2007 (Sections 4, 7, 8, 26 for authorisation, operations, and penalties); RBI Master Directions on PA and PG (March 2020, updated January 2024) available at rbi.org.in; CGST Act, 2017 and IGST Act, 2017 for GST obligations; Prevention of Money Laundering Act, 2002 (PMLA) for AML obligations; Information Technology Act, 2000 and IT (Amendment) Act, 2008 for cybersecurity; and the PCI-DSS v4.0 standard maintained by the PCI Security Standards Council.

Payment Aggregators vs Payment Gateways: The Critical Distinction

The single most important concept in this entire compliance framework is the distinction between a Payment Aggregator and a Payment Gateway. The two terms are frequently confused, but the regulatory obligations that flow from each are entirely different.

A Payment Aggregator (PA), as defined in RBI's Master Directions, is an entity that: (a) receives payment instructions from a customer; (b) temporarily holds the funds collected from the customer; (c) settles those funds to the merchant after deducting its fee. The defining characteristic is fund holding. When your customers pay through an entity like Razorpay, CCAvenue, or PayU, those entities are acting as PAs because the money passes through their escrow accounts before reaching you.

A Payment Gateway (PG), on the other hand, merely provides the technical infrastructure to route the transaction between the customer, the card network or bank, and the merchant. A PG never holds funds. The money moves directly from the customer's bank to the merchant's bank, with the PG simply transmitting the transaction data and authentication. This is the model used by many bank-provided payment gateway services, where the bank itself holds any float.

Regulatory Consequences of the Distinction

  • PAs: Require prior authorisation from RBI under Section 7 of the PSS Act. Must maintain ₹25 crore net worth. Must hold funds in a designated escrow account. Must comply with all merchant KYC, AML/CFT, and reporting obligations. Subject to direct RBI supervision and audit.
  • PGs (technical only): No RBI authorisation required. Must register with an acquiring bank (which is an RBI-regulated entity). Must comply with data localisation and PCI-DSS requirements. Oversight is indirect, through the acquiring bank.

Most large Indian payment companies are both: they provide the technical routing infrastructure (PG function) and also aggregate and settle funds (PA function). In that combined role, all PA obligations apply in full.

RBI Authorisation Process for Payment Aggregators

If your business model involves holding customer funds before settling to merchants, you are operating as a PA and must be authorised by RBI. The authorisation process under the Master Directions works as follows.

Eligibility Criteria

An applicant for PA authorisation must be: a company incorporated in India under the Companies Act, 2013 (or 1956); have a minimum net worth of ₹25 crore at the time of application; have a business plan demonstrating technical capability to operate a payment system; and have directors who meet RBI's "fit and proper" criteria (no criminal record, no insolvency, adequate experience in payments/finance).

Application and Timeline

Applications are submitted to RBI's Department of Payment and Settlement Systems (DPSS). The application must include the company's audited financials, technology architecture, security audit reports, merchant onboarding policy, escrow account arrangement letter from a scheduled bank, and AML/CFT policy. RBI processes authorisation applications within 90 days of receiving a complete application. In practice, the process has taken 6 to 12 months for most applicants due to the level of documentation required.

In-Principle Approval

RBI first grants an In-Principle Approval (IPA) valid for 6 months, during which the entity can onboard merchants but cannot go live with full operations. After demonstrating satisfactory live testing and systems compliance, the entity receives the final authorisation letter.

RBI's March 2020 Master Directions gave existing PA operators a deadline of 30 September 2021 to apply for authorisation. Entities that applied by this date were allowed to continue operations pending disposal of their application. New entrants wishing to operate as PAs must obtain authorisation before commencing operations. Operating as an unauthorised PA is a criminal offence under Section 26 of the PSS Act.

Merchant KYC: Who Can You Onboard?

One of the most operationally intensive requirements in RBI's Master Directions is the mandatory KYC and due diligence that PAs must conduct on every merchant they onboard. This is not a one-time check; it is an ongoing monitoring obligation.

Standard Merchant KYC Requirements

For all merchants, the PA must verify and retain:

  • Business registration proof: Certificate of Incorporation for companies, Partnership Deed for firms, or registration certificate for proprietorships
  • PAN of the business entity
  • GSTIN (where applicable; mandatory for merchants with turnover above GST threshold)
  • Bank account proof: cancelled cheque and bank statement
  • Identity and address proof of the beneficial owner(s) with more than 25% ownership
  • Description of business activities, website URL, and social media presence verification
  • Website / app functionality check to ensure it is live, functional, and sells lawful products or services

Enhanced Due Diligence for High-Risk Merchants

PAs must apply Enhanced Due Diligence (EDD) for merchants in categories that RBI designates as high-risk. These include: digital goods sellers (where dispute rates are higher), travel and event ticketing (high refund volumes), financial product distributors, and any merchant with prior adverse regulatory history. For EDD merchants, additional documentation includes audited financials, negative news screening, and more frequent monitoring of transaction patterns.

Prohibited Merchant Categories

PAs are prohibited from onboarding merchants engaged in: gambling and betting (except RBI/state government authorised lotteries), sale of tobacco products to minors, pyramid schemes, and any business explicitly prohibited under Indian law. PAs must also screen merchants against the OFAC, UN sanctions list, and India's designated terrorist lists under PMLA.

Escrow Accounts and Settlement Timelines

The escrow account requirement is the financial safety net at the heart of the PA regulatory framework. The purpose is to ensure that customer funds are protected and not commingled with the PA's own operating capital.

Escrow Account Mechanics

Every PA must maintain a dedicated escrow account with an RBI-approved scheduled commercial bank. Customer payments collected by the PA must be credited to the escrow account within one business day of collection. The escrow account is held in trust for merchants; it cannot be attached by the PA's own creditors, and the PA cannot use escrow funds for its own expenses, investments, or obligations.

Settlement Cycles

RBI's Master Directions prescribe settlement timelines based on the nature of goods or services:

Merchant CategorySettlement Timeline (from Transaction Date)Governing Direction
Physical goods merchantsT+1 working daysRBI Master Directions Para 8.3
Digital goods/services merchantsT+1 to T+2 working days (as agreed)RBI Master Directions Para 8.3
Airlines and travel merchantsAfter confirmation of delivery/check-in, within agreed cycleRBI Master Directions Para 8.4
Recurring payments (SIP, insurance premium)As per mandate terms, subject to T+2RBI e-NACH / e-mandate guidelines

Any deviation from these settlement timelines must be agreed in the merchant contract and must comply with RBI's maximum permitted hold periods. PAs cannot indefinitely withhold settlement to use float for treasury income.

GST on Payment Gateway and Aggregator Services

The GST treatment of payment services is governed by the CGST Act, 2017 and the rate schedule notified by the GST Council. Here is how the GST framework applies to every participant in the payment ecosystem.

Rate and Classification

Payment aggregation and gateway services fall under SAC (Services Accounting Code) 998433, described as "other financial transaction processing and clearing house services." The applicable GST rate is 18% (9% CGST + 9% SGST for intra-state, or 18% IGST for inter-state). This rate has been stable since the GST Council's rate rationalisation in FY 2019-20 and applies to all fee components: MDR, transaction fees, setup fees, and convenience fees.

Who Pays and Who Can Claim ITC?

The PA/PG is the supplier of services and is liable to collect and remit 18% GST on its fees. The merchant is the recipient of services. B2B merchants with GST registration can claim full Input Tax Credit (ITC) on the GST paid to the PA/PG, provided:

  • A valid GST tax invoice is received from the PA/PG
  • The credit appears in the merchant's GSTR-2B (autopopulated from PA's GSTR-1)
  • The merchant's business does not fall under ITC-blocked categories under Section 17(5) of the CGST Act
  • Payment is made within 180 days of invoice date (or ITC is reversed and re-claimed after payment)

Place of Supply for Digital Payment Services

Place of supply determines whether IGST or CGST/SGST is applicable. Under Section 12(12) of the IGST Act:

  • B2B transactions: Place of supply is the registered location of the merchant (recipient). If the PA is in Maharashtra and the merchant is in Delhi, IGST at 18% applies.
  • B2C transactions (e.g., wallet top-ups, consumer payment apps): Place of supply is the location of the end consumer. Complexity arises because consumer location may not be known precisely; telecom-style rules apply (billing address).
  • Export of services (PA serving foreign merchants): Zero-rated under Section 16 of the IGST Act, provided payment is received in convertible foreign exchange and the service is clearly outside India. The PA can claim a refund of input taxes paid.

GST Compliance Calendar for PAs

Return / ObligationFrequencyDue Date
GSTR-1 (outward supply details)Monthly11th of following month
GSTR-3B (summary return and tax payment)Monthly20th of following month
GSTR-9 (annual return)Annual31 December of following FY
GSTR-9C (reconciliation statement, if turnover above ₹5 crore)Annual31 December of following FY
e-Invoicing (if turnover above ₹5 crore)Per invoiceAt time of invoice generation

Data Localisation: Where Payment Data Must Live

RBI's data localisation mandate, issued through circular DPSS.CO.PD No.1810/02.14.008/2017-18 on 6 April 2018, is one of the most commercially significant compliance requirements for payment entities with global technology infrastructure. It affects cloud providers, PGs integrated with international processors, and any PA that routes transactions through overseas data centres.

What Must Be Stored in India

The mandate covers all data related to payment systems operated in India. RBI's FAQ (issued in June 2019) clarified that "end-to-end transaction details" must be stored in India. This includes:

  • Customer data: name, mobile number, email, address linked to the payment instrument
  • Payment sensitive data: full card number (PAN), CVV, expiry date (where stored, subject to PCI-DSS restrictions), bank account details
  • Payment credentials: OTP, PIN, biometric data used for authentication
  • Transaction data: amount, merchant details, timestamp, transaction reference, success/failure status
  • Logs and audit trails related to the above

What Is Permitted Abroad

Data can be sent abroad for processing (for example, fraud scoring by an overseas AI system) but the complete, processed dataset must be brought back and stored only in India within 24 hours of leaving India. The overseas system must delete the data after processing. Foreign entities used for processing cannot retain the data longer than operationally necessary for that specific transaction.

Compliance Verification

PAs and PGs must submit a System Audit Report (SAR) from a CERT-In empanelled auditor annually, certifying compliance with the data localisation mandate. RBI inspects data storage infrastructure as part of its PA supervision process. Non-compliance with data localisation has been grounds for RBI's show-cause notices to several international payment entities operating in India.

PCI-DSS Compliance: The Card Data Security Standard

PCI-DSS is the global security standard maintained by the PCI Security Standards Council (a consortium of Visa, Mastercard, American Express, Discover, and JCB). While not a statutory requirement under Indian law, it functions as a mandatory industry standard because card network membership agreements (which any entity processing Visa or Mastercard transactions must sign) require PCI-DSS certification.

PCI-DSS v4.0 Requirements Applicable to Indian PAs/PGs

The current version, PCI-DSS v4.0 (effective April 2024, with transition from v3.2.1), organises its requirements into 12 core domains:

  • Install and maintain network security controls (firewalls, access control)
  • Apply secure configurations to all system components
  • Protect stored account data (encryption at rest, key management)
  • Protect cardholder data with strong cryptography during transmission
  • Protect all systems and networks from malicious software
  • Develop and maintain secure systems and software
  • Restrict access to system components and cardholder data by business need-to-know
  • Identify users and authenticate access to system components
  • Restrict physical access to cardholder data
  • Log and monitor all access to network resources and cardholder data
  • Test security of systems and networks regularly (penetration testing, vulnerability scans)
  • Support information security with organisational policies and programmes

PCI-DSS Certification Levels for Indian PAs

The certification level required depends on transaction volume:

LevelAnnual Transaction VolumeAssessment Required
Level 1Above 6 million Visa or Mastercard transactions per yearAnnual on-site audit by Qualified Security Assessor (QSA)
Level 21 million to 6 million transactions per yearAnnual Self-Assessment Questionnaire (SAQ) + quarterly network scans
Level 320,000 to 1 million e-commerce transactions per yearAnnual SAQ + quarterly network scans by Approved Scanning Vendor (ASV)
Level 4Below 20,000 e-commerce transactions per yearAnnual SAQ (merchant self-assessment)

Most large Indian PAs operate at Level 1. Mid-size PAs and most merchants fall at Level 2 or 3. The cost of a Level 1 QSA audit in India ranges from ₹15 lakh to ₹40 lakh per engagement.

Nodal Account Reconciliation and Record Keeping

Daily nodal account reconciliation is not just an accounting best practice; it is a regulatory requirement under RBI's Master Directions. The reconciliation process ensures that every rupee collected from customers is accounted for and that no funds are misappropriated, whether through fraud, system error, or operational failure.

Reconciliation Requirements

The PA must reconcile, on a daily basis:

  • Total transactions initiated on its platform vs. total credits received in the nodal account
  • Total settlements debited from the nodal account vs. total amounts credited to merchant accounts
  • Outstanding float: funds collected but not yet settled, with age analysis
  • Refund transactions: customer refunds debited from the nodal account and credited back
  • Suspense items: transactions that cannot be matched within 2 working days must be escalated

Record Retention Under PMLA

Under the Prevention of Money Laundering Act, 2002 (PMLA) and Rules framed thereunder, PAs (as reporting entities) must maintain transaction records for a minimum of 5 years from the date of the transaction. This includes: transaction logs, customer identification records, merchant KYC documents, and any STRs filed with FIU-IND. The records must be available for inspection by the Enforcement Directorate, FIU-IND, or RBI on demand.

Card-on-File Tokenisation: The New Normal Since October 2022

RBI's circular RBI/2021-22/161 (CO.DPSS.POLC.No.S-516/02-14-003/2021-22) dated 7 October 2021, effective from 1 October 2022, fundamentally changed how card data is handled in India's payment ecosystem. Raw card data storage by merchants and PGs is no longer permitted.

How Tokenisation Works

When a customer saves a card for future payments on a merchant website or app, instead of the merchant (or PG) storing the 16-digit card number, a unique token is generated by the card network (Visa, Mastercard, or RuPay). This token is specific to the combination of the card, the merchant, and the device. The token is meaningless outside its designated context. Future payments use the token; the card network maps the token back to the actual card number internally for routing and processing.

Implementation Obligations

  • PGs must integrate with card network tokenisation APIs (Visa Token Service, Mastercard Digital Enablement Service, RuPay tokenisation)
  • Merchants must not store any card data at their end; all card references must use tokens
  • Existing stored card data (if any) must have been deleted by 30 September 2022
  • Any merchant or PG found storing raw card numbers after 1 October 2022 faces card network penalties, suspension of processing rights, and potential regulatory action under the IT Act

AML and CFT Obligations for Payment Aggregators

PAs are classified as reporting entities under Section 2(1)(wa) of PMLA, 2002, read with the Prevention of Money Laundering (Maintenance of Records) Rules, 2005. This imposes a full Anti-Money Laundering (AML) and Counter-Financing of Terrorism (CFT) compliance programme.

Core AML Obligations

  • Customer Due Diligence (CDD): KYC verification of all merchants before onboarding, as described in Section 4 above
  • Transaction Monitoring: Automated monitoring systems to flag unusual patterns: large round-number transactions, rapid succession of small transactions just below reporting thresholds (structuring), sudden spike in transaction volume from a merchant
  • Suspicious Transaction Reports (STRs): Filed with Financial Intelligence Unit - India (FIU-IND) at fiuindia.gov.in within 7 working days of forming a suspicion. An STR does not require certainty; reasonable grounds for suspicion are sufficient
  • Cash Transaction Reports (CTRs): Although PAs are digital entities, if any cash equivalent (prepaid instrument, wallet) transaction exceeds ₹10 lakh, it must be reported to FIU-IND
  • Sanctions Screening: All merchants and their beneficial owners must be screened against UN Security Council designations, OFAC SDN list, and India's designated entities lists under UAPA

The single biggest compliance gap in India's payment ecosystem is the failure to keep merchant KYC current after onboarding. RBI's Master Directions require periodic re-verification of merchant details, particularly for high-risk categories. Many PAs conduct thorough initial KYC but neglect annual refresh checks. RBI's supervisory inspections (particularly post-2023) have specifically cited outdated merchant KYC as a finding. Invest in automated periodic KYC refresh workflows before RBI asks about yours.

Cross-Border Transactions: FEMA Overlay

When payment flows cross Indian borders, the regulatory picture gains an additional layer: the Foreign Exchange Management Act, 1999 (FEMA) and the regulations framed thereunder by RBI. FEMA governs all foreign exchange transactions and is enforced by the Enforcement Directorate (ED) and RBI's Forex Control departments.

PA Obligations for Cross-Border Payments

A PA facilitating payments from Indian consumers to foreign merchants (outward remittance) must ensure:

  • The transaction falls within a permissible current account transaction under Schedule I of FEMA (Current Account Transactions) Rules, 2000
  • For transactions above USD 25,000 (or ₹20 lakh equivalent), the PA must obtain a Form A2 declaration from the remitter
  • LRS (Liberalised Remittance Scheme) annual limits of USD 2,50,000 per individual per financial year are monitored and reported
  • Tax Collected at Source (TCS) at 20% on LRS remittances above ₹7 lakh per year (Finance Act, 2023 amendment to Section 206C(1G) of the Income Tax Act) must be collected and deposited with the income tax department

Practical Compliance Checklist: What You Should Have in Place

Whether you are an operating PA, a merchant choosing between payment partners, or a startup building in the payment space, this checklist summarises the minimum compliance posture required under the current regulatory framework.

Compliance AreaRequirementApplicable ToGoverning Rule
RBI AuthorisationPrior authorisation before commencing PA operationsPAsPSS Act, Sec. 7; RBI Master Directions 2020
Net WorthMinimum ₹25 crore, maintained ongoingPAsRBI Master Directions Para 3
Escrow AccountDesignated account with scheduled bank; T+1 creditPAsRBI Master Directions Para 8
Merchant KYCPre-onboarding KYC with periodic refreshPAsRBI Master Directions Para 6
Data LocalisationAll payment data stored only in IndiaPAs, PGsRBI Circular DPSS.CO.PD No.1810 (2018)
TokenisationNo raw card storage; CoFT from 1 Oct 2022PAs, PGs, MerchantsRBI Circular RBI/2021-22/161
PCI-DSSCertified per transaction volume levelPAs, PGsCard network agreements
GST RegistrationMandatory; 18% on PA/PG feesPAs, PGsCGST Act, 2017; SAC 998433
AML/CFTFull PMLA programme; STRs to FIU-INDPAsPMLA, 2002; PML Rules, 2005
Nodal ReconciliationDaily reconciliation; 5-year record retentionPAsRBI Master Directions Para 9; PMLA
Annual System AuditCERT-In empanelled auditor annuallyPAs, PGsRBI Master Directions Para 13
Grievance RedressalNodal Officer; 30-day resolution; RBI Ombudsman escalationPAs, PGsRBI Integrated Ombudsman Scheme, 2021

What Changed in the January 2024 RBI Update

RBI's January 2024 update to the Master Directions introduced several material changes that compliance teams need to incorporate into their programmes.

Cross-Border Payment Aggregator Framework

The 2024 update introduced a specific framework for cross-border PAs, entities that aggregate payments from Indian consumers for foreign merchants or vice versa. These entities must obtain a separate authorisation from RBI as a cross-border PA, in addition to any existing domestic PA authorisation. The net worth requirement for cross-border PAs was set at ₹15 crore (lower than domestic PA to encourage the segment) with a requirement to reach ₹25 crore within 3 years.

Tightened Merchant Onboarding Timelines

The 2024 directions require PAs to complete KYC verification within 24 hours for standard merchants using an RBI-approved Video-Based Customer Identification Process (V-CIP) or digital KYC. PAs that use manual KYC must complete the process within 5 working days. Temporary onboarding (with limited transaction limits) while KYC is in progress is now capped at ₹50,000 cumulative transactions before full KYC is completed.

Enhanced Cybersecurity Requirements

The 2024 update mandated that PAs submit an annual Information Security Audit Report by a CERT-In empanelled auditor (in addition to the existing SAR), covering specifically: penetration testing results, vulnerability management programme, incident response plan, and business continuity testing. PAs processing above ₹1,000 crore monthly must conduct quarterly (rather than annual) penetration tests.

Putting It All Together: What This Means for Your Business

If you are a merchant, your primary obligations are: use a RBI-authorised PA or a bank-integrated PG, ensure you hold GST registration and claim ITC on PA fees correctly, do not store raw card data (let the PA/PG handle tokenisation), and check that your PA completes your KYC properly (it protects you as much as it protects the PA).

If you are building a fintech product that touches payments, the determination of whether your model requires PA authorisation should be your first legal analysis. If your product holds funds even for a moment before settling to a third party, you are a PA. The consequences of operating without authorisation under the PSS Act are severe: criminal liability for directors, not just civil penalties.

If you are a compliance professional at a PA or PG, the 2024 update's cross-border framework and enhanced cybersecurity requirements are your immediate focus areas for FY 2026-27. The annual CERT-In audit deadline and the cross-border authorisation requirement (for PAs already processing cross-border transactions) are the two items most likely to surface in an RBI inspection.

For assistance with GST registration for your payment business, or for company incorporation as a preliminary step before applying for PA authorisation, ProTax provides assistance for these registrations with the relevant authorities. For businesses with import-export payment flows, IEC registration and FEMA compliance are related requirements worth reviewing together.

Setting up a payment-related business in India involves navigating RBI, GST, FEMA, and PMLA obligations simultaneously. ProTax provides assistance for company registration, GST registration, IEC registration, and MSME registration as foundational steps for payment businesses. Get assistance for GST registration or company incorporation assistance to start the process.

Frequently Asked Questions

What is the difference between a Payment Aggregator and a Payment Gateway under RBI rules?

Under RBI's Master Directions on Payment Aggregators and Payment Gateways (March 2020, updated January 2024), a Payment Aggregator (PA) is an entity that receives money from customers on behalf of merchants and settles it to merchants. A Payment Gateway (PG) only provides the technical infrastructure, routes transactions, but never holds funds. PAs must obtain RBI authorisation; PGs need only a registration from their acquiring bank.

Is RBI authorisation mandatory for Payment Aggregators in India?

Yes. Under RBI's March 2020 Master Directions, all entities acting as Payment Aggregators that settle funds to merchants must obtain prior authorisation from RBI under the Payment and Settlement Systems Act, 2007 (Section 7). Entities already operating as PAs before the directions were issued were required to apply by 30 September 2021. New entities must apply for authorisation before commencing PA operations.

Do Payment Gateways need an RBI licence in India?

Payment Gateways that only provide technical routing infrastructure and do not hold or settle funds are not required to obtain RBI authorisation. However, they must register with their acquiring bank, which is itself a regulated entity. PG providers must comply with RBI's data localisation mandates (circular DPSS.CO.PD No.1810/02.14.008/2017-18) and implement PCI-DSS certification for card data security.

What are the net worth requirements for a Payment Aggregator seeking RBI authorisation?

RBI's Master Directions (updated 2024) require that a non-bank PA must have a minimum net worth of ₹25 crore at the time of applying for authorisation and maintain a net worth of ₹25 crore on an ongoing basis. PAs that also provide cross-border payment services must maintain a separate net worth threshold as applicable under FEMA. Failure to maintain net worth is grounds for cancellation of authorisation.

What merchant KYC obligations apply to Payment Aggregators?

RBI's Master Directions require PAs to conduct mandatory KYC/due diligence on all merchants before onboarding. This includes verifying business registration documents, PAN, GSTIN, bank account details, and website/app functionality. PAs must conduct enhanced due diligence for high-risk merchants (gambling-adjacent, digital goods, travel). Merchant information must be reported to RBI as part of periodic returns. PAs must not onboard unregistered or shell entities.

What is the escrow account requirement for Payment Aggregators?

RBI mandates that all PAs maintain a designated escrow account with a scheduled commercial bank for settlement of merchant funds. Funds collected from customers must be moved to the escrow account within one working day. Merchants must be settled within T+1 working days (where T is the transaction date) for physical goods PAs, unless a different settlement cycle is agreed. The escrow account cannot be used for the PA's own business expenses.

What GST rate applies to Payment Gateway services in India?

Payment Gateway and Payment Aggregator services attract 18% GST under SAC code 998433 (other financial services including payment processing). This rate applies to the service fee, transaction fee, and MDR (Merchant Discount Rate) charged to merchants. The GST liability falls on the PA/PG as the registered supplier of services. Merchants can claim input tax credit on GST paid to their PA/PG, provided they hold a valid tax invoice.

How is the Place of Supply determined for Payment Gateway services under GST?

Under Section 12 of the IGST Act, 2017, for Business-to-Business (B2B) transactions, the place of supply is the registered location of the recipient (merchant). For Business-to-Consumer (B2C) digital services (e.g., a consumer-facing wallet), the place of supply is the location of the consumer. Cross-border PA services to foreign merchants fall under zero-rated export of services under Section 16 of the IGST Act, subject to receipt of foreign currency.

What is the data localisation requirement for payment data in India?

RBI's circular (DPSS.CO.PD No.1810/02.14.008/2017-18 of 6 April 2018) mandates that all data related to payment systems operated in India must be stored only in India. This applies to full end-to-end transaction data, including customer data, payment sensitive data, and transaction logs. Data can be processed abroad for business purposes but the complete data must be brought back and stored only in India within 24 hours. Foreign processors must delete Indian data after processing.

What is PCI-DSS and is it mandatory for Indian payment entities?

PCI-DSS (Payment Card Industry Data Security Standard) is a global security standard for organisations that handle cardholder data. Although not a statutory requirement under Indian law, RBI's Master Directions and the guidelines from card networks (Visa, Mastercard, RuPay) make PCI-DSS compliance a de facto requirement for all entities processing card transactions. Non-compliance results in increased transaction fees, fines from card networks, and potential suspension of card processing rights.

What is nodal account reconciliation for payment aggregators?

RBI requires PAs to maintain a nodal account (also called a settlement account) with a scheduled bank. Daily reconciliation is mandatory: the PA must verify that every transaction recorded on its platform matches the corresponding credit in the nodal account and the settlement debited to merchants. Any mismatch must be resolved within 2 working days. PAs must preserve transaction records for at least 5 years under the Prevention of Money Laundering Act, 2002 (PMLA).

Do cross-border transactions through Payment Gateways have additional RBI compliance requirements?

Yes. PAs and PGs processing cross-border transactions must comply with FEMA (Foreign Exchange Management Act, 1999) and the RBI's Forex guidelines. PAs must ensure merchants receiving foreign currency are permitted to do so (as per the permitted current account transaction list). Repatriation of export proceeds must comply with FEMA regulations, and PAs must file Foreign Exchange Transaction returns as required by RBI's Trade Credit and Export Finance division.

What reporting and audit obligations do RBI-authorised Payment Aggregators have?

RBI-authorised PAs must submit: Annual System Audit Report by a CERT-In empanelled auditor, quarterly cybersecurity incident reports, periodic merchant settlement and transaction volume data to RBI as prescribed, compliance certificate from a qualified auditor on net worth maintenance, and immediate reporting of any cyber security breach, data compromise, or system failure per RBI's cybersecurity framework for payment system operators.

How does GST registration apply to a Payment Aggregator?

A PA operating across India must obtain GST registration under the CGST Act, 2017. Since PA services are supplied nationwide, the PA may register in each state where it has a business establishment (inter-state services attract IGST at 18%). The PA must issue tax invoices to merchants for every billing period, collect GST, file GSTR-1 (outward supplies), GSTR-3B (monthly summary), and reconcile ITC with GSTR-2B. Estimated annual GST compliance cost ranges from ₹1.5 lakh to ₹5 lakh for mid-size PAs.

What happens if a Payment Aggregator fails to comply with RBI Master Directions?

Non-compliance with RBI's Master Directions can result in: cancellation of PA authorisation under Section 8 of the Payment and Settlement Systems Act, 2007, monetary penalties up to ₹5 lakh per violation (Section 26 of the PSS Act), and directions to stop operations. RBI can also debar individuals from participating in payment system operations. In extreme cases of fraud or systemic risk, RBI can appoint an administrator for the PA.

Is a Foreign Company allowed to operate as a Payment Aggregator in India?

A foreign company cannot directly operate as a PA in India. Under RBI's Master Directions, only companies incorporated in India under the Companies Act, 2013 or the Companies Act, 1956 are eligible to apply for PA authorisation. Foreign entities wishing to offer PA services in India must incorporate an Indian subsidiary, ensure at least 25% of the board comprises Indian directors, and comply with applicable FDI policy (up to 100% FDI is allowed in fintech payment services under the automatic route under FEMA).

What is the difference between MDR, transaction fee, and convenience fee in GST terms?

MDR (Merchant Discount Rate) is the fee deducted by the PA from the settlement amount as its service charge to the merchant; it attracts 18% GST. A transaction fee is a fixed per-transaction charge levied on the merchant, also attracting 18% GST. A convenience fee is charged to the end customer (e.g., on utility bill payments) and also attracts 18% GST. All three must be separately shown on the tax invoice. Note: RBI abolished MDR on RuPay debit and UPI transactions in January 2020 for transactions below ₹2,000.

What are the customer grievance redressal obligations for Payment Aggregators?

RBI's Master Directions require PAs to maintain a dedicated customer grievance redressal mechanism with resolution within 30 days (or the timeframe specified by RBI from time to time). PAs must appoint a Nodal Officer responsible for customer complaints. Escalation to RBI's Ombudsman for Digital Payments (under the Integrated Ombudsman Scheme 2021) is available if the PA fails to resolve complaints within the specified period. Systemic patterns of complaints must be reported to RBI.

Do UPI-based Payment Aggregators have different compliance requirements?

PAs facilitating UPI transactions must additionally comply with NPCI's (National Payments Corporation of India) UPI Circular guidelines and the UPI Third Party Application Provider (TPAP) framework. UPI PAs must maintain direct settlement with NPCI-approved banks, comply with NPCI's transaction limit circulars (currently ₹1 lakh per UPI transaction, with ₹2 lakh for specific categories like capital market, insurance, and healthcare), and implement RBI's tokenisation guidelines for card-on-UPI features.

What is tokenisation and how does it relate to payment gateway compliance?

RBI's tokenisation circular (RBI/2021-22/161, October 2021) mandates that card data cannot be stored by merchants or PGs in raw form. All card transactions must use a token issued by the card network (Visa, Mastercard, RuPay). The token is specific to the card, the merchant, and the device. PGs must implement the Card-on-File Tokenisation (CoFT) framework by the RBI deadline (applicable from 1 October 2022). Storage of raw card numbers (PAN) is a violation attracting heavy penalties.

What are the AML and CFT obligations for Payment Aggregators?

As reporting entities under the Prevention of Money Laundering Act, 2002 (PMLA), PAs must implement a full AML/CFT programme: Customer Due Diligence (CDD), Enhanced Due Diligence (EDD) for high-risk merchants, transaction monitoring, suspicious transaction reports (STRs) filed with the Financial Intelligence Unit-India (FIU-IND), and record maintenance for 5 years. PAs must also screen merchants and beneficial owners against the UNSC consolidated sanctions list.

How does the RBI sandbox framework apply to new payment products?

RBI operates a Regulatory Sandbox under the Enabling Framework for Regulatory Sandbox (August 2019, updated 2024). Payment system innovations can apply for sandbox testing under the DPSS Cohort. Sandbox participants are granted temporary relaxation of certain regulatory norms for a defined test period (6 to 9 months). Successful sandbox exits can lead to fast-tracked authorisation applications. The sandbox does not exempt participants from data localisation or AML obligations.

What insurance or surety obligations do Payment Aggregators have?

RBI's Master Directions (2024 update) require PAs to maintain adequate insurance cover for cyber risks, operational failures, and settlement defaults. While RBI does not specify a minimum insurance amount, it requires PAs to demonstrate to their acquiring bank and RBI that they hold coverage commensurate with settlement volumes. In practice, PAs with monthly settlement volumes above ₹100 crore are expected to carry cyber insurance of at least ₹5 crore to ₹20 crore per incident.

Can a startup build a payment gateway product without full PA authorisation?

Yes, within limits. A startup can build a technical payment gateway (no fund holding) without PA authorisation, provided it integrates with an RBI-authorised PA for settlement. The startup acts as a technology service provider (TSP) to the PA. The TSP must still comply with data localisation requirements, PCI-DSS standards, and RBI's cloud and outsourcing guidelines (RBI/2023-24/27). The authorised PA remains the regulated entity and bears primary compliance responsibility.

What GST input tax credit can merchants claim on payment gateway fees?

Merchants registered under GST can claim Input Tax Credit (ITC) on the 18% GST paid on payment gateway/aggregator fees, provided: the PA has a valid GST registration, a proper tax invoice is issued, the merchant has not blocked ITC under Section 17(5) of the CGST Act, and the credit appears in the merchant's GSTR-2B. ITC on PA fees is claimable under input services and reduces the merchant's overall GST liability.

Frequently Asked Questions

What is the difference between a Payment Aggregator and a Payment Gateway under RBI rules?

Under RBI's Master Directions on Payment Aggregators and Payment Gateways (March 2020, updated January 2024), a Payment Aggregator (PA) is an entity that receives money from customers on behalf of merchants and settles it to merchants. A Payment Gateway (PG) only provides the technical infrastructure, routes transactions, but never holds funds. PAs must obtain RBI authorisation; PGs need only a registration from their acquiring bank.

Is RBI authorisation mandatory for Payment Aggregators in India?

Yes. Under RBI's March 2020 Master Directions, all entities acting as Payment Aggregators that settle funds to merchants must obtain prior authorisation from RBI under the Payment and Settlement Systems Act, 2007 (Section 7). Entities already operating as PAs before the directions were issued were required to apply by 30 September 2021. New entities must apply for authorisation before commencing PA operations.

Do Payment Gateways need an RBI licence in India?

Payment Gateways that only provide technical routing infrastructure and do not hold or settle funds are not required to obtain RBI authorisation. However, they must register with their acquiring bank, which is itself a regulated entity. PG providers must comply with RBI's data localisation mandates (circular DPSS.CO.PD No.1810/02.14.008/2017-18) and implement PCI-DSS certification for card data security.

What are the net worth requirements for a Payment Aggregator seeking RBI authorisation?

RBI's Master Directions (updated 2024) require that a non-bank PA must have a minimum net worth of ₹25 crore at the time of applying for authorisation and maintain a net worth of ₹25 crore on an ongoing basis. PAs that also provide cross-border payment services must maintain a separate net worth threshold as applicable under FEMA. Failure to maintain net worth is grounds for cancellation of authorisation.

What merchant KYC obligations apply to Payment Aggregators?

RBI's Master Directions require PAs to conduct mandatory KYC/due diligence on all merchants before onboarding. This includes verifying business registration documents, PAN, GSTIN, bank account details, and website/app functionality. PAs must conduct enhanced due diligence for high-risk merchants (gambling-adjacent, digital goods, travel). Merchant information must be reported to RBI as part of periodic returns. PAs must not onboard unregistered or shell entities.

What is the escrow account requirement for Payment Aggregators?

RBI mandates that all PAs maintain a designated escrow account with a scheduled commercial bank for settlement of merchant funds. Funds collected from customers must be moved to the escrow account within one working day. Merchants must be settled within T+1 working days (where T is the transaction date) for physical goods PAs, unless a different settlement cycle is agreed. The escrow account cannot be used for the PA's own business expenses.

What GST rate applies to Payment Gateway services in India?

Payment Gateway and Payment Aggregator services attract 18% GST under SAC code 998433 (other financial services including payment processing). This rate applies to the service fee, transaction fee, and MDR (Merchant Discount Rate) charged to merchants. The GST liability falls on the PA/PG as the registered supplier of services. Merchants can claim input tax credit on GST paid to their PA/PG, provided they hold a valid tax invoice.

How is the Place of Supply determined for Payment Gateway services under GST?

Under Section 12 of the IGST Act, 2017, for Business-to-Business (B2B) transactions, the place of supply is the registered location of the recipient (merchant). For Business-to-Consumer (B2C) digital services (e.g., a consumer-facing wallet), the place of supply is the location of the consumer. Cross-border PA services to foreign merchants fall under zero-rated export of services under Section 16 of the IGST Act, subject to receipt of foreign currency.

What is the data localisation requirement for payment data in India?

RBI's circular (DPSS.CO.PD No.1810/02.14.008/2017-18 of 6 April 2018) mandates that all data related to payment systems operated in India must be stored only in India. This applies to full end-to-end transaction data, including customer data, payment sensitive data, and transaction logs. Data can be processed abroad for business purposes but the complete data must be brought back and stored only in India within 24 hours. Foreign processors must delete Indian data after processing.

What is PCI-DSS and is it mandatory for Indian payment entities?

PCI-DSS (Payment Card Industry Data Security Standard) is a global security standard for organisations that handle cardholder data. Although not a statutory requirement under Indian law, RBI's Master Directions and the guidelines from card networks (Visa, Mastercard, RuPay) make PCI-DSS compliance a de facto requirement for all entities processing card transactions. Non-compliance results in increased transaction fees, fines from card networks, and potential suspension of card processing rights.

What is nodal account reconciliation for payment aggregators?

RBI requires PAs to maintain a nodal account (also called a settlement account) with a scheduled bank. Daily reconciliation is mandatory: the PA must verify that every transaction recorded on its platform matches the corresponding credit in the nodal account and the settlement debited to merchants. Any mismatch must be resolved within 2 working days. PAs must preserve transaction records for at least 5 years under the Prevention of Money Laundering Act, 2002 (PMLA).

Do cross-border transactions through Payment Gateways have additional RBI compliance requirements?

Yes. PAs and PGs processing cross-border transactions must comply with FEMA (Foreign Exchange Management Act, 1999) and the RBI's Forex guidelines. PAs must ensure merchants receiving foreign currency are permitted to do so (as per the permitted current account transaction list). Repatriation of export proceeds must comply with FEMA regulations, and PAs must file Foreign Exchange Transaction returns as required by RBI's Trade Credit and Export Finance division.

What reporting and audit obligations do RBI-authorised Payment Aggregators have?

RBI-authorised PAs must submit: Annual System Audit Report by a CERT-In empanelled auditor, quarterly cybersecurity incident reports, periodic merchant settlement and transaction volume data to RBI as prescribed, compliance certificate from a qualified auditor on net worth maintenance, and immediate reporting of any cyber security breach, data compromise, or system failure per RBI's cybersecurity framework for payment system operators.

How does GST registration apply to a Payment Aggregator?

A PA operating across India must obtain GST registration under the CGST Act, 2017. Since PA services are supplied nationwide, the PA may register in each state where it has a business establishment (inter-state services attract IGST at 18%). The PA must issue tax invoices to merchants for every billing period, collect GST, file GSTR-1 (outward supplies), GSTR-3B (monthly summary), and reconcile ITC with GSTR-2B. Estimated annual GST compliance cost ranges from ₹1.5 lakh to ₹5 lakh for mid-size PAs.

What happens if a Payment Aggregator fails to comply with RBI Master Directions?

Non-compliance with RBI's Master Directions can result in: cancellation of PA authorisation under Section 8 of the Payment and Settlement Systems Act, 2007, monetary penalties up to ₹5 lakh per violation (Section 26 of the PSS Act), and directions to stop operations. RBI can also debar individuals from participating in payment system operations. In extreme cases of fraud or systemic risk, RBI can appoint an administrator for the PA.

Is a Foreign Company allowed to operate as a Payment Aggregator in India?

A foreign company cannot directly operate as a PA in India. Under RBI's Master Directions, only companies incorporated in India under the Companies Act, 2013 or the Companies Act, 1956 are eligible to apply for PA authorisation. Foreign entities wishing to offer PA services in India must incorporate an Indian subsidiary, ensure at least 25% of the board comprises Indian directors, and comply with applicable FDI policy (up to 100% FDI is allowed in fintech payment services under the automatic route under FEMA).

What is the difference between MDR, transaction fee, and convenience fee in GST terms?

MDR (Merchant Discount Rate) is the fee deducted by the PA from the settlement amount as its service charge to the merchant; it attracts 18% GST. A transaction fee is a fixed per-transaction charge levied on the merchant, also attracting 18% GST. A convenience fee is charged to the end customer (e.g., on utility bill payments) and also attracts 18% GST. All three must be separately shown on the tax invoice. Note: RBI abolished MDR on RuPay debit and UPI transactions in January 2020 for transactions below ₹2,000.

What are the customer grievance redressal obligations for Payment Aggregators?

RBI's Master Directions require PAs to maintain a dedicated customer grievance redressal mechanism with resolution within 30 days (or the timeframe specified by RBI from time to time). PAs must appoint a Nodal Officer responsible for customer complaints. Escalation to RBI's Ombudsman for Digital Payments (under the Integrated Ombudsman Scheme 2021) is available if the PA fails to resolve complaints within the specified period. Systemic patterns of complaints must be reported to RBI.

Do UPI-based Payment Aggregators have different compliance requirements?

PAs facilitating UPI transactions must additionally comply with NPCI's (National Payments Corporation of India) UPI Circular guidelines and the UPI Third Party Application Provider (TPAP) framework. UPI PAs must maintain direct settlement with NPCI-approved banks, comply with NPCI's transaction limit circulars (currently ₹1 lakh per UPI transaction, with ₹2 lakh for specific categories like capital market, insurance, and healthcare), and implement RBI's tokenisation guidelines for card-on-UPI features.

What is tokenisation and how does it relate to payment gateway compliance?

RBI's tokenisation circular (RBI/2021-22/161, October 2021) mandates that card data cannot be stored by merchants or PGs in raw form. All card transactions must use a token issued by the card network (Visa, Mastercard, RuPay). The token is specific to the card, the merchant, and the device. PGs must implement the Card-on-File Tokenisation (CoFT) framework by the RBI deadline (applicable from 1 October 2022). Storage of raw card numbers (PAN) is a violation attracting heavy penalties.

What are the AML and CFT obligations for Payment Aggregators?

As reporting entities under the Prevention of Money Laundering Act, 2002 (PMLA), PAs must implement a full AML/CFT programme: Customer Due Diligence (CDD), Enhanced Due Diligence (EDD) for high-risk merchants, transaction monitoring, suspicious transaction reports (STRs) filed with the Financial Intelligence Unit-India (FIU-IND), and record maintenance for 5 years. PAs must also screen merchants and beneficial owners against the UNSC consolidated sanctions list.

How does the RBI sandbox framework apply to new payment products?

RBI operates a Regulatory Sandbox under the Enabling Framework for Regulatory Sandbox (August 2019, updated 2024). Payment system innovations can apply for sandbox testing under the DPSS Cohort. Sandbox participants are granted temporary relaxation of certain regulatory norms for a defined test period (6 to 9 months). Successful sandbox exits can lead to fast-tracked authorisation applications. The sandbox does not exempt participants from data localisation or AML obligations.

What insurance or surety obligations do Payment Aggregators have?

RBI's Master Directions (2024 update) require PAs to maintain adequate insurance cover for cyber risks, operational failures, and settlement defaults. While RBI does not specify a minimum insurance amount, it requires PAs to demonstrate to their acquiring bank and RBI that they hold coverage commensurate with settlement volumes. In practice, PAs with monthly settlement volumes above ₹100 crore are expected to carry cyber insurance of at least ₹5 crore to ₹20 crore per incident.

Can a startup build a payment gateway product without full PA authorisation?

Yes, within limits. A startup can build a technical payment gateway (no fund holding) without PA authorisation, provided it integrates with an RBI-authorised PA for settlement. The startup acts as a technology service provider (TSP) to the PA. The TSP must still comply with data localisation requirements, PCI-DSS standards, and RBI's cloud and outsourcing guidelines (RBI/2023-24/27). The authorised PA remains the regulated entity and bears primary compliance responsibility.

What GST input tax credit can merchants claim on payment gateway fees?

Merchants registered under GST can claim Input Tax Credit (ITC) on the 18% GST paid on payment gateway/aggregator fees, provided: the PA has a valid GST registration, a proper tax invoice is issued, the merchant has not blocked ITC under Section 17(5) of the CGST Act, and the credit appears in the merchant's GSTR-2B. ITC on PA fees is claimable under input services and reduces the merchant's overall GST liability.

Discuss This With ProTax

FROM THE PROTAX LIBRARY

Recent Articles & Guides

Practical reading on business records, tax filings and the decisions that come with running a company.

Newsletter

Stay ahead on compliance, tax & business updates

Get selected business and compliance updates by email. Once a month, no spam.

  • 100% privacy
  • 1 email / month
  • Unsubscribe anytime
Contact ProTax
Chosen by individuals and businesses

Get Help With Your Business

Tell us what you need help with. Our team will review your enquiry and explain the next steps.

Free Consultation No Obligations Expert Advice
FREE Consultation Get Started @ ₹299 ₹0

Talk To ProTax

Share Your Business Requirement

Instant Response 100% Confidential Expert Advice
FREE Consultation Get Started @ ₹299 ₹0

Request a Free Quote

Share Your Business Requirement

Instant Response 100% Confidential Expert Advice