Skip to main content
November 3, 2026 · By Piyush Sahoo DLT registration records your business, sender headers, and message templates on a telecom operator’s Distributed Ledger Technology platform in India. TRAI’s rules require it for commercial SMS and for calls on the 140xx and 1600xx series. Operators check each SMS against those records and reject traffic that doesn’t match. This guide treats DLT as a system you have to build against. It maps the records you register, follows one message through the checks, and shows which failure points to which fix. Regulatory points link to TRAI’s own documents wherever we could read them.
Key takeaways
  • DLT is a set of linked records. One Principal Entity owns many headers, and each header owns many templates. Each template links to only one header.
  • The category is a legal test. A message becomes promotional if it holds any promotional content, and a transactional message must follow a customer-initiated transaction within 30 minutes.
  • Templates are now typed. TRAI’s November 2025 direction requires a tag on every variable, and links and callback numbers are checked against your whitelist.
  • Registration can lapse. Unused headers and templates can be deactivated after 90 days, and a missed annual self-certification brings automatic suspension.
  • New rules are coming into force. The TCCCPR Third Amendment sets a six-hour limit for suspending a misused header, and a credential leak can change your IDs.

​
What is the full form of DLT?

DLT stands for Distributed Ledger Technology. TRAI’s regulations define it as a shared, sequenced, cryptographically secured record that many participants hold and act on together. In Indian telecom, the term has a narrower meaning. It refers to the ledger networks that access providers run under the Telecom Commercial Communications Customer Preference Regulations, 2018 (TCCCPR). Developers usually say “DLT” for the whole compliance regime and “the DLT portal” for the website where they file records. The regulation names separate ledgers for headers, consent, consent templates, content templates, preferences, and complaints. TRAI’s December 2024 note put the number of active Principal Entities at about 1.13 lakh. A shared record means that every operator can verify the same sender without trusting a claim in the message.

​
What do you register on DLT?

You register six kinds of record. Three of them produce the IDs that travel with every message, and the other three decide whether a given send is allowed. Relationship diagram of DLT records. A Principal Entity with a PE ID owns many headers, and each header owns many content templates. The entity also declares a telemarketer chain and registers consent templates. Tagged template variables are checked against a CTA whitelist. Every commercial SMS carries the PE ID, header ID, and template ID. Relationship diagram of DLT records. A Principal Entity with a PE ID owns many headers, and each header owns many content templates. The entity also declares a telemarketer chain and registers consent templates. Tagged template variables are checked against a CTA whitelist. Every commercial SMS carries the PE ID, header ID, and template ID. “CTA” here means a call to action, the term TRAI’s tag annexure uses for these registered links and numbers.

​
Who needs DLT registration?

Anyone sending commercial communication to Indian numbers over telecom routes needs to be in the chain somewhere. Your role decides what you file.

​
How do you complete DLT registration?

The work runs in a fixed order, because each record depends on the one before it. The approval times below come from vendor guides, because we found no regulator-published service level. Exotel’s overview puts entity and template work at one to two weeks. Treat these as a planning range.
1

Choose a portal

Operators run their own portals, and Exotel lists Jio, Airtel, Vi, BSNL, MTNL, and Smartping. Infobip’s guide covers the same model. Check your voice plans before you pick, as the table below explains.
2

Register the Principal Entity

File your legal name as it appears on your PAN, with PAN, certificate of incorporation, GST, address proof, and business proof. Vobiz’s guide quotes 24 working hours for review, and Exotel quotes 3 to 7 days.
3

Register headers

Apply for each sender name in the right category, with evidence of your brand. Exotel quotes 1 to 3 days. Expect more scrutiny for names close to a bank, a government body, or a known brand.
4

Whitelist your links and numbers

Add each URL, app link, and callback number that your templates will use. Do this before template work, because a tagged variable has nothing to validate against without it.
5

Register templates with tagged variables

Link each template to one header, pick the category, and tag every variable. Exotel quotes 1 to 3 days. Tags sit in different places by portal: MSG91 reports a separate tagging section on SmartPing and Tata, and tags inside the template text elsewhere.
6

