What Is Transactional SMS? Definition, TRAI Rules & Use Cases in India

Transactional SMS is one of the most precisely regulated categories of business communication in India. Every bank alert, every OTP, every order confirmation and appointment reminder that reaches your phone is classified, routed, and delivered under a specific legal framework governed by the Telecom Regulatory Authority of India (TRAI). Understanding this framework — what qualifies as transactional, what rules apply, and how those rules differ from those governing promotional messages — is essential for every business that communicates with customers by SMS.

This guide covers the complete picture: the official definition of transactional SMS under TRAI's regulations, how the DLT (Distributed Ledger Technology) system classifies and enforces messaging categories, every approved use case across major industries, the differences between transactional and promotional SMS in plain terms, template and registration requirements, and the most common compliance errors businesses make.

Table of Contents

1. The Official TRAI Definition of Transactional SMS

2. Transactional SMS vs. Promotional SMS — The Complete Comparison

3. The Four Categories of Commercial SMS in India (2026)

4. TRAI's DLT Framework: How Transactional SMS Is Enforced

5. DND (Do Not Disturb) and Transactional SMS: What the Rules Actually Say

6. Transactional SMS Template Registration: Requirements and Process

7. Sender ID (Header) Rules for Transactional SMS

8. Consent Rules for Transactional SMS

9. Industry Use Cases: Approved Transactional SMS Scenarios

10. Transactional SMS Template Examples by Category

11. Common Compliance Mistakes — and How to Avoid Them

12. Transactional SMS and Other TRAI/Regulatory Frameworks (RBI, SEBI, IRDAI)

13. Frequently Asked Questions

1. The Official TRAI Definition of Transactional SMS

Under the Telecom Commercial Communications Customer Preference Regulations (TCCCPR) 2018, and as operationalised through India's DLT ecosystem, transactional SMS is defined as a message sent by a business or organisation to a subscriber that:

• Is triggered by a specific action taken by the subscriber, or by a system event directly related to an existing service relationship between the sender and the recipient

• Contains information that is operationally relevant to the recipient — relating to a transaction, account activity, security event, or service update — rather than marketing or promotional content

• Does not contain any element of advertising, inducement to purchase, or unsolicited marketing communication

In practical terms, transactional SMS is any message a business is obligated or operationally required to send to a customer as a consequence of that customer's use of the business's service. The message exists to serve the customer's informational need — not to generate a commercial response.

TRAI's DLT platform further classifies transactional messages under the broader category of Service Explicit communications — messages where an explicit service relationship exists and the recipient's implicit consent to receive operational communications is considered inherent in that relationship.

Key phrase: A transactional SMS informs. It does not persuade.

The moment a message contains a promotional element — a discount code, an offer to upgrade, a "while you're here, check out this product" insertion — it ceases to qualify as transactional under TRAI's framework, regardless of whether it also contains genuinely transactional content. A message that says "Your OTP is 847291. Valid for 10 minutes. Also get 20% off on your next order" is, under TRAI's rules, a promotional message — and subject to all promotional messaging restrictions.

2. Transactional SMS vs. Promotional SMS — The Complete Comparison

The distinction between transactional and promotional SMS in India is not merely definitional — it carries significant operational consequences. The two message types are routed through different carrier paths, face different delivery windows, are filtered differently against the DND registry, and require different template structures and consent frameworks.

