Apexnode TechEnterprise Wealth Tech
Lending & Payments

Getting a Payment Aggregator License in India: RBI Rules, Platform Costs and Timeline

The capital requirement is the easy part. Escrow mechanics, India-only data storage, a CERT-In empanelled system audit and a long RBI queue decide whether your PA plan works. Here are the costs and the sequence.

By the Apexnode Tech editorial team · November 2026 · 11 min read

Who needs a payment aggregator license in India, and which category to apply for

If your company collects customer payments on behalf of merchants, holds those funds even briefly, and then settles them to the merchants, you need a payment aggregator license India regulators will recognize: formally, an authorization from the Reserve Bank of India under the Payment and Settlement Systems Act, 2007. A pure technology provider that routes transactions but never touches merchant funds is a payment gateway. RBI doesn't authorize gateways separately, so there's no standalone gateway license to apply for. RBI does expect gateways to follow its baseline technology recommendations, and banks and aggregators that use them will usually check.

The distinction matters more than founders expect. Plenty of companies launch as a gateway and later want to own settlement, because that's where the margin, the merchant relationship and the data sit. Once you hold funds, the full regime applies.

Advertisement

The three categories

RBI's payment aggregator guidelines began with a March 2020 circular for online aggregators, followed by clarifications. RBI has since consolidated them into master directions covering three activity types:

  • PA-O (online): e-commerce, subscription and in-app collections. This is the category most applicants mean.
  • PA-P (physical): face-to-face, point-of-sale aggregation. Offline aggregators that once sat outside the regime now come under it.
  • PA-CB (cross-border): import and export payments for goods and services. Flows run through banks authorized to deal in foreign exchange, with per-transaction value caps and FEMA reporting.

You can hold more than one category, but each carries its own conditions. File only for what your merchant base needs in the first two years. PA-CB adds foreign-exchange compliance, purpose-code reporting and a banking relationship that's harder to secure than domestic escrow.

Eligibility and capital

The applicant must be a company incorporated in India, and its memorandum of association must cover payment aggregation. Banks don't need separate authorization. E-commerce marketplaces can't run aggregation as a side activity and have to move it into a separate legal entity.

The capital test is a net worth of ₹15 crore at the time of application (roughly USD 1.7-1.8 million, depending on the exchange rate), rising to ₹25 crore (about USD 2.8-3 million) by the end of the third financial year after authorization. Net worth means paid-up equity plus free reserves, minus accumulated losses and intangibles. It isn't committed capital. A cash-burning startup can slip below the threshold between filing and authorization, and RBI will notice. Fund the cushion before you file.

Foreign-owned applicants should also check foreign investment rules. Investment from countries that share a land border with India needs prior government approval, which can add months before RBI's review gets going. Promoters and directors face fit-and-proper checks, and RBI looks hard at regulatory history in group entities.

Escrow, settlement and merchant due diligence: the rules that shape your ledger

Non-bank aggregators must hold collected funds in an escrow account with a scheduled commercial bank. That account is the center of a payment aggregator's operations. RBI specifies what can go in and come out, and those rules decide how your ledger, reconciliation and treasury functions get built.

Permitted credits are, broadly, customer payments, merchant refunds and inflows from other payment providers. Permitted debits are settlements to merchants, payments to other providers in the chain, customer refunds and your pre-agreed commission. Escrow balances can't fund working capital or merchant lending. Moving the account to another bank generally needs RBI's involvement, so pick a bank whose API banking and reporting you can live with for years.

Settlement timelines

Settlement deadlines run from defined trigger events, such as shipment or delivery confirmation, and they differ depending on who is responsible for delivery. Read the current master direction for the exact clocks. In practice, your platform needs reliable delivery-status signals from merchants and logic to hold or release funds merchant by merchant. It also needs a daily reconciliation that ties escrow balances to merchant payables. RBI expects periodic auditor certification of escrow balances, so build reports that make certification a matter of hours, not weeks.

Merchant onboarding

The aggregator answers for the merchants it brings on. That means a board-approved onboarding policy and KYC under RBI's KYC directions. It also means background checks, and verifying that a merchant's site or app shows its terms, refund policy and grievance contacts. Document-only checks on small merchants are no longer a safe approach. Prohibited categories and counterfeit goods have to be screened out, and monitoring has to catch merchants whose transaction patterns drift away from their declared business.

A red flag in your own plan: a sales team paid on merchant count with no risk sign-off. A wave of fraud-linked chargebacks from badly vetted merchants is the quickest route to RBI scrutiny after authorization.

