RTGS Payment Guide for Merchants: High-Value Transfers in India
By PayEurasia Team · 3 August 2026 · 6 min read
Last updated 4 August 2026
RTGS exists for one reason: moving large amounts with settlement finality. If your business collects six-figure rupee payments, this is the rail you build for.
What RTGS is
RTGS (Real Time Gross Settlement) settles each instruction individually and in real time on the books of the central bank, giving immediate finality rather than netted batch settlement.
India has the deepest real-time payment infrastructure in the region. UPI handles billions of transactions a month and has effectively replaced cards for everyday online spending.
How the flow works
- The merchant supplies beneficiary details and a unique reference for the payment.
- The customer's bank submits the RTGS instruction.
- Settlement occurs individually and in real time.
- The credit is matched and confirmed, then included in merchant settlement.
Timing and confirmation
Settlement is effectively immediate during operating hours, and finality means the transfer cannot be recalled in the way a batch instruction sometimes can.
Customers expect a payment to complete inside their own banking or UPI app in seconds, and they abandon flows that redirect them through slow intermediate pages.
Limits and ticket sizes
RTGS carries a minimum transaction value, which makes it unsuitable for consumer-sized payments but ideal for corporate and treasury flows.
This is why most Indian checkouts present a wallet option and a bank option side by side rather than choosing one. Coverage for the full India method set is described on the India Payment Gateway page.
Reconciliation
Every RTGS transaction should carry three identifiers in your ledger: your order reference, the gateway reference and the rail reference returned by RTGS. With all three stored, a settlement statement can be matched line by line, refunds can be traced, and disputes can be evidenced without manual investigation.
Settlement for India volume runs on T+0 or T+1 depending on the rail and the merchant's risk profile. Build your daily close around that window rather than assuming same-day equivalence.
Common integration mistakes
- Offering RTGS to consumers whose payments fall below the minimum.
- Not capturing the UTR reference, which is the cleanest matching key available.
- Ignoring operating-hour boundaries when promising same-day credit.
- Manual re-keying of beneficiary details instead of system-generated instructions.
Merchant benefits
- RTGS acceptance through the same API as every other India method
- Signed webhooks with idempotency and replay safety
- Line-level reconciliation data for finance teams
- Settlement on T+0 or T+1 depending on the rail and the merchant's risk profile
- Fallback routing when an upstream connection degrades
Related guides and solutions
- India Payment Gateway
- India Payment Solutions
- UPI Payment Gateway
- High Risk Payment Solution India
- Solutions overview
- Cross-Border Payment Solutions
- Payment Infrastructure
- High-Risk Merchant Payment Processing
- Countries hub
Talk to our team
If you are evaluating acceptance in India, the fastest way to get a useful answer is to share your vertical, expected monthly volume and required payout frequency. Our team can confirm which rails are available to your business, what documentation underwriting will ask for, and how quickly you can go live. Start with merchant onboarding or contact us directly.
Frequently asked questions
What is the minimum amount for RTGS?
RTGS is designed for high-value transfers and carries a minimum threshold, so smaller payments should use IMPS, NEFT or UPI.
Is RTGS irreversible?
Settlement is real time and final, which is precisely why it is used for large transfers.
Which reference should I reconcile against?
The UTR issued for the transfer, stored alongside your own order reference.
Talk to PayEurasia
Working in a high-risk vertical across South Asia? We can probably help.
Request integration →