WhatsApp for Transactional Notifications: Orders, Payments, OTPs and Bookings

Transactional notifications are the messages customers actually want: *your order is confirmed*, *your payment was received*, *your appointment is tomorrow*, *here is your login code*. On WhatsApp they arrive in the app customers already check all day, and they cost a fraction of a marketing message — as long as they are set up in the right template category.

This guide is a map of transactional messaging on the WhatsApp Business API: the two categories that cover it, what separates them from marketing, and links to ready-to-adapt templates for each common notification.

Using the WhatsApp API for transactional notifications

A transactional notification is almost always sent first by the business — the customer placed an order hours ago, or asked for a code seconds ago — so there is usually no open 24-hour window. That means it must be an approved template. Meta has two categories for this kind of message:

Both cost about a seventh of a marketing message in India (₹0.8631). That gap is why category matters so much — and why Meta checks it closely.

What keeps a notification in the utility category

Meta's rule has two parts, and a utility template must meet both:

1. It is non-promotional — no offers, recommendations, “shop now” or persuasive wording.
2. It is specific to the customer or essential — about their own order, booking, account or payment, or a critical alert such as a safety notice.

Mixed messages count as marketing. An order confirmation with “use code SAVE10 on your next order” at the bottom is a marketing template, billed at the marketing rate. Since April 2025, when Meta judges a utility submission to be marketing, it approves it as marketing; you have 60 days to ask for a review.

Ready templates for common transactional notifications

Each of these pages has English and Hindi versions written to stay in the utility category, with notes on variables and buttons:

Browse the full WhatsApp template library for more — reminders, cancellations, refunds, fee reminders and class updates.

WhatsApp Business API for two-factor authentication

One-time passwords — for sign-up, login, a second factor, a password reset or confirming a sensitive change — use authentication templates. They work differently from every other template:

• Meta writes the message. The body is fixed: “*123456* is your verification code.” You cannot add your own sentences.
• You choose the options: an optional security line (“For your security, do not share this code.”) and an optional expiry line, from 1 to 90 minutes.
• You choose how the code is delivered: a copy code button, one-tap autofill (the code fills itself into an Android app that has been set up for it), or zero-tap, where a set-up Android app reads the code without a button.
• Nothing else goes in. Offers, links to other pages and extra information belong in separate templates.

In India, authentication messages cost ₹0.115 each at Meta's rate. One detail for businesses based outside India: Meta charges a higher authentication-international rate (₹2.4971 on its INR rate card) when a business based in another country sends OTPs to Indian numbers.

OTPs need an automated sender

An OTP has to be generated and sent the instant the customer asks for it — by the same system that checks it. That means your login or sign-up system must be connected to the WhatsApp Business Platform directly and send the authentication template automatically. A team inbox, a person copying codes or a scheduled broadcast is the wrong tool for this.

WhatsApp Business API for event registration confirmation

Workshops, webinars, seminars, runs and conferences all need the same message the moment someone registers: *you are in, here is when and where, here is your registration number*. On WhatsApp this is a utility template, as long as it is only about that person's registration.

An example that stays utility:

“Hi {{1}}, your registration for {{2}} is confirmed. Date: {{3}}. Venue: {{4}}. Registration number: {{5}}. Please show this message at the entry desk.” — with a URL button to the venue map and a phone button for the organiser.

• Include a registration number. It makes the message clearly about this person's own registration.
• Leave out other events and early-bird offers. “Bring a friend for 20% off” turns it into marketing.
• Send changes as utility too. A new venue or time for an event they registered for is a genuine update.
• Invitations are different. Inviting people to an event they have not registered for is marketing.

On wbm.link, you can import registrations as a CSV — name, event, date and registration number as columns — and send the approved confirmation template as a broadcast. Questions from attendees come back into the shared inbox. See the event registration confirmation template for English and Hindi versions.

Transactional notifications and the 1 October 2026 change

Until 30 September 2026, a utility template sent while the customer already has an open window is free. From 1 October 2026, Meta charges utility templates inside the window too, at the same ₹0.115, and also starts charging service replies. Utility templates sent outside the window — the usual case for notifications — are priced as before. The details are in WhatsApp pricing change on 1 October 2026.

Checklist before you switch notifications to WhatsApp

1. Get opt-in at checkout, booking or sign-up — a checkbox or line that says you will send updates on WhatsApp.
2. Keep numbers in international format so they match WhatsApp accounts.
3. Write one template per event — confirmed, shipped, delivered — instead of one vague “update” template.
4. Check the category before submitting with the free template checker.
5. Estimate the monthly cost with the pricing calculator.
6. Decide who answers replies. Customers reply to notifications. Make sure those replies reach a person or a chatbot.