WhatsApp for businesses in Mexico 2026: pricing, CFDI, cash payments and what works

Why do Mexican businesses run orders through WhatsApp?

A Mexican shop, clinic or service business that already answers customers on WhatsApp tends to run most of the sale there: the question, the quote, the bank details for the transfer, the “it shipped” message and, at the end, the invoice. Each of those steps is a message someone types by hand on one phone. Moving to the WhatsApp Business Platform turns them into templates you can send automatically, track, and connect to the systems that hold your orders, payments and invoices.

Every sale ends in a CFDI

In Mexico the sale is not finished when the money arrives. The business also issues a CFDI, the electronic invoice defined by SAT. That makes the invoice one more message the customer expects, next to the order confirmation and the payment request, and it is usually the one that takes the most manual work.

What businesses connect WhatsApp to

The WhatsApp side is only half of the workflow. The other half lives in the systems that already run the business:

• the store or order system, which knows when an order is placed, paid or shipped;
• the bank or payment provider, which receives the SPEI transfer, the card payment or the cash payment and knows when it has landed;
• the invoicing system, which issues the CFDI;
• the courier or delivery team, for cash-on-delivery orders;
• the calendar or booking tool, for clinics, salons and services.

The rest of this article covers the cost, the invoice, the payment flows, the consent rules and the order in which to automate.

How much does WhatsApp Business cost in Mexico in 2026?

Since 1 July 2025, Meta charges WhatsApp Business Platform messages per message. The rate depends on two things: the message category and the country calling code of the recipient’s number. A message to a +52 number is billed at the Mexico rate, wherever your business is based.

Mexico rates by category

Meta’s rate card, effective 1 October 2026, in USD per delivered message (as of 1 November 2026):

The category is what drives the cost: a Marketing template costs several times a Utility one. WACRM applies 0% markup on Meta’s message fees; Meta bills your WhatsApp Business Account directly, separate from your WACRM plan (see WACRM pricing for the plans). To estimate a month of messages, use the message pricing calculator, and see WhatsApp message prices by country for the other markets.

Free service messages

Every business phone number gets 1,000 free service messages a month; Meta charges from the 1,001st. Delivery beyond that free tier needs a payment method on the WhatsApp Business Account. The free service messages guide shows how to add one at Meta.

Paying Meta in pesos

Meta’s rate card says that as of 1 July 2026, 16 currencies are enabled on the WhatsApp Business Platform, and lists the Mexican peso (MXN) as launched on 1 January 2026, with its own list-rate files. The currency is chosen when the messaging account is created and cannot be changed afterwards (Meta offers Currency Migration APIs for moving accounts). Meta’s page does not say which businesses may open an MXN account, so MXN is one of Meta’s billing currencies, not a promise that every Mexican business is billed in pesos. Check the currency before you create the account.

Can you send the CFDI on WhatsApp?

The CFDI is Mexico’s electronic invoice. SAT publishes its format as Anexo 20. According to SAT, the CFDI was updated to version 4.0 from 1 January 2022, and since 1 April 2023 version 4.0 is the only valid one.

Treat WhatsApp as a copy and notification channel for the CFDI:

• send an “invoice issued” Utility template once the CFDI is issued, with the order number;
• attach the files or a download link, if your invoicing system produces them;
• keep your normal invoice delivery (email or your invoicing portal) in place.

SAT’s CFDI 4.0 frequently asked questions do not say how a CFDI must be delivered to the customer. Whether a WhatsApp message on its own counts as delivery is to be confirmed with SAT, so do not drop your existing delivery method on the strength of a WhatsApp send.

What CFDI 4.0 requires

SAT lists these among the main CFDI 4.0 changes. They matter for WhatsApp because the data often arrives in the chat: the customer sends their tax details as a message, and someone copies them into the invoicing system.

• The receiver’s name or company name is mandatory.
• The receiver’s tax regime (“Régimen fiscal del receptor”) and tax address (“Domicilio fiscal del receptor”) are mandatory.
• An “Exportación” field states whether the invoice covers a definitive or temporary export.
• Fields for the global invoice: periodicity, months and year.
• An “Objeto del impuesto” field.

SAT’s CFDI 4.0 filling guide on the Anexo 20 page is dated 16 January 2026. A WhatsApp flow can collect these details before the invoice is issued, for example by asking the customer to confirm their tax data in a reply, but the invoice itself is still produced by your invoicing system.

Which payment flows work with WhatsApp in Mexico?

WhatsApp does not move the money in any of these flows. It carries the request, the reminder and the receipt, and the payment happens at the bank, the store or the door.

Bank transfer by SPEI (CLABE, Dimo, CoDi)

SPEI®, Mexico’s interbank electronic payment system, is administered and operated by Banco de México. Banxico describes it as a real-time settlement system, in operation since 13 August 2004, running 24/7. It lets participants send and receive electronic transfers between accounts at different financial institutions, in pesos, within Mexico. After the transfer, the receiver can look up the Comprobante Electrónico de Pago (CEP).

To send a transfer, Banxico’s MI SPEI page says the payer needs the beneficiary’s CLABE (18 digits), or a debit, electronic-payment-funds or credit card number (16 digits), and the beneficiary’s institution. There are two alternatives:

• Dimo®: the payee links a 10-digit mobile number to their account in their own bank’s app, with their consent, and can then be paid by sharing only that number. Banxico says it receives no personal data in the linking process.
• CoDi®: a platform developed by Banco de México for payments and collections by electronic transfer from mobile phones, 24x7, using QR codes and NFC. The collector creates a payment request, the payer accepts it, and CoDi notifies both of the confirmation. Banxico states that CoDi operations carry no additional fees.

