WhatsApp's Business Platform has seen several structural changes moving into 2026, and Indian businesses using the API should treat these as action items, not background noise. The most consequential ones are the retirement of the legacy On-Premises API, a shift toward local-currency (INR) billing, tighter enforcement of message template categories, and the introduction of a Calling API. Regulatory scrutiny in Europe over Meta's WhatsApp chatbot policy also signals where platform rules may tighten next.

1. The On-Premises API is being phased out

Meta has been sunsetting the older On-Premises API in favour of the cloud-hosted WhatsApp Cloud API. Businesses and BSPs (Business Solution Providers) still running on-premise deployments need to migrate their number, templates, and integrations to the Cloud API or a partner platform built on it. Businesses that delay risk losing access to support, new features, and eventually the ability to send messages at all, since Meta is not maintaining the legacy infrastructure long-term.

What to do

• Confirm with your BSP or IT team whether your deployment is still on-premises.
• Plan a migration window well ahead of any Meta-imposed cutoff rather than reacting at the last minute.
• Re-test webhook integrations, template approvals, and phone number registration after migration, since the Cloud API's infrastructure and rate limits differ from the on-premise setup.

2. Pricing is moving to local currency billing

WhatsApp Business Platform conversation-based pricing has historically been billed in USD, converted at the time of invoicing. Meta has signalled a move toward billing businesses in local currencies, including INR for the Indian market. For finance teams, this removes a layer of exchange-rate unpredictability in monthly WhatsApp API costs, but it also means budgets, quotes, and margin calculations built around USD rates need to be revisited once the migration takes effect for your account.

What to do

• Check with your BSP whether your account has already moved to INR billing or is still on the older currency model.
• Rework internal cost projections once INR billing applies, since conversation pricing tiers (marketing, utility, authentication, service) remain conversation-based even after the currency change.

3. Template category rules are being enforced more strictly

Meta tightened its message template category guidelines, requiring templates to be correctly classified as marketing, utility, authentication, or service. Businesses that mis-categorise templates — for example, tagging a promotional message as a utility update to reduce cost — risk template rejection or suspension. This matters directly for cost control, since marketing conversations are priced differently from utility and authentication conversations.

What to do

• Audit existing approved templates against their actual use case, not just their original category.
• Train marketing and support teams on the difference between utility (order updates, appointment reminders) and marketing (offers, promotions) content before submitting new templates.

4. A Calling API has entered the picture

WhatsApp has opened a Calling API, extending the platform beyond messaging into business voice calls initiated through WhatsApp. For businesses in sectors like BFSI, healthcare, and logistics, this adds a channel for verification calls, support escalations, or appointment confirmations without asking customers to leave the app. It is early days for adoption in India, but it is worth evaluating alongside your existing messaging workflows rather than treating it as a separate project.

5. Regulatory pressure on WhatsApp's AI chatbot policy

Meta's rule barring general-purpose AI chatbots (rivals to Meta AI) from operating on WhatsApp has drawn regulatory pushback in Italy, with authorities asking Meta to suspend the policy. This is a reminder that platform rules around what kind of automated agents can run inside WhatsApp are still contested and subject to change by region. Businesses building AI-driven WhatsApp bots should keep an eye on how this plays out, since policy shifts here could affect what kinds of conversational AI integrations are permitted.

What this means for Indian businesses

None of these changes are optional to ignore. On-premises migration and template category compliance affect whether your messages get delivered at all. Currency billing changes affect your monthly WhatsApp spend directly. The Calling API and the AI chatbot policy debate are earlier-stage but worth monitoring if voice or AI-driven support is on your roadmap. Working with a BSP that proactively tracks these changes, rather than leaving businesses to discover them via support tickets, is the practical way to stay compliant without disruption.