WhatsApp Pricing Changes 2026

Every dated WhatsApp Business Platform pricing change in the second half of 2026, sourced to Meta's own documentation: what changes, when, what it costs, and what you have to change in your code.

Last verified on 4 September 2026 against Meta's pricing documentation and its 1 September 2026 pricing and billing notice. Re-check the official rate card for your billing currency before committing a budget.

Direct Answer

Three things change on the WhatsApp Business Platform in the second half of 2026, and one structural change has already happened.

On 1 July 2026, Meta split non-template messages into two categories: service messages (powered by a person or a third-party AI) and Meta Business Agent messages (powered by Meta's own agent platform). Before that date, every non-template reply was a service message.

On 1 August 2026, Meta began charging for Meta Business Agent messages on a per-token basis, at one global rate of 2.00 USD per one million tokens.

On 1 October 2026, Meta will begin charging for service messages and for utility templates sent inside an open 24-hour customer service window. Both are free today. Each phone number receives 1,000 free service messages per month; only its 1,001st service message onward is charged. The allowance refreshes monthly and does not roll over. Paid service messages use the utility and authentication list rate for the recipient's market and have no volume tiers.

Also on 1 October 2026, Meta will update marketing rates in six markets and utility and authentication rates in twelve markets. Nine markets move out of regional "Rest Of" pricing onto standalone utility and authentication rate cards, and receive new authentication-international rates.

The October rate cards are now published. Use the card for your WABA's billing currency and the recipient's country calling code; do not use the examples on this page as a substitute for the official card.

The Four Changes, With Dates

Why the 1 July 2026 Category Split Matters

Most coverage of these changes starts with the money. It is easier to follow if you start with the taxonomy, because the pricing follows the category.

Meta's own wording, from its non-template messages pricing page:

Until July 1, 2026: All non-template message responses to users were service messages (category: service).

From 1 July 2026 there are two categories of non-template message:

• Meta Business Agent messages — powered by the Meta Business Agent Platform. A new category.
• Service messages — powered by a person, such as a customer service representative, or by a third-party AI solution. Any non-template message that is not powered by Meta Business Agent is a service message.

Two structural constraints follow, and both are worth internalising before reading any rate table:

1. Non-template messages can only be sent inside an open 24-hour customer service window, which opens and resets with each user message. A service message is by definition a reply. You cannot use one to reach out. Any claim that service messages will be charged "regardless of the 24-hour window" is a category error: there is no such thing as a service message outside the window. See Service Messages.
2. Only one charge ever applies per message. Meta states this explicitly. A non-template message is charged either as a Meta Business Agent message or as a service message, never both. Meta also spells out a corollary that is easy to miss: a non-template message containing promotional content does not additionally incur a marketing template charge.

Change 1: Meta Business Agent Messages, Per Token

The rate

Meta publishes a single figure, and it is global rather than per-market:

• Meter — per message, based on one per-token charge covering both AI agent processing (token consumption) and message delivery.
• Rate — one global rate of 2.00 USD per 1 million tokens.
• Cache tokens — Meta does not charge for cache tokens. The rate and typical per-message estimate already exclude them.
• Typical consumption — Meta states one message typically consumes 20,000 to 25,000 tokens, roughly 4 to 5 US cents per message.
• Cost varies with complexity. Simple responses consume fewer tokens and cost less; complex responses consume more.

Meta's own worked examples:

Note carefully that the 4-to-5-cents-per-message figure belongs to Meta Business Agent messages only. It is not the service message rate. Several secondary write-ups have carried that number across to service messages, which overstates service message cost by a wide margin in most markets: Meta's own comparison table puts message delivery for Brazil at 0.68 US cents.

Billing setup and payment methods

This is the detail most likely to break a production rollout, and Meta states it as a warning note rather than burying it:

As of August 1, 2026 at 12pm PT — Meta will begin to charge for Meta Business Agent messages delivered via our API. Meta Business Agent messages will not be delivered if a credit line is not attached to your Business Agent account.

Not "charged later." Not delivered. If you switch Meta Business Agent on without a credit line attached, your replies do not reach the user.

On who this applies to and how billing works, Meta is equally direct:

Consistent with industry norms, Meta will charge all businesses for Meta Business Agent, including those that access the WhatsApp Business Platform today supported by a Solution Provider(s). Billing for Meta Business Agent will be via monthly invoicing — via a credit line with Meta — with support for credit cards as a payment method in September (target).

Two consequences worth planning around:

• Being on a Solution Partner does not exempt you. Meta charges the business directly for Meta Business Agent even where a Solution Partner handles the rest of the WhatsApp billing relationship.
• Getting a credit line is not instant. If you already have one for ads or messaging, you attach your Business Agent account to it in Billing Hub. If you do not, Meta's wording is that you apply for one in Billing Hub and it is "subject to review and approval by Meta." Start that before you plan a launch date, not after.

Meta's 1 September notice says credit and debit cards become available as a payment method on 8 September 2026. Until then, the credit-line requirement remains the documented delivery blocker. Meta also targets 15 September 2026 for APIs that report token consumption and costs in near real time.

Currency

As of 1 July 2026, Meta lists 16 currencies enabled on the WhatsApp Business Platform, and a Meta Business Agent account can be created in one of them. If the account is not in USD, Meta invoices in that currency, converting from the global USD rate using the exchange rate on the day each message was delivered. Businesses whose Sold-To country in Billing Hub is India or Brazil can only choose their respective local currency.

One wrinkle in Meta's own table: the Brazil row lists BRL, but the footnote against it reads "not yet available." So "16 enabled" and "16 selectable today" are not the same set. If you are billing in Brazil, confirm the current position in Billing Hub before assuming you can create the account.

This matters because the Meta Business Agent rate is published as a single global USD figure. Everyone else's invoice is a conversion of it, so a currency move shows up in your costs even when Meta's rate has not changed.

Change 2: Service Messages Become Chargeable

Meta's wording:

Effective October 1, 2026 - Meta will charge on a per-message basis for all service messages, consistent with how Meta charges for template messages. These messages have not been charged since November 1, 2024.

The pricing detail, from the same page:

• Charge for — delivered messages, not sent messages.
• Meter — per message.
• Rate — by market, service message rates will be the same as the rates for utility and authentication messages in that market.
• Free monthly tier — each phone number gets 1,000 free service messages per month. The allowance refreshes monthly, does not roll over, and only the 1,001st service message onward is charged.
• Volume tiers — none. Meta states it will not offer volume tiers for service messages, while continuing to offer them for utility and authentication messages.
• Rate publication — the rates taking effect on 1 October 2026, including service-message rates, are now published on Meta's pricing page.

The free tier and volume tiers solve different problems. A number sending 100 service messages in a month pays nothing for them; a number sending 100,000 pays the same market list rate for each billable service message after the first 1,000. Unlike utility and authentication templates, service messages do not get progressively cheaper at higher volumes.

Change 3: In-Window Utility Templates Become Chargeable

Meta's wording:

Effective October 1, 2026 - Meta will charge on a per-message basis for utility messages sent in response to users (within an open 24-hour customer service window). These messages have not been charged since July 1, 2025.

Utility templates sent outside an open window have always been charged and continue to be. What ends on 1 October 2026 is the in-window exemption in place since 1 July 2025.

Practical read: the order confirmation you send while the customer is still chatting with you has been free for fifteen months. From October it costs the same as the one you send the next day.

Change 4: October Rate Card Updates

Separately from the category changes, Meta will update marketing rates across six markets and utility and authentication rates across twelve markets on 1 October 2026. Two of the marketing markets and nine of the utility/authentication markets move out of their respective "Rest Of" pricing regions.

The nine newly standalone utility and authentication markets announced in May are:

Meta's 1 September notice confirms these nine moves and says the October rates are now published. It also confirms new authentication-international rates for all nine newly standalone markets.

Because service message rates will match utility and authentication rates, a market moving onto a standalone rate card on 1 October 2026 changes that market's service message rate on the same day. The two changes compound in those nine markets.

The Complete Billing Matrix

This consolidates Meta's category table, its pricing page, and the free monthly tier announced on 1 September 2026.

That last row is the one both the mainstream write-ups and the AI summaries keep getting wrong.

The 72-Hour Free Entry Point Exception

A free entry point window opens when a WhatsApp user messages you through a Click to WhatsApp ad or a Facebook Page call-to-action button, from a device running Meta's Android or iOS app (desktop and web are not supported), and you respond within 24 hours. The FEP window then runs for 72 hours from the time you responded. Marketing, utility, authentication, and service message delivery is free while it is open; Meta Business Agent token usage is the exception.

Meta's own category table states that marketing, utility, authentication and service messages are all free inside the 72-hour FEP window. It also states, in the same table, that Meta Business Agent messages are not.

Meta spells this out:

The 72-hour free entry point window is unchanged for message delivery. Messages sent within the 72-hour free entry point window, from Click to WhatsApp Ads or Facebook call-to-action buttons, remain free for message delivery. Meta Business Agent messages are still charged for token usage as of August 1, 2026.

The logic is consistent: the FEP waiver covers message delivery. Meta Business Agent's charge is a token charge bundling AI processing and delivery, so the waiver does not neutralise it. If your acquisition funnel leans on Click to WhatsApp ads and you route those conversations to Meta Business Agent, the FEP window no longer makes those replies free. It still does if a human or your own AI answers them.

Note also that the customer service window and the FEP window are independent. If the customer service window closes, you can only send template messages, whether or not the FEP window is still open.

Meta's Worked Example: One Charge Becomes Up to Five

Meta publishes a single conversation traced across the three pricing states. It is the clearest illustration available and it comes from the primary source.

The scenario: a business sends a cart abandonment reminder, the user asks two questions answered by Meta Business Agent, the agent hands off to a human rep who answers one more question, and the business sends an order confirmation. All within one hour.

As of 1 July 2026 the same conversation carried exactly one charge. It moves to three from August, then four or five from October depending on whether the phone number has exhausted its 1,000 free monthly service messages.

The behavioural consequence is direct once a phone number has exhausted its free monthly service tier. An agent or bot that splits one answer across four short service messages can produce four charges where one would have done.

What This Will Actually Cost You

Meta has published the October rates. The remaining work is to select the correct billing-currency card, map each recipient country code to its market, and apply the free service-message tier per phone number.

The formula:

Added monthly cost from 1 October 2026
  = (service messages Meta marks billable after the 1,000-message free tier
      x service rate for each recipient market)
  + (in-window utility templates delivered per month  x  utility rate for that market)

Both inputs are things you can measure today. Neither is something you should estimate.

An illustration using a rate Meta has published. In its own cost comparison, Meta uses 0.68 US cents as the message delivery rate for utility and authentication messages to users in Brazil. Assuming one phone number, all service messages go to Brazil, none fall inside a free entry point window, and that rate is the applicable October service rate:

• 10,000 service messages: (10,000 - 1,000 free) x 0.0068 USD = 61.20 USD per month
• 50,000 service messages: (50,000 - 1,000 free) x 0.0068 USD = 333.20 USD per month

Do not carry that figure to other markets; use Meta's current rate card for each recipient market.

Meta's service versus Meta Business Agent comparison, scaled to 1,000 AI-powered replies to users in Brazil from Meta's earlier 10,000-message example. The table predates the free service-message tier, so its service delivery line is the cost after the free allowance has been exhausted. Third-party AI estimates are Meta's own, based on what it describes as publicly available information and benchmarks:

Read that table with its provenance in mind. It is Meta's comparison of Meta's product against third-party alternatives, and the third-party AI cost assumptions are Meta's own. It is not an independent benchmark of what a third-party AI stack costs you. It also does not mean the first 1,000 service messages now incur the displayed delivery charge.

How to choose the correct market rate

Meta charges by the recipient's country calling code, not by your company's headquarters, incorporation country, or server location. Look up each recipient market in Meta's current country mapping: some countries have standalone rate cards, while others share a regional "Rest of" rate.

For an international customer base, model traffic by recipient market instead of applying one headquarters-based rate. A weighted forecast across your largest destination countries is more accurate than a single global average, especially because the nine October market changes move in different directions.

Meta publishes rate cards in multiple billing currencies, including USD and EUR. The effective date and monthly volume-tier reset use the WhatsApp Business Account timezone.

For Developers: Detecting the Change in Your Own Data

This is the part of the change with an implementation cost, and the part almost no coverage addresses.

Today: free service messages

The pricing object in a status webhook for a non-template message inside the customer service window currently looks like this:

"pricing": {
  "billable": false,
  "pricing_model": "PMP",
  "type": "free_customer_service",
  "category": "service"
}

An in-window utility template currently looks like this:

"pricing": {
  "billable": false,
  "pricing_model": "PMP",
  "type": "free_customer_service",
  "category": "utility"
}

From 1 October 2026: billable service messages

Meta documents the post-change shape for a billable service message:

"pricing": {
  "billable": true,
  "pricing_model": "PMP",
  "type": "regular",
  "category": "service"
}

So the diff to watch for on a service message is billable flipping from false to true and type flipping from free_customer_service to regular. The category stays service.

That is the billable shape. Meta's 1 September notice does not document the status-webhook shape for service messages covered by the new monthly free tier, so do not assume every service delivery flips to regular on 1 October.

Do not key your cost logic on category alone. If your billing, reporting, or cost-attribution code currently treats category: "service" as a synonym for "free", it will silently under-report from 1 October 2026. Key on billable and type.

Meta has not published the equivalent post-change payload for in-window utility templates. The reasonable expectation is type moving from free_customer_service to regular with category remaining utility, but that is an inference, not a documented fact. Treat it as an assumption to verify rather than a specification to build against.

Because Dualhook routes message-path webhooks directly from Meta to your endpoint via Webhook Override, the raw pricing object arrives at your server unmodified. That is the data your October cost model should be built on — not a provider's summarised view of it.

Counting service messages before October

You can size your exposure today with the Pricing Analytics API. Query with pricing_category set to SERVICE:

{
  "start": "<START_TIMESTAMP>",
  "end": "<END_TIMESTAMP>",
  "phone_number": "<BUSINESS_PHONE_NUMBER>",
  "country": "<COUNTRY_CODE>",
  "pricing_type": "REGULAR",
  "pricing_category": "SERVICE",
  "volume": "<VOLUME>",
  "cost": "<COST>"
}

Use the returned volume to model each phone number and recipient market, then account for the first 1,000 service messages per phone number being free. Rates differ by market, and Meta has not yet documented how a number's free allowance is allocated when it serves multiple markets. Dualhook surfaces the same per-category volume breakdown on each connection's Usage tab.

Meta Business Agent analytics

Meta targets 15 September 2026 for new APIs that expose Meta Business Agent token consumption and costs across a specified timeframe in near real time. Treat that as a target, not a shipped interface, until the API documentation is live.

Volume tier webhooks

Since 1 October 2025, an account_update webhook with event set to VOLUME_BASED_PRICING_TIER_UPDATE fires when a WABA reaches a new volume tier in a market in a given month. Tiers apply to utility and authentication only, aggregate at business portfolio level across all WABAs, and reset monthly at 00:00 in the WABA's timezone. Service messages will never trigger this, because they have no tiers.

What Coexistence Users Are Not Charged For

If your number runs Coexistence, the October change does not reach messages your team sends from the WhatsApp Business app. Meta states this directly in its Coexistence onboarding documentation:

After a business customer has been onboarded to Cloud API, messages sent by the business via the WhatsApp Business app will continue to be free, but messages sent via Cloud API will be subject to Cloud API pricing.

Meta is equally explicit that app-sent messages sit outside the window machinery entirely:

The 24-hour customer service window restriction applies to messages sent via Cloud API. Messages sent from the WhatsApp Business app are not subject to the customer service window and do not create, extend or affect Cloud API conversation windows or Cloud API pricing.

The practical read for a Coexistence deployment: a human replying from the phone is free and always has been, and stays free after 1 October 2026. The same human replying through Cloud API counts as a service message from that date; it uses the number's free monthly allowance, then becomes chargeable. App-sent messages still reach your endpoint as smb_message_echoes webhooks, so you can see them, but seeing them is not sending them and carries no charge.

This is worth stating plainly because it is widely reported as an open question. It is not one — Meta answers it on the Coexistence page rather than on the pricing pages, which is why it gets missed.

Three Remaining Questions

Stating these openly is more useful than filling the gaps with confident guesses, and every one is a real question a team will hit while planning.

1. Do in-window utility templates start counting toward volume tiers once they are charged?

Meta's rule today is that only charged messages accrue toward volume tiers, and it explicitly excludes utility templates delivered inside a customer service window and inside a free entry point window. From 1 October 2026, in-window utility templates become charged. Whether they then begin accruing is not addressed in Meta's documentation as of 4 September 2026. If they do, part of the October increase is offset by faster tier progression on utility. This is an inference and should not be modelled as fact. Ask Meta or your Solution Provider to confirm.

2. How is the free service-message tier represented and allocated?

The 1 September notice establishes the 1,000-message allowance per phone number, monthly refresh, and no rollover. It does not specify the status-webhook type used for a free-tier delivery, whether free entry point deliveries consume the allowance, or how the allowance is allocated when one number serves markets with different rates. Do not build billing logic around an assumed answer.

3. Will the October rates hold?

Meta's pricing calendar permits rate updates on the first day of each quarter only: 1 January, 1 April, 1 July, 1 October. Rate card updates carry a minimum of one month's advance notice, pricing model add-ons three months, and pricing model changes six months. The next opportunity to change these rates after October is therefore 1 January 2027, with notice.

The EU and EEA AI Providers Wrinkle

There is a fourth pricing track running alongside the three above, specific to a class of business rather than a class of message. It matters disproportionately in Europe.

In October 2025 Meta updated its WhatsApp Business Solution Terms to restrict "AI Providers," defined as providers and developers of AI or machine learning technologies where such technology is the primary rather than incidental or ancillary functionality being made available. The terms took effect on 15 October 2025 for new users of the platform and 15 January 2026 for existing ones, with a carve-out permitting such technologies to be made available to WhatsApp users with European Economic Area or Brazil country codes.

Meta then introduced a pricing policy for AI Providers. Per Meta's changelog: effective 16 February 2026, in countries where Meta is legally required to support AI Providers, Meta would charge AI Providers for non-template messages sent to WhatsApp users. Meta subsequently updated that policy: effective 13 May 2026, Meta will no longer charge AI Providers for non-template messages delivered to users in EU and EEA markets. Charges for non-template messages delivered to users in Brazil remain in effect.

The backdrop is a European Commission antitrust proceeding, and it has already moved past the stage most coverage stops at. The Commission issued a Statement of Objections on 9 February 2026, saying Meta's policy change appeared at first sight to breach EU competition rules. Then, on 9 June 2026, the Commission imposed interim measures ordering Meta to restore free access to the WhatsApp Business API for third-party general-purpose AI assistants, on the terms that applied before 15 October 2025, and to keep that access in place until the investigation concludes. Interim measures are rare — this was only the second such order under Regulation 1/2003 since Broadcom in 2019.

So the EU position is not merely that Meta chose to stop charging AI Providers in EU and EEA markets from 13 May 2026; a binding order now requires free access there while the case runs. The underlying investigation is still open, so the final outcome can change again.

Two practical notes. First, this track only applies if Meta classifies you as an AI Provider, which turns on whether AI is your primary product rather than a feature supporting a business use case. A retailer running an AI order-tracking bot is not an AI Provider; a general-purpose assistant distributed over WhatsApp is. Meta reserves that determination to itself. Second, if there is any chance the classification applies to you, this is a question for counsel rather than for a pricing page. Nothing here is legal advice.

What to Do Before 1 October 2026

An ordered list. The first item is the only one that is genuinely urgent.

1. Measure service-message volume per phone number and market. Use the Pricing Analytics API with pricing_category: "SERVICE", broken out by country. Model the 1,000-message free tier per phone number before applying market rates.
2. Measure your in-window utility template volume separately. Same method, different category. Distinct line item, distinct rate.
3. Audit your reply granularity. Count average outbound messages per resolved conversation. After a number uses its monthly allowance, a bot or agent that splits one answer across several bubbles creates several service-message charges. One reply, one message, is then a cost control rather than a style preference.
4. Fix your cost-attribution code before the flag flips. If anything in your stack treats category: "service" as free, it will under-report from 1 October. Key on billable and type instead.
5. Check template categorisation. Sending a transactional confirmation as a marketing template has always cost more; from October, misclassification errors spread across more of your traffic. See template category updates.
6. Push volume where tiers still exist. Utility and authentication templates get volume tiers; service messages never will. Where a use case can legitimately be served by a utility template rather than a free-form reply, the tiered rate may end up cheaper at scale. "Legitimately" is doing work in that sentence — categorisation rules still apply.
7. Download the published October rate card for your WABA currency. Replace any July-rate assumptions and repeat the calculation per recipient market.
8. If you plan to use Meta Business Agent, confirm billing first. Meta's earlier documentation requires an attached credit line for delivery; its 1 September notice says card payments become available on 8 September. Verify that the payment method is active before launch.
9. Separate Meta's charges from your platform fees in your model. They move independently and for different reasons.

Where Dualhook Fits

Dualhook is a badged Meta Tech Partner, not a Business Solution Provider. Customers keep their own Meta Business assets and their own billing relationship with Meta, and Dualhook charges a flat platform fee. Dualhook does not resell WhatsApp messaging and does not mark up Meta's messaging charges. See Dualhook pricing and the pricing doc.

The practical consequence for these changes is narrow and worth stating precisely rather than overselling: the October increase lands on your Meta invoice at Meta's published rates, and Dualhook's fee does not move with your message volume. There is no per-message layer on top. What Dualhook does is operational — connection setup through Embedded Signup, Webhook Override so message events reach your own endpoint directly, template management, and account health monitoring.

Do not hardcode Meta's rates into billing logic. They vary by recipient market and category and can change on the first day of any quarter. Pull them from Meta's rate cards and revalidate quarterly.

FAQ

What changed on 1 August 2026?

Meta began charging for Meta Business Agent messages on a per-token basis, at one global rate of 2.00 USD per million tokens, from 12pm PT. A typical message consumes 20,000 to 25,000 tokens, roughly 4 to 5 US cents. Cache tokens are not charged.

What changes on 1 October 2026?

Two things become chargeable that are free today: service messages, meaning free-form replies sent inside the 24-hour customer service window by a person or a third-party AI, and utility templates sent inside that same window. The first 1,000 service messages per phone number remain free each month. Separately, six markets get marketing-rate updates, twelve get utility/authentication-rate updates, and nine of the latter move onto standalone rate cards.

How much will a WhatsApp service message cost?

The first 1,000 per phone number each month are free. After that, the price is the published service rate for the recipient's market, which matches that market's utility and authentication list rate. Service messages do not have volume tiers.

What is the difference between a service message and a Meta Business Agent message?

Both are non-template replies inside an open customer service window. A Meta Business Agent message is powered by Meta's own agent platform and is charged per token from 1 August 2026. A service message is powered by a person or a third-party AI and will be charged per message from 1 October 2026. Any non-template message not powered by Meta Business Agent is a service message.

Can one WhatsApp message be charged twice?

No. Meta states that only one charge applies per message. A non-template message is charged either as a Meta Business Agent message or as a service message, never both. A non-template message containing promotional content does not additionally incur a marketing template charge.

Are messages inside the 72-hour free entry point window still free?

For marketing, utility, authentication and service messages, yes. For Meta Business Agent messages, no. Meta states those are still charged for token usage from 1 August 2026, because the free entry point waiver covers message delivery while the Meta Business Agent charge bundles AI processing with delivery.

How can I pay for Meta Business Agent?

Meta's launch documentation used monthly invoicing through an attached credit line and warned that messages would not be delivered without one. Its 1 September notice says credit and debit cards become available on 8 September 2026. Confirm the active payment method in Billing Hub before sending; being supported by a Solution Provider does not exempt a business from Meta Business Agent charges.

Are inbound WhatsApp messages from customers charged?

No. Messages a user sends to your business are not charged, and they open or reset the 24-hour customer service window.

Do I need to change my code for the October 2026 pricing change?

If you attribute costs from delivery status webhooks, yes. The pricing object for a service message changes from billable: false with type: "free_customer_service" to billable: true with type: "regular". The category remains service, so logic keyed on category alone will silently under-report.

Does switching WhatsApp providers avoid the new charges?

No. These are Meta's charges, applied at Meta's rates based on the recipient's market and message category. What differs between providers is whether they add a markup on top and how much visibility you get into the underlying charge data.

How much notice will Meta give for the next change?

Meta may update pricing only on the first day of a quarter. Its published minimum notice periods are one month for a rate card update, three months for a pricing model add-on, and six months for a pricing model change.

Sources

• Meta, Pricing on the WhatsApp Business Platform
• Meta, Pricing for non-template messages
• Meta, “Pricing and billing updates – Updated rates for Oct. 1 '26 and updates for Meta Business Agent,” partner notice dated 1 Sep 2026
• Meta, WhatsApp Business Platform changelog
• Meta, AI Providers pricing policy
• Meta, Analytics, including the Pricing Analytics API
• Meta, Status messages webhook reference
• WhatsApp, Business Solution Terms
• Meta, Onboarding WhatsApp Business app users — the Pricing section covering Coexistence app-sent messages
• European Commission, antitrust investigation into Meta's policy on AI providers' access to WhatsApp
• European Commission, interim measures ordering Meta to preserve free WhatsApp access for rival AI assistants, 9 June 2026

All checked 4 September 2026. Use Meta as the authority for every rate, date, and field name. Secondary coverage is useful for confirming that a change is being widely reported, not for establishing what the change is.