RBI Payment Aggregator License Checklist: Merchant Guidelines

July 2, 2026 · Checklists · 8 min read

Quick Verdict / TL;DR: This comprehensive analysis reviews the core features, operational architecture, and key verification metrics for RBI Payment Aggregator License Checklist. Evaluating system performance profiles and security standards prevents integration failures and ensures compliance.
Official Website & Resources: rbi.org.in
₹15 Cr
Minimum net worth threshold at application submission stage
₹25 Cr
Required capital threshold scale within 3 years of licensing
100%
Security standards compliance (PCI-DSS) across checkout nodes

The RBI Payment Aggregator Regulatory Framework

The Reserve Bank of India (RBI) regulates entities that facilitate payment collection for merchants. Obtaining a Payment Aggregator (PA) license requires digital platforms to satisfy capital adequacy norms, fit-and-proper criteria, and strict cybersecurity guidelines. Startups must configure robust escrow bank accounts, establish grievance redressal loops, and satisfy capital requirements before submitting license applications.

SQL Schema for Escrow Reconciliation Logs

RBI mandates that all merchant settlements pass through an escrow pool account. The following database table structures payment flows to verify ledger accuracy:

CREATE TABLE escrow_settlement_ledger (
  tx_id VARCHAR(64) PRIMARY KEY,
  merchant_id VARCHAR(32) NOT NULL,
  settlement_amount_inr DECIMAL(12, 2) NOT NULL,
  escrow_bank_ref VARCHAR(64) NOT NULL,
  status VARCHAR(20) CHECK (status IN ('initiated', 'settled', 'disputed')),
  settled_at TIMESTAMP WITH TIME ZONE
);
This schema tracks settlement flows, maintaining a 99.99% escrow account settlement reconciliation accuracy target.

Capital Rules and Compliance Deadlines

Under RBI guidelines, fresh applicants require a 15 Crore minimum net worth requirement at the time of application. The platform must increase this base to a 25 Crore target net worth requirement within three fiscal years. Startups monitor net worth metrics, submitting audited financial reports to the RBI to prevent licensing suspensions and business halts.

RBI PA Cyber Security Policy Config JSON

To comply with RBI's cyber security mandates, PA platforms define strict system access rules using JSON configs:

{
  "regulatory_body": "RBI",
  "cyber_security_policy": {
    "encryption_algorithm": "AES-256",
    "tokenization_enabled": true,
    "api_rate_limit_per_min": 1200,
    "audit_log_retention_years": 5
  }
}
This system maps transaction routing paths, protecting consumer data against unauthorized breaches.

Escrow Auditing and Local merchant Guidelines

Reconciling merchant pools requires daily audit reports. Compliance leads build escrow transaction logs, verifying that client payouts match merchant collections. Running weekly audits ensures that payment bridges follow RBI settlement timelines. This audit trail is critical for passing the annual audits mandated by local monetary authorities.

Escrow Balance Reconciliation Sweeps and Audit Check Parameters

To secure an RBI Payment Aggregator (PA) license, fintech platforms must follow capital adequacy rules. The PA must maintain a minimum net worth of ₹15 crore on application. Settlement funds must be held in a nodal escrow account with a commercial bank.

The bank sweeps merchant payouts on T+2 schedules. Developers configure reconciliation tasks to match transaction logs with escrow ledger changes daily. This automated check prevents fund co-mingling, satisfying central bank audits.

The Daily Brief — a daily update across 12 industries

One actionable growth breakdown every morning, across 12 industries — with an audio version in 21 languages. No fluff, just hard product teardowns and India benchmarks.

or