DLT registration is how India controls commercial SMS: before a business message reaches an Indian number, the sender must register its organisation, its sender IDs (called headers) and its message templates on an operator’s DLT platform, as TRAI’s TCCCPR 2018 regulations require. Messages that do not match those records fail the operator’s checks and are never delivered, so registration comes before your first send.
This guide walks through each registration step, the message categories, the rule changes since 2024, and how to send once you are approved. If you are planning bulk SMS in India, allow time for approvals before launch.
What is DLT and who has to register?
The Telecom Regulatory Authority of India (TRAI) issued the Telecom Commercial Communications Customer Preference Regulations, 2018 (TCCCPR) on 19 July 2018. They require the access providers, India’s mobile operators, to keep registers of entities, headers, content templates, consent templates, consents, customer preferences and complaints on permissioned distributed ledger technology (DLT), so every party in the chain works from the same records.
Three roles matter to a sender:
- Principal Entity (PE): the business or organisation that sends the commercial communication. That is you.
- Telemarketer (TM): a registered aggregator or provider that carries your messages to the operator.
- Access provider: the operator that runs the DLT platform, checks each message and delivers it.
Any business sending commercial SMS to Indian numbers under its own sender ID must be a registered PE. TRAI’s guidance to senders lists entity, header, content template and consent registration, and states that skipping any of these steps will stop you sending commercial communication.
Which DLT portal should I use?
Each access provider runs its own DLT portal. Because the records sit on a ledger shared between operators, you normally register your entity on one portal and use the resulting Entity ID for traffic to all networks.
| Operator | DLT portal |
|---|---|
| Reliance Jio | TrueConnect |
| Bharti Airtel | Airtel DLT |
| Vodafone Idea (Vi) | Vilpower |
| BSNL | BSNL DLT |
Choose the portal whose interface and support suit you best. Each operator sets its own registration fee, accepted documents and review process, so read the portal’s requirements before you start.
What do you register on DLT?
| Item | What it is | Key rules |
|---|---|---|
| Entity | Your organisation’s record on DLT, identified by an Entity ID | Since the 2025 amendment, registration can include physical verification of the entity, biometric authentication of the authorised person and linking to a unique mobile number |
| Header | The sender ID recipients see | Alphanumeric, up to 11 characters, not allocated by the Department of Telecommunications for other purposes; deactivated after 90 days without use |
| Content template | The approved text of each message, with fixed parts and variables | Normally up to 3 variables, each tagged for its purpose; at least 30% fixed text; linked to only one header; deactivated after 90 days without use |
| Consent template | The wording used to ask customers for consent to promotional messages | Consent requests go out from the 127xxx short code, and the confirmation must tell the customer how to revoke consent |
| Chain (PE-TM binding) | The declared path of telemarketers from you to the operator | Traffic from undeclared chains has been rejected since 11 December 2024 |
Promotional, service, transactional or government?
The category decides what consent you need and which suffix recipients see after your header. TRAI’s Second Amendment Regulations of 12 February 2025 redefined the categories and require operators to add -P, -S, -T or -G to headers so recipients can tell them apart.
| Category | Suffix | What it covers | Consent |
|---|---|---|---|
| Promotional | -P | Offers, advertising and any message that mixes promotion with other content | Delivered only if the recipient’s preferences allow it or they have given consent; an opt-out must be in the message |
| Service | -S | Information on a product or service the customer uses: warranty, recalls, security alerts, balances, delivery updates | No explicit consent needed; messages that facilitate a new transaction need explicit consent, valid for seven days |
| Transactional | -T | Responses to a transaction the customer started, sent within 30 minutes, such as an OTP, transaction alert or refund notice | No explicit consent needed |
| Government | -G | Messages sent on the directions of central or state government bodies, TRAI or agencies it authorises, through DLT | No consent needed and cannot be blocked through preferences |
A transactional message that carries service information is treated as a service message. Choose the category carefully when you register templates, because it has to match the content.
What happens during scrubbing?
Scrubbing is the check the operator runs before delivery. TCCCPR 2018 defines it as comparing the target numbers against customer preferences and consents, and the DLT records extend the checks to your registrations. A message goes through only if:
- it comes from a registered entity, through a declared chain of telemarketers;
- the header is registered, active and linked to the template being used;
- the text matches the approved template, with only the variable parts changed;
- for promotional messages, the recipient’s preferences or consent allow it;
- every URL, APK, OTT link or call-back number in it has been whitelisted by the sender.
If any check fails, the message is rejected and your delivery report shows a failure. Nothing reaches the handset.
What has TRAI changed since 2024?
- Whitelisted links, from 1 October 2024. A TRAI direction of 20 August 2024 told operators to block messages containing URLs, APKs or OTT links that the sender has not whitelisted. By the deadline, more than 3,000 senders had whitelisted over 70,000 links, according to the government press release. The 2025 amendment added call-back numbers to the scrubbing and requires an undertaking that whitelisted links are not malicious.
- Message traceability, from 11 December 2024. Every PE must declare and bind its chain of telemarketers on DLT. After a period in which messages on undeclared paths were flagged with error codes, operators began rejecting traffic from unregistered paths on 11 December 2024.
- Second Amendment, February 2025. New category definitions and header suffixes; complaints accepted within seven days of receiving a message; action against a sender after five complaints from unique recipients in ten days, with outgoing services barred for 15 days on a first violation and one-year disconnection and blacklisting for repeat violations, as summarised in the TRAI announcement.
- Third Amendment, September 2026. On 18 September 2026 TRAI announced further changes: action can start after three unique complaints in ten days when the sender is also flagged by an operator’s AI-based spam detection; operators must suspend a misused header or template within six hours of becoming aware of the misuse; messages based on a customer’s written or digital enquiry may be sent for seven days; and verifiable legacy consents can be digitised and registered on the operators’ platforms.
How do I register on DLT, step by step?
- Register as a Principal Entity. Sign up on one operator’s DLT portal, choose your entity type, upload the business documents it asks for and complete any verification of your authorised person. Keep your Entity ID safe; every later step uses it.
- Register your headers. Apply for each sender ID you need. Choose headers that clearly match your brand, because operators scrutinise the justification and take into account how many headers you already hold.
- Register content templates. Submit each message as a template, tag each variable by purpose (for example a code, an amount or a link), keep at least 30% of the text fixed, and link each template to one header. Choose the category carefully: promotional content mixed into a service message makes the whole message promotional.
- Register consent templates if you plan to send promotional messages, and collect consent through the operator’s digital consent process.
- Whitelist your links and numbers. Add every URL, APK, OTT link and call-back number that appears in your templates, including the domain of any link shortener you use.
- Declare your chain. Bind your entity to the telemarketer or telemarketers that will carry your traffic, in the order the traffic flows. Your SMS provider tells you which telemarketer details to add.
- Share your DLT details with your provider. Send your Entity ID, approved headers and template IDs, so your traffic can be matched to your registrations.
- Test every template with a real Indian number before launch, and check the delivery report for each one.
How do I send DLT-registered SMS through an international provider?
Once your records are approved, sending from an international platform works like any other API call, with two rules: the text must match an approved template exactly, with only the variables changed, and the sender must be your registered header.
curl -X POST https://api.sms.to/sms/send \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"message": "482913 is your login code for YRBRND. It is valid for 10 minutes. Do not share it.",
"to": "+919000000000",
"sender_id": "YRBRND",
"callback_url": "https://example.com/sms/status"
}'
A few habits save support tickets:
- Keep templates and code in step. A changed word, an extra space or a new link in your code means the message no longer matches, and it is rejected.
- Use
callback_urlto receive delivery reports, and alert on failure spikes after every release that touches message text. - An OTP is transactional only when it answers a transaction the customer started. A reminder that also carries an offer is promotional.
- For sign-up and login codes, a multichannel Verify API can try WhatsApp first and fall back to SMS. Our guide to OTP best practices covers expiry and retries.
If your business is not established in India, talk to us before launch: how your traffic is registered and routed decides how your sender appears and which rate applies.
How SMS.to helps you send to India
SMS.to delivers SMS to India through the same API, web platform and SMPP connections you use for other destinations. For Indian traffic we:
- guide you through entity, header and template registration and tell you which chain details to declare;
- match your traffic to your approved headers and templates during onboarding;
- return delivery reports through webhooks, so rejected messages are visible straight away;
- help you separate OTP, service and promotional traffic onto the right headers.
India is not the only market with sender registration. Spain now blocks unregistered alphanumeric senders, as our guide to Spain’s CNMC alias registry explains, and our overview of SMS sender ID rules by country covers the rest.
Rules change often. This guide reflects the rules as of September 2026; check with your account manager before launching a campaign.
FAQs
How long does DLT registration take?
It depends on the operator and on how complete your documents are. The entity is approved first, then headers and templates are reviewed separately. Templates with more than three variables need a written justification, so allow extra time for those.
Do I need to register separately with every operator?
Normally not. DLT records are kept on a ledger shared by the access providers, so you register your entity on one portal and use the same Entity ID for traffic to all Indian networks.
Do OTP messages need DLT registration?
Yes. An OTP sent in response to a transaction the customer started is a transactional message, but it still needs a registered entity, header and content template, and it must match the template exactly.
What happens if a message doesn’t match its template?
It fails scrubbing and is not delivered. Your delivery report shows the failure, so check any template change against your approved text before release.
Do headers and templates expire?
Headers and content templates that are not used for 90 days are deactivated automatically. They can be reactivated on request through your DLT portal.
Launching in India or moving Indian traffic from another provider? Talk to sales and we will check your DLT setup and get your first templates delivering.