In short: A WhatsApp OTP in India costs Meta's ₹0.115 authentication rate per delivered message plus your provider's fee, which comes to about ₹0.215 on RichAutomate Client Pay. An SMS OTP costs roughly ₹0.11 to ₹0.25 depending on the provider and how much you recharge (checked 30 October 2026). SMS can therefore be cheaper per message at high volume, but WhatsApp OTP needs no DLT registration, is charged only when delivered and supports one-tap autofill, so the cheapest reliable setup for most apps is WhatsApp first with SMS as the fallback.
WhatsApp OTP vs SMS OTP in India, 2026: a WhatsApp OTP costs ₹0.115 (Meta's authentication rate) plus your provider's fee, about ₹0.215 per OTP on RichAutomate Client Pay, while an SMS OTP costs about ₹0.11 to ₹0.25 (MSG91 lists OTP SMS at ₹0.18 to ₹0.25; Fast2SMS goes from ₹0.25 down to ₹0.11 as the recharge grows). WhatsApp OTP needs no DLT registration, is billed only when delivered and offers one-tap autofill on Android, while SMS reaches every phone, so the cheapest dependable flow is WhatsApp first with automatic SMS fallback. On RichAutomate there is ₹0 setup and no required monthly plan; Authentication messages cost ₹0.50 each on SaaS Pay, or ₹0.10 per message plus Meta's own fee on Client Pay. Meta bills per delivered template message, so a well-designed OTP flow only pays Meta for codes people actually receive.
Disclosure: this guide is published by RichAutomate, a WhatsApp Business API platform. We do not sell SMS. SMS prices quoted here were checked on each provider's public pricing page on 30 October 2026; Meta rates are Meta's India rates for authentication and utility messages.
Key facts at a glance (checked October 2026 against the named primary source):
| Fact | Figure | Source |
|---|---|---|
| Authentication (OTP) button types | Copy code, one-tap autofill, zero-tap | Meta developer docs: Authentication templates |
| OTP code expiry setting | 1 to 90 minutes | Meta developer docs: Authentication templates |
| When a template message is charged | Only when it is delivered | Meta developer docs: Pricing |
| SMS sender header in India | Registered alphanumeric header of max 11 characters, plus registered content templates | TRAI: Advice to Senders (TCCCPR 2018) |
WhatsApp OTP vs SMS OTP — the short answer
For signup, login, password reset and transaction verification, WhatsApp OTP beats SMS on cost, delivery visibility and user experience, provided the user has WhatsApp installed. SMS remains the safety net for the small share of users who do not. The practical 2026 pattern used by most Indian fintech, D2C and SaaS teams is WhatsApp OTP first, SMS as automatic fallback — you get WhatsApp's lower cost and one-tap autofill for the majority, and guaranteed reach for everyone else.
For current per-SMS rates and DLT fees, read our SMS API pricing India 2026 guide.
WhatsApp OTP vs SMS OTP compared (India, October 2026)
| Attribute | WhatsApp OTP | SMS OTP |
|---|---|---|
| Template / channel type | Authentication-category template on the WhatsApp Business API | Transactional SMS over a DLT-registered sender ID |
| DLT / TRAI registration | Not required — WhatsApp is not on the DLT registry | Mandatory — sender ID + template registered on DLT |
| Typical India cost (checked 30 Oct 2026) | Meta ₹0.115 + provider fee: ≈₹0.215 on RichAutomate Client Pay, ₹0.50 on SaaS Pay | ≈₹0.11–₹0.25 per SMS (MSG91 OTP ₹0.18–₹0.25; Fast2SMS ₹0.25→₹0.11 by recharge size) plus DLT setup effort |
| Delivery confirmation | Sent / delivered / read receipts back to your system | Carrier "submitted" only — no read confirmation |
| Autofill | One-tap autofill / copy-code button on Android | SMS Retriever autofill on Android; manual on iOS |
| Reach | Only numbers with WhatsApp installed and a data connection | Universal — any mobile number |
| Branding | Business display name + profile photo in chat | Registered DLT sender header only |
| Format limits | Fixed: code + optional copy-code / autofill button, no extra copy | Free text within 160 chars (DLT-approved) |
| Best used as | Primary OTP channel | Fallback for non-WhatsApp users |
Why WhatsApp OTP often costs less per verified user in India
Per message, a large SMS recharge can undercut WhatsApp: at ₹0.11 an SMS is cheaper than the ≈₹0.215 a WhatsApp OTP costs on Client Pay. But the real bill includes DLT registration, template-scrubbing rejections, operator surcharges, and a chunk of undelivered messages you still partly pay for. WhatsApp Authentication templates use Meta's India-specific OTP rate, and because Meta now bills per delivered template message, you are not paying for codes that never land. Add the higher completion rate from one-tap autofill (fewer resend requests) and the effective cost-per-successful-verification often drops below SMS. Model your own numbers with the conversation window cost calculator.
Authentication templates are strictly code-plus-button. A WhatsApp OTP template can carry only the verification code and an optional copy-code or one-tap autofill button — no branding lines, no links, no marketing copy. Padding the body gets the template rejected at review. This is the single most common reason an OTP template bounces, so build it lean and keep every promotional instinct out of it.
How one-tap autofill works (and why completion rates jump)
On Android, a WhatsApp Authentication template can include a one-tap autofill button. When the user taps it, WhatsApp hands the code straight to your app — no reading, no typing, no clipboard. It relies on your app's package name and signing-key hash being registered with the template, so the OS trusts the handoff. The result is fewer mistyped codes, fewer "resend OTP" taps, and a measurably higher first-attempt verification rate. On iOS the user taps a copy-code button instead, which is still faster than reading an SMS and switching apps.
Worked cost: 2 lakh OTPs a month, WhatsApp vs SMS vs both
Here is the arithmetic for an app sending 2,00,000 login OTPs a month, using only published rates (before GST). The fallback row assumes, for illustration, that 20% of users are not reachable on WhatsApp and get an SMS instead, and that the ₹0.10 RichAutomate fee applies to every WhatsApp send attempt while Meta charges only delivered messages.
Get the India 2026 WhatsApp BSP price comparison
Wati vs AiSensy vs Interakt vs RichAutomate: Meta rates, platform fees and hidden costs, side by side. We send it to your WhatsApp in a minute.
| Setup | How it is priced | Monthly cost for 2,00,000 OTPs |
|---|---|---|
| SMS only, MSG91 OTP route | ₹0.18–₹0.25 per SMS | ₹36,000–₹50,000 |
| SMS only, Fast2SMS | ₹0.11–₹0.25 per SMS, depending on recharge size | ₹22,000–₹50,000 |
| WhatsApp only, RichAutomate Client Pay | Meta ₹0.115 + ₹0.10 per message | ₹43,000 |
| WhatsApp only, RichAutomate SaaS Pay | ₹0.50 all-in per authentication message | ₹1,00,000 |
| WhatsApp first + SMS fallback (20%) | 2,00,000 × ₹0.10 + 1,60,000 × ₹0.115 + 40,000 SMS × ₹0.18–₹0.25 | ₹45,600–₹48,400 |
The honest reading: on price per message alone, a big SMS recharge is the cheapest line in the table. WhatsApp-first earns its place on the things the table cannot show: no DLT template work for the WhatsApp leg, delivery and read receipts, one-tap autofill that reduces "resend OTP" taps (each resend is another paid message on either channel), and a verified business name in the chat. If your users are mostly smartphone users and resends are a real cost for you, the blended flow usually ends up close to SMS-only on spend. If your audience is heavy on feature phones, SMS-first is the rational choice. For the platform side of the bill, compare providers in our WhatsApp API pricing comparison for India and the cheapest WhatsApp Business API in India guide, or see RichAutomate's own rates on the pricing page.
When SMS OTP still wins
- Universal reach. SMS lands on any mobile number, WhatsApp or not. For a login flow that must work for 100% of users, SMS is the guaranteed fallback.
- First-touch signups with no WhatsApp opt-in path. If you cannot yet route the user through WhatsApp, SMS gets them verified immediately.
- Feature-phone and low-connectivity users. SMS works without a data connection; WhatsApp needs internet.
- Regulated flows that mandate SMS. A few BFSI processes still specify SMS-delivered OTPs — check your compliance requirement before switching.
None of these argue against WhatsApp OTP — they argue for WhatsApp-first with SMS fallback, which is exactly how the strongest 2026 flows are built.
How to set up WhatsApp OTP on the API — step by step
- Get on the WhatsApp Business API. Connect a number and complete Meta Business verification — the full path is in our guide to getting the WhatsApp Business API. No DLT registration is needed for WhatsApp.
- Create an Authentication-category template. Use the fixed OTP format: the code variable plus an optional copy-code or one-tap autofill button. No branding, links, or extra sentences.
- Register your app for autofill (Android). Add your package name and signing-key hash so WhatsApp can hand the code to your app on one tap.
- Wire the fallback. If the WhatsApp send fails or the number has no WhatsApp, auto-trigger your SMS OTP through your SMS provider so no user is stranded. On RichAutomate you send the template through the developer API and read its delivery status back (see the API docs); the SMS leg stays with your SMS provider.
- Read the delivery webhook. Use the sent/delivered/read status back from WhatsApp to decide when to fall back and to stop paying for undelivered retries.
Common WhatsApp OTP mistakes Indian teams make
- Padding the OTP template with branding or links. Authentication templates must be code-plus-button. Extra copy triggers rejection.
- Using a Marketing or Utility template for OTPs. Only the Authentication category gets the OTP format and India OTP rate — see the template categories guide to pick correctly.
- Skipping the SMS fallback. Without it, users who have no WhatsApp cannot log in at all.
- Ignoring one-tap autofill setup. Skipping the package-name/key-hash registration means users type codes manually and completion rates stay low.
- Assuming DLT applies. It does not — WhatsApp is not on the DLT registry, so you do not need DLT registration for the WhatsApp API.
Authority References
- Meta WhatsApp Business Platform — Authentication templates & OTP: official format rules for authentication templates and one-tap autofill. developers.facebook.com — Authentication Templates
- Meta — WhatsApp Business Pricing (per-message): category-based per-message pricing and India authentication rate. developers.facebook.com — Pricing
- TRAI — Commercial Communication / DLT framework: the SMS registration regime WhatsApp is exempt from. trai.gov.in
- DPDP Act 2023 (MeitY): consent and purpose-limitation rules governing user data in India. meity.gov.in — Data Protection Framework
Ship WhatsApp OTP with SMS fallback on RichAutomate.
Build an Authentication-category OTP template with one-tap autofill, read live delivery status, and hand failed sends to your own SMS provider as the fallback (RichAutomate does not sell SMS). ₹0 setup and no required monthly plan; optional plans start at ₹499/month. Authentication messages cost ₹0.50 each on SaaS Pay, or ₹0.10/message plus Meta direct on Client Pay. Start free with a 14-day trial and 100 message credits. WhatsApp +91 81603 11319 or book a 30-minute walkthrough.
New to WhatsApp automation? Start with our step-by-step guide to getting the WhatsApp Business API for the full picture, then come back to apply it here.
Working out the cheapest setup for login codes? See our breakdown of the cheapest OTP API in India with WhatsApp and SMS fallback, with costs at 10,000 to 10 lakh OTPs a month.
Comparing providers before you commit? Read our Gupshup alternative and Wati alternative breakdowns, or see the cheapest WhatsApp Business API in India with real per-message numbers.
Pitched a branded OTP layer? Read Truecaller Business Messaging vs WhatsApp before you sign a quote.
Related reading
- WhatsApp template categories — why OTPs must use the Authentication category and how that sets the rate
- WhatsApp vs SMS for business messaging — the broader channel comparison beyond OTP
- DLT registration and the WhatsApp API — why WhatsApp OTP skips the telecom registry SMS needs