Register consent templates where needed

You need them for promotional sends that rely on explicit consent. Vobiz’s guide requires a consent template for 140 series calling.
7

Declare the chain and give your provider the IDs

Bind your PE to each telemarketer on the path, then pass the IDs to your provider. Exotel advises allowing 5 to 7 days if an approved entity hasn’t synced across operators.

​
Which portal should you use?

Exotel says one registration is enough, because it propagates across operators. That makes the choice mostly about what you plan to do next.

​
How much does DLT registration cost?

Budget for the entity fee, and expect it to vary by portal. Exotel gives ₹5,000 to ₹10,000 as a one-time fee. Message Central gives about ₹5,000 to ₹5,900, plus up to ₹500 per header and yearly maintenance. These are vendor figures rather than official rates. The regulation lets TRAI set such fees or direct providers to, and we didn’t find a single published schedule, so confirm the amount on your portal before paying.

​
How do you choose the right message category?

Category drives consent, preference checks, and the header suffix. Work through the questions in order, because the first match wins. Decision map with five questions. Promotional content of any kind means Promotional, suffix P. Sent on the direction of government or TRAI means Government, suffix G. A response to a customer-started transaction within 30 minutes means Transactional, suffix T. Information for your own customer about their product or service means Service, suffix S. Help completing an ongoing purchase with explicit consent means Service with explicit consent, suffix S. Otherwise, get explicit consent first or don't send. Decision map with five questions. Promotional content of any kind means Promotional, suffix P. Sent on the direction of government or TRAI means Government, suffix G. A response to a customer-started transaction within 30 minutes means Transactional, suffix T. Information for your own customer about their product or service means Service, suffix S. Help completing an ongoing purchase with explicit consent means Service with explicit consent, suffix S. Otherwise, get explicit consent first or don't send. The definitions in the regulation create three traps:
  • Mixed content turns promotional. A delivery update with a discount line is a promotional message, whatever category you filed.
  • Thirty minutes is part of the test. A reminder sent the next day doesn’t fit the transactional definition, so it needs another category.
  • Explicit service consent is short. Consent for messages that complete an ongoing purchase lasts seven days, unless TRAI directs otherwise.
Filing in the wrong category costs more than a rejected message. TRAI says a template in the wrong category will be blacklisted. Under the Third Amendment, a complaint triggers that blacklisting, and five such blacklists in 90 days will suspend the sender. The suspension lasts one month, or until every template is re-verified if that takes longer. Timing also differs from what you may have read. The regulation treats time as a recipient preference that is checked during scrubbing, and vendor guides quote a fixed promotional window, such as 9 AM to 9 PM on Exotel’s page. Confirm the window with your provider before you schedule a campaign.

​
How does a DLT template get checked?

A template is a pattern with fixed and variable parts. The regulation defines transactional and service templates this way, and describes a promotional template as fixed content. The regulation tells registrars to create a one-way hash of the fixed part, and to define how the fixed and variable parts are pulled out of a real message. That design explains why small wording changes fail: your text no longer yields the same fixed part. Illustrative template split into fixed text and two tagged variables, alphanumeric and url. Fixed text is hashed at registration and compared on every send. Three example sends follow: an exact match passes, one with an added word fails because the wording changed, and one with a different domain fails because the link isn't listed. Illustrative template split into fixed text and two tagged variables, alphanumeric and url. Fixed text is hashed at registration and compared on every send. Three example sends follow: an exact match passes, one with an added word fails because the wording changed, and one with a different domain fails because the link isn't listed. The November 2025 direction sets six tag types: Build your application around these types. Generate each message from the same stored string you registered, and validate variables before you submit them. A value that passes your code but breaks its tag is still a failed message.

​
What happens when you send a message?