Dimension	Transactional SMS	Promotional SMS
TRAI Category	Service Explicit	Promotional / Bulk Commercial
Purpose	Inform — triggered by user action or system event	Market — promote products, offers, events, brand
Content Rule	Purely informational, no promotional elements	Marketing or commercial content
Delivery Window	24 hours a day, 7 days a week, 365 days a year	09:00 AM to 09:00 PM IST only
Public Holidays	Delivered — no restriction	Delivered within window — no holiday exemption
DND Numbers	✅ Delivered to DND-registered subscribers	❌ Blocked for DND-registered subscribers
NCPR Scrubbing	Not required — bypasses DND filter	Required before every campaign send
Consent Basis	Inferred — service relationship is sufficient	Explicit — subscriber must have opted in
Consent Template	Not required	Required — must be registered on DLT
Header Format	Alphabetic (A–Z), 6 characters (e.g., TECHTO)	Alphabetic, 6 characters — different header registration category
Template Type	Transactional template (DLT category: Transactional)	Promotional template (DLT category: Promotional)
Template Variables	Allowed — {#var#} format for dynamic content	Allowed — same format
Mixed Content	Not permitted — any promotional element reclassifies the message	N/A
Carrier Route	Transactional route — generally higher priority	Promotional route — may be lower priority

The Most Commonly Confused Scenarios

Scenario 1: An OTP message that includes a promotional sentence Classification: Promotional. The presence of any marketing content reclassifies the entire message.

Scenario 2: A shipping update that mentions a related product ("Your order is shipped. Also check out new arrivals at…") Classification: Promotional. The informational nucleus does not protect the message from promotional classification.

Scenario 3: A welcome SMS sent to a new subscriber ("Welcome to our platform! Your account is activated.") Classification: Transactional (Service Explicit). No promotional content; triggered by account creation.

Scenario 4: A payment receipt with the total amount and a thank-you note Classification: Transactional, as long as the thank-you note is purely courteous and contains no marketing element.

Scenario 5: A message reminding a customer of a cart abandonment ("You left something behind! Complete your order for 10% off") Classification: Promotional. It is initiated by the business, not triggered by a subscriber action, and it contains a commercial inducement.

3. The Four Categories of Commercial SMS in India (2026)

TRAI's DLT framework recognises four distinct categories of commercial SMS communication. Understanding all four is essential because businesses often incorrectly classify service implicit messages as transactional — leading to template rejections and delivery failures.

Category 1: Transactional (Service Explicit)

Messages sent in the context of an existing, explicit service relationship where the subscriber has engaged with the service. The message is directly triggered by a subscriber action or a system event related to that service. OTPs, payment confirmations, account alerts, order tracking updates, appointment reminders.

Category 2: Service Implicit

Messages sent in the context of a commercial relationship but not directly triggered by a specific subscriber action. Subscription renewal reminders, account expiry warnings, periodic account summaries, service maintenance notifications. These messages are not strictly transactional (no triggering event), but they are not promotional either. They occupy a middle category with their own DLT template classification.

Category 3: Promotional

Unsolicited marketing communications or solicited (opted-in) commercial messages promoting products, services, events, or offers. Subject to DND filtering and the 9 AM–9 PM IST delivery window. Requires explicit consent template registration.

Category 4: Government / Public Interest

Messages sent by government entities or public bodies for public service announcements, emergency alerts, citizen service updates, and policy communications. Generally exempt from DND restrictions and time window limitations.

The distinction between Category 1 (Transactional) and Category 2 (Service Implicit) is the one businesses most frequently get wrong. Registering a service implicit template under the transactional category — or attempting to route service implicit messages through transactional paths — causes template mismatch rejections and blocked messages.

4. TRAI's DLT Framework: How Transactional SMS Is Enforced

The Distributed Ledger Technology (DLT) framework, mandated by TRAI under TCCCPR 2018 and operationalised from 2021, is the enforcement infrastructure for all four categories of commercial SMS in India. It is a blockchain-based registry system that verifies the identity, intent, and content of every commercial SMS before it is delivered to a subscriber's handset.

How DLT Enforcement Works for Transactional SMS

Every transactional SMS sent in India goes through the following verification chain before delivery:

Step 1 — Entity verification The sending business must be registered on a TRAI-approved DLT platform as a Principal Entity. The entity's identity is verified via GST certificate, business PAN, and company registration documents. An unregistered entity cannot send transactional SMS through legitimate domestic routes.

Step 2 — Header (Sender ID) verification The 6-character alphanumeric Sender ID in the "from" field must be registered under the sending Principal Entity on the DLT platform, in the correct header category for the message type being sent. A header registered for transactional traffic cannot be used to send promotional messages, and vice versa. This is enforced at the carrier level — the operator checks the DLT registry before routing the message.

Step 3 — Content template matching The actual message content is matched — at the carrier's network level — against the approved DLT content templates registered by the sender. Template matching uses a regex-like pattern matching algorithm. The static portions of the message must match exactly. Dynamic variables — OTP numbers, account balances, order IDs, names — are matched against the declared variable positions in the approved template.

If the message content does not match an approved template: the message is blocked. No error is returned to the sender's application. From the sender's perspective, the message was submitted successfully; from the recipient's perspective, it never arrived. This silent blocking is the most dangerous failure mode in India's SMS ecosystem.

Step 4 — DND status check (for promotional — bypassed for transactional) For transactional messages, the DND scrubbing step is bypassed. TRAI's framework explicitly allows transactional messages to reach DND-registered subscribers because the informational content is considered to serve the subscriber's interest, not the sender's marketing interest.

Step 5 — Delivery to carrier and handset Verified messages are released to the carrier's delivery queue. The carrier delivers to the subscriber and returns a delivery receipt (DLR) to the sending entity's SMS gateway.

5. DND (Do Not Disturb) and Transactional SMS: What the Rules Actually Say

The National Customer Preference Register (NCPR), commonly called the DND registry, is managed by TRAI and maintained operationally by all licensed telecom operators. Subscribers can register to block commercial communications — either fully (all commercial categories) or partially (selected commercial categories only).

What DND Means for Transactional SMS

Transactional SMS is explicitly exempted from DND restrictions under TRAI's regulations. A subscriber who has registered on the fully blocked DND list will still receive:

• OTPs for authentication and verification

• Banking transaction alerts (debit, credit, fraud alerts)

• Order status updates from e-commerce purchases they made

• Appointment reminders for bookings they initiated

• Flight, train, or bus booking confirmations

• Payment receipts and invoice notifications

• Account security alerts (login from new device, password change)

This exemption exists because transactional SMS is recognised as serving the subscriber's own interest — information they need as a consequence of actions they took. The DND registry was designed to protect consumers from unsolicited commercial communication, not from the operational consequences of their own service relationships.

What DND Does NOT Exempt

The DND exemption applies to genuinely transactional messages only. Businesses that attempt to route promotional content through transactional templates — to bypass DND restrictions and reach non-consenting subscribers — are in violation of TCCCPR 2018. TRAI has the authority to impose financial penalties and suspend sending privileges for such violations. Operators are required to report and escalate suspected category misuse.

The DND Exemption in Practice

A subscriber who registered for full DND protection because they were tired of promotional messages will still receive their bank OTPs, delivery notifications, and account alerts. This is intentional, appropriate, and legally mandated — those messages exist because the subscriber initiated the underlying transaction, not because the business decided to send them a message.

6. Transactional SMS Template Registration: Requirements and Process

Content template registration is the most operationally significant step in transactional SMS compliance — and the step most responsible for delivery failures when done incorrectly. Every format of transactional message a business sends must be pre-registered as an approved content template on the DLT platform.

What Is a Content Template?

A content template is the pre-approved pattern for a specific message type. It defines the static text of the message and declares the positions and expected nature of any dynamic variable content. For example, a login OTP template might look like:

Your OTP for login to {#var#} is {#var#}. Valid for {#var#} minutes. Do not share this with anyone.

The carrier's matching algorithm confirms that the actual message sent matches this pattern — with real values substituted in the declared variable positions.

Template Registration Requirements

Category selection: Templates must be submitted under the correct category (Transactional, Service Implicit, or Promotional). A transactional template submitted under the wrong category will be approved in the wrong routing class and may fail during carrier-level template matching.

Variable formatting: Dynamic fields must use TRAI's approved variable syntax: {#var#}. Custom variable naming formats, curly braces without the #var# pattern, square brackets, or other substitutions are not accepted by the DLT platform and will cause template rejection.

Identity inclusion: TRAI requires that every commercial SMS template include the sender's brand or trademark identity somewhere in the message text — not just in the Sender ID field. This allows recipients to identify the sender even if they save the Sender ID under a different name.

Character limits: GSM-7 encoding supports 160 characters per SMS part. Unicode (for Indian language SMS) supports 70 characters per part. Concatenated messages (multiple parts) are supported but must be accounted for in the template as registered. A template registered as a single-part message cannot be sent as a multi-part message without re-registration.

Restricted content: Templates containing URLs in URL shortener format (bit.ly, goo.gl, etc.) may face rejection. Full-domain URLs are preferred. Certain categories of content — financial inducements, competitive brand mentions, misleading claims — are rejected regardless of message category.

Approval timeline: Template approval typically takes 24–72 hours. Some operators process approvals faster; others take the full 72 hours. Plan template registration at least 5 business days before a planned go-live date to account for potential revision requests.

The Template Mismatch Problem — and Why It Is More Common Than Businesses Expect

The most frequent transactional SMS delivery failure that businesses report — "our messages are submitted successfully but recipients aren't receiving them" — is almost always caused by template mismatch. The message content the application is sending does not exactly match the approved template pattern on file.

Common mismatch causes:

• A developer updated the message format (e.g., changed "Your OTP is" to "OTP:") without re-registering the template

• A variable was moved to a different position in the message text

• Extra punctuation, capitalisation changes, or line breaks were introduced

• A new field (like the recipient's name) was added to the message without updating the template to include a corresponding {#var#} placeholder

• The message is being sent with a different Sender ID than the one the template is linked to

Any of these changes — even a single character difference — causes the carrier's template matching algorithm to reject the message. The rejection is silent. It looks like a successful send from the application's perspective.

7. Sender ID (Header) Rules for Transactional SMS

In India, the Sender ID for transactional SMS must be a 6-character alphabetic string — only letters A–Z, no numbers, no special characters. This is different from some other countries' SMS frameworks where numeric sender IDs are common.

Transactional vs. Promotional Sender IDs

Under TRAI's DLT framework, sender headers are registered in specific categories:

• Transactional headers: 6 alphabetic characters. Used for OTPs, alerts, banking messages, order updates. Can be sent 24/7 to all numbers including DND.

• Promotional headers: 6 alphabetic characters. Used for marketing campaigns. Subject to time window and DND restrictions.

• Service Implicit headers: Registered separately for the service implicit category. Distinct from both transactional and promotional.

A header registered for transactional use cannot be used to send a promotional message — the DLT platform will block it. A header registered for promotional use cannot bypass DND restrictions even if the message content is genuinely informational — the header category determines routing.

Practical Header Naming

Businesses choose their 6-character Sender ID to reflect their brand — TECHTO, HDFINC, BKOFIN, SHOPNW, AIRBNB. The Sender ID is what the recipient sees instead of a phone number. Because the header directly shapes the recipient's recognition and trust response, it is worth investing time in choosing a Sender ID that is clear, recognisable, and brand-consistent.

A single business can register multiple Sender IDs — a different header for banking communications, for logistics updates, for security alerts — all registered under the same Principal Entity.

8. Consent Rules for Transactional SMS

Transactional SMS in India operates on the principle of inferred consent — an explicit opt-in from the subscriber is not required. The basis for inferred consent is the existence of an active service relationship: the subscriber has used or is using the business's service, and the message is sent in direct connection with that usage.

What Constitutes an Adequate Service Relationship

For inferred consent to apply, the following conditions must be met:

Active engagement: The subscriber has actively transacted with the business — made a purchase, created an account, initiated a service request, booked an appointment, opened a bank account, submitted a form, or completed a registration.

Message relevance: The transactional message is directly related to that specific engagement. A customer who placed an order receives order updates. A banking customer receives account alerts. A patient who booked an appointment receives appointment reminders. The service relationship must connect the message to the subscriber's specific action.

No promotional contamination: The message must contain only the information the subscriber would reasonably expect as a consequence of their action. A payment confirmation is expected. A follow-on product recommendation is not — and its inclusion breaks the inferred consent basis.

No Consent Template Required

Unlike promotional SMS, transactional SMS does not require a separately registered consent template on the DLT platform. The inferred consent framework means businesses do not need to document, register, or prove the basis of individual subscriber consent for each transactional message category. The service relationship itself is the consent documentation.

This significantly simplifies the operational compliance burden for transactional messaging compared to promotional messaging, where detailed consent template registration — documenting how, when, and where consent was obtained — is mandatory.

9. Industry Use Cases: Approved Transactional SMS Scenarios

The following use cases are recognised — explicitly or by category definition — as qualifying transactional SMS under TRAI's framework. They are organised by industry vertical.

Banking, Payments, and Financial Services

Account transaction alerts: Every debit and credit transaction on a bank account triggers an alert — amount, merchant name, remaining balance, date, and time. These messages are mandatory for banks under RBI guidelines and are among the highest-volume transactional SMS category in India.

OTP for authentication: Login OTPs, payment authentication OTPs, KYC verification OTPs, fund transfer confirmation OTPs. The RBI's Digital Payment Security Controls (2021) mandate OTP-based authentication for digital payment transactions above specified thresholds.

Fraud and security alerts: Suspicious transaction detected, login from unrecognised device, multiple failed PIN attempts, card blocked for suspected misuse. These messages have heightened delivery priority because delivery failure can result in real financial harm to the subscriber.

Loan and EMI updates: EMI amount due, payment received, overdue notice, loan disbursed, loan account opened. Financial institutions send these to maintain account-level transparency.

Credit card statements and bills: Statement generated, minimum payment due, payment received, credit limit updated.

Investment and brokerage alerts: Trade executed, portfolio value update, dividend credited, SIP instalment processed. SEBI guidelines for investor communication require electronic delivery of these notifications, and SMS is the most reliably received channel given non-uniform email open rates.

Insurance policy updates: Premium due, premium received, policy renewal reminder, claim registered, claim status update, policy document issued.

E-Commerce, Retail, and Logistics

Order confirmation: Order placed confirmation immediately after payment completion. Contains order ID, item summary, estimated delivery, and payment method used.

Order status updates: Order packed, order dispatched, out for delivery, delivery attempted, delivery successful, return initiated, return picked up, refund processed. Each status change in the order lifecycle is a distinct transactional event.

Delivery OTP: For high-value shipments, the delivery agent presents a 4–6 digit OTP that the customer must share to confirm delivery. This prevents fraudulent delivery confirmation and is now standard practice for premium logistics.

Shipment exception alerts: Delivery delayed, address undeliverable, delivery rescheduled, held at customs (for international shipments). These inform the customer of an operational problem with their order.

Return and refund notifications: Return pickup scheduled, item picked up, quality check in progress, refund initiated, refund credited.

Healthcare and Medical Services

Appointment confirmation and reminder: Appointment booked for [date, time, doctor, department] — sent immediately after booking. Reminder sent 24 hours and 2 hours before the appointment. Reduces no-shows by 25–35% per published healthcare operations research.

Lab report availability: Your report for [test name] is ready for collection / is available on the patient portal. Reduces inbound calls to lab reception.

Prescription and medication reminders: Your prescription is ready for pickup. Refill reminder for ongoing medication. Take your [medication name] — reminder message for chronic disease management.

Surgery and procedure instructions: Pre-operative fasting instructions, admission time, documents to bring. Sent after a procedure is scheduled and confirmed.

Discharge summary notification: Your discharge summary is available. Your follow-up appointment is scheduled for [date, time].

Diagnostic billing: Invoice for [test name] — amount due, payment options. Receipt for payment received.

Education and EdTech

Admission and enrolment: Application received, shortlisted, interview scheduled, offer letter issued, seat confirmed. Each is triggered by a specific event in the admission process.

Exam and assessment: Exam schedule published, admit card available, exam reminder (24 hours before), result declared, scorecard available.

Fee payment: Fee statement generated, payment due reminder, payment receipt, outstanding balance alert.

Attendance notification: [Student name] was absent on [date] — notification to parents triggered by the school management system. Present in most school ERP systems and classified as transactional.

Class and schedule changes: Class rescheduled, faculty change, venue change — triggered by timetable updates in the institution's system.

Assignment and assessment submissions: Assignment submission confirmed, deadline reminder (triggered when a submission is not received 24 hours before deadline), grade published.

Travel, Hospitality, and Transportation

Booking confirmation: Hotel reservation confirmed, flight booked, train ticket booked, cab booked — sent immediately after payment confirmation. Contains reservation code, dates, and cancellation policy.

Check-in reminders: Online check-in opens in 24 hours, check-in reminder, boarding pass available.

Flight and transport status: Departure delayed by [X] minutes, flight gate changed to [gate], boarding commences, flight cancelled.

Hotel arrival information: Your room is ready, early check-in confirmed, checkout time extended.

Cab dispatch and arrival: Your cab is confirmed — [driver name, vehicle number] is on the way, driver is 5 minutes away, ride started, ride completed with fare summary.

Government and Public Services

Utility bills: Electricity bill generated — amount, due date, consumption; water bill due; gas connection booking confirmed.

Tax and compliance: Advance tax payment reminder, TDS certificate available, GST return filing reminder, income tax refund credited.

Welfare scheme notifications: Benefit disbursed, application status update, verification appointment scheduled.

Emergency and public safety alerts: Natural disaster warning, evacuation advisory, public health emergency notification. These carry the highest delivery priority of any SMS category.

Passport, PAN, and Aadhaar services: Application received, appointment confirmed, document dispatched.

10. Transactional SMS Template Examples by Category

The following are illustrative template structures. Variable positions use TRAI's approved {#var#} placeholder format.

OTP — Login Authentication:

{#var#} is your OTP for login to {#var#}. Valid for {#var#} minutes. Do not share this OTP with anyone. - TECHTO

OTP — Payment Authorisation:

{#var#} is your OTP to authorise payment of Rs.{#var#} to {#var#}. OTP expires in {#var#} mins. Do not share. - HDFINC

Banking — Debit Alert:

Rs.{#var#} debited from your account {#var#} on {#var#} at {#var#}. Available balance: Rs.{#var#}. Not done by you? Call {#var#}. - BKOFIN

Banking — Fraud Alert:

Alert: Suspicious transaction of Rs.{#var#} attempted on your {#var#} card ending {#var#}. Card temporarily blocked. Call {#var#} if not you. - BKOFIN

E-Commerce — Order Confirmation:

Order #{#var#} placed successfully. {#var#} item(s) worth Rs.{#var#} will be delivered by {#var#}. Track: {#var#} - SHOPNW

E-Commerce — Delivery OTP:

Your delivery OTP for Order #{#var#} is {#var#}. Share ONLY with the delivery agent. Do not share with anyone else. - SHOPNW

Healthcare — Appointment Reminder:

Reminder: Your appointment with Dr. {#var#} at {#var#} is scheduled on {#var#} at {#var#}. Reply CANCEL to cancel. - APOLLH

Healthcare — Lab Report:

Your {#var#} report is ready. Collect from {#var#} or view at {#var#} using ID {#var#}. - MEDLAB

Education — Fee Payment:

Fee of Rs.{#var#} for {#var#} is due by {#var#}. Pay at {#var#} or via net banking. Ref: {#var#}. - SCHPAY

Logistics — Shipment Update:

Your shipment #{#var#} is out for delivery. Expected by {#var#}. OTP for delivery: {#var#}. Track: {#var#} - DELVRX

11. Common Compliance Mistakes — and How to Avoid Them

These are the most frequently occurring transactional SMS compliance errors in India, based on patterns across the business SMS ecosystem.

Mistake 1: Inserting Promotional Content into a Transactional Template

The most common and most damaging error. An OTP message that appends "Get 20% off your next order" is no longer a transactional message under TRAI's framework. If sent through a transactional header and template, this constitutes category misuse — a TRAI violation. Separate templates and separate headers must be used for any message containing commercial content, regardless of the primary informational purpose.

Mistake 2: Template Mismatch Due to Developer Changes

A backend developer updates the message format — changes "Your OTP is" to "Use OTP" — without updating the DLT template. The carrier's matching algorithm blocks the message silently. The business sees successful API submissions; customers don't receive their OTPs. This typically requires 24–72 hours to diagnose and resolve (new template registration). Any change to message format requires template re-registration before deployment.

Mistake 3: Using a Promotional Header for Transactional Messages

A business registers their Sender ID in the promotional category (because they initially set it up for marketing campaigns) and then attempts to send transactional OTPs through the same header. The DLT platform recognises the header as promotional and applies promotional routing rules — including DND filtering. OTPs are blocked for DND-registered subscribers. The fix is to register a separate header in the transactional category.

Mistake 4: Categorising Service Implicit Messages as Transactional

A subscription renewal reminder is a service implicit message — it is related to an existing service relationship, but it is not triggered by a specific user action. Registering it as a transactional template and routing it through the transactional path is a category misclassification. While it may not always cause a delivery failure (template matching may succeed), it creates compliance exposure if audited.

Mistake 5: Sending Outside Registered Template Scope

An e-commerce company registers a template for order confirmation but uses the same template ID for delivery status updates by changing the static text in the message. The dynamic variables may pass matching, but altered static text causes a mismatch block. Each distinct message format — order placed, dispatched, delivered, return initiated — requires its own registered template.

Mistake 6: Failure to Include Brand Identity in Template

TRAI requires that the sender's brand name or trademark appear in the message body — not just in the Sender ID field. Templates that omit the business name may be rejected during registration or may face compliance scrutiny. Including the brand name in the message body ("— TECHTO" at the end, or "Your [BrandName] OTP is…") satisfies this requirement.

12. Transactional SMS and Other Regulatory Frameworks (RBI, SEBI, IRDAI)

TRAI's TCCCPR framework governs the how of commercial SMS in India — the registration, routing, and delivery rules. But for regulated industries, additional sector-specific regulations govern the what — the content and timing of specific transactional messages.

RBI and Banking/Fintech

The Reserve Bank of India's Digital Payment Security Controls circular (2021) mandates OTP-based authentication for:

• All digital payment transactions (NEFT, RTGS, IMPS, UPI) above specified thresholds

• Login to internet banking from new devices

• Beneficiary additions for fund transfers

• High-value card-not-present transactions

Banks and payment aggregators are legally required to send these OTPs — the TRAI transactional SMS framework is the mandated delivery mechanism. Delivery failure on RBI-mandated OTPs creates both a regulatory compliance exposure and direct customer harm.

SEBI and Investment Platforms

SEBI's investor communication regulations require brokers and investment platforms to send:

• Trade execution confirmations (contract notes)

• Portfolio and ledger balance updates

• Corporate action notifications (dividends, rights issues, bonus)

• SIP and MF transaction confirmations

These are mandatory disclosures. SMS is the required channel for subscribers who do not have active email or do not open emails for financial communications. Delivery failures on SEBI-mandated messages can constitute a regulatory breach.

IRDAI and Insurance

The Insurance Regulatory and Development Authority of India requires insurers to send:

• Policy issuance confirmation

• Premium receipt acknowledgement

• Policy renewal reminder (this may be service implicit rather than transactional — the classification depends on how the reminder is triggered)

• Claim registration confirmation and status updates

Insurance companies sending these messages must comply with both IRDAI content requirements and TRAI's DLT framework simultaneously.

13. Frequently Asked Questions: Transactional SMS

What is the simplest definition of transactional SMS? A transactional SMS is a text message sent by a business to a customer that provides information directly related to an action the customer took or a service the customer uses. OTPs, order confirmations, bank alerts, and appointment reminders are the most common examples. It does not contain any marketing or promotional content.

Can transactional SMS be sent to DND-registered numbers? Yes. TRAI's framework explicitly exempts transactional SMS from DND (Do Not Disturb) restrictions. A subscriber who has registered on the full DND list will still receive OTPs, banking alerts, and other genuinely transactional messages. This exemption does not apply if the message contains any promotional element — even a single promotional sentence in an otherwise transactional message causes the entire message to be treated as promotional.

What time can transactional SMS be sent? Transactional SMS can be sent at any time — 24 hours a day, 7 days a week, including weekends and public holidays. There is no time window restriction for transactional messages. This is one of the key operational differences from promotional SMS, which is restricted to 9:00 AM to 9:00 PM IST.

Does transactional SMS require prior consent from the recipient? No explicit opt-in is required. Transactional SMS operates on the basis of inferred consent — the existence of an active service relationship between the sender and the recipient is sufficient. The recipient's act of creating an account, making a purchase, or initiating a service relationship implies acceptance of operational communications related to that relationship.

What is DLT registration and is it mandatory for transactional SMS? DLT (Distributed Ledger Technology) registration is TRAI's framework for verifying business identities, sender headers, and message templates before commercial SMS is delivered. It is mandatory for all commercial SMS in India — including transactional messages. Without DLT registration, transactional messages will be blocked at the carrier level before reaching the recipient.

Why are my transactional SMS messages being blocked even though I'm registered on DLT? The most common cause is template mismatch — the actual message content your system is sending does not exactly match the approved template registered on the DLT platform. Any deviation in static text, variable position, punctuation, or capitalisation causes the carrier's matching algorithm to reject the message silently. Other causes: the Sender ID used is not registered in the transactional header category, or the Sender ID is not linked to the template being used.

Can OTPs be sent to all mobile numbers in India regardless of operator? Yes, provided the sending entity is properly DLT-registered, the Sender ID is registered in the transactional header category, and the OTP template is registered and approved. OTPs route through transactional paths that reach all four major Indian operators: Airtel, Jio, Vodafone Idea (Vi), and BSNL.

What happens if I mix transactional and promotional content in the same message? The entire message is reclassified as promotional. It becomes subject to DND filtering (blocked for DND-registered subscribers), time window restrictions (9 AM–9 PM IST only), and consent template requirements. Sending a mixed-content message through transactional routing — to reach DND subscribers or outside the time window — constitutes a TCCCPR violation and can result in penalties and suspension of sending privileges.

How long does it take for a transactional SMS template to be approved? Template approval typically takes 24–72 hours from submission on the DLT platform. The time varies by operator — Airtel's TrueConnect, Jio's platform, and Vi's platform each process approvals independently. Register templates at least 5 business days before the planned go-live date to allow for potential revision requests.

Is there a difference between transactional SMS and OTP SMS? OTP SMS is a subcategory of transactional SMS. All OTPs are transactional messages, but not all transactional messages are OTPs. Transactional SMS is the broader category that includes OTPs, account alerts, order updates, appointment reminders, and all other information-only messages triggered by subscriber actions or system events.

Can a business use the same Sender ID for both transactional and promotional messages? No. Under TRAI's DLT framework, Sender IDs are registered in specific categories — transactional or promotional. A header registered as transactional cannot be used for promotional sends, and vice versa. A business that wants to send both transactional and promotional messages must register separate Sender IDs for each category.

Summary: The 10 Things Every Business Needs to Know About Transactional SMS in India

1. Transactional SMS is defined by purpose: it informs, it does not market. Any promotional element reclassifies the entire message.

2. Transactional SMS can be delivered 24/7 — there is no time window restriction.

3. Transactional SMS reaches DND-registered subscribers — the DND filter is bypassed for genuinely transactional messages.

4. Transactional SMS does not require explicit subscriber consent — inferred consent from the service relationship is sufficient.

5. DLT registration is mandatory — Principal Entity, Sender ID in the transactional header category, and pre-approved content templates.

6. Template matching is enforced at the carrier level — any deviation in message format from the approved template causes silent blocking.

7. Sender IDs are category-specific — transactional and promotional messages must use separately registered headers.

8. TRAI's TCCCPR framework operates alongside sector-specific regulations — RBI, SEBI, and IRDAI impose additional requirements on regulated-industry transactional messages.

9. Four message categories exist (Transactional, Service Implicit, Promotional, Government) — Service Implicit messages are commonly misclassified as Transactional, creating compliance exposure.

10. Template variables must use TRAI's approved {#var#} format — custom variable syntax causes template rejection.

Related Resources

• SMS Gateway India — Platform & Carrier Guide

• Send SMS Online — Quick Start Guide

• SMS Software for Business — Full Suite

• DLT Registration India — Step-by-Step

• SMS Text Gateway Comparison 2026

• Bulk SMS Pricing

This guide is maintained by the Techto Networks compliance team and reflects TRAI regulations as of 2026. For the most current regulatory guidance, refer to the official TRAI website at trai.gov.in and the TCCCPR 2018 regulations.