Why banks call travel 'high risk': the gateway playbook

You submit your KYC to a payment gateway expecting the usual onboarding wait, and then the mail arrives: your business is classified "high risk," the MDR quoted is meaningfully above what a retail merchant pays, and a slice of every settlement will sit in a rolling reserve for months. If you've been comparing options for the best payment gateway for travel agency India offers, this is the wall almost every operator hits, and almost nobody explains why.

The reason is structural, not personal. A client pays you today for a departure four to twelve months out, so the gateway is underwriting a promise, not a completed sale, and plenty can go wrong (illness, a visa rejection, a cancelled flight, a supplier going under) between the charge and the trip. That gap is why gateways price travel differently from retail, and why reading a merchant agreement carefully, before you sign, saves your agency real money.

This post covers what high-risk classification costs you, how to compare gateways for a travel business, what underwriting teams want, the rules for taking international cards, and when UPI-plus-bank-transfer beats a gateway outright.

Why banks call travel a high-risk merchant category

Travel gets classified high risk because of the long gap between collecting payment and delivering the service, stacked on high average ticket sizes and heavier chargeback exposure. An underwriter sees a booking, not a completed transaction, and prices that gap.

As gateways' own guidance to travel merchants puts it, travel businesses face 4-12 month lead times between booking and fulfilment, which is why processing fees run 20-30% higher than a standard retail merchant, on top of rolling reserves and chargeback fees. Four things stack into that pricing:

• Time lag risk. A lot changes between a January booking and an October departure: airline schedule changes, visa denials, political instability, the client's own circumstances. The gateway is exposed if a dispute lands months after the original charge.
• High ticket sizes. A single international package can easily run into lakhs per traveller. One disputed transaction does more damage to a gateway's risk book than a hundred small retail ones.
• Chargeback exposure. Clients dispute charges for reasons that have nothing to do with fraud: a change of plan, a family emergency, a supplier going bust. Card networks still process these as formal disputes, and fighting a dispute costs the gateway money whether or not you win it.
• Refund complexity. Cancellation terms are rarely all-or-nothing. Partial refunds, credit notes, and non-refundable supplier components make travel refunds harder to automate than a standard e-commerce return.

None of this means your agency did anything wrong. The category carries the underwriting cost, and every gateway operating in India prices for it, not just the one that flagged you.

What high-risk classification actually costs you

Three costs usually stack together: a higher MDR (merchant discount rate), a rolling reserve that holds back a slice of every settlement, and slower access to your own money.

Higher MDR. Expect a quote running the 20-30% premium noted above over what a retail merchant would pay for the same card mix. Run the arithmetic on your own ticket sizes: if a retail merchant is quoted 2% and your travel quote comes in at 2.5-2.6%, that half-point difference on a ₹2,00,000 package is roughly ₹1,000 per booking, and it adds up fast across a season.

Rolling reserve. A rolling reserve holds back a percentage of each day's settlement for a fixed window, releasing it once that window passes without a dispute against it. It's a cushion for the gateway if a chargeback arrives after your money has left, not a penalty, but it still means part of your own turnover sits somewhere you can't spend it.

Example: Say your agency processes ₹15 lakh a month through a gateway holding a rolling reserve. At any given time, a meaningful slice of that month's turnover sits locked up rather than in your account, with the oldest portion only starting to release once the reserve window passes. Build that lag into your working-capital planning, especially in the months before a peak season when you need cash free for hotel deposits, not stuck in reserve.

Slower settlement. High-risk merchants often get pushed onto longer, less predictable settlement cycles than standard retail merchants get. Ask for the exact cycle in writing, not "standard settlement," which means nothing on its own.

Careful: Don't judge a gateway quote by its headline MDR alone. A slightly higher MDR with a shorter rolling reserve and faster settlement can be cheaper for your cash flow than a lower MDR that locks up money for three months. Ask for all three numbers together, in the same email, before you compare anything.

Comparing gateways for a travel business

Razorpay and PayU both publish travel-specific onboarding guidance because they actively compete for this segment, but headline rates published on a website rarely match what your agency will be quoted once underwriting looks at your live business. Run this checklist against any written quote before you sign with any gateway.

What to ask for	Why it matters	Red flag
MDR broken down by card type (domestic debit, domestic credit, international, UPI)	International and credit-card MDR is usually higher than UPI or domestic debit; a blended "average" rate can hide this	Gateway won't break it down in writing
Settlement cycle in calendar days	Determines when booking money actually reaches your account	"Standard settlement" with no number attached
Rolling reserve percentage and release window	This is the working capital that's actually locked up	Reserve terms only in a linked PDF, not in the quote itself
Chargeback and dispute support process	Someone needs to represent your side when a client disputes a charge months later	No named contact or SLA for dispute response

Ask each shortlisted gateway for these numbers side by side, in the same format. A gateway that answers cleanly and in writing is telling you something about how it'll behave the day you actually need to dispute a chargeback.

Surviving underwriting: what gateways want to see

Risk teams approve travel merchants faster when the application already answers the questions they'd otherwise raise a month into review. Front-load these before you submit:

1. GST registration and business PAN, matching the entity name on the bank account you'll settle to.
2. Bank statements for the account you'll settle to, showing it's an active business account.
3. Your published cancellation and refund policy, ideally already live on your website or booking terms.
4. Sample invoices or quotations showing typical ticket size and package structure.
5. If you're switching gateways, your chargeback ratio from the last 6-12 months of processing, rather than letting the new gateway discover it later.

