MSG91 is one of the better-known communication platforms in India, covering SMS, OTP, voice, email and WhatsApp, with DLT handling built in for Indian SMS rules. Its WhatsApp pricing pitch is clear: "Meta Price is Your Price." MSG91 says it bills only what Meta charges, with no markup on top, and it contrasts that with providers that add a percentage or a fixed amount per message.
That claim is worth taking seriously, and it shapes what an alternative can and cannot offer. If you want the official WhatsApp Business API, MSG91's pass-through model is hard to beat on per-message cost. A flat-rate alternative is a different kind of product, and the case for it depends on your volume and what you send.
What you actually pay on MSG91
There are two layers.
Meta's charges. MSG91's own help page states them for India from 1 October 2026. The first 1,000 service messages per business number each month are free, and after that each delivered service message is ₹0.115 plus GST. Customer-initiated messages stay free, as do eligible replies inside the 72-hour window from click-to-WhatsApp ads. Utility templates sent inside an open service window are now chargeable. There is no volume discount on any of this. Marketing messages in India cost ₹0.8631 each from 1 January 2026, up from ₹0.7846. A utility or authentication template is ₹0.115, so a marketing message costs about 7.5 times as much.
MSG91's own charge. The help page says "any MSG91 subscription or platform charges are separate," but the pages I could read do not state the amount. A competitor's comparison reports a ₹500 monthly platform fee plus 18 percent GST, with the first two months discounted. That is a rival's figure, so ask MSG91 for the current number in writing, along with any setup fee or minimum recharge.
Where the per-message model starts to cost
Take 10,000 OTP or utility messages a month. At ₹0.115 each that is ₹1,150, plus the reported ₹500 platform fee, so about ₹1,650 before GST. At that size the official route is cheap, and no flat-rate session API is going to make a meaningful difference in rupees.
Now change what you send. Ten thousand marketing messages at ₹0.8631 come to ₹8,631 plus the platform fee, around ₹9,100. And at 100,000 utility messages a month, the Meta charge alone is ₹11,500, so roughly ₹12,000 with the platform fee, somewhere around $135 to $145 depending on the exchange rate. A flat session plan costs $5 to $35 whatever the volume. Our 2026 pricing breakdown has the country-by-country rate card and worked examples if you want to model your own numbers.
The pattern is that India's Meta utility rates are low enough that flat pricing only wins clearly at high volume, or when most of your traffic is marketing, or when your conversations are long and mostly inside the service window, which is now partly metered.
What a flat-rate API trades away
This part matters more than the price. A flat-rate, QR-linked API such as WaHttp is not an official WhatsApp Business API. It connects your number as a linked device, outside Meta's platform. That brings the usual terms-of-service exposure and unpredictable enforcement, and no verified badge, no catalogs and no official template system. Our Cloud API versus session-based comparison goes through what you lose and gain on each side, and how to avoid getting your number banned covers the behaviours that raise risk.
There is also a regulatory point specific to India. MSG91's strength is that its SMS, OTP and WhatsApp traffic runs through registered, compliant channels. If your messages are regulated, financial, or sent to people who have not opted in, the official route protects you in a way a session API does not.
Where MSG91 is the better choice
If you send OTPs and transactional alerts at moderate volume and want them delivered reliably through an official channel, MSG91 is a good fit, and its pass-through pricing keeps the cost near Meta's own. If you already use it for SMS and voice, one vendor and one wallet is a real convenience. If you need the verified badge, click-to-WhatsApp ad flows, or a vendor that carries compliance paperwork for you, a flat-rate session API cannot replace that.
Where flat pricing wins
A flat-rate API suits conversational support on a number your customers already know, internal notifications, agency work across many client numbers, and anything where per-message billing makes the economics awkward. WaHttp is $5 a month for one session with unlimited messages, $12 for three, $22 for six and $35 for ten, with REST endpoints and webhooks on every plan. It is WhatsApp only, so it will not replace MSG91's SMS or voice. Plenty of teams use both: official templates for OTPs and campaigns on MSG91, and everything conversational on a flat plan. If you are comparing other India-focused options, our Interakt alternative post covers the commerce-focused end of the market.
Side by side
| MSG91 WhatsAppWaHttp | ||
| Type | Official Business API | QR-linked session API |
| Message cost | Meta's rate, no markup (per MSG91) | None, flat per session |
| Platform fee | Separate, amount not published on pages I could read | $5–$35 per month, by session count |
| Utility message, India | ₹0.115 | Included |
| Marketing message, India | ₹0.8631 | Included |
| Other channels | SMS, OTP, voice, email | WhatsApp only |
| Verified badge, templates | Yes | No |
| Meta approval required | Yes | No |
Choosing
Choose MSG91 if the messages are transactional or regulated, volume is modest, and an official channel is part of the requirement. Choose a flat-rate API if volume is high, traffic is mostly conversational, or your costs are being driven by marketing-rate messages you do not strictly need to send officially. If you are unsure, a cheap flat-rate session next to your MSG91 account lets you move the conversational traffic and keep the compliance-sensitive traffic where it is. For a wider view of how the options compare, see the full WhatsApp API provider comparison.
Migration notes
Moving conversational traffic is simple. Sends map to a REST call with a recipient and a body or media URL, number pairing is a QR scan, and inbound events arrive as webhooks you remap to your handler. Do not move template-based traffic, such as OTPs and approved campaigns, to a session API without thinking it through, because those depend on Meta's template system and the compliance that comes with it. Keep them on MSG91 or another official provider.