Why This Is More Urgent Than a Typical Compliance Gap
RBI’s Regulation of Payment Aggregators Directions, 2025 consolidated years of prior guidance into a single framework, and one of the six explicit conditions for a non-bank PA to get authorized is registering with FIU-IND.
The compliance deadline for existing entities to be authorized, or wind up operations, was 28 February 2026.
Who This Is For
Non-Bank Payment Aggregators
Online (PA-O), physical/proximity (PA-P), or cross-border (PA-CB), that haven’t completed FIU-IND registration as part of their RBI authorization.
Payment Gateways Operating Under Legacy Guidance
RBI’s 2025 Directions replaced the older 2020 PA-PG Guidelines. If your compliance was built for the old framework, it likely needs updating.
Businesses That Assumed RBI Authorization Alone Was Enough
FIU-IND registration is a condition of that authorization, not an optional add-on to it.
Cross-Border Payment Aggregators Specifically
Face additional obligations — separate Inward and Outward Collection Accounts, restrictions on foreign currency dealing — on top of the standard FIU-IND requirement.
What We Do
Confirm Where You Actually Stand
We check whether your FIU-IND registration is in place and correctly tied to your RBI authorization status, not assumed.
Handle the Registration Itself
Including Principal Officer appointment, timed to support your RBI authorization application rather than running as a disconnected process.
Build the Reporting Infrastructure You Need
Automated sanctions screening at onboarding, STR and CTR workflows sized for high transaction volumes.
Support Cross-Border Structuring
If you’re a PA-CB, including how escrow and collection account requirements interact with your FIU-IND reporting obligations.
Benefits of Getting This Right
| Benefit | What It Means for Your Business |
|---|---|
| Your authorization isn’t at risk | Since FIU-IND registration is a condition of RBI authorization, getting it wrong doesn’t just create a PMLA problem, it threatens your ability to operate as a PA at all |
| You’re not caught by the transition | RBI consolidated three separate prior frameworks into one. Businesses still compliant with the old rules are compliant with nothing current |
| Merchant and partner confidence | Banks and enterprise merchants increasingly ask PAs to demonstrate FIU-IND registration before integrating, not just an RBI authorization letter |
Eligibility and What Needs to Be in Place
Before registering, a payment aggregator generally needs:
- A functioning KYC/CDD program meeting both RBI’s onboarding requirements and PMLA’s reporting-entity standard.
- Escrow account arrangements with a Scheduled Commercial Bank, no co-mingling of merchant funds with operational funds.
- A Principal Officer appointed and filed with FIU-IND specifically.
- Automated transaction monitoring capable of flagging patterns at the volume and speed PA transaction flows actually run at, not a manual process.
- Data localization compliance, since payment transaction data must sit on India-based servers, relevant to how your monitoring and reporting systems are actually built.
Documents Involved
| Document | Why It’s Needed |
|---|---|
| RBI authorization application or Certificate of Authorisation | Establishes your PA status and category (PA-O/PA-P/PA-CB) |
| Escrow account confirmation | Shows fund segregation meets RBI’s structural requirements |
| Principal Officer appointment (FIU-IND specific) | Separate filing from anything submitted to RBI |
| AML/CFT policy sized for transaction volume | Generic policies rarely reflect real PA transaction speed and scale |
| Net-worth and capital documentation | Supports the RBI side of authorization, relevant context for FIU-IND review too |
Why Choose Finlaw Consultancy?
We Treat FIU-IND Registration as Part of Authorization, Not Separate From It
Most compliance support handles these as two disconnected projects. We coordinate them, since RBI now requires that they be coordinated.
We Track the Current Framework, Not the 2020 One
RBI’s 2025 Directions changed enough that older guidance is no longer a safe reference point.
We Understand PA-CB Specifically
Cross-border payment aggregators carry obligations — InCA/OCA structuring, foreign currency restrictions — that most generalist compliance advisors don’t handle regularly.
The Process
We Assess Your Current Authorization and FIU-IND Status Together
Since for a payment aggregator, the two aren’t meaningfully separate questions anymore.
We Register or Correct Your FIU-IND Status
Including Principal Officer appointment, structured to support rather than complicate your RBI authorization position.
We Build Reporting Systems Sized for Real Transaction Volume
Since a PA’s STR/CTR workflow needs to handle scale a smaller reporting entity never has to.
How Long It Takes
| Stage | Roughly How Long |
|---|---|
| Authorization and FIU-IND status review | 1–2 weeks |
| FIU-IND registration and Principal Officer filing | 2–6 weeks |
| Reporting infrastructure setup | 3–6 weeks, can run in parallel |
Ongoing Obligations
- STR filing within the required window, sized for the transaction volume a PA actually processes, not a low-volume reporting entity’s pace.
- CTR filing for qualifying cash-equivalent transactions, where applicable to your PA model.
- Escrow account integrity, no co-mingling, verified on an ongoing basis, not just at authorization.
- Data localization maintained continuously, not just demonstrated once at onboarding.
- Legacy merchant re-verification, if you had merchants onboarded under prior guidance who haven’t yet been brought up to current due-diligence standards.
Penalties for Getting This Wrong
The PMLA side follows the same Section 13 framework as every reporting entity: warnings, compliance directions, and monetary penalties.
- Warnings and directions to comply with specified instructions
- Monetary penalties under PMLA Section 13
- The risk of being an unauthorized PA required to wind up operations entirely, since FIU-IND registration is now tied to RBI authorization itself
Common Mistakes We See
- Treating FIU-IND registration as separate from RBI authorization. Under the current framework, it isn’t. Getting one wrong affects the other.
- Building compliance around the old 2020 PA-PG Guidelines. RBI’s 2025 Directions replaced that framework. Old documentation won’t satisfy current review.
- Underestimating cross-border obligations. PA-CB entities have structural requirements, InCA/OCA separation, foreign currency restrictions, that a generic PA compliance approach misses.
- Assuming legacy merchants are automatically compliant. Merchants onboarded under prior standards may need re-verification under current due-diligence requirements.
- Sizing AML systems for the wrong volume. A monitoring system built for a low-transaction-volume reporting entity won’t hold up against real PA transaction flow.
Not Certain Your Payment Aggregator Business Is Fully Authorized and FIU-IND Registered?
We’ll check both, tell you plainly where you stand, and fix whatever gap exists before it becomes an authorization problem.
