What do “real time” and “gross” mean?
“Real time” refers to processing instructions when they are received. “Gross” means that each instruction is settled individually rather than being offset against other instructions to produce a net amount.
RBI’s RTGS FAQ, updated 14 October 2026, explains both terms. It also says settlement occurs in RBI’s books and is final and irrevocable.
This is a description of settlement. It does not mean a customer should ignore a bank warning, skip beneficiary checks or assume that a separate merchant platform has updated its own records immediately.
How is RTGS different from NEFT?
The main distinction is the processing arrangement. RBI describes NEFT as operating in batches and RTGS as settling individual instructions in real time.
| System | Processing concept |
|---|---|
| RTGS | Individual real-time gross settlement |
| NEFT | Electronic transfers processed through batch cycles |
Both require the correct destination information. The terms are not descriptions of different kinds of customer account, and neither eliminates the need to verify the beneficiary.
Use the option supported by the bank for the intended payment. A shop operator should not promise a particular outcome solely because the customer selected the word RTGS.
Which amount and availability rules apply?
The RBI FAQ checked on 12 November 2026 states a minimum RTGS remittance amount of ₹2 lakh, with no upper ceiling set by the RTGS system. It describes the system as available throughout the year, around the clock.
That does not establish an unlimited transaction allowance for every individual banking channel. The bank’s account controls, channel limits and applicable checks still need to be followed.
Likewise, system availability is different from a physical branch being open. Check the actual channel through which the customer intends to submit the payment. Our bank-holiday guide explains why retailer operations and branch services can be affected differently.
Why beneficiary details deserve a careful check
RTGS settlement finality makes it especially unhelpful to treat a payment as an experiment. Confirm the recipient’s account details, branch IFSC and amount before authorising the instruction.
If information is inconsistent, resolve it first. Do not guess a branch code from a bank name or use an account number taken from an unverified message.
If a customer later reports an error, they should contact the initiating bank immediately through its official process. A retailer should not promise a unilateral reversal or suggest that a new payment will undo the first one. Settlement finality and the bank’s handling of an error are different matters.
An example of a provider-account update
Illustrative example: A business sends a large payment by RTGS to a service provider. The bank records the transfer, but the provider’s portal still shows the previous balance.
The business keeps the bank reference and checks whether the provider has matched the receipt to the correct customer account. The bank transfer and the provider’s internal posting are separate records.
The business should not make another payment merely to force the portal balance to change. It first asks the provider to identify the original receipt using the required reference and account details. Our UTR explanation covers that record-matching context.
Questions about RTGS
Does “no upper ceiling” mean my banking app has no limit?
No. RBI’s system-level statement does not remove the bank’s channel or account controls.
Does the RTGS reference prove the provider updated my wallet?
No. It identifies the bank-transfer record. The provider must separately recognise and post the funds in its own arrangement.
Can SiOnline decide RTGS rules?
No. RBI and the participating banking institutions govern the system and customer transfer process. A retailer-service provider does not set those rules.