DLT Registration for Bulk SMS in India: 2026 Step-by-Step Guide
DLT registration is the TRAI-mandated process that every business must complete before sending commercial SMS in India. Under the TCCCPR 2018, you register three things on a DLT (Distributed Ledger Technology) operator portal — your entity, your sender IDs (headers) and your message templates — so operators can verify and deliver your messages. It costs about ₹5,900 + GST one-time and takes roughly 3–7 working days. Skipping it is not an option: unregistered SMS is simply blocked at the operator level. Worse, even registered senders see messages fail "silently" when content does not exactly match an approved template. This guide walks the full process step by step, lists the real fees and timelines for 2026, and shows you the scrubbing traps that quietly kill delivery — so your first campaign actually lands. If you would rather have it handled for you, Ojiva AI guides DLT setup as part of onboarding to our bulk SMS service. But it pays to understand the process either way.
What Is DLT Registration?
DLT stands for Distributed Ledger Technology — a blockchain-based system that India's telecom operators use to record and verify who is allowed to send commercial SMS. TRAI introduced it under the Telecom Commercial Communications Customer Preference Regulations (TCCCPR) 2018 to stamp out spam and unsolicited messages. The principle is simple: if your entity, sender ID and exact message content are not on the ledger, the message does not go out.
Every commercial SMS is checked in real time against these registered records — a process called scrubbing — before an operator delivers it. That is why DLT registration is the foundation of reliable SMS in India, not an optional formality.
Mandatory for commercial SMS: Promotional, transactional, service and OTP SMS all require DLT registration. Person-to-person messages do not.
One ledger, all operators: Jio, Airtel, Vi and BSNL share the same DLT backbone, so you register once and it applies network-wide.
.png)
Who Needs to Register?
Any business or organisation that sends commercial SMS to Indian mobile numbers needs DLT registration — regardless of size or volume. If you send OTPs, order updates, reminders, alerts or promotions, you are a Principal Entity (PE) in DLT terms and must be on the ledger.
Banks, fintech and NBFCs: OTPs, transaction alerts, EMI and KYC messages.
E-commerce and retail: Order confirmations, delivery updates, offers and cart reminders.
Healthcare, education, logistics and services: Appointment, fee, shipment and renewal messages — essentially every business that texts customers.
The 3 Things You Register: Entity, Header & Template
DLT registration is not one form — it is three linked registrations that must agree with each other. Getting the relationship right is what prevents failures later.
1. Principal Entity (PE): Your business itself — verified with GST/PAN and incorporation documents. This is the paid, one-time registration.
2. Header (Sender ID): The 6-character alphanumeric ID customers see, e.g. OJIVAI. Each header is tied to a category (promotional, transactional or service).
3. Content Template: The exact message text, with variables as {#var#}. Every content variation must be approved before you can send it.
Step-by-Step: How to Complete DLT Registration
Here is the full process from zero to your first compliant campaign. Have your GST, PAN and incorporation documents ready before you start — missing paperwork is the number-one cause of delay.
Step 1 — Choose a DLT operator portal: Register on any one of Jio, Vodafone Idea (Vilpower), Airtel (SmartPing) or BSNL. You only need one; the ledger syncs your data across all networks.
Step 2 — Register your Principal Entity (PE): Submit business details, GST/PAN, authorised-signatory and address proof, and pay the ~₹5,900 + GST one-time fee. You receive a unique PE ID, usually in 1–3 working days.
Step 3 — Register your Header (Sender ID): Request a 6-character header under the right category. TRAI now requires the header to indicate the message type, so map promotional, transactional and service traffic to the correct headers. Approval is typically 1–2 days.
Step 4 — Register your Content Templates: Submit each message with fixed text and variables written exactly as {#var#}. Choose the matching category. Each template is usually approved in 1–3 days.
Step 5 — Map to your SMS provider and send: Link your approved entity, headers and templates to your bulk SMS platform, capture consent for promotional sends, and launch. Messages now pass scrubbing and deliver. DLT Registration Fees & Timeline (2026)
Here is the honest cost-and-time picture so you can plan. Fees are one-time; the headline cost is the entity registration, while headers and templates are usually free on most portals.
| Registration step | Typical fee (2026) | Timeline |
|---|
| Principal Entity (PE) | ~₹5,900 + GST (one-time) | 1–3 working days |
| Header (Sender ID) | Usually free | 1–2 working days |
| Content Template | Usually free | 1–3 working days each |
| Total to go live | ~₹5,900 + GST | ~3–7 working days |
Fees vary by operator: Airtel SmartPing and Jio commonly charge around ₹5,900 + GST for entity registration. Confirm the current fee on your chosen portal before you pay.
Plan a buffer: Timelines assume clean documents. A mismatch on GST name or signatory proof can add days, so submit carefully the first time.
Header & Template Rules That Trip People Up
Most DLT pain is not in registering — it is in getting templates approved and keeping sent content matched to them. These are the rules that catch teams out.
Variables must be exactly {#var#}: Not [name], not {{otp}}, not %s. Use {#var#} for every dynamic field, or the template is rejected.
Static text must match character-for-character: The fixed parts of a sent message must match the approved template exactly — an extra space, emoji or word breaks the match.
Category must match content: Marketing wording under a transactional header is rejected. Keep promotional, transactional and service templates under the right header.
Whitelist your URLs: Links in transactional templates must be whitelisted. A non-whitelisted or shortened URL is a common silent rejection.
Silent Blocking: Why Your SMS Fails Scrubbing
The most frustrating problem in Indian SMS is messages that show as "failed" with no obvious reason. This is almost never a network issue — it is DLT scrubbing rejecting a mismatch in real time. Scrubbing checks your PE ID, header, content template ID, the PE-to-telemarketer binding chain and the recipient's DND status on every single message. If any one fails, the message is dropped.
Template mismatch: Sent content differs from the approved template — the most common cause. Fix the content or update and re-submit the template.
Wrong category: Promotional content sent on a transactional route gets scrubbed. Match the message to the right header and template category.
Header issues: An inactive, blacklisted or mismatched header — or one that does not pair with the template — fails the binding check.
DND on promotional: Promotional SMS to numbers on the DND/NCPR list is blocked. Transactional and service messages and OTPs are not affected by DND.
Read your delivery report: A "failed" status with a DLT error code points to the exact mismatch. A good provider surfaces these so you can fix the template, not blame the network.
How Ojiva AI Handles Your DLT Registration
DLT is three linked records that must agree — and that's exactly where teams stumble. Ojiva AI sets it all up for you as part of onboarding to our bulk SMS service.
Document guidance: We tell you exactly which GST, PAN and authorisation papers you need — so you clear entity approval the first time.
Entity, header & template setup: We register and map all three, in the correct categories, so they bind cleanly at scrubbing.
Category mapping done right: Promotional, transactional and service traffic routed to the correct headers — no mismatched rejections.
Faster go-live: We keep the 3–7 day timeline on track and handle the back-and-forth. Book a demo to get sending. How Ojiva AI Prevents Silent SMS Failures
The worst DLT problem is messages that fail with no clear reason. Ojiva AI's platform catches the mismatch before it costs you a campaign.
Template-match validation: We check sent content against your approved template — including {#var#} placeholders — so it passes scrubbing.
Readable error codes: When a message fails, we surface the exact DLT reason so you fix the template, not blame the network.
URL whitelisting help: We flag non-whitelisted or shortened links — a common silent rejection — before you send.
Live delivery reports: Real-time DLRs show what landed and what bounced, so issues are caught in minutes, not campaigns.
.png)
Ojiva AI's Bulk SMS Platform: What You Get
Beyond compliance, the platform itself is built to make high-volume SMS simple, fast and measurable.
Scheduling & campaigns: Plan, schedule and personalise template campaigns from one dashboard — within the 9am–9pm promo window automatically.
High-throughput OTP route: A priority path keeps login codes landing in seconds, even during bulk sends.
Simple REST API: Fire SMS from your app, CRM or backend on real events — order placed, payment due, code requested.
Multi-template management: Store and reuse all your approved templates and language variants, so you're never blocked mid-campaign.
One Platform Beyond SMS: WhatsApp, OTP, RCS & Voice
SMS rarely works alone. With Ojiva AI, every channel lives on one platform — so a message that fails on one route has a fallback on another.
WhatsApp Business API: Add rich, conversational messaging with no DLT needed — see App vs API. OTP across channels: OTP & 2FA over SMS, WhatsApp and voice with automatic fallback, so logins never stall. Voice & RCS: Layer in voice reminders and branded RCS from the same dashboard and contact data. One dashboard, one team: Manage every channel, report and compliance setting in one place — no juggling vendors.
Documents You Need for DLT Registration
Missing paperwork is the number-one cause of delay. Have these ready before you start your entity registration and you'll clear approval in the first attempt.
GST certificate & PAN: Company PAN plus the GST certificate — the name must match exactly across both and your entity application.
Incorporation / business proof: Certificate of Incorporation, partnership deed, or shop & establishment registration, depending on your entity type.
Authorised signatory ID: PAN/Aadhaar of the signatory plus a Letter of Authorisation on company letterhead.
Address & contact proof: Registered address proof, a company email and (often) a verifiable website or domain.
SMS Categories: Promotional, Transactional & Service
Every header and template is tied to a category, and the category decides the rules — including whether DND applies. Picking the wrong one is a top reason messages get scrubbed.
| Category | Used for | DND applies? |
|---|
| Promotional | Offers, discounts, marketing blasts | Yes (9am–9pm, opt-in) |
| Transactional | Banking OTPs, transaction alerts | No |
| Service (implicit) | Order/delivery updates to existing customers | No |
| Service (explicit) | Promotional-style messages to opted-in users | Needs consent |
OTPs sit under transactional/authentication: They're DND-exempt and high priority, which is why login codes still land on numbers that block promotions.
DLT Costs Beyond Registration: What You Pay to Send
The ~₹5,900 + GST entity fee is one-time. Once you're live, your ongoing cost is per-message — and it's worth knowing the parts so a quote can't surprise you.
Per-SMS charge: A few paise per SMS, varying by volume, route (promotional vs transactional) and provider. Higher volume lowers the rate.
Scrubbing charge: A nominal per-message fee operators levy for the real-time DLT check — usually bundled into your SMS rate.
No recurring entity fee: Header and template registration are typically free, and you don't re-pay the entity fee — you only pay for messages sent.
Add 18% GST: GST applies on SMS spend. A transparent provider shows the route rate and GST separately — compare on our bulk SMS provider guide. DLT for OTP & High-Priority Messages
OTPs are the most delivery-critical SMS you send — and DLT treats them differently from marketing. Getting this right means codes that land in seconds, every time.
Use authentication/transactional templates: Register OTP content with the code as {#var#} under the correct category, or it won't pass scrubbing.
DND-exempt: OTP and transactional messages reach numbers on the DND/NCPR list — unlike promotional SMS.
Prioritise a high-throughput route: OTP traffic needs low-latency delivery; a dedicated route keeps codes from queuing behind bulk campaigns.
Plan a fallback: If an SMS OTP fails, a WhatsApp or voice fallback rescues the login — our OTP & 2FA service spans all three. DND, Consent & Timing Rules You Must Follow
DLT registration gets you delivery; these rules keep you compliant and your entity in good standing. They apply mainly to promotional traffic.
Respect DND/NCPR: Promotional SMS to numbers on the National Customer Preference Register is blocked at scrubbing — clean your lists against it.
Send promos 9am–9pm only: TRAI restricts promotional sends to daytime hours. Transactional and OTP messages have no time limit.
Keep consent proof: Maintain opt-in records for promotional recipients — your defence if a complaint is raised.
Offer a clear opt-out: An easy STOP/unsubscribe protects your sender reputation and your quality of delivery over time.
DLT vs Other Channels: SMS, WhatsApp, RCS & Voice
DLT is SMS-specific. If you message across channels, each has its own compliance route — here's the quick map.
| Channel | Compliance route | Best for |
|---|
| SMS | DLT (TRAI/TCCCPR) | OTPs, alerts, universal reach |
| WhatsApp | Meta verification + templates | Rich, conversational, media |
| RCS | Google / operator onboarding | Branded, rich messaging |
| Voice (OBD/IVR) | TRAI/TCCCPR & consent | Reminders, confirmations, calls |
The Risks of Skipping or Breaking DLT Rules
DLT isn't optional, and non-compliance costs more than a blocked message. Here's what's actually at stake.
Messages simply don't deliver: Unregistered SMS is blocked at the operator level — no entity, header and template means no delivery, full stop.
Header blacklisting: Repeated violations can get your sender ID blacklisted, killing a brand identity customers recognise.
Entity suspension & penalties: Spam complaints and rule breaches can trigger graded financial penalties and even suspension of your registered entity.
Reputation damage: A poor sending record drags down delivery for all your future traffic — hard to undo, easy to avoid.
DLT Compliance Best Practices
Once you are registered, a few habits keep delivery high and your entity in good standing.
Pre-register template variations: Register every wording you expect to use, including language variants, so you are never blocked mid-campaign.
Keep clean consent records: Maintain opt-in proof for promotional sends — it protects your entity if a complaint is raised.
Remember other channels differ: WhatsApp and RCS do not use DLT — see WhatsApp Business App vs API for how WhatsApp verification works instead. For login codes, our OTP & 2FA service spans SMS, WhatsApp and voice. Conclusion
DLT registration looks bureaucratic, but it is straightforward once you see it as three linked records — entity, header and template — that must agree. Budget around ₹5,900 + GST and 3–7 working days, write your variables as {#var#}, keep content matched to approved templates, and you will avoid the silent scrubbing failures that frustrate most senders.
If you would rather skip the paperwork, Ojiva AI handles DLT entity, header and template setup as part of onboarding to our bulk SMS service, and flags scrubbing errors before they cost you a campaign. Book a demo to get registered and sending faster.
By Ananth · Updated 12 June 2026
Frequently Asked Questions: DLT Registration for Bulk SMS
DLT (Distributed Ledger Technology) registration is a TRAI-mandated process under the TCCCPR 2018. Every business sending commercial SMS in India must register its entity, sender IDs (headers) and message templates on a DLT operator portal before messages will be delivered.
Principal Entity (telemarketer) registration costs around ₹5,900 plus GST as a one-time fee on operator portals such as Airtel SmartPing and Jio. Header and template registration are typically free on most portals.
If your documents are in order, the full process takes about 3–7 working days: entity registration approves in 1–3 days, header registration in 1–2 days after the entity is live, and each template in 1–3 days.
No. You register on one operator portal — Jio, Vodafone Idea (Vi), Airtel or BSNL — and the data is shared across all four through the DLT blockchain backbone.
A header is the 6-character alphanumeric sender ID customers see as the SMS sender, for example OJIVAI. Each header is registered against a category (promotional, transactional, service) and must match the templates sent under it.
Almost always a scrubbing mismatch, not a network fault. Common causes are content that does not match the approved template, variables not written as {#var#}, promotional content sent under a transactional header, non-whitelisted URLs, or a header–template mismatch.
Every dynamic field must use the exact placeholder {#var#}. Formats like [name], {{otp}} or %s are rejected. The static (fixed) text must match the approved template character-for-character.
No. DLT is specific to SMS. WhatsApp uses Meta verification and template approval; RCS uses Google/operator onboarding. Only SMS requires DLT entity, header and template registration.