Card data is its own constraint. Aggregators and merchants can't store full card numbers. Card-on-file has to use network tokenization, and only limited data such as the last four digits and issuer name can be kept. If you're planning repeat-payment or subscription products, design around tokens from day one.

Data localization, security controls and the audit cycle

RBI's 2018 directive on storage of payment system data requires payment data to be stored only in India. The domestic leg of a transaction has to be processed in India too. For cross-border transactions, the foreign leg can be processed abroad, but the data must come back to India and be deleted from foreign systems within a short window, generally one business day. This rules out the common global setup where a parent company runs a single processing core in Ireland or Singapore and serves India from it. You need India-resident primary and disaster recovery environments, India-resident logs and backups, and evidence of all of it.

On top sits India's Digital Personal Data Protection Act, 2023, and the rules under it, which cover consent, purpose limitation, breach notification and data-principal rights for personal data you process about customers and merchant staff. DPDP is more about how you process data than where you store it, so your privacy team needs a separate workstream next to RBI localization. Teams already running GDPR programs in Europe will recognize the structure but shouldn't assume the obligations match.

Security and incident reporting

Expect to comply with:

  • PCI DSS at the level your volumes require. Applicants targeting serious card volume should plan for an assessment by a qualified security assessor.
  • RBI's cyber resilience and digital payment security controls for non-bank payment system operators, covering governance, a board-level IT strategy committee, vulnerability management, multi-factor authentication, fraud monitoring and vendor risk.
  • CERT-In incident reporting, which requires notifying specified cyber incidents within six hours, alongside reporting to RBI, and keeping ICT logs in India for a mandated period.

The system audit that gates authorization

After in-principle approval, RBI gives you a fixed window to submit a System Audit Report from a CERT-In empanelled auditor, and the approval letter sets the deadline. The report has to show that the live environment meets RBI's technology requirements. So the platform must be built, hosted in India and operationally ready before final authorization, while you still can't onboard merchants as an aggregator. Teams that treat the audit as paperwork miss the window. Teams that run a pre-audit gap assessment several months ahead usually don't. After authorization, system audits continue every year.

The technology stack an applicant has to stand up, and what it costs

The main build-versus-buy decision is the core processing platform. You can license a white-label gateway from an established vendor such as FSS, ACI Worldwide or Worldline and add your own merchant experience on top. Or you can build the core in-house and buy components around it. For most first-time applicants, licensing is the better choice. A fixed audit window punishes unfinished software, and a vendor platform with existing Indian deployments arrives with documentation auditors already know. Build only if you have a payments engineering team that has shipped a switch before and a product strategy that depends on owning the routing logic.

Around the core you'll need:

  • Merchant onboarding and KYB: Indian verification APIs (Signzy, IDfy, HyperVerge and similar) for business registration, tax ID, bank account and director checks, plus case management for exceptions.
  • Fraud and transaction risk: a real-time rules and model engine such as FICO Falcon, Feedzai or a lighter alternative, plus merchant-level monitoring for chargeback ratios and category drift.
  • Ledger, escrow reconciliation and settlement: a double-entry ledger that ties to bank statements daily and produces the certification reports.
  • Tokenization: token requestor integration with the card networks' token services.
  • Key management: on-premises HSMs (Thales, Utimaco) or cloud HSMs in an Indian region.
  • Hosting: Indian regions from AWS, Azure or Google Cloud, or Indian colocation, with DR in a second Indian location.
  • Security operations: SIEM, managed SOC, vulnerability scanning and log retention set up for CERT-In requirements.
  • Disputes and grievance redressal: a ticketing workflow that tracks RBI's turnaround times for failed transactions and complaints.

Indicative year-one budget

The ranges below are indicative 2026 market ranges for a mid-sized PA-O applicant. They vary widely by contract, volume commitments and how much you do in-house. Indian vendors often quote in rupees, and global vendors tend to sit at the higher end. Confirm current pricing with each vendor.

Cost lineIndicative year-one range (USD)Main cost driver
Core gateway/switch (license and implementation)$150,000 - $800,000Licensed vs. built; payment methods covered
Cloud or colocation hosting, primary + DR in India$60,000 - $300,000Transaction volume; active-active vs. warm DR
Fraud and risk engine$40,000 - $200,000Per-transaction pricing; model customization
KYC/KYB verification APIs$0.10 - $1.50 per checkDepth of checks; merchant volume
HSMs and key management$40,000 - $150,000Hardware pair vs. cloud HSM
SIEM and managed SOC$50,000 - $250,000Log volume; 24x7 coverage
PCI DSS assessment and remediation$30,000 - $120,000Scope and starting maturity
CERT-In empanelled system audit$10,000 - $40,000Scope; re-audit if findings stay open
Legal, regulatory and application advisory$40,000 - $150,000Group complexity; foreign ownership
Compliance, risk and security staff$150,000 - $500,000Team size; local vs. expatriate hires

