please wait

DLT Registration

What is DLT Registration?

The Telecom Regulatory Authority of India (TRAI) has made it mandatory for all entities to register in the Distributed Ledger Technology (DLT) platform.  Distributed Ledger Technology (DLT) is a Blockchain-based registration system. This Ledger keeps track of all the records of transactions made by network participants. Where telemarketers have to be registered with operators and users & resellers with operators but through Telemarketer.  This has been done to make to bring down the spam message volumes and protect user’s privacy.

“To comply with the new regulation, all enterprises need to be registered with the DLT system.” 

Being an enterprise, it is mandatory to register in at least one DLT platform, however if you are using our multi route approach (switching of provider when there is low delivery rate in a provider) then you have to register in other DLT platforms as well. 

What is DLT Registration?

To know more about the regulation:

Registering on DLT platform as Entity

Register on any of the DLT platforms below by filling in the required information and documents and get a temporary ID. After the verification of your documents by the Operator, you will receive your unique Entity ID.


Vilpower – Vodafone Idea Ltd DLT Platform

Jio DLT Platform

Airtel DLT Platform

Videocon DLT Platform

BSNL DLT Platform

Details Required for DLT Registration for your organisation:

❖ Business PAN Number with Soft Copy.

❖ GST Number (GST Certificate)

❖ Business Established Certificate.

❖ Complete Business Address.

❖ Proof of Business Identity (PAN Card) with Softcopy.

❖ Proof of Business Entity with Softcopy (GST Reg./Business Reg.)

Registration Process

❖ Have you registered with any other Mobile Operator DLT Network? Select: No.

❖ Enter Your Business PAN Number.

❖ Fill the form with Required Details.

❖ Verify with OTP.

❖ Verify Your Email.

❖ Login to Portal.

❖ Upload Required Documents and Fill the Required Details.

❖ After Completion you will receive the temporary Registration Number.

❖ You will get your unique entity id after 2 working days.

Detailed Registration process for each Operator is given below:



Header Registration

Types of Headers (Sender ID)



Headers that can be used for sending Promotional messages fall under PROMOTIONAL type. Promotional message means commercial communication that can be sent to a mobile subscriber whose preferences are not set (not on DND). Or, any commercial communication that an enterprise can send to an intended recipient after taking consent to send such messages.

Header (6 numeric): 565690, 787878, 987123, 555555, etc.

Promotional Headers should start with the number that matches with the category (as per DND Preferences).


❖ 1-Banking/Insurance/Financial products/ credit cards. Ex: 123890, 154987

❖ 2-Real Estate Ex: 234567, 264789

❖ 3-Education Ex: 397134, 321456

❖ 4-Health Ex: 467931, 444654

❖ 5-Consumer goods and automobiles Ex: 582974, 564123

❖ 6-Communication/Broadcasting / Entertainment/IT Ex: 631469, 693147

❖7- Tourism and Leisure Ex: 789456, 714369

❖ 8-Food and Beverages Ex: 896321, 816934

❖ 0-(Zero) Others – Category that doesn’t appear in 1-8 Ex: 012389, 098654


Headers that can be used for sending Transactional, Service Implicit and Service Explicit message fall under OTHER type. Same Header can be used against all three type of messages. All These Headers are Case Sensitive.

Header (6-alpha): TRUBLQ, TRUblq, TRubLQ, trublq, KLMNOP, DLTdlt, etc.

Transactional: Message which contains One Time Password (OTP) and requires to complete a banking transaction initiated by the bank customer. This is applicable to all banks including national/ scheduled/ private/ Govt. and MNC banks.

Ex: TRHDFC, DCBmsg, MkotaK


Service Implicit: Messages arising out of customer’s actions or his relationship with the Sender, that is not promotional, and is not in the interest of the customer to block such communications. These messages may or may not be triggered by a subscriber-initiated transaction and will not be blocked for subscribers who have otherwise blocked service messages also.

❖ Confirmation messages of a net banking or a credit/debit transaction.

❖ Product purchase confirmation.

❖ Delivery status of a parcel.

❖ OTP required for e-commerce website, app login, social media apps, KYC, etc.

❖ Messages from schools regarding attendance/transport.

❖ Messages from hospitals/clinics regarding appointment/discharge reports.

❖ Govt./TRAI/DoT mandated messages, advisories, messages from state Govt., LEAs, local authorities, traffic advisories, election commission, disaster management advisories.

❖ Service messages from car workshops, gadget service centres.

❖ Day-end/ month-end settlement alerts to securities/demat account holders.

Ex: ABCDE, AFioma, uniFco.

Service Explicit: Any service message which doesn’t fall under the category of service message (Implicit) will be sent only against service explicit, digitally verified/verifiable consent that has been taken from the subscriber by the respective enterprise.

Ex: NUTUKI, PRizem, semRTA

OTHER – Govt. Only Govt. entities can register these Headers that can be used for sending Transactional, Service Implicit and Service Explicit messages.

