Regulatory Guidelines for Online Transfer Apps in India
Sending money in and out of India has moved almost entirely into apps. The rules that govern those apps have not stayed still. If you run a fintech that touches cross-border transfers into India, or you use one, understanding the regulatory scaffolding matters. It shapes what an app can offer, how it prices, how fast money settles, and what it must do when a transaction looks off.
This is a working guide to the framework a US-to-India online transfer app operates inside today. It covers RBI licensing, ongoing compliance obligations, reporting requirements, and the penalties for getting any of it wrong.
The regulatory stack, at a glance
Online transfer apps live at the intersection of two rulebooks. On the US side, they follow FinCEN’s money services business (MSB) framework and state-level money transmitter laws. On the India side, they follow the Reserve Bank of India (RBI) and the Foreign Exchange Management Act (FEMA), 1999. Neither side is optional.
For inbound remittances into India, RBI has laid out two main channels: the Rupee Drawing Arrangement (RDA) and the Money Transfer Service Scheme (MTSS). Both require a licensed Authorized Dealer bank in India as the settling partner. A foreign transfer app does not send rupees into India on its own. It routes the payment through a partner bank that holds an AD Category-I license and is empowered to credit the recipient’s account or UPI ID.
The mechanics matter because the licensing burden splits accordingly. The India-side partner bank carries the RBI license. The foreign app carries the US-side licenses and the operational responsibility for KYC, AML monitoring, and transaction records.
RBI licensing norms
The clearest way to read the licensing rules is to look at who does what.
Authorized Dealer banks handle the actual foreign exchange conversion and the domestic settlement inside India. They apply to RBI for AD Category-I authorization. A US-facing remittance app cannot become an AD bank itself.
Payment aggregators and payment gateway operators that process domestic transactions in India need a Payment Aggregator (PA) license from RBI under the March 2020 guidelines. This covers apps that collect payments on behalf of merchants.
For cross-border payment aggregation, RBI introduced the Payment Aggregator – Cross Border (PA-CB) framework in October 2023. It creates three categories: PA-CB for exports, PA-CB for imports, and PA-CB for both. Any app that intermediates cross-border payments for merchants (as opposed to person-to-person remittances) needs authorization under this framework.
For personal remittances specifically, foreign apps typically operate through the RDA route in partnership with an Indian bank, and their India-side flows are governed by that bank’s AD license and RBI’s master direction on RDA.
Prepaid Payment Instrument (PPI) licenses are a separate track and apply to wallets that hold value in INR for users. Most cross-border transfer apps do not need a PPI because they do not hold customer INR balances. Sliq Pay is a cross-border payments app, not a wallet. It links a US bank account and sends the money directly through partner rails, so no INR balance is stored.
Compliance obligations
Once an app is up and running, the compliance workload is continuous. Six areas draw the most regulator attention.
KYC and customer due diligence. RBI’s Master Direction on KYC sets the baseline. Every remittance customer must be verified at onboarding using government-issued identity documents and address proof. For cross-border apps, verification of both the sender (US side) and the beneficiary (India side, where the app has that information) matters. Enhanced due diligence applies to higher-value transfers and to any customer flagged as high risk.
AML and CFT programs. Under the Prevention of Money Laundering Act (PMLA), 2002 and its updated rules, reporting entities must maintain a written AML program, appoint a Principal Officer, and screen transactions against sanctions and watch lists. The Financial Intelligence Unit – India (FIU-IND) is the reporting body for suspicious activity.
Transaction limits. For inbound personal remittances via the RDA channel, RBI caps individual transfers at USD 25,000 equivalent per transaction (subject to update), and there is no annual limit for personal remittances into India. For business remittances, the limits and purpose-code framework are different, and each transfer must be tagged with the appropriate purpose code under FEMA.
Purpose codes. Every cross-border transfer must carry an RBI purpose code identifying why the money is moving. Family maintenance is a different code than education fees, which is different from a business supplier payment. Apps must build purpose-code selection into the user flow, and the beneficiary bank reports the coded flows back to RBI. Sliq Pay makes it easier to pick the right purpose code by surfacing the options a user is likely to need at the point of sending.
Data localization. RBI’s 2018 directive requires that payment system data collected for transactions processed in India be stored on servers physically located in India. Foreign apps that route through Indian banking rails must comply, usually through their India-side partner.
Consumer protection and grievance redress. RBI’s Integrated Ombudsman Scheme covers digital transactions and requires apps to publish grievance officer contacts, respond within defined timelines, and escalate unresolved complaints to the RBI Ombudsman.
Reporting requirements
Reporting into Indian regulators happens on several tracks.
The India-side partner bank files R-Returns to RBI covering foreign exchange transactions on a fortnightly basis, categorized by purpose code and corridor. The transfer app supplies the underlying transaction data.
Suspicious Transaction Reports (STRs) go to FIU-IND when a transaction fits any of the red-flag criteria in the PMLA rules. There is no monetary threshold; the trigger is the suspicion itself. Cash Transaction Reports (CTRs) apply to cash of INR 10 lakh and above, which is less relevant for pure digital apps but still tracked at the partner-bank level.
Cross-Border Wire Transfer Reports (CBWTRs) are filed for transactions above the defined threshold and are how FIU-IND builds visibility into international flows.
Sanctions screening against the UN, OFAC, EU, and India MHA lists must be run at onboarding and again at transaction time. Positive matches must be frozen and reported, and false positives must be documented and cleared.
Penalties for getting it wrong
The consequences of non-compliance sit on a spectrum.
Under FEMA, contraventions can attract monetary penalties of up to three times the transaction amount involved, or INR 2 lakh where the amount is not directly quantifiable. Continuing contraventions attract additional daily penalties. FEMA violations can also lead to compounding proceedings and, in serious cases, prosecution.
Under PMLA, failures in AML compliance can lead to monetary penalties, and in serious cases, prosecution of the Principal Officer and directors. Repeated failures can trigger a review of the underlying license and, at the extreme, suspension or cancellation.
RBI can also issue directions restricting the volume or geography of transactions, freezing new customer onboarding, or requiring divestment of certain business lines. Public enforcement actions have been increasingly common in the payments space over the past three years.
Reality Check: What this means for users
A well-regulated app is slower to launch, more careful about what it asks at signup, and often more transparent about fees than a lightly regulated one. If an app cannot tell you who its partner bank is, which regulator licenses it, or how to file a grievance, that is a signal.
Sliq Pay operates in the US as a registered Money Services Business with FinCEN (NMLS ID 2714589; MSB Registration No. 31000298221871) and settles India-side transactions through a licensed banking partner under the RDA framework. That structure is what allows transparent, mid-market FX and instant settlement while staying within the RBI rulebook.
Travel Tip: Before you pick an app
Before you send your first transfer, take two minutes to check three things. Look for the app’s operating entity and license number. Look for a named partner bank on the India side. Look for a published grievance officer and complaint timeline. If any of the three is missing, keep looking.
FAQs
Which regulator licenses online money transfer apps for India? RBI licenses the India-side infrastructure, primarily the Authorized Dealer bank the app partners with. The app itself is licensed in its country of origin. In the US, that is FinCEN registration plus state-level money transmitter licenses.
What is the difference between MTSS and RDA? MTSS is used by overseas principals partnering with Indian agents for small-value personal remittances, usually paid out in cash. RDA is used for higher-value personal remittances that are credited to bank accounts or UPI IDs, and it is what most modern digital apps use.
Is there an annual limit on how much I can receive from abroad in India? For personal inward remittances under RDA, there is no annual cap for the recipient. Each individual transfer is capped at USD 25,000 equivalent (subject to RBI updates). Business inward remittances follow separate purpose-code rules.
Do I need to declare inward remittances on my Indian income tax return? Inward remittances that are gifts or family maintenance from close relatives are generally not taxable, but disclosure rules apply above certain thresholds. This is a tax question, not a payments question, and a chartered accountant is the right person to ask.
What is a purpose code, and why does the app ask? Every cross-border transfer must be tagged with a purpose code that tells RBI why the money is moving. The tag flows through to R-Returns filed by the partner bank. Getting the code right protects both sender and recipient from downstream questions.
How does an app like Sliq Pay stay compliant while still being fast and cheap? Speed and cost come from routing through modern instant-payment rails (UPI, IMPS) rather than legacy wires, and from carrying zero FX markup. Compliance comes from full US MSB registration, an India-side AD bank partner, biometric KYC, and AI-based AML monitoring on every transaction. The two are not in tension. You can join the waitlist at sliq-pay.com.
What happens if I send money for the wrong purpose code? The partner bank may reject the transaction, or credit it and later request clarification. In serious cases (for example, using a personal remittance code for a business transaction), FEMA penalties can apply.
Can an app operate in India without a partner bank? No. Foreign apps cannot directly credit rupees to Indian accounts. The India-side leg is always run by a licensed Authorized Dealer bank.
Disclaimer
The information provided on this blog is for general informational purposes only and does not constitute legal, financial, tax, or professional advice. Product features, pricing, eligibility, and availability may vary by country, user type, regulatory requirements, and are subject to change.
Please refer to Sliq Pay’s Terms of Use and official product pages for the most accurate and up-to-date information. Sliq Pay makes no representations or warranties regarding the completeness, accuracy, or reliability of the content.