For a WhatsApp flow, that means a “payment details” template can carry your CLABE or Dimo number, the amount and an order reference, so the customer does not have to ask for them again. SPEI, Dimo and CoDi are services the customer’s bank and yours provide. WACRM does not connect to Banxico; it sends the message, and your bank or payment system tells you when the transfer has arrived.

Cash payment references

Some customers pay for online orders in cash. If your payment provider offers payment at a convenience store (OXXO stores are one example), it issues a payment reference for the order. A Utility template can send that reference and its expiry date, and a reminder can follow before it expires. How references, expiry and payment confirmation work is set by your payment provider, so check its documentation. WACRM has no native connector for any payment provider; the provider’s “paid” notice reaches WACRM through the API, set up as part of the build.

Cash on delivery

When the customer pays at the door, a confirmation before dispatch avoids sending a parcel that will not be accepted. The COD confirmation guide covers that flow: a Utility template with the order and the amount, a reply to confirm or cancel, and a person on the orders that need a call.

What consent do you need?

Mexico’s private-sector data-protection law is the Ley Federal de Protección de Datos Personales en Posesión de los Particulares (LFPDPPP). The current text on the Orden Jurídico Nacional is a new law published in the Diario Oficial de la Federación on 20 March 2025, in force the day after publication, which repealed the law of 5 July 2010. It names the Secretaría Anticorrupción y Buen Gobierno as the authority. Here is what it says, in summary, for WhatsApp messaging:

• Consent (Art. 7): processing of personal data is subject to the data subject’s consent, except where the law provides otherwise. Consent can be express (verbal, written, electronic or other unequivocal means) or tacit (a privacy notice made available and no objection); tacit consent is valid as a general rule unless a rule requires express consent.
• Financial data (Art. 7): financial or patrimonial data need express consent. Keep bank details out of free-text chat notes where you can.
• Revocation (Art. 7): consent can be revoked at any time.
• Sensitive data (Art. 8): need express written consent. Clinics in particular should keep health details out of marketing lists.
• Privacy notice (Art. 15–16): tell people who you are, what data you process and why, how to limit its use, how to exercise their ARCO rights, and how changes to the notice are communicated. When data are collected electronically, the simplified notice is provided.

On top of the law, Meta’s opt-in rules ask you to make clear that the person is opting in to WhatsApp messages from your business, name the business, comply with the law that applies to you, and give and honor clear opt-out instructions.

The LFPDPPP leaves it to the applicable rules whether marketing consent must be express or tacit, so ask counsel which applies to your messages. WACRM records opt-outs per channel and gates template and broadcast sends on consent; the opt-out and consent guide shows how.

What should a Mexican business automate first?

Start with the messages a customer expects after doing something, because they are Utility messages and cost the Utility rate. Meta’s template categorization says Utility templates follow up on a user action and must be non-promotional; a template that mixes utility and marketing content is categorized as Marketing. So keep the discount code out of the payment reminder.

A sensible order:

1. Order confirmation when the order is placed, with the total.
2. Payment details: CLABE or Dimo number for a SPEI transfer, or the cash payment reference, with the order number.
3. Payment reminder before the reference expires or the order is cancelled, stopped as soon as the payment lands.
4. COD confirmation before dispatch, for cash-on-delivery orders.
5. Invoice issued once the CFDI is issued, with a request for the customer’s tax data first if it is missing.
6. Delivery update when the order ships.

Keep a person on the exceptions: a transfer for the wrong amount, a refund, a customer who replies with a question instead of paying, a COD order that comes back. Leave promotions until the Utility flows are running, and send them only to contacts who opted in to marketing.

Do it yourself

If your orders come from a connected store and you are comfortable writing templates, you can do this in Workspace: get templates approved (see template approval), then create automations for New order, Order fulfilled, Cart abandoned and Booking reminder. Keep your phone number in the app with coexistence if you want to.

When a setup service pays off

The payment and CFDI parts sit in your bank, payment provider and invoicing system, so they need a connection built to WACRM’s API and webhooks. If you would rather have that done for you, Setup Commerce connects your store and builds your first order templates, and Custom Development builds the payment and invoice connections. If you only need the number connected, Quick Setup covers it. For shops, see WACRM for online shops; for couriers and delivery teams, WACRM for delivery. Selling in Brazil too? The Brazil country insight covers Pix and NF-e, and the Pix payment reminders insight walks through a reminder sequence.

How do WACRM and Netbase JSC set it up?

Illustrative scenario, not a customer case: an online shop in Guadalajara that takes orders on WhatsApp, is paid by SPEI transfer, by cash at a store through its payment provider or on delivery, and issues a CFDI for every order.

How the pieces fit in WACRM:

• Automations have 5 triggers and 4 actions. The “Send a template” action checks the contact, AI pause, consent and template approval before it sends anything. “Propose an agent action” always waits in the approval queue for a person.
• Webhooks send message.inbound and message.status events to your systems, so a reply or a failed delivery reaches the team.
• API and MCP: the send_template call takes an Idempotency-Key, so a retried reminder call with the same key never sends twice. See the API and MCP quickstart.

Setup steps with Netbase JSC: connect the number (or keep it in the app with coexistence), get the Utility templates approved, connect the store, then connect the payment provider and invoicing system through the API. Tell us which systems you use on the contact page, or read about Netbase JSC.