Hypothetical worked example: say a lending-tech company with 80 staff wants to add online collections for 2,000 small merchants. With a licensed core, cloud hosting, a mid-market fraud engine and a lean five-person compliance and security team, its year-one technology and compliance spend could plausibly land between USD 700,000 and 1.3 million. That sits on top of the ₹15 crore net worth, which has to stay intact on the balance sheet. The same firm building its own switch should plan for the top of that range or beyond, and a longer path to audit-ready.

A phased timeline from application to go-live, and the decision rule

RBI doesn't publish a guaranteed processing time, and in practice timelines vary a lot. Applications can be returned for incomplete documentation, net-worth shortfalls or concerns about promoters, and a returned application can mean starting over. Plan for the realistic range below, not the best case.

PhaseKey activitiesPlanning range
PreparationEntity and MOA changes, net-worth funding, foreign investment approvals if needed, board policies, gap assessment2 - 6 months
Application filingSubmission with financials, auditor certificates, promoter declarations and business plan2 - 6 weeks
RBI review to in-principle approvalQueries, clarifications, background checks with other regulators6 - 18 months, sometimes longer
Build and system auditProduction environment in India, PCI DSS, CERT-In empanelled audit, report submitted within the window set by RBIFixed by approval letter
Final authorizationRBI review of the audit report and compliance confirmation2 - 6 months
Go-live and rampMerchant migration, escrow live, first certifications1 - 3 months

End to end, 12 to 30 months is a sensible planning range, and these are planning figures, not RBI commitments. Two sequencing choices matter most. First, start building the platform during the RBI review, not after in-principle approval. Whatever is left to build then has to fit inside the audit window. Second, keep your commercial business running in the meantime by partnering with an authorized aggregator or a bank. Contract so you can migrate merchants later, and make sure the partner agreement doesn't block you from moving their data and settlement history.

Red flags that stall applications

  • Net worth met only through recent capital that isn't yet reflected in audited financials.
  • Group entities with unresolved regulatory actions in India or elsewhere.
  • A business plan that describes marketplace activity as aggregation.
  • Processing or log storage that touches non-Indian infrastructure with no clear localization design.
  • A compliance function made up of consultants, with no named, accountable employees.

The decision rule: pursue your own authorization if you can fund ₹25 crore of durable net worth, expect aggregation to become a core profit line within three years, and can staff a permanent compliance and security team. If any of those is uncertain, use an authorized PA partner. Revisit the decision once your volume makes the partner's take rate cost more than the regime would. Either way, commission a localization and escrow-ledger gap assessment this quarter. It's the cheapest way to learn how far you are from audit-ready. Have Indian regulatory counsel confirm current requirements before you file.

Questions buyers ask

Do I need a license to run a payment gateway in India?

No. RBI doesn't separately authorize gateways that only provide technology and never handle merchant funds. RBI does recommend that gateways follow its baseline technology standards, and banks and aggregators usually require this by contract. Once you collect and settle funds for merchants, you need payment aggregator authorization.

Can a foreign company get a payment aggregator license in India?

Not directly. The applicant has to be a company incorporated in India, though it can be foreign-owned within India's foreign investment rules. Investors from countries that share a land border with India need prior government approval, which adds time before RBI reviews the application. All payment data still has to be stored in India, whoever owns the company.

How does the escrow account for a payment aggregator work?

Non-bank aggregators keep customer collections in an escrow account at a scheduled commercial bank. RBI restricts credits and debits to specific categories such as merchant settlements, refunds and the aggregator's agreed commission. Balances can't be used for lending or operations. Auditors certify the balances periodically, and changing the escrow bank generally involves RBI.

Is a PA-CB cross-border license worth applying for alongside PA-O?

Only if a meaningful share of your merchants are importers or exporters. PA-CB adds foreign-exchange compliance, transaction value caps, purpose-code reporting and a bank relationship for foreign-currency flows, which raise costs and review time. Many applicants secure domestic authorization first and add cross-border later. Check current requirements with Indian regulatory counsel before deciding.

Written by the Apexnode Tech editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.