Your message passes through a declared path, and each stage has a defined way to stop it. The diagram simplifies the order, because operators can split these checks across their own systems. Flow from your application through an optional aggregator telemarketer and a delivery telemarketer to the originating access provider. The provider checks the chain, the header and template link, the fixed text, and the tagged variables, and a failure rejects the message. A failed preference or consent check stops delivery to that recipient. Passing messages go to the terminating provider and then the recipient. Flow from your application through an optional aggregator telemarketer and a delivery telemarketer to the originating access provider. The provider checks the chain, the header and template link, the fixed text, and the tagged variables, and a failure rejects the message. A failed preference or consent check stops delivery to that recipient. Passing messages go to the terminating provider and then the recipient. Use the pattern of the failure to find its layer. Error codes differ by operator and provider, so this table starts from symptoms.

​
What has changed in the DLT rules?

Most of today’s enforcement arrived from 2024 onward. If you registered before then, compare your setup with each step. Timeline of DLT rules. TCCCPR issued 19 July 2018. Direction on header and template misuse 20 August 2024. Link whitelisting enforced 1 October 2024. PE-TM chain enforced 11 December 2024. Second Amendment 12 February 2025. Variable pre-tagging direction 18 November 2025. 1600-series adoption dates January to March 2026. Third Amendment notified 18 September 2026, starting 30 to 90 days after Gazette publication. Timeline of DLT rules. TCCCPR issued 19 July 2018. Direction on header and template misuse 20 August 2024. Link whitelisting enforced 1 October 2024. PE-TM chain enforced 11 December 2024. Second Amendment 12 February 2025. Variable pre-tagging direction 18 November 2025. 1600-series adoption dates January to March 2026. Third Amendment notified 18 September 2026, starting 30 to 90 days after Gazette publication. Three of these deserve a closer read. Link whitelisting came in stages. TRAI moved the date to 1 October 2024 for URLs, APKs, and OTT links, and left callback numbers for later. The November 2025 direction then added callback numbers to the tag checks. Variable tagging had a logging period. The direction allowed 60 days of logging from the start of tag scrubbing, during which failing messages were still delivered. After that, they are rejected outright. Fast2SMS says new templates had to be tagged after 14 January 2026. We couldn’t confirm a single operator-wide end date, so treat tagging as already required and check your templates now. The Third Amendment changes incident response. TRAI announced it on 18 September 2026. The notification starts most provisions 30 days after Gazette publication. The misuse sequence below starts after 60 days, and the wrong-category suspension after 90. We couldn’t confirm the publication date, so check whether each one applies today. Once in force, a misuse case follows this sequence:
  1. The originating provider suspends the misused header or template within six hours of noticing it, and sends you a notice within 48 hours.
  2. You reset passwords, API keys, and system permissions within three business days of the notice, and file a complaint with a law enforcement agency in that same period.
  3. If credentials leaked, your registrar de-registers all your headers and templates within five business days, or in phases if it allows. You then re-register them, and they receive new IDs.
  4. You review every registered header and template within ten business days, and report the cause to the provider.
Point three has a direct engineering consequence. Keep your IDs in configuration rather than in code, so a forced re-registration doesn’t need a release. The penalties for unregistered senders are heavier still. The Second Amendment applies when an investigation upholds complaints against one. It bars outgoing services on all of the sender’s telecom resources for 15 days on a first violation. Later violations disconnect those resources for one year, across all providers, along with blacklisting. The Third Amendment keeps these steps.

​
How do you keep a DLT registration healthy?

Treat DLT records like production configuration with an owner and a review date.
  • Self-certify every year. Providers must suspend senders automatically when details, headers, or templates go uncertified. Put the date on a shared calendar.
  • Audit idle records every quarter. List headers and templates that won’t send within 90 days, and either retire them or plan for reactivation.
  • Limit portal access. Each credential can now trigger a sender-wide event, so use named users and remove leavers quickly.
  • Keep consent evidence. Under the Third Amendment, an inquiry supports messages for seven days only when it was written or digital and you hold it in verifiable form. Legacy consent counts only if you obtained it through verifiable means and register it on the providers’ digital platform.
  • Review your templates against your product copy. A copy edit can break a match with a valid template, so add template checks to your copy review.

