EDICT · Indian regulatory framework

TRAI DLT in practice: Principal Entity, Header ID, Content Template and the PE → TM → TSP scrub chain for A2P SMS into India

The Telecom Regulatory Authority of India (TRAI), through TCCCPR 2018 read with the Telegraph Act, 1885 and the TRAI Act, 1997, runs the world's only blockchain-enforced A2P SMS registry — the Distributed Ledger Technology (DLT) consortium operated by Vodafone-Idea, Jio, Airtel and Tanla. Four TSPs cover the country: Jio, Airtel, Vi (Vodafone Idea) and BSNL. Every Principal Entity must onboard, reserve a six-character Header ID, and lock each Content Template to the Header before despatch. 4notify carries Principal Entities across all four TSPs with tier-1 direct connections, mirrors the DLT registry at the API edge and signs a five-year audit envelope.

The four Indian TSPs (Telecom Service Providers)

Reliance Jio

Share: ~40% · P50: 2.4 s

Largest subscriber base in India; tier-1 priority routing for transactional traffic with strong DLT scrub-chain enforcement.

Bharti Airtel

Share: ~32% · P50: 2.6 s

Second-largest TSP; strong enterprise A2P market share and rapid Header ID activation.

Vi (Vodafone Idea)

Share: ~18% · P50: 2.9 s

Merged Vodafone India and Idea Cellular; complete DLT consortium operator status.

BSNL

Share: ~9% · P50: 3.4 s

State-owned operator; mandatory for full subscriber reach including rural circles.

The four Content Template categories

TransactionalBank OTP, authentication, statutory alerts. Exempt from DND. Headers prefixed VK-, JK-, JM-, AD-, AX-, JD-.
Service ImplicitCustomer-service alerts implicit from the customer relationship (order updates, delivery). Exempt from DND.
Service ExplicitService alerts requiring explicit consent (cross-sell, loyalty).
PromotionalMarketing content. Filtered against TRAI NCPR; time-window 09:00–21:00 IST.

TRAI DLT compliance chain in five steps

  1. 01

    Principal Entity onboarding on DLT

    The brand registers on any one DLT platform (Vodafone-Idea, Jio, Airtel or Tanla). The record replicates across the consortium ledger, so the four TSPs all read the same chain.

  2. 02

    Six-character Header ID reservation

    Header per category (T / SI / SE / P). Bank-grade prefixes (VK-, AD-, AX-, JD-, JK-, JM-) auto-assigned. Activation typically 24-72 hours; regulated sectors (BFSI, healthcare, government) take longer.

  3. 03

    Content Template registration

    Each message body registered under one of the four categories. Variable placeholders ({#var#}), up to 30 variables per template; the Template is locked to a specific Header.

  4. 04

    Telemarketer chain binding

    Principal Entity binds 4notify as registered Telemarketer (TM); the PE → TM → TSP chain is locked on-ledger.

  5. 05

    Scrub-chain + NCPR filter at the API edge

    Before despatch the API edge verifies the on-ledger Header + Template + Variable count. Promotional traffic is filtered against the TRAI NCPR (DND); mismatches are rejected before reaching the TSP.

Frequently asked questions

Do I need an Indian company to send SMS into India?

Principal Entity registration on DLT requires Indian KYC documentation (GST/CIN, PAN, authorised signatory letter). For overseas brands without an Indian entity, the recommended route is a partner Principal Entity with a transparent service agreement. 4notify supports both modes.

What is the penalty for sending without a registered Header ID?

The TSP blocks the traffic and, on repeat offence, suspends the Header. TRAI may impose financial disincentives on the TM. 4notify ensures every despatch carries a live on-ledger Header + Template before it leaves the API edge.

How long does Header ID and Template activation take?

Header ID typically 24-72 hours after KYC. Content Templates usually activate within 24 hours. Regulated sectors and unusual category combinations may take longer because of additional vetting.

Start free

Full TRAI DLT compliance. Header ID in 24-72 hours. English-language support on weekdays.