• 228 destinations
  • No KYC, ever
  • Bitcoin, Monero, USDT and 4 more

ComplianceAdvanced7 min readUpdated 18 October 2026

Bulk SMS to India: DLT registration and what foreign senders can do

India's DLT rules under TRAI's TCCCPR 2018: entity, headers, templates, consent and DND, what foreign senders can still deliver, and what it costs.

What DLT is

Since 2020 the Telecom Regulatory Authority of India requires commercial SMS to pass through a distributed-ledger system run by the operators. Every sender, every sender name and every message template is registered on it, and messages that do not match a registered template are blocked. The purpose is to make each commercial message traceable to a legal entity and a consent.

The legal basis is TRAI's Telecom Commercial Communications Customer Preference Regulations, 2018, usually shortened to TCCCPR. They define the categories of message, the customer preference register, the complaint process and the duties of senders, telemarketers and operators; the DLT platforms are how the operators enforce them. Each large operator runs its own platform, but they share one ledger, so an entity registered on one is known to all. TRAI amends the regulations from time to time, so check the current text before you register.

What gets registered

  • The entity: an Indian business, with its registration documents.
  • Headers: the sender names, six letters for transactional and service traffic, numeric for promotional.
  • Content templates: the text of each message with variables marked, categorised as transactional, service or promotional.
  • Consent templates for promotional traffic, checked against the national do-not-disturb preferences.

The entity, called the principal entity, registers once and receives an entity ID. Headers should reflect the brand or the entity's name; generic words and names that resemble someone else's brand are commonly rejected. Templates fix the wording and mark each variable as {#var#}, for example Your ACME order {#var#} has shipped and arrives on {#var#}. Every message on a domestic route carries the entity ID and the template ID, and the operator compares the text with the registered template before delivery; a changed word or an extra link is enough to block it. On the handset, the header appears after a two-letter prefix and a hyphen added by the network.

Message categories

Every template belongs to a category, and the category decides who the message can reach. The names are TRAI's, and transactional is narrower than most senders expect.

CategoryWhat it coversNumbers on the DND register
TransactionalCodes and alerts that complete a bank transaction, sent by banks to their own customersDelivered
Service, implicitMessages that follow from the customer's own action or an existing relationship: codes, order and delivery updates, account noticesDelivered
Service, explicitMessages, promotional ones included, to customers whose explicit consent is recorded on DLT through a consent templateDelivered once consent is recorded
PromotionalOffers and marketingNot delivered

A one-time code from an app or a shop is therefore a service message, not a transactional one, in DLT's vocabulary. Promotional messages are the ones bound by the 10:00 to 21:00 window; codes and alerts can be sent around the clock.

DND and the preference register

The National Customer Preference Register, still widely called DND, records each subscriber's choice: block all promotional messages, or only some categories, such as banking and financial products, real estate, education, health, consumer goods and automobiles, communication and entertainment, tourism and leisure, or food and beverages. Subscribers register by calling or texting 1909 or through an app, and the operators scrub promotional traffic against the register on DLT. Promotional messages cannot reach registered numbers and may only be sent between 10:00 and 21:00. Subscribers also complain about unwanted messages through 1909, and complaints that are upheld lead to action against the sender.

Separately, the Digital Personal Data Protection Act, 2023 governs the personal data in your list as its provisions come into force. DLT consent and data protection consent are different records, and a careful sender keeps both.

Links, apps and call-back numbers

Since 2024, links, APKs and call-back numbers must also be whitelisted in the templates. A message that carries a URL, an app download link or a phone number not declared for its template is blocked, even when the rest of the text matches. For a registered entity this means declaring every domain and number it uses, and keeping links on its own domains. For codes, on any route, the simplest rule is the one that works everywhere: no links at all.

Registering with an Indian entity

For a business that has, or can form, an Indian entity, registration follows a fixed order, and a domestic provider can guide it:

  1. Register the principal entity on one operator's DLT platform, with its business documents.
  2. Register the headers it will use, matched to its brand.
  3. Register consent templates if it will send on the basis of explicit consent.
  4. Register a content template for every message, with its category, its variables and every link, app and call-back number it contains.
  5. Give the entity ID and the template IDs to the domestic provider, which sends them with every message.

Each item is approved separately, so prepare the templates well before a launch. Any change to the wording means a new template.

Without an Indian entity

A foreign sender without a registered Indian entity cannot hold a DLT header. Traffic then enters India on international routes, which operators price above domestic traffic and deliver from numeric or shared senders rather than from your brand. One-time codes and service messages to your own users deliver this way; large promotional campaigns under your own header do not, because they require exactly the registration you do not have. India is therefore marked "registration required" on our India page, and messages leave from a shared sender unless a registration exists.

The international route suits traffic that genuinely originates abroad: a foreign app sending codes to its Indian users, a foreign service sending alerts and receipts. Operators watch these routes for domestic marketing that tries to avoid DLT and filter what looks like it, so promotional content on an international route is fragile even when it is lawful. Treat the route as a channel for codes and notifications, and leave marketing to India to a registered sender.

Content and timing

Promotional messages are restricted to daytime hours and blocked for numbers on the do-not-disturb registry. Keep codes free of links, identify your brand in the first words, and keep to GSM-7 where you can. Messages in Hindi or other Indian scripts are Unicode: 70 characters per segment, 67 per part.

Hindi written in Latin letters, as many people text it, stays in GSM-7 at 160 characters. For codes, the format that travels best is the brand, the code and its lifetime in one segment: ACME: 493 201 is your code. It expires in 10 minutes. Send codes and alerts with the transactional flag so they leave at any hour, and leave the quiet-hours window to promotions. A long Unicode message can run to six parts, the maximum, so check the segment count before sending; the guide to GSM-7 and Unicode explains the arithmetic, and the OTP use case covers code delivery.

Price

Domestic DLT traffic costs a fraction of a cent because it is sold inside India by Indian providers to registered entities. International routes cost several cents: large platforms quote 6 to 8 US cents. Our published rate for India is $0.0256 per segment, with no monthly fee and no template fee.

The rate is per segment, so a two-part Hindi message costs twice a one-part English code. Messages refused before sending are not billed; messages handed to a carrier are, whether they are delivered or fail. The calculator prices a planned volume, and the cost preview shows the exact total per destination before anything is charged.

Deciding

If India is your main market and you have, or can form, an Indian entity, register on DLT with a domestic provider: it is cheaper and carries your header. If India is one of many destinations for codes and notifications, an international route is the practical answer, and it needs no paperwork.

QuestionDLT with an Indian providerInternational route
What you needAn Indian entity, with headers and templates registered on DLTAn account
What recipients seeYour registered headerA numeric or shared sender
PromotionsYes, within the rules on hours and DNDNot a dependable channel
PriceA fraction of a cent$0.0256 per segment here
Best forIndia as a main marketCodes and service messages among many destinations

This guide is general information, not legal advice.

Put it into practice.An email address opens the account. Rates are public, payment is crypto, and the test key is free.
Start sending

Something unclear or out of date? Tell us on the support page; corrections are folded back into the guide and the update date changes.