Defines the four template categories and their distinct routing and consent requirements.
TRAI DLT Content Template ID: transactional, service-implicit, service-explicit and promotional categories on the PE → TM → TSP scrub chain
Beyond the Header ID, every single SMS that runs through the Indian A2P pipe must reference a pre-registered Content Template ID, in one of four categories: transactional (banking, authentication), service-implicit (order updates, service alerts), service-explicit (consent-based service), or promotional. The PE → TM → TSP scrub chain enforces, in real time, that the Header, Template and Variable-Value placeholders match what is on the ledger. 4notify mirrors the DLT registry at the API edge and rejects mismatches before they reach Jio, Airtel, Vi or BSNL.
Whereas, by virtue of the powers vested by the Telegraph Act, 1885 and the Telecom Regulatory Authority of India Act, 1997, and in furtherance of the TCCCPR 2018 read with the Code of Practice for Content Templates, this edict is issued upon the registration of Content Template IDs on the Distributed Ledger Technology platform.
Variable placeholders {#var#}, header binding, and scrub-chain enforcement at the TSP.
Header-Template lock-in and mandatory consent gateway for promotional traffic.
Content Template registration
Each message body is registered on the DLT platform under one of the four categories. Variable placeholders use the {#var#} convention; up to 30 variables per template.
Header-Template lock-in
Every Template ID is locked to a specific Header ID. 4notify enforces this binding at the API edge — sending a transactional template with a promotional header is rejected.
Scrub-chain verification (PE → TM → TSP)
Before delivery, the TSP scrubs the request against the on-ledger Header + Template + Variable count. 4notify mirrors the DLT registry every 5 minutes so mismatches are caught at the API edge, not at the TSP.
DND filter for promotional
Promotional templates are checked against the TRAI National Customer Preference Register (NCPR) at the API edge; subscribers under Full DND or category-DND are filtered before despatch.
json
{
"event": "sms.deliver",
"header_id": "VK-FOURNT",
"template_id": "1207168760000123456",
"category": "transactional",
"variables": ["Rahul", "INR 12,500", "8429"],
"scrub_chain": {
"pe_id": "1102458790000123456",
"tm_id": "1701560000000789012",
"tsp_scrubbed": true,
"ncpr_checked": false
},
"tsp_route": "jio_direct"
}VK-FOURNT: Dear Rahul, INR 12,500 has been credited to your account ending 8429 on 27-May-2026. UPI Ref UPI/12345678901. T&C apply.
- All Content Templates registered on DLT and lock-bound to a Header ID
- Variable placeholders ({#var#}) match the template registration
- Promotional traffic filtered against TRAI NCPR at the API edge
- Scrub-chain mismatches rejected before the TSP
4notify is the only A2P provider that mirrors the TRAI DLT Content Template registry at the API edge, enforces Header-Template lock-in before despatch, and applies the NCPR filter pre-TSP across all four operators (Jio, Airtel, Vi, BSNL).
What happens if a template doesn't match the registered version on the ledger?
The TSP rejects the message and may suspend the Header ID after repeated mismatches. 4notify catches this at the API edge, so the TSP never sees the bad request — preserving the Header's good standing.
Can transactional templates be sent to DND-registered numbers?
Yes — TCCCPR 2018 exempts transactional and service-implicit traffic from DND. Only promotional and service-explicit are filtered against the NCPR.
Start free
14 days, no card. English-language support on weekdays.