Header (3 to 9 numeric and should start with 1): 1444, 19898, 15555, 19090909, etc.

Header Registration Process Guide






Adding Consent & Content Templates

Template Registration Guide – DLT Platforms

As part of the DLT registration process all entities are required to register their templates in the DLT platforms. Once a template is created, the entity retains the template ownership across all platforms.

Enterprises needs to add

  • Consent Templates
  • Content Templates


Consent Templates

Consent templates are the Standard message that is sent to end users of the enterprise for their consent to receive communications from respective enterprise.


The steps to add the consent templates in various platform are given below:




BSNL : The process of consent template addition in BSNL in very similar to the process in VILPOWER. Request you to refer the VILPOWER document in case of any doubts.

Content Templates

Templates are created for commercial communication and as per TRAI guidelines all the principle entities need to register their templates before sending commercial communication.


Types of Templates:

  • Transactional : Any message which contains OTP and requires to complete a banking transaction initiated by bank customer will only considered as transactional. This is applicable to all banks (national/scheduled/private/govt and even MNC’s).


  • Service Implicit : Any message arising out of customers action or his existing relationship with the enterprise, that is not promotional will be considered as Service-Implicit message.


  • Service Explicit : These are the messages which requires explicit consent from customer, that has been verified directly from the recipient in robust and verifiable manner and recorded by consent registrar. Any service message which doesn’t fall under service-implicit category.


Important: Additionally, customer consent template needs to be linked to content templates in service explicit category.

Click Here to access the sample messages and details about types of content templates.

Latest updates from the operator regarding your DLT registration

  • As part of the attest DLT process, operators will stop sharing the delivery reports for the Promotional SMS sent to customers (SMS sent using numeric headers like 582974)
  • Every Content Template that is being registered by a Principal Entity should contain ‘Brand Name(s)’ in the content field. This is mandatory from October 01, 2020. Templates could be rejected if the same is not incorporated while registering.


Below are examples for your understanding in mentioning ‘Brand Name(s)’:

Scenario 1:

Entities having multiples brands operated under its registered name, should use their complete brand name.

Entity Name: Caspar Technologies PVT LTD

Template eg.1: Thank you for opting Platinum plan – cmercury marketing automation. Your account has been activated. –

Template eg.2: You have successfully registered for the webinar “Intelligent Emails – Revolutionising Email Marketing”. Click on the link below to join the webinar – cmercury Academy

Template eg.3: We are excited to announce the completion of the 10th digital brand engagement. – cmercury Media



