RBI Advises UCBs to Levy SMS Alert Charges on Actual Usage Basis
No longer current — withdrawn, no replacement on file yet
Source: Reserve Bank of India · RBI/2013-14/403 · issued 06 Dec 2013 · ~2 min read
Quick answerRBI advises Urban Co-operative Banks to charge SMS alerts on actual usage basis only, ensuring fairness and equity. No flat fees allowed. Banks must leverage existing technology to implement this as per circular dated December 6, 2013.
What changed
RBI reiterated that UCBs must charge SMS alerts based on actual usage, not flat rates. This aligns with earlier 2007 guidelines on reasonable bank charges and 2009/2011 mandates for online alerts on card transactions. The circular references the Second Quarter Review of Monetary Policy 2013-14.
What it means for you
UCBs can no longer levy uniform SMS alert charges; they must bill per alert actually sent. This protects customers from paying for alerts they don't receive or use. Banks need to upgrade or use existing systems to track and bill accurately, potentially impacting fee income from SMS services.
Historical instruction — do not use for current compliance. This is what was required at the time; it no longer reflects current RBI requirements. If no replacement rule is linked above, that only means none is recorded on our register yet — it does not prove no later applicable rule exists. Confirm on the official RBI source below.
What banks were required to do at the time
Audit current SMS alert charging model and switch to actual-usage billing as advised.
Coordinate with telecom providers to implement per-alert tracking and billing.
Update customer terms and conditions to reflect actual-usage charges.
Ensure compliance with earlier circulars on online alerts for card transactions.
Communicate the change to customers and train staff on the new charging mechanism.
Who it affects
All Primary Urban Co-operative Banks (UCBs), Customers using ATM/debit cards and receiving SMS alerts, Bank IT and operations teams handling SMS alert systems
❓ Common questions
Regulatory timeline
Decoded by BankPulse2026-06-18 11:31 IST
repealed_by — Consolidation of Regulations — Withdrawal of circulars (28 Nov 2025)
Status change: withdrawn03 Aug 2026, 04:00 IST
Built from our lineage records — each fact carries its provenance; missing history simply is not shown (never guessed).
Does this circular apply to all SMS alerts or only card transactions?
The circular advises actual-usage charging for SMS alerts generally, referencing earlier mandates for online alerts on card transactions. The scope is SMS alerts sent by banks, but the primary context is card-related transactions.
Can UCBs still charge a flat monthly fee for SMS alerts?
No. The circular requires charges to be levied on actual usage basis, so flat fees are not permitted.
What if our bank cannot technically implement per-alert billing?
RBI expects banks to leverage available technology and work with telecom providers. If implementation is not feasible, banks should seek guidance from RBI or upgrade systems.
📜 This document’s life story (1 recorded event, each backed by RBI’s own words)
Repealed byRBI/2025-26/100 — Consolidation of Regulations — Withdrawal of circulars (28 Nov 2025)
RBI’s words: “Official withdrawal register entry #970: UBD.CO.BPD.(PCB).Cir.No.42/12.05.001/2013-14 — "Charges Levied by Banks for Sending SMS Alerts" dated December 6, 2013”
📜 Read the original circular — full text as issued by RBI
RBI/2013-14/403
UBD.CO.BPD.(PCB).Cir.No.42/12.05.001/2013-14
December 6, 2013
To,
The Chief Executive Officer
All (Primary) Urban Co-operative Banks
Dear Sir / Madam,
Charges Levied by Banks for Sending SMS Alerts
Please refer to paragraph 37 of the Second Quarter Review of Monetary Policy Statement 2013-14 announced on October 29, 2013 ( extract enclosed ) on 'Customer Service- Charges Levied by Banks for Sending SMS Alerts'.
2.In this connection, a reference is also invited to our circular UBD.CO.BPD.(PCB) No. 31/12.05.001/2006-07 dated March 9, 2007 on 'Report of the Working Group to Formulate a Scheme for Ensuring Reasonableness of Bank Charges' whereby Urban Co-operative Banks (UCBs) were advised to identify basic banking services on the basis of broad parameters indicated by the Working Group constituted by Reserve Bank of India for the purpose and the principles to be adopted/ followed by them for ensuring reasonableness in fixing and communicating the service charges for the basic banking services.
3. Urban Co-operative Banks are required to put in place a system of online alerts for all types of transactions irrespective of the amounts involving usage of cards at various channels in terms of circular RBI/DPSS.No.1501/02.14.003/2008-2009 dated February 18, 2009 and DPSS.CO.PD.2224/02.14.003/2010-2011 dated March 29, 2011 .
4.At present, UCBs are providing ATM services and issuing ATM cum debit cards to their customers as envisaged in our circular UBD. (PCB).BPD.Cir No. 50/09.69.000/2005-06 dated April 28, 2006 . Considering the technology available with UCBs and the telecom service providers, it should be possible for banks to charge customers based on actual usage of SMS alerts. Accordingly, with a view to ensuring reasonableness and equity in the charges levied by banks for sending SMS alerts to customers, UCBs are advised to leverage the technology available with them and the telecom service providers to ensure that such charges are levied on all customers on actual usage basis.
Yours faithfully,
(A K Bera)
Principal Chief General Manager
Extract from Second Quarter Review of Monetary Policy 2013-14
Customer Service - Charges Levied by Banks for Sending SMS Alerts
37. With a view to ensuring reasonableness and equity in the charges levied by banks for sending SMS alerts to customers, banks are advised to leverage the technology available with them and the telecom service providers to ensure that such charges are levied on all customers on actual usage basis.
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2013-14/403 · issued 06 Dec 2013. The plain-English explanation above is BankPulse’s own independent summary.
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=8622&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.