WhatsApp API Pricing by Country: How to Budget Across Markets

WhatsApp API pricing by country is the first thing a business selling across borders gets wrong — because there is no single WhatsApp price. Meta charges per delivered message, and the rate depends on two axes at once: the message category (marketing, utility, authentication, service) and the destination country. A marketing message to one market can cost several times a utility message to another. This post shows how to read Meta's rate card, why the rates differ, and how to budget when your customers live in more than one country.

How to read the rate card

Meta's rate card is a table: rows are countries, columns are categories, cells are per-message prices in US dollars. To budget, you need three inputs for each market: how many outbound messages you send there per month, split by category, and the cell for each combination. Inbound messages are free everywhere and never enter the table. The 1,000 free service messages per number per month apply per number, not per country — they shave the service column, not the marketing one. Rates change: re-check the card each quarter, and never budget from a screenshot older than the current quarter. The mechanics behind the table — including the October 2026 change that ended free in-window replies — are in the

per-message pricing guide.

Why rates differ so much between countries

Rates reflect local telecom and market conditions: operator termination costs, fraud and spam pressure, and how Meta prices each market's messaging ecosystem. The practical consequence is a spread, not a ranking to memorise: some markets price messages at a fraction of a cent, others at several cents, and marketing always costs more than utility in the same market. The spread matters most for campaigns: a marketing blast priced for a low-rate market becomes a different budget in a high-rate one, which is why country mix belongs in the campaign budget before the audience is chosen, not after.

Three multi-country budgets (illustrative rates)

The worked examples below use labelled illustrative rates — $0.005 per message in Market A, $0.02 in Market B, $0.05 in Market C — because real rates must come from Meta's current card for your exact markets, and this post does not quote them. A language school with 2,000 monthly messages split evenly between two low-rate markets: at the illustrative $0.005, about $10 in Meta fees. A furniture store with 6,000 messages split between a low-rate and a mid-rate market: roughly $30 at $0.005 plus $60 at $0.02, about $90 before its platform plan. A clinic group with 4,000 messages concentrated in a high-rate market: about $200 at the illustrative $0.05. The lesson is not the totals — they move with real rates — it is the method: split by country, split by category, multiply, then add the platform plan. Neksio's plan is the same in every country (Free 100 AI replies a month on WhatsApp, Starter $8.99 for 5,000, Growth $11.99 for 15,000 including Facebook and Instagram, Scale $29.99); only Meta's line moves with geography.

The mistakes multi-country businesses make

First, budgeting from one market's rate for all markets — the average hides the expensive market. Second, forgetting the category split: a month of utility reminders budgeted at the service rate, or marketing templates budgeted at the utility rate, each misstates the bill in opposite directions. Third, ignoring currency: Meta bills in dollars while your revenue may be in reais, pesos, or dirhams, so a rate-card price and a revenue line in different currencies need converting before the margin makes sense. Fourth, running one number for all markets and wondering why the free service tier vanished early: the 1,000 free messages are per number, so a single number serving five countries burns one shared tier.

Owner: “Our Brazil month cost triple our Mexico month — same messages.” Same count, different rate card cells, different categories. The country mix was the budget all along.

A one-page budgeting routine

List your markets and last month's outbound messages per market per category. Look up each cell on Meta's current rate card. Multiply, sum, add your platform plan, and compare against last month's actual Meta invoice — the gap is your forecasting error, and it shrinks fast once the category split is right. Keep a payment method on file in Meta's Billing Hub for every number, and remember the scope note: Neksio is not a bulk or broadcast tool, so cross-border budgets here assume customer conversations and opted-in service messages, not list blasts — a broadcast-sized volume in a high-rate market is a different budget conversation entirely.