A clean chargeback history, even a short one, is the single strongest lever you have to negotiate a lower reserve percentage after six months to a year of processing. Ask explicitly; gateways rarely offer a reduced reserve unprompted.

Accepting international card payments legally

To take international card payments, your agency needs a gateway that's actually licensed for cross-border processing, not one that simply shows an "accept international cards" toggle in its dashboard. Cross-border processing requires RBI-authorised payment aggregator status, data localisation compliance and FEMA purpose codes on the gateway's side.

What this means for you in practice:

• RBI-authorised aggregator. Confirm your gateway holds this authorisation directly; some smaller resellers route through a licensed aggregator without saying so, which matters if something goes wrong.
• Data localisation. Transaction data has to be stored in India. This is the gateway's compliance burden, but ask about it anyway, because an unlicensed operator cutting corners here is a business you don't want processing your clients' card data.
• FEMA purpose codes. Every cross-border transaction needs the correct purpose code recorded, which is how the gateway and RBI classify what the payment is for. Your gateway handles the code assignment, but you should know it exists so a mislabelled transaction doesn't hold up a settlement.

None of this is something you configure yourself. It's a filter for picking a gateway: ask directly whether they hold RBI payment aggregator authorisation, in writing, before you route a single international card payment through them. These RBI and FEMA requirements reflect guidance current as of July 2026 and can change; confirm the latest position with your CA or the gateway's compliance team before you rely on it for a live transaction. This sits alongside the rules for paying foreign DMCs and hotels from India legally, which cover the outbound side of the same FEMA framework.

Rolling reserve meaning, and how to negotiate it down

A rolling reserve is a percentage of each settlement that the gateway holds back for a fixed period rather than paying out immediately, releasing it once that window passes without a chargeback against it. It's the gateway's insurance against disputes that land after your money's already gone out the door.

It isn't fixed forever. After 6-12 months of clean processing (low chargeback ratio, no repeated disputes), most gateways will discuss reducing either the reserve percentage or the holding window, but only if you ask. Put the request in writing, reference your processing history, and ask for the revised terms in an amendment, not a verbal assurance from a relationship manager.

When UPI and bank transfer beat a gateway entirely

For a domestic-heavy book with clients comfortable paying by UPI or NEFT, a gateway isn't always worth the MDR and reserve overhead. If most bookings are Indian clients on domestic or short-haul packages, a straightforward UPI collection link plus bank transfer for larger advances can be cheaper and simpler than routing everything through a high-risk-priced gateway.

The trade-off: you lose the ability to take international cards or offer card-EMI on large outbound packages, and you take on more manual reconciliation matching payments to bookings without an automated payment page. It also gives clients less recourse in a genuine dispute, which cuts both ways: fewer chargebacks against you, but a client base that expects you to sort problems directly.

The honest rule: if outbound and card payments are a small share of your revenue, don't pay high-risk gateway pricing on your entire turnover just to cover that slice. Route the international, high-ticket packages through a gateway, and let UPI and bank transfer carry the rest. Keep your advance receipt format consistent either way, so a client paying by UPI gets the same GST-ready paperwork as one paying by card.

Common questions

What is a rolling reserve on a payment gateway?

A rolling reserve is a percentage of each day's card settlement that a gateway holds back rather than paying out immediately, releasing it after a fixed window once no dispute has landed against those transactions. It protects the gateway against chargebacks that arrive after your money would otherwise have been paid out, and it's standard for merchants classified high risk, travel agencies included.

Why do payment gateways call travel agencies high risk?

Travel gets the high-risk label because of the long gap, often four to twelve months, between when a client pays and when the trip actually happens, combined with large average ticket sizes and above-average chargeback rates. Underwriters price that gap into a higher MDR and a rolling reserve rather than declining the merchant category outright.

Can a small travel agency accept international card payments in India?

Yes, but only through a gateway that holds actual RBI payment aggregator authorisation and meets data localisation and FEMA purpose-code requirements for cross-border transactions. Ask any prospective gateway to confirm this authorisation in writing before routing international card payments through them, rather than assuming a feature toggle means it's licensed for it.

What should I expect from Razorpay or PayU onboarding for a travel business?

Expect a request for GST registration, business PAN, bank statements, and your published cancellation and refund policy, followed by a quote that includes a higher-than-retail MDR and a rolling reserve. Treat the first quote as a starting point for negotiation, not a fixed number, especially once you have six months or more of clean processing history to point to.

The short version

• Travel is priced as high risk because of the 4-12 month gap between booking and travel, plus high ticket sizes and chargeback exposure, not because of anything your agency did wrong.
• Expect processing fees roughly 20-30% above retail rates, plus a rolling reserve and possible chargeback fees, per gateways' own travel guidance.
• Compare gateways on four numbers together: MDR by card type, settlement cycle in days, rolling reserve percentage and release window, and dispute-support process, not on headline MDR alone.
• Front-load your GST registration, bank statements, refund policy and chargeback history in your underwriting application to speed up approval.
• Confirm any gateway claiming to support international cards actually holds RBI payment aggregator authorisation before you route cross-border transactions through it.
• After 6-12 months of clean processing, ask in writing for a reduced rolling reserve; gateways rarely offer it unprompted.
• If your book is mostly domestic clients paying by UPI or bank transfer, don't pay high-risk gateway pricing on your entire turnover to cover a small international slice.