Meta's WhatsApp rates by market, and the countries it does not name

Meta’s WhatsApp pricing page does not print a price. We fetched it on 19 September 2026 and there is no currency amount anywhere in its text. The per-market numbers ship as 48 downloadable files, and the page’s own worked examples put letters where the thresholds would go. So this article explains what sets your rate and prints no table of per-country amounts. That is our editorial choice about a table that would age badly, not a claim that the files cannot be read: the conditions under which a downloaded card can be cited are at the end of this page.

One thing before you compare quotes. If you are asking what a message to the United States costs, there is a rate and it is not filed under that name. The United States is not a market row on Meta’s card; it is half of a market row Meta calls North America, and that row is the one that prices your message.

What sets the price, and whose geography it is

Meta ties the rate to the person receiving the message, not to where you are: “Rates vary based on the template’s category and the recipient WhatsApp phone number’s country calling code”. Category is the second axis, and for two categories a volume tier is the third.

The geography is not a country, though. It is a market, and the table mapping one to the other is headed “Calling Code (and network prefix if applicable)”. That parenthesis is doing real work. We counted 140 countries in it, arranged into 38 market rows, only 30 of which are a single named country. Anything unlisted falls to a bucket Meta describes as “Other All other countries Varies by country”, a market with no calling code at all.

Calling code 1 is two different markets

The row for North America flattens, in the page text we read, to:

North America Canada United States 1 1 CA US

Two countries, one market, one calling code. That is the whole of the American pricing story: anyone quoting you a US rate is reading a regional row and relabelling it, and Canada gets the same number by construction.

That is also why the network prefix column exists: a +1 number is not automatically North America. Three members of Rest of Latin America share calling code 1, separated only by area code: the Dominican Republic as “1 (809, 829, 849)”, with Jamaica and Puerto Rico listed the same way. Bucket by calling code alone and +1 809 lands in the wrong market.

The volume tiers, in Meta’s own letters

Utility and authentication messages get cheaper with volume. The mechanics are in prose; the thresholds are not. Accrual is portfolio-wide: “Messages are aggregated at the business portfolio level, across all WhatsApp Business accounts (WABAs) owned by the portfolio”. Tiers are not global either, because “Volume tiers are aligned to our rate cards and differ by market (e.g., Brazil or Rest of Latin America) and category (utility, authentication)”. Crossing one is not retroactive: “they unlock the rate of the next tier, specifically for messages in that tier”.

Then Meta’s own worked example, which says where the numbers are not:

The table below is illustrative and only highlights the dynamics of volume tiers. Please refer to our rate cards to see the rates charged.

It reads “List rate for the first A messages. Tier rate 1 for messages A+1 to B.” Meta explains the shape of the discount in public and puts the discount itself in a file.

Service messages sit outside the mechanism: “Meta will not offer volume tiers for service messages.” The category you answer customers in has one price per market at any volume, and what Meta starts charging for a service message on 1 October is flat at every scale rather than a tier to grow into. Whether you may send one at all is a different question from what it costs, and it is settled by the 24-hour customer service window.

One wrinkle multiplies markets rather than countries. Meta runs a second authentication rate in some, and on its own page “The following markets have authentication-international rates:” is followed by names and launch dates with no prices. Eligibility is yours, not the market’s: “Meta will determine eligibility for authentication-international based on messages across these 18 markets.” The numbers are elsewhere again: “Please see Rate cards for the list of countries with authentication-international rates.”

The one rate Meta prints in prose, and what it is doing there

Across the pricing pages we read on 19 September 2026, exactly one per-market figure appears as page text, and not on a rate card. It is an input to a cost comparison for AI-answered messages:

The 0.68 USD cent message delivery rate is based on the current rate (as of July 1, 2026) for utility and authentication messages to users in Brazil.

A Brazil number, current at a stated date, printed to make a different argument. Brazil is one of the 30 standalone markets, so it means what it says. Nothing equivalent exists for North America, and we will not pull a regional figure out of a downloaded file and hand it to you as a country price.

Meta has a rate calculator, and its HTML contains no rates

The developer page points to one: “This information is also available interactively on our WhatsApp Business website”. It asks you to “Select the market, currency and message category to understand what we charge.” We fetched that page on 19 September 2026. Its menus are in the served markup and the rates are not: the message rate row is empty, the tier table arrives with headers and no rows, and the figures are pulled in afterwards by a script. The endpoint that script calls refused our request for want of a session token, which appeared nowhere in the page we were served.

Its market menu confirms the missing row a second time. Read down it alphabetically and it ends “Turkey United Arab Emirates United Kingdom Other”. North America is in that list, between Nigeria and Pakistan. The United States is not in it at all.

The same page still says “That’s why we do not charge for service messages, or for utility messages businesses send in response to users”, which stops being true on 1 October 2026 under Meta’s own schedule.

The card moves quarterly, and has already needed a correction

The change window is fixed:

Meta may update pricing only on the 1st day of each quarter, thus up to 4 times per year: January 1, April 1, July 1, and/or October 1.

The assets are not infallible. Meta’s own note, still on the page when we read it:

The PDF of to-be rates in USD contained errors, for volume tiers of specific markets. This was updated as of Sep. 14, 2026. Please rely on the CSVs published since September 1, 2026 or the PDF published as of Sep 14, 2026. All other assets published on Sep. 1, 2026 remain accurate: The other 15 PDFs and all 32 CSVs.

A card corrected in one currency thirteen days after publication is not something to transcribe into an article and leave for a year.

So what do you do about an actual number

Pull it yourself, from Meta, in your own currency, on the day you need it. The cards are linked from the pricing page, one rates CSV and one volume tiers CSV per currency, and Meta says of the current set that “These rate cards reflect our current rates and volume tiers, effective July 1, 2026, based on WhatsApp Business account timezone.” Read the market row rather than a country name, and date the number in your own model.

A downloaded card is a primary source, and we should be straight about that rather than hiding behind the file format. It is citable, and the four things that make it citable are the four things a blog table never carries: the currency, the market row and which countries map to it, the effective period Meta stamps on the asset, and which version of the file you opened, given that Meta corrected one of them thirteen days after publishing it. Record those four and you have a checkable figure. Omit any one and you have a number.

So this page prints no per-market table for a reason that is about the table rather than about the file. A per-country grid transcribed once goes stale on Meta’s own quarterly schedule, it cannot be re-checked against a snapshot of a page the way every other quotation in this corpus can, and the one asset we know of was wrong for part of the period it covered. Where we do use a figure from a card elsewhere on this site, it carries those four things in the article’s frontmatter and names the row rather than a country.

What you should not accept from anybody, us included, is a per-country table with no date and no source. A vendor publishing no number at all is the adjacent problem, and we read that category’s pricing pages one at a time in review management software. Meta is the opposite failure. It calls what it does publish transparent, “we publish our rates for transparency”, and the rates genuinely are published. They are simply published somewhere a reader cannot check our copy of them against the page we read, which is a different complaint from unavailability.