​
Does DLT apply to voice calls?

Yes. The regulation’s template definitions cover voice calls as well as messages, and TRAI required the 140xxx series to move onto DLT in 2024. On voice, Vobiz’s guide notes that the header is the DID itself. The number series depends on the call type. Promotional calls use 140xx, and regulated financial entities and government bodies use 1600xx for service and transaction calls. TRAI’s November 2025 direction set dates for RBI, SEBI, and PFRDA entities in phases. The dates for RBI-regulated entities ran from 1 January to 1 March 2026. Check the annexure for your entity type, because some intermediaries remain voluntary. Automated calling gets its own rule. The Third Amendment defines application-to-person (A2P) calls as those an application or automated platform starts without direct human dialing. You must declare them to your provider in advance, with the caller ID ranges you plan to use, or they count as unsolicited. The notification starts this rule 60 days after Gazette publication.

​
How Vobiz handles DLT

Vobiz supports DLT for both messaging and voice. You keep your own registration on a DLT portal, and Vobiz carries the identifiers.
  • SMS fields. Send a message accepts dltEntityId, dltHeaderId, and dltTemplateId. The India DLT guide explains how they map to your records. Vobiz stores them on the message, and operators check each message against your registration.
  • Broadcasts. Broadcasts take the same three fields once, up to 64 characters each, and copy them onto every recipient’s message. After variables are substituted, each message must still match the template.
  • Sender IDs. India uses registered headers rather than long codes. The available numbers endpoint returns an empty list for country=IN, with a hint that explains why. To use a header as a from value, register it and contact Vobiz support.
  • Market rules. The coverage endpoint returns market notes for a country, plus a sendWindow where the country restricts sending hours, so your code can read them.
  • Opt-outs and events. Opt-outs record STOP replies, and later sends to those recipients return 422. You can follow delivery through webhooks (callbacks).
  • 140 and 160 voice. The DLT entity guide covers your organisation’s records, DID provisioning covers each number, and the acquisition guide covers how numbers are sourced. Vobiz’s docs use “160 series” for this service and transactional range.
  • Complaints. The UCC and NDNC page explains complaint handling, and India calling regulations covers the wider voice rules.
Messages and calls reach real people and are billed to your account. Run them with your own Auth ID and Auth Token, and confirm numbers and wording before you send. Current rates are on the Vobiz pricing page.

​
Frequently asked questions

DLT stands for Distributed Ledger Technology. In Indian telecom, it refers to the operator-run ledgers that TRAI’s rules use to record commercial senders, headers, templates, consent, and customer preferences. It’s why developers talk about DLT registration when they mean getting set up to send commercial SMS.
Not commercial SMS. Operators pass that traffic only with registered headers and templates, and they reject messages with no DLT data. If you use a provider’s pre-registered template, the registration still exists under someone’s entity. Personal messages between individuals aren’t commercial communication.
Yes. TRAI’s definition of a transactional message names OTPs from banks, e-commerce, and app logins. An OTP needs a registered header and template, with the code in a tagged numeric variable. It must follow a customer-initiated transaction within 30 minutes to qualify as transactional.
Plan for about one to two weeks in total. Vendor guides quote up to seven days for the entity and one to three days each for headers and templates. Synchronisation across operators can add more. We found no regulator-published service level, so ask your portal for current times.
Usually not. Vendor guides quote roughly ₹5,000 to ₹10,000 for entity registration, and some mention yearly charges. TRAI’s regulation allows TRAI or providers to set these fees, and we found no single published schedule. Check your chosen portal before paying, because amounts vary.
Yes. Promotional calls in India use the 140xx series, which moved onto DLT in 2024. Regulated financial entities and government bodies use 1600xx for service and transaction calls. On voice, the phone number acts as your header, and templates describe the call’s content.

​
Further reading on Vobiz

​
Sources

Indian regulators Vendor guides, used for portal lists, approval times, and fees

Send your first message to India

Add your DLT IDs to the Vobiz Messaging API.