Everything you need to get your OTP SMS templates DLT-approved and actually delivering — numeric sender IDs, template variables, and the PE-TM binding step most businesses miss. Free setup with MetaReach.
OTP SMS runs on the same TRAI DLT framework as every other commercial SMS category in India — but the rules for entity registration, sender ID format, and template wording are stricter and more specific than for promotional or general transactional messages. Get any one of these wrong and your OTPs stop reaching users, usually with no clear error beyond a failed delivery report.
This guide covers exactly what MetaReach configures for every OTP SMS Services and OTP API customer — entity registration, numeric sender ID approval, template variable formatting, and the PE-TM binding step that most businesses discover only after their first delivery failure.
DLT (Distributed Ledger Technology) is the TRAI-mandated registry that records every business
sender, message header, and approved template used for commercial SMS in India.
1. Without DLT registration, telecom operators block the message before it ever reaches a
handset — there is no grace period or warning traffic.
2. For OTP SMS specifically, DLT registration exists to stop spoofed or fraudulent numeric
headers from impersonating banks and apps to phish users.
3. A DLT-approved OTP route is what allows MetaReach's
OTP SMS service to deliver in
under 6 seconds on a priority channel that bypasses DND filtering entirely.
OTP templates are approved under the Transactional category and follow a narrower rule set
than promotional or Service-category templates.
Numeric sender ID: OTP headers use a numeric format (e.g.
140XXXXXXXX) rather than the 6-character alphanumeric header (e.g.
MTRCHR) used for promotional and alert SMS.
Variable syntax: The OTP code must be marked with the standard variable
placeholder, written as {#var#}, in the exact position it will appear in the
live message.
No promotional content: A Transactional-category template can only state
the OTP, its purpose, and a validity window — no offers, brand taglines, or links are
permitted.
Fixed wording: Once approved, the live message text must match the
registered template exactly, including spacing and punctuation — the sending system rejects
any mismatch.
Example approved format: "<OTP> is your OTP. Valid for 5 minutes. Do not share
this with anyone. — MetaReach"
DLT approval of your entity, sender ID, and template is necessary but not sufficient.
1. PE-TM binding links your business (the Principal Entity) to your SMS
provider (the Telemarketer) on the DLT portal — without it, even a fully approved OTP
template is blocked at the network scrubbing layer.
2. This is the single most common reason OTP delivery fails after a business believes DLT
setup is complete.
3. MetaReach is a TRAI-registered telemarketer with an active TM ID on Jio Trueconnect,
Airtel DLT, Vi Business DLT, and BSNL Sanchar Saathi, so binding is completed for you as
part of onboarding — see our full
PE-TM
binding guide for the technical walkthrough.
Step 1 — Register as a Principal Entity: Submit your business documents
(GST, PAN, incorporation certificate) to create a Principal Entity profile on a DLT portal.
Step 2 — Apply for a numeric OTP sender header: Request a numeric header
under the Transactional/OTP category — this is a separate application from any alphanumeric
headers you may already have for promotional SMS.
Step 3 — Submit the exact OTP template text: Enter the final wording with
the {#var#} placeholder in place, and select "Transactional" as the message
category.
Step 4 — Complete PE-TM binding: Approve the binding request from your
chosen telemarketer so your approved header and template are authorized to route through
their gateway.
Step 5 — Test before going live: Send a sandbox OTP through your provider
to confirm end-to-end delivery before switching production traffic over.
MetaReach handles all five steps for
OTP SMS and
OTP API customers,
typically completing the full chain within 4 hours of receiving valid documents.
| Rejection Reason | Fix |
|---|---|
| Wrong variable bracket format | Use {#var#} exactly — not {{otp}},
%otp%, or other custom formats. |
| Promotional wording inside a Transactional template | Remove offers, taglines, and links — state only the OTP, purpose, and validity window. |
| Entity category mismatch | Match your Principal Entity category (e.g. Banking, E-commerce, SaaS) with the template's declared purpose. |
| Wrong sender ID digit count | Confirm the numeric header length required by your chosen DLT platform before submitting — most require a fixed 10 or 11-digit format. |
| PE-TM binding skipped after template approval | Approve the binding request from your telemarketer on the DLT portal — an approved template alone will not deliver without it. |
| Live message text doesn't match approved template | Even small wording or spacing changes need a fresh template submission — keep production text identical to what was approved. |
For a broader look at DLT rejection patterns across all SMS categories, see our guide on common DLT registration mistakes.
| Requirement | OTP SMS | Promotional SMS |
|---|---|---|
| TRAI Category | Transactional (OTP) | Promotional |
| Sender ID Format | Numeric (e.g. 140XXXXXXXX) | 6-character alphanumeric (e.g. MTRCHR) |
| DND Bypass | Yes | No |
| Sending Time Window | 24/7 | 9 AM – 9 PM only |
| Consent Requirement | Implied by user action (login, payment) | Explicit opt-in consent required |
| Allowed Content | OTP code, purpose, validity window only | Offers, discounts, marketing messages |
See the full breakdown, including transactional-alert SMS, in our OTP vs Normal SMS comparison guide.
✅ Principal Entity registered with valid business documents
✅ Numeric OTP sender header approved under the Transactional category
✅ Template submitted with correct {#var#} variable syntax
✅ Template contains no promotional wording, links, or offers
✅ PE-TM binding completed with your chosen telemarketer
✅ Live message text matches the approved template exactly
✅ Test OTP sent successfully through sandbox before going live
Ready to go live? MetaReach handles every item on this checklist as part of OTP SMS Services onboarding at no extra cost. Call +91-7669999219 or request a free demo.
OTP SMS DLT Compliance, OTP DLT Registration India, PE-TM Binding for OTP, OTP Template Approval, DLT Registered OTP SMS, TRAI OTP Compliance 2026
From startups to enterprises — brands that grow with MetaReach
