A WhatsApp OTP (authentication-template) message in India costs ₹0.115, Meta's per-message authentication rate, plus your provider's fee: on RichAutomate that is ₹0.10 per message on Client Pay (about ₹0.215 per OTP, Meta billed to you directly) or ₹0.50 all-in on SaaS Pay. So 40,000 OTPs a month cost about ₹8,600 on Client Pay (₹4,600 to Meta plus ₹4,000 to RichAutomate), against roughly ₹4,400 to ₹10,000 for the same volume over DLT SMS at ₹0.11 to ₹0.25 per message (checked 30 October 2026). Setup is ₹0 and no monthly plan is required.
Disclosure: this guide is published by RichAutomate, a WhatsApp Business API platform; the RichAutomate prices below are our own. We do not sell SMS. Third-party prices were checked on each provider's public pricing page on 30 October 2026.
WhatsApp OTP has quietly become the default second factor for Indian fintechs, D2C brands, logistics apps and neobanks — delivery comes with sent, delivered and read receipts, codes can autofill in one tap, and users already live inside WhatsApp. But the pricing is layered, and most "cost calculators" online quote outdated 2023 conversation-based numbers. This guide breaks down exactly what an authentication-category message costs in India in 2026, with worked math in rupees, and shows where you actually save money.
How WhatsApp authentication pricing works in India (2026)
Since Meta moved to per-message pricing for authentication and utility categories, every OTP you send is billed individually rather than as part of a 24-hour "conversation." That change matters for OTP-heavy senders: an authentication template is a single-shot message, so per-message billing is usually cheaper and far easier to forecast than the old conversation model.
Your total cost per OTP is the sum of two things:
- Meta's per-message authentication rate for India — currently ₹0.115 per delivered message (the same as the utility rate; marketing is ₹0.8631), set by Meta and revised periodically. Always check the current Meta rate card before you model a budget; Meta has adjusted category rates more than once and India-specific authentication pricing is a lever they tune.
- Your BSP / platform markup — what your WhatsApp Business Solution Provider adds on top. This is where costs balloon or stay lean, because many providers charge a per-message markup and a fixed monthly platform fee on top of Meta's rate.
The Meta component is largely non-negotiable — everyone pays Meta. The BSP component is where you win or lose. If you want the full backdrop on how the platform layer is priced, our breakdown of how much the WhatsApp Business API costs in India in 2026 maps every fee line most vendors bury in their contracts.
RichAutomate authentication pricing: two clean models
RichAutomate runs a usage-first pricing model — ₹0 setup and no required monthly fee (optional plans start at ₹499/month for teams that want extra features). You can stay pay-as-you-go and pay only when you send. There are two ways to buy:
- Client Pay — you bring your own Meta WhatsApp Business Account and pay Meta directly for conversation/message charges. RichAutomate adds a flat ₹0.10 per message platform markup and nothing else. This is the leanest possible structure for high-volume OTP senders.
- SaaS Pay — RichAutomate bills you all-in, so you get one invoice instead of juggling a Meta billing account. All-in rates are ₹1.50 per marketing message and ₹0.50 per utility or authentication message, Meta's charge included.
On Client Pay the authentication charge itself is Meta's ₹0.115, billed by Meta; on SaaS Pay you pay one ₹0.50 rate that includes it. Neither model has a required monthly fee. Compare that against our full transparent WhatsApp API pricing page and you'll see there is no "minimum monthly commitment" line, which is the single biggest hidden cost in this market.
Worked cost math: what OTP volume actually costs
Abstract per-message rates mean nothing until you plug in real volume. Below is the full monthly cost for four common Indian sender profiles on RichAutomate's Client Pay model: Meta's ₹0.115 per authentication message plus the ₹0.10 platform fee, before GST. The Meta part is identical with every provider; the fee is the part you choose.
| Sender profile | OTPs / month | Meta @ ₹0.115 | Platform fee @ ₹0.10 | Total on Client Pay |
|---|---|---|---|---|
| Early-stage D2C store | 8,000 | ₹920 | ₹800 | ₹1,720 |
| Growth-stage fintech | 40,000 | ₹4,600 | ₹4,000 | ₹8,600 |
| Logistics / delivery app | 1,20,000 | ₹13,800 | ₹12,000 | ₹25,800 |
| Neobank / large marketplace | 5,00,000 | ₹57,500 | ₹50,000 | ₹1,07,500 |
The pattern to check with any provider: the fintech sending 40,000 OTPs pays ₹4,000 in fees on a per-message model, while a provider that also charged, say, a ₹10,000 monthly plan would more than triple the controllable part of the bill before a single extra OTP is sent. Per-message fees are not automatically the lowest, though: Gupshup's self-serve WhatsApp fee is listed at US$0.001 (about ₹0.088) per message plus Meta (checked 30 October 2026), which is below RichAutomate's ₹0.10. Compare the full price, including any plan, in our WhatsApp API pricing comparison for India.
Client Pay vs SaaS Pay: which is cheaper for OTP senders?
For pure OTP traffic the decision usually comes down to how you want to handle Meta billing. Client Pay is the mathematical floor: you settle Meta's authentication charges directly and RichAutomate adds only ₹0.10 per message, so there is no intermediary margin on the Meta portion at all. This suits fintechs and marketplaces that already run a Meta billing account and want the absolute lowest per-OTP number.
SaaS Pay trades a sliver of that saving for a single consolidated invoice and no Meta billing account to manage — RichAutomate handles the Meta relationship and bills you all-in. For OTP traffic the gap is real: SaaS Pay charges ₹0.50 per authentication message, against about ₹0.215 on Client Pay, so 40,000 OTPs cost ₹20,000 a month on SaaS Pay versus about ₹8,600 on Client Pay. SaaS Pay makes sense while volume is low and you want one rupee invoice without a Meta payment method; once OTP volume grows, Client Pay is the cheaper choice, and you can switch without changing platforms.
Send these messages on WhatsApp, from your own number
We get your templates approved on the official WhatsApp API and set up your first broadcast with you. ₹0 platform fee, you pay only Meta's per-message rate.
WhatsApp OTP vs SMS OTP cost in India
The real comparison most teams care about is WhatsApp versus the SMS OTP they're currently paying for. DLT-registered OTP SMS in India runs roughly ₹0.11–₹0.25 per message on public price lists (MSG91 lists OTP SMS at ₹0.18–₹0.25; Fast2SMS goes from ₹0.25 down to ₹0.11 as the recharge grows; checked 30 October 2026), and that's before resends and the DLT template registration work.
| Factor | SMS OTP (India) | WhatsApp OTP (India) |
|---|---|---|
| Per-message cost | ≈₹0.11–₹0.25 (DLT-registered) | ₹0.115 Meta + ₹0.10 fee ≈ ₹0.215 (RichAutomate Client Pay) |
| Delivery / read visibility | Sent only; no read receipt | Delivered + read receipts |
| Retry cost on failure | Charged again per resend | Charged per message; higher first-try success |
| Registration overhead | DLT header + template scrubbing | Template approval inside WhatsApp Manager |
| Fraud / spoofing risk | Exposed to SIM-swap and SMS interception | End-to-end encrypted, business display name shown |
SMS still wins on absolute floor price per message, especially on a large recharge, and it is the only option for feature-phone users. For smartphone-first Indian users WhatsApp OTP narrows the gap once you count resends avoided by one-tap autofill and codes Meta never charges because they were not delivered. We've worked through the numbers at 2 lakh OTPs a month in WhatsApp OTP vs SMS OTP in India for 2026.
The hidden costs nobody quotes you
Sticker per-message rates hide three line items that decide your real annual spend:
- Setup / onboarding fees. Some providers charge a one-time onboarding fee to provision your WABA; check their pricing page before you sign. RichAutomate's is ₹0.
- Monthly platform / seat fees. The killer. A ₹2,500-a-month plan is ₹30,000 a year before you send one OTP. Pay-as-you-go models remove this.
- Minimum commitments and message-credit expiry. Prepaid credit that expires monthly is a hidden fee — you pay for volume you never sent.
Below is how the same 40,000-OTP fintech's annual cost compares across pricing structures, including Meta's ₹0.115 per OTP (₹55,200 a year) so the totals are comparable, before GST:
| Pricing structure | Setup | Monthly platform fee | Fee on 40k OTPs / month | Annual total incl. Meta |
|---|---|---|---|---|
| RichAutomate Client Pay | ₹0 | ₹0 (plans optional) | ₹4,000 | ₹1,03,200 |
| RichAutomate SaaS Pay (₹0.50 all-in) | ₹0 | ₹0 (plans optional) | Included in ₹20,000 | ₹2,40,000 |
| Gupshup self-serve (US$0.001 ≈ ₹0.088 + Meta) | See their pricing page | See their pricing page | ≈₹3,520 | ≈₹97,440 + any plan |
| Subscription-based provider | See their pricing page | Plan price | Plan-dependent | ₹55,200 + 12 × plan + any markup |
Same Meta rate, same 40,000 OTPs, but the annual bill can move by more than ₹1 lakh purely on pricing structure, and the cheapest per-message fee is not always ours. If minimising total cost is the goal, our deep-dive on the cheapest WhatsApp Business API in India with total cost decoded walks through every one of these line items with worked examples.
GST, DLT and going live: the compliance line
Two factual notes for Indian budgeting. First, GST applies to your platform and messaging spend, so add 18% to the controllable figures above when you forecast cash outflow. Second, Meta business verification asks for documents that prove your legal business; in India a GST certificate is the most commonly used, with other registration documents as alternatives. Have them ready from day one so a launch isn't blocked at the verification step. DLT registration is not needed for WhatsApp OTP, only for any SMS fallback you keep.
How to cut your WhatsApp OTP bill
Four levers, in order of impact:
- Kill the monthly platform fee. Move to a pay-as-you-go provider if your plan buys features you do not use. This alone often saves more than any per-message optimisation.
- Use authentication templates, not utility, for OTPs. Categorising correctly keeps you on Meta's authentication rate and avoids mis-billing.
- Cut retries with WhatsApp-first delivery. Higher first-attempt success means fewer paid resends than SMS fallback chains.
- Bring your own WABA (Client Pay). If you already have a Meta billing relationship, paying Meta directly plus a ₹0.10 markup is the floor.
For the full authentication setup walkthrough — template creation, approval, and rate configuration — see our guide to WhatsApp OTP and authentication in India for 2026.
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.
The bottom line on WhatsApp OTP cost in India
In 2026 the price of a WhatsApp OTP in India is Meta's ₹0.115 authentication rate (revised periodically, so check the current Meta rate card) plus your provider's fee. The Meta half is the same for everyone; the fee half, plus any monthly plan, is where accounts with identical volume diverge. RichAutomate's model is ₹0 setup, no required monthly fee and ₹0.10 per message on Client Pay (about ₹0.215 per OTP), or ₹0.50 all-in on SaaS Pay. See every line on our pricing page and the cheapest WhatsApp Business API in India guide.
Ready to send OTPs at pass-through cost? Create your free RichAutomate account and start with ₹0 setup, a 14-day trial with 100 message credits, and per-message pricing you can actually forecast.
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.