SMS sender IDs in India follow a defined format under the Telecom Regulatory Authority of India's (TRAI) commercial communication framework. These sender IDs, also known as SMS headers, help identify the business or organization sending a message.
A typical Indian SMS sender ID includes a telecom access provider prefix, a service area code, a registered header, and, where applicable, a message category suffix. Understanding this structure helps businesses and developers recognize SMS sender IDs and understand how DLT-compliant messaging works in India.
An SMS sender ID is an alphanumeric identifier displayed as the sender of an SMS on a recipient's mobile phone. Under TRAI's Telecom Commercial Communications Customer Preference Regulations (TCCCPR), 2018, these identifiers are known as headers.
A registered header identifies the Principal Entity (PE), such as a business, bank, institution, or government organization, sending commercial communications.
For example, a sender ID may appear in a format such as JD-IPAYTM-T, where the components identify the originating access provider and service area, the registered entity header, and the applicable message category.
The traditional Indian SMS header structure is represented as:
XY-ABCDEF
The components are:
• X: Code identifying the originating telecom service provider or access provider.
• Y: Code identifying the provider's Licensed Service Area (LSA).
• ABCDEF: The alphanumeric header assigned to the Principal Entity.
Under the current framework, a message category suffix may also be displayed where applicable.
For example, a sender ID may appear as JD-IPAYTM-T.
| Component | Example | Meaning |
|---|---|---|
| First character (X) | J |
Reliance Jio Infocomm Ltd. |
| Second character (Y) | D |
Delhi service area |
| Registered header (ABCDEF) | IPAYTM |
Header assigned to the Principal Entity |
| Category suffix | T |
Transactional message category, where applicable |
The first character identifies the originating access provider. The following table reproduces the provider codes listed in TRAI's published header-prefix reference.
| Telecom Service Provider | Code |
|---|---|
| Aircel Ltd. / Dishnet Wireless Ltd. | D |
| Bharti Airtel Ltd. / Bharti Hexacom Ltd. | A |
| Bharat Sanchar Nigam Ltd. (BSNL) | B |
| Quadrant Televentures Ltd. | Q |
| Mahanagar Telephone Nigam Ltd. (MTNL) | M |
| Reliance Communications Ltd. | R |
| Reliance Jio Infocomm Ltd. | J |
| Reliance Telecom Ltd. | E |
| Tata Teleservices Ltd. | T |
| Vodafone Idea Ltd. (Vi) | V |
| V-CON Mobile & Infra Pvt. Ltd. | C |
The second character identifies the originating access provider's Licensed Service Area. These codes are also referred to as telecom circle or region codes.
| Service Area | Code |
|---|---|
| Andhra Pradesh | A |
| Assam | S |
| Bihar | B |
| Delhi | D |
| Gujarat | G |
| Haryana | H |
| Himachal Pradesh | I |
| Jammu & Kashmir | J |
| Karnataka | X |
| Kerala | L |
| Kolkata | K |
| Madhya Pradesh | Y |
| Maharashtra | Z |
| Mumbai | M |
| North East | N |
| Odisha (Orissa) | O |
| Punjab | P |
| Rajasthan | R |
| Tamil Nadu, including Chennai | T |
| Uttar Pradesh East | E |
| Uttar Pradesh West | W |
| West Bengal | V |
Message category suffixes help distinguish the purpose or category of a commercial message. Under the relevant header-identification implementation, these suffixes may appear at the end of the displayed sender ID.
For example, a header may be displayed with -P, -S, -T, or -G, depending on the category assigned under the applicable rules and telecom provider implementation.
| Suffix | Category | General Purpose |
|---|---|---|
P |
Promotional | Marketing and promotional communications |
S |
Service | Applicable service messages and customer notifications |
T |
Transactional | Applicable transactional communications, including supported OTP use cases |
G |
Government | Applicable government communications |
The traditional format is XY-ABCDEF. The first character identifies the originating telecom access provider, the second identifies its Licensed Service Area, and the remaining characters represent the registered entity header. A category suffix may also be displayed where applicable.
The first letter identifies the originating access provider. For example, A is associated with Bharti Airtel and J with Reliance Jio Infocomm in the published prefix reference.
The second letter identifies the originating access provider's Licensed Service Area. For example, D represents Delhi and M represents Mumbai in the published code list.
These suffixes are used to identify message categories: P for promotional, S for service, T for transactional, and G for government communications, subject to the applicable header-identification requirements.
Check the complete displayed sender ID against the latest header information published by TRAI and the relevant telecom access provider. Do not rely solely on the sender ID to determine whether a message is genuine.
Send OTPs, alerts, notifications, and other transactional SMS using Textplate's built-in, ready-to-use TRAI-compliant DLT templates. With a simple web dashboard and REST API, you can integrate SMS into your business workflows without managing your own DLT registration or template submissions for supported messaging use cases. Get started with 7 days of free access and 20 SMS credits.
Contact: 303 R.P. Business Park, Hyderabad, IN - 500008 • Email: support@textplate.in