Understanding SMS sender ID codes in India helps quickly identify who sent the message, through which operator/state, and whether it’s promotional, service, transactional, or government. This guide explains how to decode IDs like AA-AIRTEL-S, AD-HDFCBK, VM-ICICIB, and what suffixes like P/S/T/G mean — without external links.
Key Takeaway
Indian SMS sender IDs follow a fixed pattern: the first letter is the operator, the second is the telecom circle (state/region), and the following 6 characters identify the brand/service. Newer formats may include a suffix to show the message category:
- P = Promotional
- S = Service
- T = Transactional (e.g., OTPs)
- G = Government
What Is an SMS Sender ID in India?
For commercial/government SMS, India uses a standardized sender ID format to increase transparency and reduce spam. You’ll usually see formats like:
- AD-HDFCBK
- VM-ICICIB
- JX-AMAZON
- AA-AIRTEL-S
- VZ-PAYTM-T
These aren’t random. Each part conveys specific information.
The Format Explained
Typical formats you’ll encounter:
- XY-ABCDEF
- XY-ABCDEF-Z (with a suffix for category)
Where:
- X = Operator code (A/V/J/B/M/T/R/Q/C/D based on operator)
- Y = Circle/Service Area code (A/D/M/X/Z/T/P/G/H/I/J/K/B/N/O/R/V/W/E/Y etc.)
- ABCDEF = 6-character brand/service identifier (e.g., HDFCBK, AMAZON, PAYTM)
- Z (optional) = Category suffix (P/S/T/G)
Example: AD-HDFCBK-T
- A = Airtel (operator)
- D = Delhi (circle)
- HDFCBK = HDFC Bank (brand)
- T = Transactional (category)
Operator Codes (First Letter)
Common operator codes you’ll see:
- A = Airtel (Bharti Airtel/Bharti Hexacom)
- V = Vodafone Idea (Vi)
- J = Reliance Jio
- B = BSNL
- M = MTNL
- T = Tata Teleservices
- R = Reliance Communications
- Q = Quadrant Televentures
- C = Videocon (legacy)
- D = Aircel/Dishnet (legacy)
Note: Some legacy operators may still appear in older databases or historical messages.
Circle/Service Area Codes (Second Letter)
The second letter indicates the originating telecom circle (state/region). Common mappings:
- A = Andhra Pradesh
- D = Delhi
- M = Mumbai
- X = Karnataka
- Z = Maharashtra
- T = Tamil Nadu
- P = Punjab
- G = Gujarat
- K = Kolkata
- L = Kerala
- H = Haryana
- R = Rajasthan
- B = Bihar
- S = Assam
- N = North East
- O = Odisha
- V = West Bengal
- W = UP West
- E = UP East
- I = Himachal Pradesh
- J = Jammu & Kashmir
- Y = Madhya Pradesh
Tip: Circles are standardized. If you see an unusual operator-circle combo (e.g., a circle that operator doesn’t serve), treat it as a red flag.
The 6-Character Brand/Service ID
The next six characters identify the brand or service:
- HDFCBK = HDFC Bank
- ICICIB = ICICI Bank
- PAYTM = Paytm
- AMAZON = Amazon
- AIRTEL = Airtel
- FLIPKT = Flipkart (common abbreviation where needed)
Legitimate enterprises register these IDs. Misspellings (e.g., “HDFCBK” vs “HDFCBA”) or vague IDs can indicate phishing.
The Category Suffix: P / S / T / G
Many senders now append a suffix to indicate message category:
- P = Promotional (offers, marketing, sales)
- S = Service (alerts, updates to existing customers)
- T = Transactional (OTPs, order confirmations, banking)
- G = Government (official government communications)
Examples:
- VM-ICICIB-T → OTP from ICICI via Vodafone Mumbai (Transactional)
- JX-AMAZON-S → Order/shipping update from Amazon via Jio Karnataka (Service)
- AD-MYNTRA-P → Discount campaign from Myntra via Airtel Delhi (Promotional)
- BP-UIDAIG-G → Aadhaar-related message via BSNL Punjab (Government)
Decoding Examples (Step-by-Step)
- AD-HDFCBK-T
- A = Airtel (operator)
- D = Delhi (circle)
- HDFCBK = HDFC Bank (brand)
- T = Transactional (OTP or secure transaction)
- JX-AMAZON-S
- J = Jio
- X = Karnataka
- AMAZON = Amazon
- S = Service (order status, delivery updates)
- VM-ICICIB
- V = Vodafone Idea
- M = Mumbai
- ICICIB = ICICI Bank
- No suffix in older format; context/content indicates type
- AA-AIRTEL-S
- A = Airtel
- A = Andhra Pradesh
- AIRTEL = Airtel brand
- S = Service (account alerts, plan updates)
- VZ-PAYTM-T
- V = Vodafone Idea
- Z = Maharashtra
- PAYTM = Paytm
- T = Transactional (OTP, payment confirmation)
How to Verify Legitimacy
- Check operator and circle: Do they make sense for the sender?
- Check brand ID: Is it a known, correctly spelled 6-character code?
- Check suffix vs content:
- OTP should be T (Transactional)
- Ads should be P (Promotional)
- Order updates likely S (Service)
- Government messages should be G (Government)
- Consistency: Banks and large brands use consistent IDs over time.
- Content quality: Phishing often includes urgent threats, unusual links, or asks for PIN/OTP.
If anything feels off, don’t click links or share information. Verify via official app/website/helpline.
Common Red Flags
- Wrong category: A promo marked as T (Transactional)
- Odd brand spellings: HDFCBNK, ICIC1B, PAYTMM
- Mismatched circle: Rare circles for a nationwide sender without pattern
- Unregistered or generic IDs: “NOTICE”, “INFOCN”, “ALERTS” without brand traceability
- Unexpected OTPs: OTPs without initiating an action
Why These Codes Exist
- Transparency: Lets recipients identify source and intent at a glance
- Compliance: Standardized across operators/circles
- Spam control: Easier to filter and report violators
- Trust: Banks and brands build recognizable, consistent sender IDs
Quick Reference: Decode Any Sender in 10 Seconds
- First letter = Operator (A/V/J/B/M/T etc.)
- Second letter = Circle (A/D/M/X/Z/T/P/G etc.)
- Next 6 characters = Brand (e.g., HDFCBK/AMAZON/PAYTM)
- Optional last letter = Category (P/S/T/G)
- Cross-check content vs category; verify brand spelling
FAQs
Is every message required to have a suffix?
- Not always, especially in older/legacy formats. Newer implementations increasingly include P/S/T/G for clarity.
Can two brands share similar IDs?
- Registered IDs are unique per principal entity. Look closely at spelling and messaging history.
Why do I sometimes see different operators for the same brand?
- Brands may use multiple DLT routes/operators for redundancy and delivery optimization.
Are personal messages (from friends/family) covered by this?
- No. These codes apply to enterprise/commercial/government messages, not person-to-person messaging.
Final Tips for Users and Businesses
For users:
- Save known, legit IDs (e.g., your bank) to recognize them instantly
- Treat unknown IDs with caution; verify via official channels
- Never share OTPs or sensitive data over SMS
For businesses:
- Use correct category (P/S/T/G) to maintain deliverability and trust
- Keep brand ID consistent across campaigns
- Ensure content aligns with registered purpose and regional regulations
Understanding these sender IDs turns a cryptic code into a clear identity and intent signal, protecting against fraud and making mobile communication more trustworthy.