Template eg.1: Congratulations! n Your shopping has unlocked a gift voucher of Rs.1000 redeemable on on Rs.2499 spend. Valid till 15th Dec. TC. Use Code: {#var#} – Pantaloons

Template eg.2: As we turn 2 in India, visit the Allen Solly store and get a {#var#} OFF on our ENTIRE COLLECTION, exclusively for you! Limited period offer. *T&C apply. Stay safe and keep shopping with us! Learn more – Allen Solly

Template eg.3: Congratulations! n Your shopping has unlocked a gift voucher of Rs.{#var#} redeemable at {#var#} on Rs.{#var#} spend. Valid till {#var#}. TC. Use Code: {#var#} – Louis Philippe


Scenario 2:

Entities notably called with abbreviations and unique


Template eg.:  OTP for online purchase of Rs. {#var#} at {#var#} thru State Bank Debit Card {#var#} is {#var#}. Do not share this with anyone – SBI or State Bank of India


Scenario 3:

Entities whose abbreviations represent 2 different names, must use complete entity name at the footer.

Entity name with same abbreviations:

National Payments Corporation of India (NPCI);


Template eg.1: Amt. of {#var#} for {#var#} ({#var#}) will be credited to ur A/C of {#var#} – National Payments Corporation of India

Template eg.2: Amt. of {#var#} for {#var#} ({#var#}) has been generated with the due date of {#var#} – Nuclear Power Corporation of India


Scenario 4:

Entities whose registered name is different from their registered trademark name, can use their trademark name.

Entity name:

Bundl Technologies Private Ltd (Swiggy)
Atria Convergence Technologies Ltd (ACT Fibernet)


Template eg.1: Dear Customer, ₹{#var#} has been deducted from your Swiggy Money (Powered by ICICI Bank) balance at {#var#}. Updated Swiggy Money balance is ₹{#var#} – Swiggy

Template eg.2: Dear Customer, thank you for choosing ACT. Our engineer will visit in the next {#var#} hours to confirm feasibility at your location. – ACT Fibernet


Last date to update your content templates with ‘Brand Name(s)’ is October 31, 2020. Post which the contents without brand names will be considered invalid


Some important points to keep in mind while creating content templates are:


  • 2 or more spaces are not supposed to use between 2 words, before word or afterword.
  • All special characters (found on the keyboard) are allowed, except < and > symbols.
  • The variable format is {#var#} which is case sensitive.
  • Or variable can be inserted by clicking the radio button (insert variable) above the text box in your DLT platform.
  • Trans/Service category messages should have variables mandatorily.
  • Promo category can have complete fixed content or with a variable part
  • There is no limitation in no. of variables per message.
  • Values like amount, date, a/c no, merchant names, OTP, codes, URL, customer names, card type, etc. need to be replaced with variables.
  • In case trying to upload the same template, the portal would show an error as “Template Message already registered (Template Name – ****)”
  • A single SMS has a character limit of 160 characters. If your message exceeds the limit, an alert is shown on the screen allowing you to continue typing the message beyond the character limit. This message will count for 2 or more SMS
  • Each variable can consist of up to 30 characters.


DOs for Content Templates:


  • Use the promotional category for communications intended to send from numerical sender id only.
  • The transactional category is to be used by banking enterprises only & for OTP messages during fund transfer; online payment; merchant transaction only.
  • Service – explicit category needs to link consent templates as well, without which the template gets rejected.
  • Choose a relevant/recognizable name for templates
  • Use the message type as “TEXT” for all general messages & “Unicode” for regional messages.
  • Variable {#var#} insertion to be required against values like a date; amount; a/c no; OTP; names; etc.
  • Always use notepad or notepad ++ to create a template, to avoid additional spaces and invalid characters
  • The minimum fixed characters required in templates is 10 characters (applicable in pure OTP messages only)
  • Linking of consent templates for content template categories “promotional” & “service – explicit” is optional (not mandatory)


DON’T’s for Content Templates:


  • Same content template against multiple headers.
  • Header selection against irrelevant templates
  • Selecting the “Transactional” category by non-banking enterprises.
  • No or invalid variable format in templates.
  • Using double spaces in templates (this can be pre-checked by verifying the template on notepad++ before template submission)
  • Templates with less than 10 characters or variable insertion alone as a template using multiple templates (eg: Dear customer {#var#}{#var#}{#var#}.)
  • Use external fonts or characters other than those that appear on the keyboard, like the example mentioned explaining the brand name field.
  • We hope this helps you in creating the templates in the DLT platform without any concerns.

The steps to add the consent templates in various platform are given below:


The process of consent template addition in Vilpower in very similar to the process in BSNL DLT platform. Request you to refer the BSNL document in case of any doubts.

We have identified a few key issues that are causing messages to fail and want you to get these checked from your end so that you can continue to send messages to your customers with no difficulties.


Please make sure that the SMS sent from your website/app is an exact match of the approved template. Even a minute change in the registered content template can cause delivery failure.

Below are some of the use cases where the SMS will not be delivered.

  1. If the static content sent in the message is not a 100% match to the template uploaded in the DLT portal.

Example 1: If the message registered is:

“Success! We’ve received your entry. We’ll contact you if you are declared a winner. Visit Stay #abcready. Team abc. T&Cs apply”.

and if the message sent is:

Success! We’ve received your entry. We’ll contact you if you’re declared a winner. Visit Stay #abcready. Team abc. T&Cs apply”.

Why did this message fail to deliver?

The template was rejected because in the registered template, “you are” is registered instead of “you’re.”

 Example 2: if the message registered is:

Hello, your OTP for abc transaction is {#var#}

and if the message sent is:

Hello, your OTP for abc transaction is {#var#}.

Why did this message fail to deliver?

The template was rejected because in the registered template “full stop(.)” was not registered.

  1. If the brand name is not added as per the registered template on the DLT platform.

Example: If the message registered is:

{#var#} is your one time password for ABC login. It’s valid for {#var#} minutes only.

and if the message sent is:

{#var#} is your one time password for ABC login. It’s valid for {#var#} minutes only. – ABC

Why did this message fail to deliver? 

The template was rejected because in the registered template, the Brand name – ABC is not mentioned at the end of the message. 

  1. If a spacing difference is there on the registered message template on DLT and the message sent.

Example: If the message registered is:

Hello, your  _OTP is {#var#}

and if the message sent is:

Hello, your OTP is {#var#}

Why did this message fail to deliver?  

The template was rejected because, in the registered template, double spacing was registered between “your” and “OTP”.

  1. A new line or paragraph is added in the registered template, but not in the message sent.

A new line or paragraph is formed when we press “enter” to move to the next line. If a new line was added while registering the message content with the operator, but when the same is not encoded and sent while pushing the messages via API, these messages will be rejected.

Example: If the message registered is:

Hello, Your OTP is {#var#}

and if the message sent is:


Your OTP is {#var#}

Why did this message fail to deliver?   

The template was rejected because in the sent message there is a NEW LINE between “Hello,” and “Your”.

You can fix the message failed issue with your SMS services either by uploading a new template that you wish to send, in the DLT portal, OR by sending the message content in the exact format that has been registered in the DLT platform.