Pix payment reminders on WhatsApp: how Brazilian businesses automate collection

Why move payment reminders from manual chats to WhatsApp templates?

Pix is the instant payment system created by Banco Central do Brasil: money moves in seconds, any time, any day. Banco Central lists “facilitates reconciliation, automation and system integration” among its advantages. Paying is instant. Chasing a payment that has not come in still means someone scrolling a phone, copying a code into a chat and remembering who already paid.

Moving reminders to approved WhatsApp templates changes three things:

• the reminder goes out on time, from the system that knows the due date, not from someone’s memory;
• every message is the same approved wording, so it stays inside Meta’s Utility category;
• the sequence stops by itself when the payment provider reports the charge as paid.

This insight covers the Pix side and the WhatsApp side. For costs and the rest of the Brazilian picture, read WhatsApp for businesses in Brazil 2026. Selling in Mexico too? The Mexico country insight covers CFDI, SPEI and cash payments.

Pix Cobrança, Pix Automático or boleto: which should the message link to?

A reminder is only as good as the charge it links to. Banco Central describes the options like this:

Pix Cobrança is a Pix feature Banco Central created for businesses and professionals to manage and receive charges. With Pix Automático, the company sends the charge to the payer’s bank in the days before payment; the bank schedules it and notifies the payer. That means a Pix Automático customer already gets a notice from their bank, so your WhatsApp message is a courtesy, not the charge itself.

Two practical notes. Dynamic QR codes and batch charges are optional for Pix participant institutions, so check what your bank or payment provider supports. And Meta’s Payments API for Brazil lists dynamic Pix codes, payment links, boleto and payment request templates, but does not say who is eligible; plan on sending the Pix Copia e Cola code or payment link in a normal template.

Is a payment reminder a Utility or a Marketing message?

Meta bills per message by category and the recipient’s country calling code, and Marketing costs several times Utility. The Brazil rates are on WhatsApp message prices by country. So the category of your reminder template matters.

Meta’s template categorization says Utility templates follow up on a user action, must be non-promotional, and must be specific to the user or essential to them. Meta’s own Utility examples include “Reminder: Your monthly payment for {{service}} will be billed on {{date}}”. A template that mixes utility and promotional content is categorized as Marketing.

Wording that stays Utility

The examples are illustrations of wording, not approved templates. Submit your own for approval; the template approval guide walks through it.

Consent and opt-out

Meta’s opt-in rules ask you to make clear the person is opting in to WhatsApp messages from your named business, to comply with the law that applies to you, and to give clear opt-out instructions and honor them. In Brazil that law includes the LGPD (Lei nº 13.709/2018), overseen by ANPD. WACRM records opt-outs per channel; see opt-outs, consent and cost reports.

What does a reminder sequence look like?

Illustration, not a rule from Meta or Banco Central. Pick the timing that suits your customers and your contract.

1. Charge created. Your payment provider creates a Pix Cobrança with a due date for the invoice.
2. Charge sent. A Utility template sends the amount, the due date and the Pix Copia e Cola code or payment link.
3. Reminder before the due date. A short Utility reminder with the same code.
4. Reminder on the due date. The last automatic message.
5. Paid. The provider’s “paid” event cancels any reminder still scheduled and sends a thank-you template.
6. Still unpaid. The case goes to a person, who decides what happens next.

Every step after the first checks whether the charge is still open, so a customer who already paid never gets the next message.

Which steps can AI run, and which need a person?

In WACRM, the AI sends a reply on its own only when auto-reply is enabled, not paused, and auto-send is on for that conversation; otherwise its draft waits as a proposal. See AI reply drafts. For a payment conversation, keep auto-send off and let the team answer.

How do WACRM and Netbase JSC build it?

Before → After

Illustrative scenario, not a customer case: a language school that charges monthly fees.

Setup steps

WACRM has no built-in Pix or payment-provider trigger; its Automations triggers are New order, Order fulfilled, Cart abandoned, Inbound message and Booking reminder. The Pix events come from your payment provider and reach WACRM through the API, built as a Custom Development project:

1. Get the charge, reminder and thank-you templates approved as Utility.
2. Connect your payment provider’s “charge created” and “paid” events to WACRM’s API, which sends templates with send_template and an Idempotency-Key, so a retried call never sends twice (see the API and MCP quickstart and API and MCP).
3. Subscribe to WACRM webhooks (message.inbound, message.status) so customer replies and failed deliveries reach your system.
4. Use Automations with the Inbound message trigger to label payment conversations or open a ticket; “Send a template” checks contact, AI pause, consent and template approval before it sends.
5. Route exceptions to the team. “Propose an agent action” always waits in the approval queue.

For schools and clinics, see WACRM for education and WACRM for clinics. To scope your own setup, contact us.