WhatsApp Business API pricing in 2026: per-message rates, the October changes and India's rupee deadline

Since 1 July 2025, WhatsApp charges businesses per delivered template message, priced by category (marketing, utility, authentication) and by the recipient's country. On 1 October 2026 rates changed in 17 markets and regions, and service messages became chargeable. Businesses billed from India must switch to rupee billing by 31 December 2026.

All rates below are Meta's USD list rates from the official rate cards, downloaded on 25 September 2026. Your volume tier, billing currency and partner fees can change what you pay. WhatsApp and Meta are named descriptively; MobileValidate is not affiliated with either.

#How does WhatsApp per-message pricing work in 2026?

You pay for each delivered template message. Meta's pricing page says you are "only charged when a template message is delivered", and that rates vary by "the template's category and the recipient WhatsApp phone number's country calling code" (Meta, 2026).

Four things set the price of a message:

The model replaced conversation-based pricing on 1 July 2025. Meta may only change rates on the first day of a quarter (1 January, 1 April, 1 July, 1 October), with at least one month's notice for a rate change and six months for a change of pricing model (Meta, 2026).

Some messages stay free. All messages sent inside an open free entry point window are free for 72 hours, templates included (Meta's page explains when that window opens). Messages from users are never charged.

#What does a WhatsApp message cost by country?

Here are list rates from the USD rate card effective 1 October 2026 for common markets (Meta rate card, 2026). Utility, authentication and service share one rate in every market on this card.

Across the October card, marketing ranges from $0.0109 (Turkey) to $0.1597 (Netherlands). Utility and authentication range from $0.0008 (Colombia) to $0.0550 (Germany). The full card for every market and both quarters is in our dataset, WhatsApp rate-card history (CSV and JSON, CC BY 4.0).

#What changed on 1 October 2026?

Three kinds of change took effect, all announced on Meta's pricing page (Meta, 2026):

1. Rate changes. Marketing went up in Mexico, Saudi Arabia, the UAE, Rest of Middle East and Rest of Asia Pacific. Utility and authentication went up in Pakistan, Peru and South Africa.
2. Nine new standalone markets. Bangladesh, Iraq, Kazakhstan, Kuwait, Morocco, Nepal, Oman, Sri Lanka and Ukraine left their regional groups. Each now has its own rates, its own volume tiers and a new authentication-international rate.
3. Service and in-window utility messages became chargeable (next sections).

Comparing the two official cards line by line, these are the rate changes for markets that existed on both:

The new standalone markets moved in both directions. Utility and authentication in Sri Lanka ($0.0020), Nepal ($0.0034) and Bangladesh ($0.0037) are now below the Rest of Asia Pacific rate ($0.0113). Kuwait ($0.0440), Oman ($0.0247) and Morocco ($0.0230) are now above their former regional rates ($0.0091 for Rest of Middle East, $0.0040 for Rest of Africa).

India, Brazil, Indonesia, the UK, Germany and North America had no rate changes on the October card.

#Which messages became chargeable on 1 October 2026?

Two message types that used to be free now cost money (Meta, 2026):

• Service messages. These are free-form replies inside the 24-hour customer service window. From 1 October 2026 they are charged "with rates the same as those of utility and authentication, by market". Each business phone number gets a free tier of 1,000 delivered service messages per month, shared by one-to-one and group sends. Unused messages don't roll over.
• Utility templates sent in response to users. These are order updates or receipts sent while the service window is open, free since 1 July 2025 and charged from 1 October 2026.

Meta adds one operational warning. Without a payment method on the account, service messages are delivered only within the free tier, and later ones are not delivered at all.

The change is visible in your webhooks. For messages over the free tier, the pricing object on status webhooks changes from "type": "free_customer_service" to "type": "regular" with "billable": true. If your cost reports assume every service message is free, update them before the October invoice.

#What is the authentication-international rate?

It is a higher authentication rate for big senders messaging users in another country. Meta's rules (Meta, 2026):

• You become eligible if you send "more than 750K messages outside of customer service windows in a moving 30-day period" to markets that have the rate.
• You get 30 days' notice before the rate applies.
• You always pay the normal authentication rate in the country of your primary business location.

Until 30 September 2026, nine markets had the rate: Egypt, India, Indonesia, Malaysia, Nigeria, Pakistan, Saudi Arabia, South Africa and the UAE. From 1 October 2026 the nine new standalone markets add their own, so up to 18 markets count, and eligibility has been measured across all 18 since 1 September 2026.

The gap can be large. Sri Lanka's authentication rate is $0.0020, but its authentication-international rate is $0.1440, 72 times higher. In India the two rates are $0.0014 and $0.0304. A global app sending codes to South Asia should model both.

#What changes for India and Brazil billing in 2027?

WhatsApp billing in local currency becomes mandatory for eligible businesses in both countries (Meta, 2026):

Meta offers a Currency Migration API (available since 1 June 2026) to move accounts. Local-currency rate cards are published next to the USD cards.

What this means in practice: if you send WhatsApp messages as an India-billed business, the migration is not optional, and missing it stops delivery. Put it in your Q4 plan, check each messaging account in your business portfolio, and confirm that your solution provider has migrated its side.

#How has the rate card changed over time?

Meta's page lists earlier updates in its "Previous rate card updates" section. The main ones since the per-message model began:

The pattern is steady: one change set per quarter, markets moving out of regional groups, and authentication-international spreading. Budget for a review every quarter, not once a year.

#How do I estimate my monthly WhatsApp bill?

Multiply each category's volume by the share that gets delivered and the market rate, then add service messages above the free tier:

Monthly cost per market = Σ (templates sent × delivered share × rate) + max(0, service messages − 1,000 per phone number) × service rate

A worked example for one business phone number sending to Brazil in a month, using October list rates (before any volume-tier discount), with every message delivered:

The same traffic costs 12% more in October with no rate change for Brazil. The whole difference comes from the two newly charged message types. The volumes are illustrative. Replace them with your own, per market, and apply your volume tier from Meta's tier files.

The delivered share matters for forecasting. If 8% of the numbers you message have no WhatsApp account, those messages aren't delivered or charged, and your WhatsApp bill is 8% lower than a naive forecast. But those users still need your message through SMS or e-mail, which has its own price.

#How does checking numbers first help with cost?

Honestly, it doesn't lower Meta's bill: undelivered messages are already free. It lowers the cost around the message:

• No wasted fallback time. A one-time code sent to a number without WhatsApp fails first, and only then does your SMS go out. The user waits, and some give up.
• No double sends. Teams that fire SMS on a timer, "just in case", pay for both channels when both arrive.
• Better forecasts. Knowing the share of your list that is on WhatsApp gives you the delivered share for the formula above, per market.

MobileValidate's whatsapp check returns registered: true, false or null (unknown) with a checked_at time. Here's a test-mode request with documented test numbers:

curl https://api.mobilevalidate.com/v1/lookup \
  -H "Authorization: Bearer $MOBILEVALIDATE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"numbers": ["+447700900001", "+447700900002", "+447700900003"], "checks": ["whatsapp"], "wait": 5}'

In test mode …001 is registered, …002 is not registered and …003 is unknown. Route true to WhatsApp, false straight to SMS, and null to your default flow. Never block a user on an unknown. The check has a real-time and a lower bulk price (see pricing for current prices), and unknown results and cache hits are free. The check isn't free, so it pays off when it saves a fallback delay or a duplicate send, not on Meta's bill. For the one-time code case, see WhatsApp OTP vs SMS OTP, which works out cost per verified user.

#What should I do before the next rate card?

Meta can change rates only on 1 January, 1 April, 1 July and 1 October, and it publishes upcoming cards on the pricing page ahead of time. A short routine each quarter keeps surprises off the invoice:

1. Download the upcoming card from the "Updates to rate cards" section when it appears, and diff it against the current one by market and category. Our dataset does this for the USD cards.
2. Re-run your forecast per market with your real volumes, delivered share and volume tier.
3. Check your template categories. Meta charges the category applied to a template when it is used, and businesses are responsible for reviewing it. A utility template recategorised as marketing can cost several times more; in Brazil the October list rates are $0.0068 and $0.0625.
4. Watch authentication-international eligibility if you send codes across borders at scale. Meta gives 30 days' notice.
5. Confirm billing currency for India (INR by 31 December 2026) and Brazil (BRL by 30 June 2027).
6. Update webhook-based cost reports for new pricing types. The October change moved service and in-window utility messages to "billable": true.

#How was the rate-card dataset built?

We downloaded Meta's official USD rate cards on 25 September 2026 from the links on the pricing page. The card effective 1 July 2026 is a CSV and the card effective 1 October 2026 is an XLSX, which we read with openpyxl. We transcribed each market's rates as published, to four decimal places, with n/a recorded as empty. Then we compared the two cards market by market to fill change_vs_previous. Rows for sanctioned countries, which MobileValidate doesn't serve, are left out: the dataset has 38 of the card's 39 standalone markets.

Limits:

• List rates only. Volume tiers are in separate files and are not included.
• The history starts on 1 July 2026. Earlier cards are shared as expiring download links, and we couldn't retrieve them from a primary source. The table of earlier changes above is Meta's own description, not our numbers.
• Quarterly updates. We add each new card when Meta publishes it.

Download: /datasets/whatsapp-rate-card-history (83 rows).

#What are the key takeaways?

• WhatsApp charges per delivered template message by category and recipient market. The October 2026 USD card runs from $0.0008 (Colombia utility and authentication) to $0.1597 (Netherlands marketing).
• On 1 October 2026, rates changed in 8 existing markets and regions, 9 markets became standalone with authentication-international rates, and service and in-window utility messages became chargeable. There is a free tier of 1,000 service messages per phone number per month.
• India-billed businesses must be on INR billing by 31 December 2026, or messages stop on 1 January 2027. Brazil's BRL deadline is 30 June 2027.
• Forecast with delivered share × rate per market, plus service messages above the free tier. Review every quarter.
• Checking numbers first doesn't cut Meta's bill, because undelivered messages are free. It cuts fallback delay and double sends.