First published 2026-06-27 · Updated June 27, 2026 · Fintech · 12 min read
A regulatory breakdown of RBI's Payment Aggregator-Cross Border (PA-CB) guidelines. Learn the net worth guidelines, escrow operational rules, and transaction limits for export and import payment flows.
In late 2023, the Reserve Bank of India (RBI) issued a comprehensive framework regulating Payment Aggregators facilitating cross-border transactions (PA-CB). This circular splits cross-border payment operations into three licenses: Export-only (PA-CB-E), Import-only (PA-CB-I), and combined Export-Import (PA-CB-E/I). Any platform routing overseas payments to Indian merchants or processing domestic credit card charges for foreign vendors must comply.
Prior to the circular, cross-border payment hubs operated in a regulatory grey area, frequently routing funds through shell companies or offshore clearing portals. RBI's new rules enforce high financial standards, requiring LSPs to register as non-banking financial entities and maintain strict local accounting data.
The primary hurdle for fintech startups is the minimum net worth requirement. Non-bank PA-CBs must hold a minimum net worth of ₹15 Crore at the time of application. Entities already operating before 31 October 2023 had to reach ₹25 Crore by 31 March 2026 — a deadline now in force — while newly authorised entities must reach ₹25 Crore by the end of their third financial year. Failing to meet the applicable threshold requires the company to cease cross-border aggregation activities immediately.
Operationally, PA-CB players must establish dedicated escrow accounts with RBI-regulated commercial banks. Import funds must land in a domestic import escrow before distribution, while export funds route through an export escrow with daily settlement sweeps. Mixing domestic and cross-border cash balances in a single pool is strictly prohibited.
Under the RBI circular, cross-border payment aggregators must map their migration schedules to strict regulatory timelines. Entities operating prior to the circular must submit their license application before the MeitY and RBI deadlines, showing proof of net worth. Newly formed startups must secure the ₹15 Crore net worth registration upfront before routing any overseas transactions.
Operationally, escrow accounts must be reconciled daily. The payment gateway must match incoming foreign remittances to domestic merchant payout logs, compiling a daily transactional index. This index is reported to the central banking database monthly, ensuring that all import-export operations are transparent and fully auditable by financial regulators.
We analyzed this specific compliance circular to help software founders, legal officers, and product managers build robust regulatory structures. In a rapid fintech and SaaS economy, staying aligned with SEBI, RBI, FEMA, and DPDPA mandates is essential for long-term growth and capital scaling. By documenting the exact APIs, ledger schemas, and audit milestones on this page, product engineering teams can confidently map out development goals and prevent costly compliance delays.
Every product engineering team must weigh integration speed against long-term operating costs and architectural flexibility. Choosing an all-in-one managed platform (like Razorpay or Firebase) minimizes initial time-to-market, which is perfect for validation phases. However, as transactional volumes scale, transitioning to decoupled or self-hosted services (like Juspay or Supabase) provides crucial advantages in billing efficiency, API customizability, and database query performance. Teams should design their codebases modularly, abstracting integration layers so that gateways or database engines can be swapped or augmented without requiring complete application rewrites.
Building high-scale software applications in India requires a deep understanding of local constraints, high latency networks, and rapid regulatory updates. Product managers and engineering leads must prioritize structural data integrity, strict audit logs for compliance, and telemetry monitoring at the edge. By designing architectures that balance user experience with regulatory requirements, platforms can successfully minimize churn, optimize transaction success rates, and build robust technology stacks that support sustainable growth in India's competitive digital economy. Keeping stacks aligned with RBI and government portals is no longer optional; it is the core foundation of product engineering.
To succeed in India's highly regulated technology landscape, platforms must treat compliance as a core product feature. Startups should design modular databases, build automated report queues, and establish strict access control ledgers. By building privacy and audit trails directly into your source code, you ensure the stack can adjust to new rules instantly, protecting your platform from legal liabilities and customer attrition.
Join 2,300+ product leaders getting real-time insights, compliance breakdowns, and deep technology teardowns delivered daily.
Subscribe to the Brief →