What is PE-TM chain binding?
PE-TM chain binding is India's rule that every commercial SMS must travel along a chain of companies declared in advance. The chain starts with the principal entity (PE) — the business registered on DLT as the sender — and lists each telemarketer (TM) that handles the message on the way to the operator: the platform the business submits to, any aggregator that platform passes traffic to, and the telemarketer that finally delivers to the operator. The PE and its telemarketers bind this chain on the DLT platform, and the operator compares each message's actual path with it.
TRAI introduced it to make spam and fraud traceable. Its direction of 20 August 2024 told access providers to make messages traceable from PE to recipient and to reject traffic whose telemarketer chain was undefined or did not match, from 1 November 2024. A direction of 28 October 2024 moved enforcement to 1 December; on 30 November 2024 TRAI extended the declaration deadline from 30 November to 10 December, with rejection from 11 December 2024. Since then, a message whose chain is not declared or does not match the declared one is dropped before delivery.
Chain binding governs the delivery path, not the message. The header, the content template, consent and DND preferences are separate checks in DLT scrubbing, so a perfectly registered template still fails if it arrives through an aggregator the PE never declared. That makes it the regulator's answer to grey routes and unknown resellers: if a provider quietly hands traffic to a cheaper partner, the extra hop is visible and the message is rejected.
Key takeaways
- PE-TM chain binding means a principal entity declares on DLT every telemarketer its commercial SMS passes through, in order.
- Operators reject any message whose path of telemarketers is undeclared or does not match the declared chain.
- TRAI's 20 August 2024 direction required traceability; after two extensions, rejection of non-matching traffic began on 11 December 2024.
- It controls the delivery path, not the content: headers, templates, consent and DND are separate checks in DLT scrubbing.
- Every change of SMS provider, or of a provider's upstream aggregator, needs the chain updated on DLT before traffic moves.
Trace an SMS along its declared chain
- Principal entity to DLT platform: declare chain
- DLT platform to Operator: chain for checks
- Principal entity to Telemarketer 1: SMS + PE ID
- Telemarketer 1 to Telemarketer 2: declared hop
- Telemarketer 2 to Operator: delivers
- Operator to Recipient: path matches
- Telemarketer 1 to Undeclared TM: undeclared hop
- Undeclared TM to Rejected: operator rejects
Hop 8 of 8
Undeclared TMRejectedoperator rejects
Arrives at Rejected — Chain mismatch.
Hop 8 of 8: Undeclared TM to Rejected — operator rejects.
Key facts at a glance
PE-TM chain binding: key facts and limits
- Declared by
- The principal entity, with each telemarketer accepting its hop
- Checked by
- Access providers (operators) during DLT scrubbing
- TRAI direction
- 20 August 2024: traceability from PE to recipient
- Declaration deadline
- 30 November 2024, extended to 10 December 2024
- Enforcement
- Undeclared or mismatched chains rejected from 11 December 2024
- What it checks
- The path of telemarketers, not the content
- Applies to
- Commercial SMS in India, not WhatsApp
How does PE-TM chain binding work?
Map the full path
Ask your SMS provider which telemarketers carry your traffic to each operator, including any aggregator behind them, with their DLT telemarketer IDs.
Declare the chain on DLT
On the DLT portal where your entity is registered, start the chain with your telemarketer, who accepts it and adds any onward hops. Chains move through states such as requested and pending approval.
Approve the final chain
When every telemarketer in it has accepted, the principal entity approves the complete chain and it is marked registered for scrubbing.
Send with your identifiers
Each message carries the header, your PE ID and the content template ID, and the operator checks the telemarketer path against the bound chain.
Keep it current
Bind a new chain before switching providers or adding a backup route, test at low volume, then move traffic; remove chains you no longer use.
Why does PE-TM chain binding matter?
For a business, a broken chain means OTPs and alerts silently fail even though the header and template are fine. For a compliance team, the chain is the record of who is allowed to carry the company's name. Keeping it accurate — especially when changing providers, or when a provider changes its own upstream partners — now matters as much to SMS deliverability as template registration.
PE-TM chain binding in code
POST /v1/sms HTTP/1.1Host: api.sms-provider.exampleAuthorization: Bearer {API_KEY}Content-Type: application/json{"to": "919812345678","header": "EXMPLE","dlt_entity_id": "{PE_ID}","dlt_template_id": "{CONTENT_TEMPLATE_ID}","text": "482913 is your login OTP. It expires in 5 minutes. Do not share it. - Example Finance"}
Field names vary by provider; over SMPP the same identifiers travel as operator-defined optional TLVs. The chain is not in the request: the operator knows which telemarketer handed it the message and checks that path against DLT.
Example: One operator goes quiet
A Mumbai NBFC sends EMI reminders and OTPs through a messaging provider that hands traffic for one operator to an aggregator. In early December 2024 the NBFC's declared chain listed only the provider. From 11 December, messages to that operator's subscribers began failing while the rest were delivered. The provider shared its full path; the NBFC declared provider and aggregator in sequence on its DLT portal, both accepted, the NBFC approved the final chain and delivery to that operator recovered. Its vendor contracts now require chain details and advance notice of any upstream change.
Common wrong turns
Common mistakes with PE-TM chain binding
Declaring only your direct provider
If your provider passes traffic to an aggregator, the chain must include that hop too. Ask for the complete path for every operator.
Switching providers before binding
Traffic sent through a new telemarketer before its chain is approved is rejected. Bind first, test at low volume, then move traffic.
Confusing chain errors with template errors
A rejection with a correct header and template often means a chain problem. Read the provider's error code and check the chain's status on DLT before rewriting templates.
Leaving stale chains in place
Old chains with former vendors let traffic in your name travel paths you no longer control. Remove them when contracts end.
PE-TM Chain Binding FAQs
What is PE-TM chain binding in DLT?+
When did PE-TM chain binding become mandatory?+
Who does PE-TM chain binding, the business or the SMS provider?+
Does PE-TM chain binding apply to WhatsApp messages?+
Good practice
Best practices for PE-TM chain binding
- Keep a register of every chain, the telemarketer IDs in it and the contract behind each.
- Require vendors to tell you before they change upstream aggregators.
- Watch rejection rates per operator: a chain gap often shows up on one network first.
- Bind a backup provider's chain in advance so failover is compliant on day one.