If you send one-time passwords by SMS to Indian mobile numbers, every message has to match a record on a DLT (Distributed Ledger Technology) platform before the operator will deliver it. That surprises many teams who are used to sending SMS in other countries with nothing more than an API key.

This guide walks through DLT registration for OTP SMS step by step: what you register, what each item looks like for an OTP use case, the mistakes that get templates rejected, and how to keep sending OTPs while you wait for approval.

Four DLT steps for OTP SMS in India: entity, sender ID, OTP template, go live

What DLT is, in one paragraph

DLT is the registration system Indian telecom operators run under TRAI’s commercial communication rules (TCCCPR 2018). Businesses that send SMS, called principal entities, register themselves, their sender IDs (also called headers) and their message templates. When an SMS is sent, the operator checks it against these records. If the sender ID or the text does not match an approved record, the message is blocked.

What you register for OTP SMS

ItemWhat it isFor OTP messages
Principal entityYour business, verified with documentsRegistered once, shared across operators
Sender ID (header)The name shown as the senderSix letters for service messages, for example ACMEIN
Content templateThe exact message text with variablesService Implicit (Transactional for banks), the code as {#var#}
Consent templateProof that users agreed to receive messagesNot needed for OTPs a user requests themselves
The four DLT records and how they apply to OTP SMS

Before you start: keep these ready

Exact document lists differ slightly between operator portals, so check the list on the portal you choose before you begin.

Step 1: Register your business as a principal entity

Choose one operator’s DLT portal (Jio, Airtel, Vi and BSNL each run one), create an account and submit your business details and documents. After approval you receive an Entity ID. You only do this once: other operators can see the same registration.

Step 2: Register a sender ID for OTPs

Request a header for service messages. It is made of six alphabetic characters and should clearly relate to your brand. ACMEIN for a company called Acme is fine; a random string or someone else’s brand will be rejected. Users trust an OTP more when the sender name matches the app they are logging in to.

Step 3: Register your OTP content template

Templates contain the fixed text plus variables written as {#var#}. For an OTP, the code is the variable. Choose the Service Implicit category unless you are a bank or regulated financial institution, which can use Transactional.

A template that is usually approved looks like this:

{#var#} is your OTP to log in to Acme. It is valid for 10 minutes. Do not share it with anyone. - Acme

Tips for OTP templates:

Step 4: Connect your SMS provider

Your messages reach operators through a messaging provider. Under TRAI’s message traceability rules, the chain of providers that carries your traffic is declared on the DLT portal. Your SMS provider gives you the details to add. On EazyOTP, contact our team to activate the SMS DLT Eazy OTP route on your account and connect your approved DLT details.

Step 5: Test, then go live

Send a test OTP to your own phone from the sandbox in your dashboard, which sends to one mobile number, and check that the sender ID and text appear exactly as registered. With EazyOTP each OTP is one GET request with the user’s number. The platform generates the code and returns it to your server for verification. See the ready-to-use OTP API for the request and response.

Why DLT templates get rejected

How long does DLT approval take?

It depends on the operator and on how complete your documents are. Entity, header and template approvals happen one after the other, so plan for several working days from start to finish, and longer if anything is sent back for correction.

Need OTPs before your DLT approval comes through?

You don’t have to delay your launch. On EazyOTP:

For an overview of every SMS option, read SMS OTP services in India. If you are still choosing a provider, our guide to picking an OTP SMS service provider in India covers what to ask.

Frequently asked questions

Do I need DLT registration to send OTP SMS in India?

Yes, if you send SMS to Indian numbers over domestic routes. Your business, sender ID and OTP message template must be registered on an operator DLT platform. Messages to numbers outside India do not use DLT.

Which DLT template category is used for OTP messages?

OTP templates are normally registered as Service Implicit content. Banks and other regulated financial institutions may register OTPs as Transactional. The DLT portal shows the categories available to your entity type.

Do I have to register on every operator’s DLT portal?

No. Register your entity on one operator’s DLT platform. The registration is shared with the other operators.

Can I send OTPs while my DLT approval is pending?

Yes, with EazyOTP. The Global SMS route can deliver OTPs to Indian numbers without a DLT template or sender ID, and WhatsApp OTP uses Meta-approved authentication templates instead of DLT. Read instant SMS OTP India.

Does my OTP template need my brand name?

It should. Templates that name your business are clearer for users and are less likely to be rejected than generic text such as “Your code is {#var#}”.

Send OTPs today, add DLT when it’s ready

Create your account, test in the sandbox and start on Global SMS or WhatsApp while your DLT approval is pending.

Prefer chat? Message EazyOTP on WhatsApp