Home Blog TRAI & DLT Compliance Guide 2026
DLT Compliance · June 2026

TRAI & DLT Compliance Guide India 2026
How to Send Legal, Deliverable Bulk SMS

Entity registration. Sender IDs. Template approval. Message categories. DND rules. Consent. Penalties. Everything your business needs — in plain language.

By Ravi Kant June 9, 2026 10 min read Delhi NCR · All India
Quick Answer — What is DLT?

DLT (Distributed Ledger Technology) is TRAI's mandatory blockchain-based registration system for bulk SMS in India. Every business sending commercial SMS must register their company, sender ID, and message templates on a TRAI-approved DLT portal before sending. If you skip this, Jio, Airtel, Vi and BSNL silently block your messages — including OTPs.

You've set up your SMS campaign. You've written the message. You've loaded your contact list. You hit Send — and then… nothing. No delivery reports. No customer replies. No error message. Just silence.

This is exactly what happens when a bulk SMS campaign isn't DLT compliant. The telecom operator's filter catches your message before it ever reaches a phone. And the worst part? You often don't know it's happening until customers start calling to say they didn't receive their OTP.

This guide covers everything you need to send legal, deliverable bulk SMS in India in 2026 — no legal jargon, no confusion. If you're working with a bulk SMS service provider, understanding these rules will help you ask the right questions and stay protected.

1. What DLT Compliance Actually Means

DLT registration is TRAI's answer to India's spam and fraud problem. Before the framework, anyone could send SMS from any number — and millions of fraudulent messages were reaching Indian consumers every day.

Today, every SMS sent commercially in India is checked against DLT records before delivery. If your entity, sender ID, or template isn't registered, the operator's filter rejects the message automatically — no error, no warning, no refund.

Key Point:

Registration on any one TRAI-approved DLT platform is recognised across all operators. You register once — not separately on Jio, Airtel, Vi, and BSNL.

2. The Three-Phase Registration Process

DLT compliance follows three sequential phases. You can't skip Phase 1 and jump to Phase 3 — each stage builds on the previous one.

Phase 1 — Entity (Principal Entity) Registration

This is the one-time registration of your business. You register as a "Principal Entity" on any approved DLT portal. Documents you'll need:

Cost: Approximately ₹1,000–5,000 depending on the operator. Once approved, your business gets a unique Entity ID.

Phase 2 — Sender ID (Header) Registration

A sender ID is the name or code that appears as the SMS sender on your customer's phone — for example MTRECH or 581204. Each header must be registered against your Entity ID and tied to a message category.

Timeline: Typically approved within 1–2 working days.

Phase 3 — Content Template Registration

Every unique message you intend to send must be pre-approved as a template. Templates combine fixed text with variable placeholders written as {#var#}.

Example: "Dear {#var#}, your order {#var#} has been shipped and will arrive by {#var#}. — MTRECH"

2025 update: TRAI now requires a message-category suffix so recipients can tell at a glance whether a message is promotional or transactional. Templates without the correct identifier are rejected.

If you're sending multiple types of messages — OTPs, order alerts, and promotional offers — each needs its own registered template. A single character difference between your live message and your registered template causes the operator's filter to reject it.

MetaReach handles all three phases end-to-end through our DLT registration support service. Most clients are live and sending within 5–7 working days.

3. The Four Message Categories — and Why Getting This Wrong Kills Campaigns

The single most common reason a compliant-looking campaign gets blocked is choosing the wrong message category. TRAI recognises four types, and each has its own consent rule, delivery window, and sender ID format.

Category Used For Consent Required Delivery Window
Transactional OTPs from banks; customer-initiated transaction alerts within 30 minutes None (not promotional) 24/7 — any time
Service Implicit Order updates, delivery status, renewals, account alerts for existing customers Implied by existing relationship 24/7 — any time
Service Explicit Service-related but promotional-flavoured updates to opted-in users Explicit opt-in required 10 AM – 9 PM only
Promotional Offers, discounts, sales, lead generation, marketing campaigns Non-DND, or explicit DCA consent for DND numbers 10 AM – 9 PM only

Important note: Under current rules, the pure Transactional route is effectively reserved for banks sending OTPs. Most "transactional-looking" business messages — order updates, shipping alerts, appointment reminders — now fall under Service Implicit. Using the wrong category routes your message through the wrong filter and causes silent blocking.

For businesses sending OTP SMS, choosing the right category is critical. A mis-categorised OTP causes login failures and lost transactions. For transactional SMS like order confirmations, Service Implicit is usually the correct category.

4. Consent, DND, and the DCA Process

The national DND (Do Not Disturb) registry — also called NCPR — blocks promotional SMS for any subscriber who's registered. This isn't a setting you can bypass. Promotional messages to DND numbers are dropped silently. You won't see an error, and the customer never receives the message.

Transactional and service messages always reach DND subscribers. If you're sending order updates, OTPs, or service alerts, DND doesn't affect delivery.

Reaching DND Numbers Legally

There is one legal route to send promotional SMS to a DND subscriber: the Digital Consent Acquisition (DCA) facility. The subscriber verifies their consent via an OTP triggered by the telecom operator, and the consent is recorded on the DLT Consent Register. Once recorded, you can send promotional messages to that subscriber.

The DPDP Act Layer

Separately from TRAI rules, India's Digital Personal Data Protection (DPDP) Act requires specific, granular, and informed consent for marketing communications. Treat DLT consent and DPDP consent as two separate compliance layers — both must be satisfied. This is particularly relevant for businesses in fintech, healthcare, and e-commerce who handle sensitive customer data alongside messaging campaigns.

5. Delivery Windows and Operational Rules

6. What Non-Compliance Actually Costs You

Most businesses don't discover a DLT problem until a customer calls to say their OTP never arrived — or until a big campaign produces zero responses. By then, the damage is done.

  1. Silent message blocking — your SMS simply never arrives. No error returned. You may not realise delivery has stopped for days.
  2. Header or template blacklisting — one non-compliant send can disable an entire sender ID or campaign template.
  3. Financial penalties from telecom operators for repeated violations, and suspension of your sender ID.
  4. No audit trail — if TRAI or an operator queries your consent or delivery records, being unable to produce them compounds any penalties.
  5. Lost customer trust — blocked OTPs, missing order confirmations, and undelivered alerts are directly felt by your customers.

7. Your Pre-Send Compliance Checklist

Use this before every campaign. If any item is unchecked, do not send.

How MetaReach Handles DLT for You

Most businesses don't have the time or the patience to navigate the TRAI DLT portal, chase template approvals, or stay on top of consent compliance. That's exactly why we built our end-to-end DLT registration service.

We handle entity registration, sender ID approval, template submission and review, DND compliance, and ongoing monitoring — so your messages actually get delivered. Whether you're sending promotional SMS, transactional alerts, or OTP verification codes, we make sure the compliance layer is solid before a single message goes out.

If you're building an automated messaging flow or need API-level SMS integration, see our SMS API documentation — it covers DLT-aware template usage with working code examples for PHP, Python, Node.js, and Java.

Need Help Getting DLT Compliant?

MetaReach manages end-to-end DLT registration — entity, header, and template approval — alongside Bulk SMS, OTP, RCS, and WhatsApp Business API. We handle the compliance so your messages get delivered.

Get Free Demo DLT Registration Service →

Our Happy Clients

Trusted by 500+ Businesses Across India

From startups to enterprises — brands that grow with MetaReach


WhatsApp Facebook Instagram YouTube LinkedIn X / Twitter

☎ Instant Call Back FREE
or request a call back

We'll call you back within 5 minutes