Meta has been restructuring how businesses pay for WhatsApp Business Platform messaging, moving away from the older per-conversation pricing model toward pricing based on individual messages and templates. At the same time, Meta is phasing out the legacy On-Premises API in favour of the Cloud API. For Indian businesses running WhatsApp campaigns, support desks, or order updates, these two changes affect cost planning and technical setup, and it is worth understanding both before you budget for the next quarter.

From per-conversation to per-message billing

For several years, Meta billed businesses per 24-hour conversation window, grouping all messages exchanged with a customer in that window into a single charge based on the conversation category (marketing, utility, authentication, or service). Meta has been shifting this model toward charging per message or per template sent, rather than bundling an entire day's exchange into one conversation fee. This changes how costs scale: a business sending several follow-up messages within one conversation window may now be billed differently than under the old bundled model.

The practical effect for Indian businesses is that cost estimates built around the old conversation-based model need to be revisited. Marketing-heavy use cases, such as broadcast promotions or cart-recovery nudges, are the most exposed to this shift because they typically involve template messages sent to large lists. Utility and authentication messages, such as OTPs and order confirmations, remain comparatively predictable since they are typically single-message exchanges.

On-Premises API sunset: migration is not optional

Meta has documented the sunset of the On-Premises API, its older self-hosted deployment option, in favour of the Cloud API, which is hosted by Meta and accessed via standard REST endpoints. Businesses and BSPs (Business Solution Providers) still running On-Premises deployments need to migrate to the Cloud API to keep sending messages. This is not simply a policy preference; Meta's own developer documentation frames it as a scheduled retirement of the older infrastructure.

For Indian businesses that set up WhatsApp Business API integrations several years ago, often through a BSP or system integrator, this migration should be treated as a technical project with a deadline, not an optional upgrade. Key steps typically include:

• Confirming with your BSP or provider whether your account is already on the Cloud API or still on the older infrastructure.
• Reviewing webhook URLs, message templates, and phone number configurations, since these need to be re-verified during migration.
• Testing template approval and delivery in a staging environment before cutting over production traffic.
• Auditing any custom code that depended on On-Premises-specific endpoints or response formats.

Why this matters for Indian businesses specifically

India is one of WhatsApp's largest markets, and a large share of e-commerce, D2C, BFSI, and healthcare businesses in the country rely on WhatsApp for order updates, OTPs, and customer support. Because template-based marketing messages are the category most affected by the shift to per-message billing, businesses running high-volume promotional campaigns should re-run their cost projections rather than assuming last year's per-conversation math still holds. Businesses that rely mainly on utility and authentication messages will see less disruption, since those message types were already priced closer to a per-message basis in practice.

It is also worth noting that Meta continues to publish changes to the WhatsApp Business Platform through its official developer changelog. Any business running WhatsApp API at scale should treat that changelog, along with communication from their BSP, as the authoritative source for pricing and policy updates, rather than relying on older blog posts or cached pricing pages.

What to do now

If your business sends WhatsApp messages through the API, ask your provider two direct questions: whether your account has fully migrated to the Cloud API, and how your current message mix (marketing versus utility versus authentication) is billed under the current pricing structure. Getting clear answers to both will let you budget accurately rather than discovering a change in your next invoice.

Frequently asked questions

Is the On-Premises API still usable?

Meta has scheduled the retirement of the On-Premises API in favour of the Cloud API. Businesses still on the older infrastructure should confirm their migration timeline with their BSP rather than assume indefinite support.

Does the pricing change affect OTPs and order updates?

Authentication and utility messages, such as OTPs and delivery updates, are generally less affected by the shift away from conversation-based billing since they are typically single, transactional messages rather than multi-message marketing exchanges.

Who should I ask about my specific pricing?

Your BSP or WhatsApp API provider can confirm exactly how your account is billed today. Meta's own developer changelog is the authoritative source for platform-wide policy and pricing changes.