Cross-Border Payment Compliance in India: FEMA, RBI Regulations and PA-CB Framework

India’s cross-border physical and digital trade has been on a growing path as Indians received $155 billion in gross cross-border remittances in FY 2025-26. 

From IT and SaaS exporters to traders, Indians are invoicing clients in dollars every month as brands and businesses ship goods and services to Dubai and New York from the same warehouse that serves Delhi, and freelancers routinely collect fees from three continents in a single week. 

Add LawBhoomi as your preferred source on Google.

Add Now →

However, for corporate counsels and compliance officers, cross-border payment compliance is not a back-office reconciliation task. It is an operational continuity issue wherein a misclassified purpose code, even if done by mistake, can freeze a shipment’s export benefits. 

An unregistered payment aggregator can trigger regulatory action mid-transaction, or a missed FIRC can delay a GST refund cycle by months. 

The legal framework governing these flows has also tightened considerably over the past two years, and businesses operating on outdated assumptions about “standard banking rules” are the ones most exposed.

The Key Indian Regulatory Frameworks and Architecture for Cross-Border Payments

1. Foreign Exchange Management Act, 1999

FEMA remains the foundational statute governing every cross-border payment in India today, and its central distinction is between current account and capital account transactions. 

Find the latest legal internship opportunities, updated daily.

Find Internships →

Everything from export and import proceeds, service fees, and most trade-related remittances falls under current account transactions, which are generally permissible subject to RBI-specified conditions. 

However, capital account transactions like equity investment and external commercial borrowing, and similar flows, sit under a separate, more restrictive regime. 

Getting this classification wrong at the outset cascades into downstream reporting errors, so it remains the first checkpoint in any cross-border payment workflow.

2. RBI’s PA-CB Framework

The Reserve Bank of India’s October 2023 circular brought every entity facilitating cross-border payments for the import or export of goods and services under direct regulatory supervision as a Payment Aggregator – Cross Border (PA-CB) framework. 

This replaced the older Online Payment Gateway Service Provider (OPGSP) regime, which had permitted a simple and lenient standing arrangement with an Authorised Dealer bank rather than direct RBI authorisation.

However, as per the new consolidated Master Directions on Payment Aggregators shared in September 2025, the framework now governs and checks online PAs, cross-border PAs and even the offline PA category. Key parameters include;

• A per-transaction cap of ₹25 lakh for goods and services processed through a PA-CB.
• Enhanced due diligence requirements for transactions exceeding ₹2.5 lakh.
• A minimum net worth of ₹15 crore at the time of authorisation, rising to ₹25 crore by March 31, 2026, for existing non-bank PA-CBs.
• Import-only PA-CBs must route funds through an escrow arrangement into an Import Collection Account maintained with an AD Category-I bank.

3. AML/CFT and KYC Mandates

Cross-border flows are also under the purview of Prevention of Money Laundering Act, 2002 (PMLA) obligations that apply to regulated payment intermediaries. 

The key requirements of this framework include;

Find the latest legal internship opportunities, updated daily.

Find Internships →

• Beneficial ownership verification
• Ongoing transaction monitoring calibrated to risk
• Alignment with FATF’s travel rule expectations on originator and beneficiary information accompanying fund transfers 

For a compliance officer, the practical implication is that KYC on a cross-border payment partner cannot be a one-time onboarding exercise, and it has to be continuously auditable, particularly as transaction volumes and counterparty geographies expand.

Operational Challenges Businesses Face with International Settlements

The stringent legal framework implemented in India means execution frequently breaks down at three specific points.

• Purpose Code Allocation: Every inward or outward remittance must be tagged with an RBI purpose code that identifies the nature of the underlying transaction. A generic or mismatched code is not just an admin issue, but can lead to three problems;

• Misrepresent the nature of the transaction for tax purposes
• Delay GST refund eligibility
• Complicate DGFT incentive claims that depend on accurate classification

• Trade Settlement Reconciliation: The RBI needs to match customs data with bank remittances, and for this, it checks two databases;
  • Export Data Processing and Monitoring System (EDPMS) 
  • Import Data Processing and Monitoring System (IDPMS) 

So, if a transaction doesn’t match within the stipulated window, which is nine months, the business risks Caution List action, and it can restrict future outward remittances. 

RBI’s October 2025 circular eased this for small-value entries up to ₹10 lakh, permitting closure through self-declaration, but larger transactions still demand precise, document-backed reconciliation.

• Documentary Proof and Realisation: The physical Foreign Inward Remittance Certificate (FIRC) has been phased out in favour of electronic FIRCs and, from EDPMS data, electronic Bank Realisation Certificates. These are mandatory for GST refunds and export incentive claims. 

Choosing Between Manual Compliance and Regulated Automated Architecture

Build the Right Infrastructure to Operationalise Cross-Border Compliance

The regulatory shift toward PA-CB authorisation effectively pushes compliance obligations into the technical architecture of the payment stack itself, rather than leaving them to post-facto documentation. 

A licensed PA-CB is structurally required to embed purpose code mapping, escrow-based fund segregation, and reporting mechanics into the transaction flow, not as an add-on service, but as a condition of operating.

Cashfree, as one of the early entities to receive RBI’s PA-CB authorisation for exports and imports, illustrates how the regulatory framework can be operationalised through payment infrastructure. Its cross-border payment solutions are designed to support businesses with cross-border payment flows and associated compliance requirements. 

• Cross-border infrastructure automates purpose code assignment at the point of transaction.
• Generates e-FIRCs without the multi-week bank turnaround that manual channels typically involve.
• Maintains escrow-based fund segregation consistent with PA-CB requirements, without introducing friction into the buyer-facing checkout experience. 

For a compliance officer, the relevant point is not the speed claim itself, but the fact that these controls are built into the transaction layer, which materially reduces the manual reconciliation burden that otherwise falls on internal legal and finance teams.

Conclusion

RBI is consolidating oversight of cross-border payment intermediaries, and while doing so, the apex bank in India is tightening net worth and reporting standards, and digitising the reconciliation infrastructure that connects Customs, banks, and exporters. 

Explore LawBhoomi's free law library for students and lawyers.

Visit Library →

Businesses that treat this as a checklist to only satisfy the conditions post-transaction will keep encountering the same friction points like delayed FIRCs, unmatched EDPMS entries, misclassified purpose codes. 

Businesses that instead select payment infrastructure built around the PA-CB framework from the outset convert compliance into a structural advantage. It becomes the mechanism that lets a growing exporter scale into new markets without re-architecting its payment stack every time a regulatory circular is issued.