Is your OTP SMS transactional or service? The 2026 answer

· BharatCaller team

You're registering an OTP template on a DLT portal and the form asks for a category. Transactional sounds right. Service sounds right too. For years the honest answer was "it depends on who you are". TRAI's Third Amendment of 18 September 2026 makes it depend on what the OTP is for.

The short answer

  • Login, sign-up, password reset and two-factor OTPs are service messages. TRAI's amended definition, in force from about 18 October 2026, lists "OTPs for authentication, such as app login, password reset, two-factor authentication" among service messages. They don't need explicit consent.
  • An OTP that completes a transaction the customer has just started is transactional. A transactional message is one sent in response to a customer-initiated transaction, within 30 minutes of it. The definition's examples include OTPs from banks and from non-bank businesses such as e-commerce.

Operators add -S to the sender name of service messages and -T to transactional ones, so your customers see the difference on every message.

How the definitions moved

2018: broad law, narrow practice

The 2018 regulations defined a transactional message as one triggered by a transaction the customer performed, sent within 30 minutes, and gave "delivery of OTP" as an example. Operators' DLT codes of practice were narrower. Route Mobile's 2021 guide and Vi's DLT FAQ both describe the Transactional category in terms of banks, and Vi's FAQ lists an OTP for an e-commerce site or app login under Service Implicit. So most businesses registered their OTPs as Service Implicit.

2025: transactional widened

The Second Amendment of 12 February 2025, in force from about mid-March 2025, rewrote the transactional definition to cover "OTP from banks, non-bank-entities like e-commerce, apps login etc.".

2026: login OTPs moved to service

The Third Amendment deleted "apps login" from the transactional definition and added authentication OTPs to the service definition. TRAI's explanatory memorandum says login OTPs had been "inadvertently mentioned" under transactional, because authentication OTPs are about using a service, not only about transactions.

Which category for which OTP

  • Login, sign-up, device verification, password reset and 2FA: service. On portals that still split service types, that means Service Implicit, where these OTPs have long been registered.
  • A bank or card payment OTP: transactional.
  • A payment or order OTP from a business that isn't a bank: the 2025 and 2026 definitions treat it as transactional if it answers a transaction the customer started, within 30 minutes. Whether your portal lets a non-bank choose Transactional is a separate question. SMS providers disagree about current portal practice, and Vi's FAQ still describes the category in bank terms. Check your portal. If it doesn't offer Transactional to you, service is where such OTPs have been registered for years.
  • An OTP with an offer attached: promotional. Since the 2025 amendment, a message that mixes promotional content with transactional or service content counts as promotional.

One more wrinkle, in both the 2025 and 2026 texts: a transactional message that also carries service information is treated as a service message. Keep payment OTPs to the code, the amount and the merchant.

Does the category change delivery?

Less than many people fear. Transactional and service messages aren't unsolicited commercial communication under the rules, so DND preferences don't stop them. Under the 2026 text, BLOCK PROMO and the time-band and day blocks never block transactional or service messages. The old FULLY BLOCK option is gone too: existing FULLY BLOCK settings were to move to BLOCK PROMO within 15 days of commencement. An OTP at 2 AM is fine. Only promotional messages are limited to a default window, which we cover in promotional SMS timing.

The category matters most when it's wrong. Since TRAI's Direction of 20 August 2024, a template that draws a complaint for being in the wrong category is blacklisted, and five blacklisted templates suspend the sender for a month or until all its templates are re-verified. From about 17 December 2026, the regulation counts five within 90 days, across all operators. TRAI's memorandum says most wrong-category cases are promotional messages registered as service. The safe rule: keep anything that sells out of an OTP template.

What an OTP template still has to pass

Choosing the right category is one check among several. An OTP is rejected if any of these fail:

  • Registered header and template, linked to each other, one header per template.
  • Exact template match. Only the variable parts may change.
  • A tagged variable. Since TRAI's Direction of 18 November 2025, each variable must be pre-tagged. A numeric code goes in #numeric#, which accepts digits only. See DLT variable pre-tagging.
  • Brand name in the text, which Vi has required in templates registered since 11 October 2020.
  • Whitelisted links and callback numbers, if the OTP message contains any.
  • A declared telemarketer chain. Messages sent through an undeclared path have been rejected since 11 December 2024. TRAI made sure the switch didn't disrupt OTPs by letting undeclared traffic through with error codes during the transition.

A simple service OTP template looks like this: "Your BRAND login code is {#numeric#}. It expires in 10 minutes. Do not share it with anyone. - BRAND". Your portal's exact tag syntax may differ, so follow its examples. If messages still fail, work through why your SMS failed DLT scrubbing.

Voice OTPs

If you also read OTPs out by automated call, the 2026 rules reach you too. From about 17 November 2026, every sender must declare automated (A2P) calls and the number ranges it uses to its operator in advance, and undeclared A2P calls count as unsolicited commercial communication. Separately, TRAI's directions of November and December 2025 require banks, insurers and many other regulated financial firms to make service and transaction calls from the 1600 series. More in voice OTP after the 2026 A2P call rules.

Quick answers

Is a login OTP transactional or service?

Service, under the definitions in force from about 18 October 2026.

Is a payment OTP transactional?

Yes, if it responds to a transaction the customer started, within 30 minutes. Whether a non-bank can pick Transactional on its portal varies, so check.

Do I need to re-register my existing OTP templates?

We found no TRAI instruction to re-categorise existing OTP templates. A login OTP registered as Service Implicit already matches the 2026 definition. If you have login OTPs registered as Transactional, ask your portal or SMS provider whether to move them.

Do OTPs reach numbers on DND?

Yes. DND preferences don't block transactional or service messages.

Last checked: 6 November 2026. Sources: TRAI's TCCCPR 2018, Second Amendment 2025 and Third Amendment 2026 with its explanatory memorandum; TRAI Directions of 20 August 2024, 18 November 2025, 19 November 2025 and 16 December 2025; TRAI press release No. 92 of 2024; Vi DLT FAQ; Route Mobile DLT guide (2021). Third Amendment dates are counted from the notification date, so they are approximate. Portal category options vary; check your DLT portal.