Standardised RTGS Return Process and Customer Alerts
Current · Source: Reserve Bank of India · RBI/2008-09/499 · issued 16 Jun 2009 · ~1 min read
Quick answerRBI mandates uniform return info in RTGS R42 messages using field tag 7495 (lines: RETURN, UTR, reason) from July 15, 2009. Banks must also explore SMS/email alerts for RTGS debits/credits to improve customer experience.
The rule, in the simplest words
When a bank cannot put money into the right person's account, it must send the money back within 1 hour 30 minutes.
The return message must use a special code (field tag 7495) with three lines: first line says 'RETURN', second line has the original transaction number (UTR), third line says why it was returned.
Banks can add extra info in lines 4 to 6 if needed, but the first three lines are required.
RBI also asks banks to think about sending SMS or email to customers when money comes in or goes out through RTGS.
All banks must follow these rules by July 15, 2009.
How it plays out — a real example
Rajesh, RTGS operations head at a large bank, receives a returned R42 message. He checks field tag 7495: Line 1 'RETURN', Line 2 'XYZ123456789', Line 3 'Invalid account number'. He immediately credits the sender using the original UTR, avoiding delays.
What changed
Previously, RTGS return messages (R42) lacked standard fields for return details, causing delays in crediting senders. Now, all participants must use field tag 7495 with three mandatory lines: 'RETURN', original UTR, and reason. Banks are also urged to send SMS/email alerts for RTGS transactions.
What it means for you
Banks must update their RTGS systems to populate field tag 7495 uniformly, reducing manual tracing and speeding up refunds. The alert recommendation pushes banks toward better customer communication, though not mandatory. Non-compliance may delay beneficiary credit and increase operational friction.
What you must do
Update RTGS software to include field tag 7495 with mandatory lines: RETURN, original UTR, and reason for return.
Ensure compliance by July 15, 2009.
Test the new return process with counterparties to avoid message rejection or delays.
Who it affects
All banks participating in RTGS, RTGS operations teams, IT and system integration teams, Customer service and complaint handling units
❓ Common questions
What is the new format for RTGS return messages?
Use field tag 7495 in R42 messages: Line 1: 'RETURN', Line 2: UTR of original transaction, Line 3: reason for return. Additional info can go in lines 4-6.
Is sending SMS/email alerts mandatory?
No, RBI advises banks to 'explore the possibility' of sending alerts. It is a recommendation to make RTGS more customer-friendly, not a mandate.
What happens if we don't comply by July 15, 2009?
The circular does not specify penalties, but non-standard returns may cause delays and operational issues. Banks should implement by the deadline to avoid confusion.
📜 Read the original circular — full text as issued by RBI
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2008-09/499 · issued 16 Jun 2009. The plain-English explanation above is BankPulse’s own independent summary.
Test the new return process with counterparties to avoid message rejection or delays.
💻 IT / Systems
Update RTGS software to include field tag 7495 with mandatory lines: RETURN, original UTR, and reason for return.
📜 Compliance
Ensure compliance by July 15, 2009.
Grouped from the action items above — a single circular may involve more than one team.
Worked example & action-note template
Example: if you are an IT/Systems lead at a bank this circular applies to (All banks participating in RTGS, RTGS operations teams, IT and system integration teams, Customer service and complaint handling units), your first concrete step on “Standardised RTGS Return Process and Customer Alerts” is: “Update RTGS software to include field tag 7495 with mandatory lines: RETURN, original UTR, and reason for return.” (RBI issued this 16 Jun 2009).
Circular: RBI/2008-09/499 -- Standardised RTGS Return Process and Customer Alerts
Issued: 16 Jun 2009
Action required: Update RTGS software to include field tag 7495 with mandatory lines: RETURN, original UTR, and reason for return.
Action required: Ensure compliance by July 15, 2009.
Action required: Test the new return process with counterparties to avoid message rejection or delays.
Owner: ____________ Target date: ____________
Board/committee approval needed? Y / N
Evidence filed in compliance register on: ____________
Built only from this circular’s own published fields — not legal advice; always confirm against the official RBI source.
💬 Banker Discussion
Discuss this circular with fellow bankers — reply, upvote what helps, report what doesn’t belong. Be professional; no client data. Views are the commenter’s own, not BankPulse’s.
BankPulse Compliance Evidence Pack — generated 03 Aug 2026 · status cross-checked against RBI’s official withdrawal register (refreshed weekly). Official RBI source: https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=5036&Mode=0 — Plain-English summary by BankPulse (bankpulse.ai), reviewed by our expert reviewer, CA Amit Jain. Independent platform, not affiliated with the Reserve Bank of India; is our own plain-English paraphrase, not RBI’s original wording.
Help us keep this accurate
Found an inaccuracy or have an improvement? Tell us. Every report is reviewed by our team before any change is made — nothing goes live unverified.
Public beta — plain-English informational summaries. Always verify against the official RBI source (circular number cited on every page) before making compliance, credit, treasury, audit, or operational decisions. · Join our WhatsApp channel ↗
BANKPULSE · FREE DAILY BRIEF
Get RBI updates for your role
Every important RBI update, decoded in plain English — for your career, exams & financial awareness.
We collect only your email, name and role, used solely to send your brief — never sold or shared. Withdraw anytime via the unsubscribe link in any email. Independent platform, not affiliated with the RBI. Information, not legal advice.
REPORT AN ERROR · BETA
Spotted an error? Earn 500 BankPulse Credits
Help us stay accurate. If your correction is verified true and approved by our founder, you earn 500 BankPulse Credits — redeemable when the platform monetises.
Reviewed by a human before any credit is awarded. We never change the site from crowd input without verification.
WANT A NEW FEATURE · BETA
What would make BankPulse more useful for you?
Tell us what to build next — a tool, a data view, a role page, anything. We read every suggestion.
Thank you — your ideas directly shape what we build.