WhatsApp API starts charging for customer replies, and tap-to-pay Pix loses its R$500 cap

Two changes on October 1, one common theme: the cost of talking to customers and charging them

On October 1, 2026, two things changed at the same time, and both affect how your company talks to customers and gets paid by them. The first: the official WhatsApp API started charging for service messages, meaning the replies a business sends when the customer starts the conversation. The second: tap-to-pay Pix (Pix is Brazil's instant payment system) no longer has the fixed R$500 cap per transaction.

They look like news from different worlds, one about customer service and the other about payments. But think about the path of a small sale: the customer messages you on WhatsApp, asks a question, places the order, and pays. That whole path changed last week, and anyone running a small business needs to know both changes.

In this article, we explain each one without jargon, run the numbers with real figures, and leave you with checklists of what to verify. In August, we covered another billing change, Meta's own AI agent, which started charging per token. This one is a different subject: charging for ordinary replies on the API, which affects far more people.

One caveat: this article offers general information. Prices, vendor rules, and card-machine behavior change, so confirm the details of your own case before deciding.

Who is affected by the WhatsApp charge, and who is left out?

The charge applies only to companies that use the official WhatsApp Business API, usually connected through a CRM or a chatbot. It started at 12:00 a.m. on October 1, 2026, in the account's time zone. The free WhatsApp Business app and regular WhatsApp are unchanged, according to Forbes Brasil.

If you handle customers from your phone, opening the app and replying by hand, relax: nothing changes for you. The WhatsApp Business app is still free, and so is regular WhatsApp.

The change hits those who use the API. How do you know if that's you? Some common signs:

• You use a customer service platform where several agents reply from the same number.
• A chatbot answers on its own, with an options menu or with artificial intelligence.
• Your CRM or online store sends automatic order notices through WhatsApp.
• Whoever set up the system talked about the "official API" or a "WhatsApp provider."

If you ticked any of these, your company is probably on the API. If you're unsure, ask your system vendor. It's a simple question, and the answer determines everything else in this article.

What is a "service message"?

A service message is a reply the business sends inside a conversation the customer started. If the customer asks "has my order arrived?" and the bot or the agent replies, that reply is a service message. Until September, these replies inside the customer service window were free. Now they cost money, after a monthly allowance.

How much does it cost to reply to a customer on the API?

Each number connected to the API gets 1,000 free service messages per month. Charging starts at message 1,001, at R$0.035 each, according to Forbes Brasil, for accounts billed in reais. That is equivalent to US$0.0068 and is the same rate charged for utility and authentication messages.

It's worth detailing the allowance rules, because they determine your bill:

• The allowance is per connected number, not per company.
• It resets every month.
• What's left over doesn't carry forward. If you used 300 messages, you don't get 700 of credit for the next month.
• Charges only show up after the 1,000 run out.

On the price: Tribuna de Jundiaí and Canaltech mention something between R$0.035 and R$0.04 per message. Meta's pricing page doesn't list a fixed value; it only says charges follow the "published rates." That's why we work here with Forbes's R$0.035, but confirm the exact value on your vendor's invoice.

The examples published by the press

Forbes Brasil published three scenarios that help size things up:

• A company with about 800 messages per month pays R$0, because it stays within the allowance.
• A company with 5,000 replies per month pays for 4,000 of them, which comes to about R$140.
• An e-commerce store with 50,000 automatic replies per month pays about R$1,715.

Tribuna de Jundiaí presented two other references: 10,000 billed messages cost about R$350, and 100,000 billed messages cost about R$3,500.

Notice one thing: whoever is in the first scenario feels nothing. The problem shows up for those who have grown, or those with a "chatty" chatbot.

Doing the math for your case

The formula is simple: (messages in the month minus 1,000) times R$0.035. Here are two hypothetical examples, calculated with the R$0.035 rate and the 1,000 free messages.

Hypothetical example 1. A store that sends 2,500 service messages per month. After subtracting the 1,000 free ones, 1,500 are billed. 1,500 times R$0.035 comes to R$52.50 per month.

Hypothetical example 2. A clinic with 20,000 service messages per month. That leaves 19,000 billed. 19,000 times R$0.035 comes to R$665 per month.

Neither amount breaks a business. But it's a cost that didn't exist in September, it's recurring, and it grows along with conversation volume. And growing conversation volume is usually good news, as long as the math keeps working.

Why does a chatbot that sends several short messages cost more?

According to Forbes Brasil, chatbots that split one reply into several short messages generate several charges. The charge is per message sent, not per conversation or per question answered. A bot that replies in three little bubbles costs three times as much as one that replies in a single bubble, once the allowance runs out.

Plenty of people set up the bot this way on purpose, because three short messages feel more "human" than one block of text. Before, that cost nothing. Now it does.

See the effect in a hypothetical example, with the R$0.035 rate and the 1,000 free messages. A store serves 600 customers per month, and each one receives 4 replies from the bot. If each reply is split into 3 messages, that's 7,200 messages per month. After subtracting the 1,000 free ones, 6,200 are billed, or R$217.00.

If the same bot delivered each reply as a single consolidated message, it would be 2,400 messages. After subtracting the 1,000 free ones, 1,400 are billed, or R$49.00. The difference is R$168 per month, without losing a single customer and without changing the content, only the format.

How to consolidate without making the text heavy

A single reply doesn't have to be a wall of text. Some practical ideas:

• Use short paragraphs and blank lines within the same message.
• Put the most important information on the first line.
• Use simple lists, one item per line, instead of one message per item.
• If a question has many possible answers, offer a menu instead of dumping everything.
• Ask the customer what they want before explaining everything, so you don't spend messages on what they didn't ask for.

In our experience, most customer service flows have more messages than the customer needs. Trimming them usually improves the conversation, on top of making it cheaper.

What stays free on WhatsApp?

Messages the customer sends remain free, and so do conversations started by "Click to WhatsApp" ads within a free window. The length of that window varies by source; confirm it in Meta's documentation. Eligible governments and nonprofit organizations continue to pay nothing beyond the allowance until December 31, 2027, according to Meta.

To sum up what stays out of the bill:

• What the customer sends you isn't charged. The charge applies to what the business sends.
• Conversations that began from a "Click to WhatsApp" ad are free within a time window. Forbes and Tribuna de Jundiaí cite one length, while Meta's documentation describes another. Since the sources disagree, we won't commit to a number. Read Meta's documentation or ask your vendor before planning a campaign around it.
• Eligible governments and nonprofit organizations keep service messages free beyond the allowance until the end of 2027.

What about utility messages?

Here is a change that slips by unnoticed. Since July 1, 2025, utility message templates sent within the 24-hour window were free. Now they are charged from the first message, and they don't use up the 1,000 free ones. In other words, notices like "your order is out for delivery" or "your appointment is confirmed" may have started generating costs, and that cost runs separately from the allowance.

If your system sends a lot of automatic notices, this is a good point to audit.

What happens if the company has no payment method on file?

Meta states that companies without a payment method registered by September 30, 2026 may have their service messages interrupted once billing starts. The Digisac blog, a vendor in the sector (secondary source), says that messages beyond the 1,000 aren't delivered without that registration.

In plain English: the risk isn't just paying more, it's no longer being able to reply. If there's no payment method on file and the allowance runs out in the middle of the month, customer service can go silent on your busiest day.

The September 30 deadline has already passed. If you aren't sure a card or other payment method is on file, do this today:

1. Ask your vendor or technical contact who owns the WhatsApp Business account on Meta.
2. Confirm that a valid payment method is registered on that account.
3. Check that the card doesn't expire in the coming months and that its limit can handle the monthly charge.
4. Decide who receives the invoice notice, so the email doesn't land in an inbox nobody reads.

A detail that only shows up in practice: at many companies, the person who signed up for the system has left, and the account email belongs to someone who no longer works there. Worth checking.

Does third-party AI also count toward the bill?

Forbes Brasil states that AI replies made by third-party tools are charged as service messages, on top of the tool vendor's monthly fee. Meta's own agent, Meta Business Agent, is charged per token, as we explained in an earlier article. Meta's documentation, on the other hand, says the October 1 changes do not apply to "AI providers."

The two pieces of information don't fully match. So the prudent stance is to assume nothing and ask your vendor. One direct question settles it:

"Do the replies the AI assistant sends through my number show up on my Meta invoice as service messages? On top of your monthly fee, is there any other charge?"

Ask for the answer in writing. If the vendor says there's no extra charge, great. If they say there is, you already know you need to factor it in.

How to audit your WhatsApp customer service in one afternoon

Before changing anything, measure. The audit fits in one afternoon and answers one question: how many service messages does your number send per month, and how much of that is waste?

Step 1: pull the numbers

Ask your vendor (or open the system dashboard) for the total messages sent by the company over the last three months, broken down by type: service, utility, marketing, and authentication. If the report doesn't separate them, ask that it start doing so. Without that, the invoice will arrive and you won't know where it came from.

Step 2: compare with the allowance

Add up the service messages for each number. If you're comfortably under 1,000, the change doesn't weigh on you. If you're close or above, keep going. Remember that utility messages run on the side and don't consume the allowance.

Step 3: find the messages that didn't need to exist

Read 20 to 30 real conversations, start to finish. Look for:

• Repeated "one moment, I'll be right with you" messages.
• Replies broken into three or four bubbles.
• Confirmations that repeat what the customer already knows.
• Long welcome texts, sent every time the customer comes back.
• A customer who sends "ok" and the bot replies with yet another text.

Each of these is both cost and friction.

Step 4: multiply by the rate

Take the monthly volume, subtract the 1,000 free messages, and multiply by R$0.035. That's your reference cost. Then estimate how much it would fall with the fixes from step 3.

How do you redesign the flow without making customer service worse?

Redesigning the flow means adjusting what the bot sends, without losing quality. The golden rule is one complete reply per question. The fewer bubbles per conversation, the fewer charges after the allowance. But the goal isn't to cut at all costs: it's to remove what doesn't help the customer.

Some changes that tend to work:

• One consolidated reply per question. Merge what currently goes out in three bubbles.
• Menu before explanation. Offer short options and only then detail what the customer chose.
• Self-service outside WhatsApp. Order tracking, duplicate invoices, and opening hours can live on a page of your website, with a link in the message.
• Human handoff at the right moment. When the subject is delicate, passing it to a person avoids ten pointless message exchanges.
• A clear end to the conversation. If the customer replied "thanks," there's no need for yet another goodbye text.

A warning: don't cut so much that the customer gets lost. Service that saves messages but forces the customer to ask three times ends up costing more, because each extra question from the customer also generates a billed reply.

When it's worth taking long text out of WhatsApp

Information that rarely changes (return policy, price list, address) works well on a fixed page. You send the link once and save text. This also has a nice side effect: the information lives in one place, and you fix it in one spot, not in fifty canned replies.

Free app or API: which makes sense for your business?

The choice depends on volume and on how much automation you need. The WhatsApp Business app is free and isn't subject to the new charge. The API offers multiple agents on the same number, bots, and system integration, but now carries a per-message cost above 1,000 per month, on top of whatever the vendor charges.

Think of it this way:

The app still makes sense if:

• you handle few conversations per day;
• one or two people reply;
• you don't need a bot or system integration.

The API makes sense if:

• several people need to serve customers from the same number;
• you automate replies, order notices, or appointment scheduling;
• you need reports and history integrated with your CRM or online store.

There's an uncomfortable middle ground: the business that signed up for the API "because it was modern," but sends 400 messages a month. In that case, the new charge doesn't weigh, but the vendor's monthly fee may be weighing more than it should. Compare what you pay today with what you actually use.

The opposite also happens: the business on the app that has grown and keeps losing messages because only one person replies. There, the API can pay off even with the new rate, because the cost of losing a sale is greater than R$0.035.

In practice, the honest math adds up three things: the vendor's monthly fee, the messages billed by Meta, and your people's time. Looking only at the first gives an incomplete picture.

What changed with tap-to-pay Pix?

On October 1, 2026, tap-to-pay Pix stopped having the fixed R$500 limit per transaction. The legal basis is Central Bank Normative Instruction (IN BCB) No. 746, from June 2026. There is no new single cap in its place: what applies now is the limit the customer has set with their own bank.

In practice, a R$600 or R$1,000 tap-to-pay payment can now go through, as long as it fits within the customer's limit. Customers can ask their bank to raise or lower that limit, and banks must offer a way to manage it in their app.

The rule also applies to Pix by QR code, by key, and by Open Finance without redirection.

Is tap-to-pay Pix already widely used?

Not yet. According to Agência Brasil, via Tecnoblog (single source), there were about 2 million transactions in August 2026, equivalent to 0.06% of all Pix. The feature has existed since February 2025, and adoption remains small.

That changes the size of the urgency. It's not the time to rush and overhaul your whole operation. It's the time to understand what exists, because the topic tends to come up in conversations with customers and with your card-machine company.

What needs to be in place for it to work

Paying by tap requires two sides to be ready:

• The merchant needs a card machine or terminal that accepts tap-to-pay Pix. Banks and card-machine companies aren't required to offer it.
• The customer needs a phone with NFC, the tap technology.

According to Tecnoblog, Google Wallet and Samsung Wallet support it. Apple Wallet doesn't. So an iPhone customer, for now, is left out of this method.

What to check before accepting larger amounts by tap

Without the R$500 cap, customers can pay more in a single tap. Before you promote that, a practical check is worth it: your terminal supports the feature, your team knows how to run it, and the customer knows their own limit. Here is some general advice, without inventing rules.

A checklist for the register:

1. Ask your card-machine company whether the terminal accepts tap-to-pay Pix, whether it's enabled on your account, and whether the new scenario changes anything for you. Don't assume.
2. Test it for real. Make a small payment with your own phone and confirm the money shows up where it should.
3. Train whoever works the counter. The person needs to know how to explain to the customer what to do when the payment doesn't go through.
4. Understand declines. If an R$800 payment is declined, the most likely cause is the customer's own limit, which they adjust with their bank. It's not a defect in your machine.
5. Have a plan B. Keep another way to charge (Pix by QR code, card) at hand, so the sale doesn't stall.
6. Check reconciliation. Verify that the payments show up in your statement and in your bookkeeping system the way you expect.
7. Communicate carefully. Only tell customers you "now accept larger amounts" after testing.

We won't get into fees, terminal prices, or fraud risk here, because those vary by company and aren't something we can state in general terms. Ask your vendor, in writing.

Which common mistakes will cost you the most with these two changes?

Mistakes usually come from assumptions, not bad management. Those who assume that "nothing changes for me" or that "this is for big companies" tend to find out late. The most frequent ones are below.

On WhatsApp:

• Thinking the change applies to the regular app. It doesn't. It only affects the API.
• Ignoring the payment method. The risk is a service interruption, not just the invoice.
• Forgetting utility messages. They are now charged from the first message and don't use up the allowance.
• Letting the bot split everything into little bubbles. Every bubble counts.
• Committing to a free-window length without checking. The sources disagree, so a campaign decision calls for reading Meta's documentation.
• Not asking the AI vendor. The source says one thing and the documentation says another.

On tap-to-pay Pix:

• Promoting it before testing. If the card machine doesn't support it, the promise turns into embarrassment at the register.
• Forgetting iPhone customers. Apple Wallet isn't supported, according to Tecnoblog.
• Blaming the machine for a decline. Often it's the customer's limit.
• Overestimating adoption. It's 0.06% of all Pix, according to Agência Brasil via Tecnoblog.

Notice a pattern: nearly all of them are solved with one question to the vendor and one hour of testing.

Quick questions

Has the WhatsApp Business I use on my phone started being charged?

No. The charge applies only to companies using the official WhatsApp API, generally connected to a CRM or chatbot. The free WhatsApp Business app and regular WhatsApp weren't affected, according to Forbes Brasil.

How many messages are free and how much does it cost after that?

Each number connected to the API has 1,000 free service messages per month. From message 1,001 on, Forbes Brasil reports R$0.035 per message, for accounts billed in reais. The allowance resets every month and what's left over doesn't carry forward.

What happens if I haven't registered a payment method?

Meta says companies without a payment method registered by September 30 may have their service messages interrupted. Register one as soon as possible and confirm with your vendor how this works on your account.

Does tap-to-pay Pix now have no limit at all?

Not quite. The fixed R$500 cap is gone and no other single cap replaced it. What applies now is the limit the customer has with their bank, and they can ask to raise or lower it. That's why a R$1,000 payment may go through for one customer and be declined for another.

Do I need to replace my card machine?

Not necessarily. To accept tap-to-pay Pix, the terminal must support the feature and the customer's phone must have NFC. Banks and card-machine companies aren't required to offer the service, so ask your vendor before any replacement.

Can iPhone customers pay by tap?

According to Tecnoblog, Google Wallet and Samsung Wallet support tap-to-pay Pix, and Apple Wallet doesn't. That customer can still pay by QR code or by key. It's worth keeping those options always available.

Where Diglion comes in

Diglion helps small and mid-sized businesses audit their WhatsApp customer service: we measure how many service and utility messages your number sends per month, point out where the bot splits replies unnecessarily, rewrite the flow for consolidated replies, and work out with you whether it makes more sense to stay on the API or go back to the app, before the invoice arrives.

Sources consulted

• Forbes Brasil, Responder cliente no WhatsApp passa a ter custo para empresas a partir de hoje, retrieved 2026-10-06.
• Meta for Developers, WhatsApp Business Platform: updates to pricing, retrieved 2026-10-06.
• Tribuna de Jundiaí, WhatsApp Business será pago a partir de outubro: mensagem assusta pequenos negócios, mas cobrança não funciona como parece, retrieved 2026-10-06.
• Canaltech, API do WhatsApp terá cobrança por mensagens de serviço: entenda, retrieved 2026-10-06.
• Tecnoblog, Pix por aproximação deixa de ter limite de R$ 500: agora vai?, retrieved 2026-10-06.
• Agência Brasil via DGABC, Pix por aproximação deixa de ter teto fixo de R$ 500, retrieved 2026-10-06.
• Correio da Manhã, Pix por aproximação deixa de ter teto de R$ 500, retrieved 2026-10-06.