License for Money Transfer Business in India: Which Route Fits?

There is no universal license for a money transfer business in India. The required Reserve Bank of India (RBI) authorization depends on your activity: payment aggregation, cross-border merchant collections, foreign exchange, personal inward remittances, or regulated wallet issuance. A company paying its own suppliers through authorized providers is different from a business accepting and transferring money for customers.

For finance teams managing international payouts, the first question is therefore not “Which license should we buy?” It is “Which regulated activity does our funds flow create?” Transaction volume alone does not answer that question.

This guide focuses on Indian operations and India-linked commercial payment flows. It is a planning framework, not a legal determination; confirm current RBI directions and your proposed structure with Indian regulatory counsel before launching.

Start with the activity, not the payment rail

The Payment and Settlement Systems Act, 2007 governs authorization to operate payment systems. The Foreign Exchange Management Act, 1999 (FEMA) governs foreign exchange activities. A cross-border product can engage both frameworks.

Before selecting a route, document:

• Whose obligation is being paid: your company's invoice, a customer's remittance, or a marketplace seller's proceeds?
• Who controls the funds: which legal entity receives, holds, converts, releases, and refunds them?
• Payment purpose: goods, services, family maintenance, or another permitted purpose?
• Direction: domestic, inbound to India, or outbound from India?
• Customer relationship: who contracts with and onboards the payer and recipient?

Using NEFT, a bank API, or an overseas collection account does not itself establish permission to conduct the underlying business. An INR payment into an Indian bank account can still be the final leg of a cross-border commercial transaction.

Which regulatory route fits your business?

These categories are not interchangeable licenses. More than one regulated participant may be needed to execute a payment.

Payment aggregator authorization: merchant money, not every transfer

A payment aggregator facilitates merchant payments and handles funds within the applicable collection and settlement structure. The RBI's September 2025 framework distinguishes online, physical, and cross-border aggregation, as described in Saraf and Partners' analysis of the Payment Aggregator Directions.

For a non-bank applicant, the framework requires an Indian-incorporated company. The cited analysis describes minimum net worth of INR 15 crore at application, increasing to INR 25 crore by the end of the third financial year after authorization. These are net-worth requirements, not a license purchase price or a complete launch budget.

Cross-border payment aggregation requires separate attention. Import, export, and combined scopes are distinguished in Skydo's explanation of PA-CB authorization. Domestic authorization alone should not be treated as permission to aggregate cross-border payments.

For operators, this means mapping each collection and settlement account to its permitted function. Do not assume that one pooled balance can support domestic merchant settlements, export receipts, outward supplier payments, and refunds without restrictions.

Foreign exchange authorization: the permitted activity matters

FEMA authorization is separate from payment-system authorization. Authorized Dealer Category-I banks, Category-II entities, and Full-Fledged Money Changers have different permitted activities. An FFMC license is not a general license to transfer business payments internationally.

Ask which entity performs the foreign exchange transaction and under which permission. A service provider arranging a conversion is not necessarily authorized to deal in foreign exchange itself.

The supplied research includes a press report of expanded AD-II permissions in May 2026, but does not independently establish the governing RBI text. Do not build a trade-remittance product around that report: obtain the applicable direction and the provider's authorization conditions.

MTSS: personal inward remittances, not vendor invoices

The Money Transfer Service Scheme supports eligible personal remittances from abroad, including family maintenance and assistance to visiting tourists. It is not a substitute for commercial import or export payment infrastructure. Razorpay's inward-remittance guide explains the distinction between personal-remittance channels and business receipts.

A contractor's service invoice does not become a family remittance because the beneficiary is an individual. The economic purpose, not simply the recipient's legal form, determines the appropriate route.

PPI authorization: stored value is a separate question

Issuing regulated prepaid payment instruments can trigger a separate authorization requirement. The RBI's November 2022 PPI FAQs explain instrument categories and distinguish closed-system instruments from RBI-regulated PPIs.

That historical guidance should not be treated as confirmation of every current permission. The supplied research identifies draft PPI changes circulated in 2026, but does not establish their finalization. Verify the operative rules before relying on capital thresholds, transfer functionality, or cross-border use.

Do you need your own authorization or a regulated partner?

Paying your company's own obligations does not, by itself, make the company a money transfer operator. However, receiving customer funds, maintaining customer balances, or deciding how third-party proceeds are distributed can change the analysis.

A partner-led model can reduce the regulated activities you perform directly, but it is not a blanket exemption. Contracts and actual operations must agree on who handles funds, onboards customers, conducts checks, executes transfers, and resolves complaints.

Before integration, request the partner's exact legal name, authorization status, permitted activities, relevant restrictions, and banking arrangements. Distinguish an application or in-principle approval from permission to conduct the proposed live activity. Our guide to evaluating cross-border payment companies in India addresses the subsequent provider-selection decision.

Build an application and launch-readiness checklist

The filing route and documents depend on the authorization category. Prepare the following before treating an application as submission-ready:

1. Written regulatory classification. Describe each service, payment purpose, jurisdiction, funds owner, and regulated participant. Include refunds and failed transfers.
2. Corporate and ownership records. Prepare incorporation documents, appropriate constitutional objects, ownership information, and director and management disclosures.
3. Capital evidence. Obtain the required auditor certification and model ongoing compliance. Separate regulatory net worth from operating expenditure and settlement liquidity.
4. Banking and account design. Document account ownership, permitted credits and debits, safeguarding arrangements, reconciliation, and settlement responsibilities.
5. Compliance procedures. Define customer due diligence, beneficial-owner checks, sanctions screening, transaction monitoring, reporting, and escalation responsibilities.
6. Technology controls. Document access rights, security policies, audit trails, business continuity, incident response, and applicable data-storage requirements.
7. Submission and launch gates. Confirm the current RBI application channel, required attachments, approval conditions, and any restrictions before commencing business.

Supporting KYC/KYB and tax-documentation workflows can organize evidence, but software does not confer regulatory permission or replace the accountable entity's obligations.

Turn the legal analysis into a payment-level control

The most useful output is not just a license checklist. It is an eligibility record attached to each payment, showing why that transaction belongs on the selected route.

Capture the payer and beneficiary legal identities, residency, commercial purpose, invoice or contract reference, currency, destination account, and responsible regulated provider. For Indian bank payouts, beneficiary name, account number, and IFSC will commonly be needed; cross-border documentation depends on the purpose and provider. Confirm requirements before promising a payment date.

Hypothetical example: An overseas company pays Indian designers for services. Its operations team should classify the payments as commercial receipts, not personal remittances. It should establish who onboards the designers, which permitted route carries the funds, who performs FX, and what receipt evidence the designers can obtain.

If that company later collects buyers' money and distributes proceeds to independent sellers, the original analysis may no longer hold. Customer-fund handling and merchant settlement introduce different questions, even if the payout API remains unchanged.

Maintain a launch gate for each new payment purpose, direction, or customer type. Separately measure FX costs, fees, document-review delays, and final credit confirmation: regulatory eligibility and payment speed are different controls.

Choose the permission before scaling the payout operation

The right license follows the activity—not the business name, interface, or number of recipients. Classify the funds flow, establish which permissions cover it, and then assign operational responsibilities.

Once that foundation is clear, evaluate Payouts.com payout automation for coordinating payment workflows and reconciliation. Start with a documented India corridor and a verified provider scope; expand only when the next flow has passed the same review.

Created with AI assistance. Sources are linked in the article; this content is general information, not legal, tax, or financial advice.