Table of Contents
With the rapid growth in India’s outbound travel market, global travel merchants are increasingly serving the Indian travellers across flights, hotels, tours and international experiences. While the opportunity is clear, many merchants overlook an important aspect; the reality of payment infrastructure. Outbound travel transactions from India fall under LRS, i.e., India’s Liberalised Remittance Scheme (LRS – Travel), when processed through local payment rails.
Understanding LRS Travel isn’t about compliance checklists. Understanding LRS travel includes deep diving into how real payment flows must be structured to avoid friction, drop-offs and operational overhead – especially with India’s growing foreign travel spending.
What Is LRS Travel?
The Liberalised Remittance Scheme (LRS) is a foreign exchange policy initiative introduced by Reserve Bank of India (RBI) under which resident individuals are allowed to remit up to USD 2,50,000 per financial year (April – March) for a set of permitted purposes, without requiring prior approval from the RBI.
LRS is not limited to travel. It governs a wide range of outward remittances made by individuals, including:
- International travel and tourism
- Education abroad
- Medical treatment overseas
- Maintenance of relatives outside India
- Gifts and donations
- Overseas investments such as stocks, securities, or property
Within this framework, travel is one of the most common and recurring use cases. Payments for flights, overseas hotels, tour packages, cruises, and international experiences all fall under the LRS – Travel category when made by Indian residents.
Though RBI has not published a detailed monthly breakdown of LRS remittances by purpose, industry and banking data consistently point towards travel forming a significant share of outward remittances. This is true especially during peak travel seasons. This matches the broader market projections that suggest the India’s outbound travel market has a strong trajectory through the end of the decade.
The key takeaway for global travel merchants is that LRS is not an edge-case regulation. It is the primary framework under which Indian residents are allowed to pay for international travel and it directly influences how such payments must be structured when Indian payment rails are involved.
Why LRS Travel Affects Payment Design
Whenever a travel payment moves from India to a foreign merchant through an Indian payment aggregator, it is processed as an LRS – Travel remittance.
This includes payments for flights, overseas hotels, tour packages, cruises, and international experiences.
Once Indian payment rails like UPI, RuPay, or NetBanking are involved, the transaction is no longer just a payment — it becomes a regulated foreign-exchange flow.
That has immediate product implications.
At the point of checkout, the payment must already carry the information Indian banks require to clear and settle the transaction:
- Traveller identity (who is paying)
- Travel purpose classification (why the money is moving abroad)
- Compliant FX routing through RBI-authorised channels
- Bank-ready reporting for reconciliation and settlement
These are not post-payment checks.
They must be embedded into the payment flow itself.
When payment stacks aren’t built this way, the failure shows up in very real ways:
- Transactions drop or get held after authorisation
- Settlements slow down or trigger bank queries
- Reconciliation becomes manual and error-prone
In short, LRS Travel isn’t a compliance layer you add later.
It’s a design constraint that shapes how India-origin travel payments must work from checkout through settlement when local payment methods are enabled.
Core LRS Travel Requirements Explained
Here are the elements that matter most to merchants and their payment stacks:
Purpose Code Tagging
Every LRS travel transaction must be tagged with an RBI-defined purpose code that identifies the reason the funds are being sent abroad.
Purpose codes are not optional:
- Without accurate tagging, banks struggle to classify transactions
- Outbound FX tracking can break
- Settlements may be delayed or questioned
In stacks that retrofit LRS after payment, this typically becomes a manual, post-transaction step.
PAN Capture
LRS requires capture of the traveller’s Permanent Account Number (PAN), a unique identifier essential for:
- Tracking cumulative spend against the annual USD 250,000 limit
- Accurate reporting and bank reconciliation
- Downstream tax and regulatory processes such as TCS
Capturing identity data without interrupting checkout flow is a design challenge most global stacks aren’t optimised for.
TCS
For certain outbound travel spends beyond defined thresholds, Tax Collected at Source (TCS) applies under Indian tax regulations.
From a payment design perspective, this means:
- Identifying when TCS is applicable
- Calculating the correct TCS amount
- Collecting and reporting it in a traceable manner
When TCS handling is unclear or inconsistent:
- Customers face pricing confusion at checkout
- Finance teams deal with reconciliation gaps
- Merchants inherit avoidable compliance risk
Well-designed LRS flows treat TCS as part of the payment logic.
A2 Reporting & Bank Alignment
Authorised Dealer (AD-I) banks demand detailed reporting for outward remittances, including:
- Reason for remittance
- Identity of the remitter
- Nature and value of the foreign exchange outflow
Incomplete or inaccurate reporting can lead to:
- Delayed settlements
- Reconciliation mismatches
- Increased scrutiny in audits
These consequences rarely appear at low volumes but become visible quickly as travel demand grows.
FX Routing, Different From Card FX
LRS travel transactions must go through RBI-authorised FX routes, distinct from standard card-network FX flows.
Without compliant FX routing:
- Transactions can be flagged
- Settlement timelines become unpredictable
- Finance teams lose visibility and control
This area is one of the most common failure points for global stacks.
Why LRS Travel Matters to Merchants
For global travel merchants, LRS Travel becomes relevant when payments are routed through an Indian payment aggregator to enable local payment methods.
When transactions are processed entirely through foreign payment aggregators using international cards, LRS requirements are not enforced at checkout. These setups are operationally simple, but they limit access to India-native payment methods and often result in lower conversion.
LRS becomes relevant at the moment merchants move to Indian payment infrastructure to unlock higher checkout success. At that point, LRS Travel affects three practical dimensions of the business:
1. Conversion: Unlocking India’s Preferred Payment Methods
Conversion challenges are not caused by LRS compliance itself. They arise when merchants rely only on international card acceptance via foreign PAs, which do not support India-native payment methods.
Indian consumers prefer UPI, RuPay, and NetBanking, which deliver higher success rates and better conversion rates. Enabling these methods is the primary lever for improving conversion from Indian travellers.
2. Checkout Experience: Where LRS Comes Into Play
Once payments are routed through Indian payment rails, outbound travel transactions fall under LRS – Travel.
At this stage, requirements such as PAN capture, purpose declaration, and transaction classification must be handled correctly within the payment flow without disrupting checkout.
Payment stacks that treat these as manual or post-transaction steps often reintroduce friction just as conversion improves.
3. Settlement Predictability and Operational Scale
As India volumes grow, correct LRS handling becomes critical for settlement reliability.
LRS-aligned flows help ensure:
- Proper reporting to authorised dealer banks
- Approved FX routing
- Fewer settlement exceptions and bank queries
For merchants, this results in predictable settlements, cleaner reconciliation, and lower operational overhead at scale.
LRS- Travel Context in Numbers
- India’s LRS allows up to USD 250,000 per resident individual per year.
- Outbound travel remittances from India alone were estimated at ~USD 17 billion in FY24, making travel one of the largest and most consistent categories under LRS.
- Within monthly snapshots, travel remittances routinely exceed $1 billion.
- Travel often accounts for the largest share of LRS outflows, compared with other purposes such as education or investment.
These figures underscore just how large and dynamic this segment is, and why it must be built into commercial payment design.
Where LRS Shapes the Payment Experience
Once a travel merchant starts accepting payments through Indian payment rails, LRS becomes a structural part of how the payment flow is designed and settled. It shapes how identity is captured, how money moves, and how reliably settlements scale.
For global travel merchants, the implication is simple: India cannot be served with card-only assumptions or post-transaction fixes. Payments must be designed for Indian behaviour and Indian infrastructure from day one.
That design lens is what separates experimentation from scale, and it’s exactly what global merchants need to understand before going deeper into India’s outbound travel opportunity.
