India’s digital payments ecosystem runs on strict regulatory oversight, especially for entities that handle customer funds. Payment Aggregators sit at the center of this structure. They onboard merchants, collect payments, manage escrow accounts, and settle funds. Because they directly touch money, RBI imposes clear licensing, capital, and governance requirements.
In recent years, RBI has tightened compliance timelines for PAs that do not meet the required standards. Some were told to pause onboarding. Others were instructed to wind down activities entirely. These decisions came as part of the RBI’s objective to strengthen financial stability and ensure that customer funds remain protected at all times.
Understanding the compliance timeline and wind-down rules helps merchants choose platforms that can continue to operate smoothly without disruption.
Why RBI Enforces Strict Timelines for PAs
The Payment Aggregator Framework introduced a compulsory authorization requirement. Any entity that collects payments on behalf of merchants must be approved by RBI and must demonstrate:
• minimum net worth thresholds
• escrow account controls with scheduled commercial banks
• audit readiness and governance policies
• merchant onboarding standards
• KYC and risk monitoring capability
When an application is submitted, RBI reviews the PA’s internal systems, capital structure, promoters, data policies and fund flow architecture. If the PA fails to meet the criteria within the compliance window, RBI does not allow it to continue operating in the same capacity.
What Happens When a PA Fails Compliance
If a PA does not meet RBI’s requirements, it must begin a structured wind down. The regulator usually specifies:
- A deadline for stopping new merchant onboarding.
- A deadline for completing existing settlements.
- A requirement to return unsettled funds without delay.
- A clear instruction to close or migrate merchant accounts.
- A prohibition on handling new transactions.
These steps ensure that merchants and customers do not face risk due to operational gaps.
Common Triggers for Wind Down Decisions
RBI may instruct a PA to wind down if it identifies issues such as:
• insufficient net worth
• failure to maintain escrow norms
• poor governance or incomplete audits
• weak KYC practices
• non compliant data storage or processing
• high operational risk or recurring settlement delays
The regulator prioritizes financial safety. If a PA cannot meet these standards, the wind down requirement protects merchants from future disruptions.
Timeline Usually Followed During Wind Down
Although RBI decides timelines on a case by case basis, the pattern is consistent across past directives.
Stage 1: Pause on onboarding
The PA must immediately stop onboarding new merchants. Existing merchants may continue processing transactions for a limited time.
Stage 2: Restriction on new transactions
RBI may instruct the PA to stop accepting new transactions entirely once the initial period ends.
Stage 3: Settlement of all pending amounts
The PA must settle all pending merchant payouts within a specified deadline. This is non negotiable.
Stage 4: Merchant migration
Merchants must be given time to move to alternative providers. The PA must cooperate fully with this transition.
Stage 5: Closure of accounts
Once all settlements are complete, the PA winds down operations in accordance with RBI’s directive.
The timeline is designed to prevent interruptions in the merchant’s business while ensuring an orderly exit for the non compliant PA.
How This Impacts Indian Merchants
Merchants often face disruptions when a PA is instructed to wind down:
• payouts may take longer than usual
• support teams may be overloaded
• refund or dispute management could slow down
• merchants must quickly search for new platforms
• documentation may need to be revalidated
This is why merchants are advised to choose platforms with clear licensing, strong compliance and stable operational practices.
Why India Focused Inward Remittance Platforms Offer Stability
Platforms designed directly for India’s regulatory environment face fewer compliance conflicts because their systems are built for RBI norms from the start. They do not operate global wallet models or multi region data structures that often clash with local regulations.
This alignment creates a straightforward onboarding experience and reduces the risk of sudden operational interruptions.
Conclusion
RBI’s compliance timelines and wind down rules exist to protect merchants and customers from operational and financial risk. When a payment aggregator fails to meet regulatory standards, the structured wind down process ensures that settlements are completed, funds are returned and merchants have time to shift to a compliant provider.
For businesses that depend on smooth and predictable cross border payments, choosing a platform that is fully aligned with India’s regulatory framework is essential. It reduces the risk of service disruption and provides long term stability in how international payments are received and settled.
Why BRISKPE Provides a Stable Alternative for Cross Border Receivables
BRISKPE operates entirely within India’s inward remittance rules, which means its flows, documentation and KYC structure match RBI expectations from the beginning. There is no dependence on global wallet architecture or restricted features. Foreign payments are collected through virtual account details, converted at live interbank rates and settled in INR with complete compliance documentation.
Because this model is built for India, the risk of sudden regulatory disruption is significantly lower. Exporters, freelancers and agencies get predictable settlements without facing the uncertainty that arises when a non compliant PA is instructed to wind down.
