Billing customers on WhatsApp in 2026: what actually changed
By José Pedro · Co-founder of CRPRO
Billing a customer on WhatsApp means sending the charge through chat and receiving the money outside it — no card payment inside the conversation anymore. See the real instruments (Pix key, PSP link, Payments API), what COBV is, what changed in October 2026, and what consumer law forbids.
Billing a customer on WhatsApp in 2026 means sending the charge through the chat and receiving the money outside it: through a Pix key on the business profile, through a payment link from your provider (PSP), or through the Payments API. Billing on WhatsApp Business keeps working just fine — what changed is where the money lands. Card payment inside the conversation was discontinued on January 15, 2026. And no: Brazil's Central Bank hasn't authorized any "WhatsApp Pay" this year.
What's myth and what's fact in WhatsApp billing?
| What's going around | What it actually is |
|---|---|
| "The Central Bank authorized WhatsApp Pay in January 2026" | No such authorization happened. What happened in January was the opposite: card payment inside the chat was discontinued on 01/15/2026. |
| "Pix in chat costs 0.99% and card 2.98%" | Those numbers don't come from any published table. The rate you pay is your payment provider's (PSP), under the contract you signed — and Pix received by key is usually charged per transaction, not as a card-style percentage. |
| "Meta receives the money and marks the invoice as paid" | Meta isn't an acquirer and doesn't reconcile anything. It carries the message; your PSP and your own system are what process the payment and mark it paid. |
| "You can just blast the invoice to your whole list" | Billing is a business-initiated message. It requires opt-in and an approved template — and outside of that, cost and risk. |
The source is always the same: AI-written text copying other AI-written text, with no primary source underneath. The same rule that applies to API pricing applies here: any number that doesn't show up in a Meta or Central Bank document was made up. It's the same pattern as conversation-based pricing, retired in July 2025 and still republished as if it were current.
How do you actually receive payment through WhatsApp today?
1. A Pix key on the business profile. You publish the key and the customer copies it. Works for anyone selling low volume and handling it manually by hand. The limit is obvious: the key is static. It carries no amount and no order ID, and it notifies nobody when the payment lands. You reconcile by checking your bank statement.
2. A payment link from your PSP inside the message. The most common approach in Brazil. The link already carries the amount, the due date, and an identifier; the customer picks Pix, card, or boleto on the provider's page; and the PSP's webhook notifies your system when it's paid. It isn't native to WhatsApp.
3. Payments API. Brings the charge inside the conversation itself, with the order structured right in the message. The accepted methods and availability depend on the enabled provider — confirm with yours before designing the flow. It requires real integration work, and the money still flows through your PSP, not through Meta.
| Pix key on the profile | PSP link in the message | Payments API | |
|---|---|---|---|
| Effort to set up | Minutes | Low (simple integration) | High (real integration) |
| Amount and due date on the charge | No | Yes | Yes |
| Identifier per charge | No | Yes | Yes |
| Automatic reconciliation | No | Yes, via PSP webhook | Yes, via PSP webhook |
| Who processes the money | Your bank | Your PSP | Your PSP |
| Makes sense for | Low volume | Most operations | High volume and catalogs |
What is COBV and when does it replace a boleto?
COBV is the Pix charge with a due date, as defined by Brazil's Central Bank. When the conversation is about an installment, a monthly fee, or an overdue invoice, the right instrument isn't a loose Pix key — it's this one.
| COB (immediate Pix) | COBV (Pix with due date) | |
|---|---|---|
| Due date on the document | No | Yes |
| Interest, late fee, discount, and rebate built in | No | Yes, right in the QR code |
| Amount changes depending on the day the customer pays | No | Yes, with no manual recalculation |
| Typical use | One-off sale, pay-on-the-spot | Monthly fee, installment, overdue invoice |
It's what replaces the boleto in practice, with settlement in seconds. The second gain is the identifier: every COBV carries a txid that ties the payment to the contract, the installment, and the customer. That's what enables automatic reconciliation — and it's exactly what a static Pix key doesn't have.
Reconciliation is your problem, not Meta's
The most expensive mistake in this setup has nothing to do with fees. The correct flow has four points: your system generates the charge, the CRM sends the message, the PSP notifies the payment via webhook, and the collection cadence stops charging that customer. If the fourth point doesn't exist, the classic happens: the customer pays at 9:12am and gets "your invoice is overdue" at 10am. You didn't lose a message fee — you lost the trust of someone who just paid.
The check before any reminder is a single one: has this contract been marked paid since the last message? If it has, cancel. It's the same suppression discipline used in abandoned cart recovery.
Billing is a utility template — and mixing in an offer gets expensive
Billing is almost always a message you initiate, outside the 24-hour window: approved template, utility category. It isn't bureaucracy — on the official API, sending free-form text outside the window isn't even possible; the request comes back with error 131047.
The cost risk is in the classification. A due-date reminder is utility. If you slip a promotion into the middle of it, the template tends to get reclassified as marketing — and the order-of-magnitude difference in Brazil is large: marketing runs around US$0.0625 per delivered message (rate in effect as of August 2026), about R$0.32, against roughly US$0.0068 per utility or authentication message on the same date. That's nearly ten times more expensive per message sent, for the same reminder.
How much does billing cost since the October 2026 change?
Until September 30, 2026, the back-and-forth inside the 24-hour window was free. Since October 1, 2026, Meta charges per message for service messages and utility templates sent inside the window — and service is the only category with no volume discount. The service-message rate is in Meta's current price table; anyone quoting a figure without citing it is guessing.
This weighs more on billing than on the average case, because billing generates negotiation: a reminder that turns into "can I pay on the 20th?" opens a ten-to-twenty-message conversation. Free until September 30; not anymore. The impact by operation profile is in who feels October's charge the most.
How many billing messages can you send without burning the number?
| Moment | Message | Category | Note |
|---|---|---|---|
| Due date minus 3 days | Reminder with a link or COBV | Utility | Only for whoever hasn't paid yet |
| Due date (D0) | Due today, with the code ready to copy | Utility | One, in the morning |
| D+1 | Overdue notice, already showing interest and late fee in the COBV | Utility | No threatening tone |
| D+5 | Installment offer or a new date | Utility | This is where conversation — and cost — start |
| D+15 | Close out the WhatsApp cadence | — | Continue by phone or email |
Four touches resolve most cases of forgetfulness-driven non-payment. From the fifth on, the return drops and the risk rises: blocks and reports tank the quality rating — which Meta calculates over the last 7 days, weighting recent days more heavily (a window stated in Meta's documentation, in effect as of August 2026) — and can take the number down. It cuts both ways: a number on the official API also gets deactivated; the difference there is a quality score, a warning, and an appeal. To take this off your hands, see how to schedule a WhatsApp message.
What does the law forbid in WhatsApp billing?
Brazil's Consumer Protection Code is direct in Article 42: a customer in default can't be exposed to ridicule or subjected to embarrassment or threats. Article 71 makes abusive collection a crime. Translated to WhatsApp:
- Never bill inside a group, and never mention the debt anywhere someone else can read it.
- Never write to a relative, neighbor, boss, or coworker of the debtor.
- Don't use a profile photo, status, or broadcast list to expose who owes money.
- Respect business hours and stop when the person asks you to.
- Treat "I don't want to receive this anymore" as an immediate opt-out, no exceptions.
Billing is legitimate. Embarrassing someone isn't — and on WhatsApp, embarrassment turns into a report, which turns into risk for the number.
How to set this up in practice
- Pick the instrument by the type of debt: a Pix key for a one-off sale, COBV for anything with a due date.
- Wire your PSP's webhook into your CRM before writing the first message.
- Get two or three utility templates approved and resist putting an offer inside them.
- Set payment-based suppression as an eliminating rule in the collection cadence.
- Measure how many messages go out per resolved collection. That's the number that turns into cost.
The full breakdown of what the official API charges today is in how much the official WhatsApp API costs in 2026.
On CRPRO, you connect the number through the official API or through QR code and build the collection cadence with payment reconciliation tied straight to the contact — which is the part no bulk-sender solves.
Frequently Asked Questions
Can you still pay by card inside WhatsApp chat?
No. Card payment inside the conversation was discontinued on January 15, 2026. The current path is Pix or a payment link processed by your provider, with WhatsApp delivering the charge.
Did the Central Bank authorize WhatsApp Pay in 2026?
No. There was no such authorization in 2026, and the rates circulating in articles and AI-generated answers don't come from any primary source. What you pay is your PSP's fee.
What's the difference between COB and COBV in Pix?
COB is an immediate charge: a fixed amount, no due date. COBV is a charge with a due date and accepts interest, late fees, early-payment discounts, and rebates right in the document, with an identifier that enables automatic reconciliation. For monthly fees and installments, the right instrument is COBV.
How much does it cost to send a billing message through the official API?
Billing is a utility template, currently around US$0.0068 per delivered message in Brazil (about R$0.035; rate in effect as of August 2026). Marketing runs close to US$0.0625 per delivered message on the same date. Since October 1, 2026, service messages and utility templates inside the 24-hour window are also charged; the service rate is in Meta's current price table.
Can I bill someone on WhatsApp who never authorized contact?
You shouldn't. Meta's policy requires opt-in: the person needs to have given the number and authorized contact. In billing, that authorization is usually already in the contract or the sign-up form — what doesn't count is using a purchased list or a list scraped from a group.
Does Meta reconcile the payment for me?
No. Meta carries the message and doesn't act as an acquirer. Payment confirmation arrives through your provider's webhook and needs to be recorded in your own system, or the collection cadence keeps billing someone who already paid.