Meta is retiring the On-Premises WhatsApp Business API and steering all businesses toward the Cloud API, which it hosts and manages directly. If your business still runs the older self-hosted client, you will eventually need to migrate. This matters for Indian businesses because it changes how messages are billed, how templates are approved, and who is responsible for uptime and security.

What is changing

The original WhatsApp Business API required businesses (or their partners) to host the software themselves, on their own servers, with manual updates and infrastructure maintenance. Meta has moved development and support toward the Cloud API, which runs on Meta's own infrastructure. New features, template types, and platform updates are released on the Cloud API first, and in many cases exclusively.

For businesses still on the On-Premises setup, this means reduced support, no access to newer capabilities, and eventual mandatory migration. Meta has communicated timelines for this transition directly to partners and Business Solution Providers (BSPs), so any business still on the legacy client should confirm its migration deadline with its current provider rather than assume it has unlimited time.

Why Meta made this shift

Hosting the API centrally lets Meta push security patches, rate-limit changes, and new features (such as catalog messaging, Flows, and richer template formats) to every business at once, instead of waiting for each company to update self-hosted software. It also reduces the operational burden on businesses that previously needed dedicated servers and technical staff just to keep the API running.

How WhatsApp Business API pricing works

Regardless of which version you use, Meta bills WhatsApp Business API usage through conversation-based pricing, organised into categories:

• Marketing: promotional messages, offers, and business-initiated outreach.
• Utility: transactional updates such as order confirmations, shipping alerts, and appointment reminders.
• Authentication: one-time passwords and verification codes.
• Service: replies within an active customer support conversation, which Meta does not charge for when the customer initiates contact within the 24-hour session window.

Each category is billed per conversation (a 24-hour messaging window), not per individual message. Businesses that message customers frequently for promotions should expect higher costs under the Marketing category, while routine order updates fall under the cheaper Utility category. Any message sent outside an active 24-hour window, or any business-initiated message, must use a pre-approved message template.

What Indian businesses should check now

• Confirm with your BSP or Meta partner whether you are on the On-Premises API or the Cloud API.
• If you are still on-premises, ask for a documented migration timeline and plan, since template libraries and phone number registration need to be carried over correctly.
• Review your message mix across Marketing, Utility, Authentication, and Service categories to understand where your costs are concentrated.
• Re-test all approved templates after migration, since formatting and category classification can affect approval and billing.

The practical takeaway

The end of the On-Premises API is not a sudden cutoff so much as a steady narrowing of support for the older system. Businesses that migrate early avoid last-minute disruption to customer messaging, order confirmations, and OTP delivery — all of which are business-critical for Indian companies using WhatsApp for e-commerce, logistics, and customer support. Working with an established BSP simplifies the migration, since template re-approval, number porting, and category classification are handled as part of the transition rather than left to in-house teams unfamiliar with Meta's requirements.

Frequently asked questions

Do I have to pay to reply to a customer on WhatsApp?

No. If a customer messages your business first, you can reply for free within the 24-hour session window under the Service category. Charges apply once you send a message outside that window or initiate contact using a template.

What happens if I don't migrate from the On-Premises API?

Support and new features are being withdrawn from the On-Premises client over time. Businesses that delay risk losing access to updates, newer message types, and eventually the ability to send messages at all once Meta fully sunsets the legacy system.

Is the Cloud API free to use?

Meta does not charge a licensing fee for the Cloud API itself, but businesses pay per conversation based on category (Marketing, Utility, Authentication, or Service). Many businesses also pay a BSP for onboarding, template management, and support.

Can I switch providers without losing my WhatsApp number?

Yes, phone numbers can generally be migrated between BSPs, but the process requires coordination to avoid downtime, and existing approved templates need to be re-verified with the new provider.