The WhatsApp API can now be billed in reais: what changes in your budget
By José Pedro · Co-founder of CRPRO
BRL billing removes daily exchange-rate swings and foreign-currency operating costs from your WhatsApp API bill — but it doesn't freeze the price and doesn't touch October 2026's new charges. See the two billing arrangements, the dates that matter, and a checklist to switch without mixing it into the October effect.
BRL billing for the official WhatsApp API is the option to receive Meta's invoice in Brazilian reais instead of US dollars: it's been available since July 1, 2026 and becomes mandatory by June 30, 2027. In practice: the bill Meta charges for messages, which in Brazil used to be denominated in dollars, starts getting issued in the currency you budget, sell, and pay taxes in. You have until June 30, 2027 to make the switch on your own schedule — but there's a concrete reason not to push it that far, and it has less to do with exchange rates than with what changed on October 1, 2026.
Is Meta's invoice yours, or your vendor's?
That's the first question, and a good chunk of businesses answer it wrong. There are two billing arrangements on the official WhatsApp API, and they completely change what this article means for you.
| Arrangement | Who issues the invoice | Currency you receive today | What changes for you |
|---|---|---|---|
| You pay Meta directly | Meta, under your company's tax ID | US dollars, in most cases | The currency switch is yours to make |
| Your vendor pays Meta and resells | The BSP or the CRM platform | Reais, baked into the monthly fee or passed through with a markup | Very little: the currency exposure was already the vendor's |
If you don't know which of the two you're in, the answer shows up in two places: the footer of the invoice that lands in your email (who issued it?) and your WhatsApp Business account manager, under the payments section. Worth checking before touching anything, because half the steps in this article only apply to the first case.
What dates actually matter in this transition?
| Date | What happens |
|---|---|
| 07/01/2026 | BRL billing becomes available. Opt-in, not mandatory. |
| 10/01/2026 | Service messages and utility templates inside the 24h window are charged per message (they were free until 09/30/2026). |
| 06/30/2027 | Final deadline. BRL billing stops being optional. |
The date in the middle is why this matters now. It isn't that reais will save you money — it's that October changed the size of your bill, and you don't want to be measuring that change across two currencies at once. If the currency switch lands in the middle of your October-versus-September comparison, it will mix two different effects together.
What the currency switch takes out of your cost
The dollar's daily swings. With the bill in dollars, your cost per message wobbled every month without you sending a single extra message. Two months identical in volume closed with different figures, and nobody in finance could say whether the campaign got expensive or it was just the exchange rate. One honest warning: billing in reais doesn't freeze the price. Meta reviews its rate tables periodically, and a real-denominated table can be adjusted just like any other. What disappears is the daily swing entering your bill — the currency risk shifts to whoever issues the invoice.
The cost of operating in a foreign currency. Paying in dollars isn't just the rate. There's the conversion spread charged by whoever processes the payment, and taxes on foreign-currency transactions, which vary depending on the payment method and the company's structure. Those figures rarely show up in your cost-per-lead math, but they show up on the statement. Talk to your accountant before estimating how much this represents for you — the rule isn't the same for everyone.
The parallel exchange-rate spreadsheet. An invoice in reais, under the right tax ID, is what finance can reconcile with no manual conversion. If you've ever tried explaining to accounting why August's message cost doesn't match July's, you know what that's worth.
What doesn't change with BRL billing?
To avoid setting the wrong expectation, it's worth listing what the currency switch doesn't solve:
- The billing structure. It's still per delivered template message, as it has been since July 1, 2025. The old conversation-based pricing model stays dead, in any currency.
- October's charge. Service and utility inside the 24-hour window are charged the same way. We broke down who feels it most in who feels October's charge the most.
- Ban risk. Billing currency has nothing to do with number quality, opt-in, or bans. The official API doesn't eliminate ban risk — it gives you visibility and due process: quality rating per number, calculated over the last 7 days of recipient reactions (window stated in Meta's documentation, in effect as of August 2026), an email warning with a deadline to fix things, and a formal appeal. That stays the same in reais or in dollars.
- The platform's monthly fee. That's a separate line, charged by whoever gives you your inbox, and it was almost always already in reais.
How do you build a cost forecast in reais this month?
The service-message rate is in Meta's current price table, not in this article. What you can do now is fix the baseline with these references, by category:
| Category | Approximate rate | In reais |
|---|---|---|
| Marketing | ~US$0.0625 per delivered message | ~R$0.32 per message |
| Utility | about US$0.0068 per message | about R$0.035 per message |
| Authentication | about US$0.0068 per message | about R$0.035 per message |
| Service (inside the 24h window) | charged per message since 10/01/2026 (free until 09/30/2026) | in Meta's current price table |
Reference figures verified on August 27, 2026. The utility and authentication numbers are market estimates, not an official real-denominated table — use them for order of magnitude, not as a contract basis.
An operation sending 3,000 marketing templates and 5,000 utility templates a month lands around R$960 + R$175, somewhere near R$1,135 a month in Meta's fee (estimate at the rates in effect as of August 2026). Add the platform's monthly fee and you have the channel's real cost. Save that number: it's the baseline you'll compare future months against.
If you want to open up the full breakdown, with the three cost lines separated, it's in how much the official API costs in 2026 and in WhatsApp Business API pricing.
Checklist to make the switch
- Identify who issues your invoice. Meta directly, or a vendor. If it's a vendor, ask them what their plan is for the transition and whether the passed-through price changes.
- If the invoice is yours, make the change outside peak season. Don't switch currencies in the middle of Black Friday or at month-end when you're closing the budget.
- Freeze one reference month. Export your volume by category for September 2026, in reais — the last month before the new charge. Without that you can't separate the effect of the new charge from the effect of having sent more messages.
- Notify accounting. The document changes, the entry changes, the way the cost gets recognized changes. Better they know beforehand.
- Revisit the estimate against Meta's current price table.
And what about whoever operates through QR code?
Whoever connects WhatsApp through QR code receives no invoice from Meta, and none of this article applies to them: there's no per-message fee, because there's no official API contract behind it. The channel's cost is the platform's monthly fee and nothing else. In exchange, there's also no visibility package that comes with an official account.
| WhatsApp via QR code | Official WhatsApp API | |
|---|---|---|
| Meta's per-message invoice | Doesn't exist | Exists, per delivered template |
| Channel cost | Just the platform's monthly fee | Monthly fee + per-message rate |
| Per-number quality rating | Doesn't exist | Exists, calculated over the last 7 days |
| Warning before restriction | Doesn't exist: the regular app can block with no warning | Email warning, with a deadline to fix things |
| Formal appeal | Doesn't exist | Exists |
It's a legitimate trade-off, and the right answer depends on your volume and how critical the channel is to your revenue. If you're still weighing that decision, it's worth reading when not to migrate to the official API.
On CRPRO you operate both ways — and we help you look at the invoice, so you know where you're starting from. Plans are here.
Frequently Asked Questions
Do I need to switch to BRL billing right now?
No. It's been available for opt-in since July 1, 2026 and becomes mandatory by June 30, 2027. But if Meta's invoice is yours, make the switch at a quiet time and keep a reference month from before the new charge, so the comparison isn't mixed with a currency change.
Will billing in reais make my bill cheaper?
Not directly. The per-message rate is the same. What changes is that the dollar's daily swings and the cost of operating in a foreign currency come off your bill. Whether that means savings depends on your payment method and your company structure — ask your accountant.
Does billing in reais freeze the message price?
No. Meta can adjust its rate tables in any currency. What disappears is the currency swing entering your invoice month to month.
I already pay my CRM in reais. Does this affect me?
Probably not. If the vendor buys Meta's volume and passes it to you in reais, the currency exposure was already theirs. Confirm it anyway: some platforms charge the monthly fee in reais and pass through Meta's rate converted, in which case the source currency still matters.
Where do I find the service-message rate?
In Meta's current price table. This article quotes no figure for it; any exact figure circulating without citing that table is a guess.
Does changing the invoice's currency affect the number's ban risk?
No relationship. A block depends on opt-in, message quality, and recipient reports. What the official API gives you, and QR code doesn't, is visibility and due process over that risk — per-number quality rating, calculated over the last 7 days, and a formal appeal. Not immunity.