WhatsApp Commerce in India: UPI Payments, Flows and Order Automation

WhatsApp commerce in India has moved past "send us your order on WhatsApp and we will share a UPI ID". Businesses can now show a catalogue, collect structured details with in-chat forms, take UPI and card payments without the customer leaving the chat, and send confirmations and delivery updates automatically.

For a retailer, distributor, D2C brand, school, salon chain or service business, this matters because the customer is already on WhatsApp. Every extra hop, to a website, a payment page or a phone call, loses some of them.

This guide explains the building blocks that exist in 2026 (the Payments API, WhatsApp Flows, catalogues and templates), what they cost, the policy limits on AI, and an architecture for order automation that reconciles cleanly with your accounts. It is written for businesses in general; for hospitals and clinics, see our separate guide to WhatsApp automation for hospitals and clinics.

Why WhatsApp commerce works in India

Two habits make India unusual. Customers prefer to talk to businesses on WhatsApp, and they pay with UPI, which processes billions of transactions a month and keeps setting new records in 2026. Combining the two removes the main friction points of mobile commerce: app downloads, account creation and card entry.

Meta has leaned into this. In September 2025 it announced India-specific features including payments inside the WhatsApp Business app for small businesses and pilots of Business AI for automated support. For larger businesses on the WhatsApp Business Platform (the API), payments and structured forms are available through official APIs.

The building blocks

In-chat payments: how the Payments API works

Meta's Payments API for India lets a business send an order_details message: an itemised order summary with a Review and Pay button. The customer can pay through any UPI app on their phone, and, through supported payment gateways, by cards, net banking and wallets.

There are two main integration patterns:

• Payment gateway integration: you link a supported payment gateway account in WhatsApp Manager as a "payment configuration". Your system sends the order_details message referencing that configuration, the gateway processes the payment, and you receive the status by webhook.
• UPI intent with your own gateway: your server obtains a UPI payment intent from your gateway and builds the order_details message around it. Meta recommends a dynamic VPA flow for this.

A few practical details matter:

• Each order carries a reference ID. Use your own order number and keep it unique, because it is how you reconcile.
• If the payment configuration name is wrong or missing, the customer receives the order but cannot pay. Test this in every environment.
• Payment status should be confirmed from the gateway's signed webhook or API, never from a message in the chat or a screenshot.

WhatsApp Flows: structured data without a website

WhatsApp Flows are native, multi-screen forms that open inside the chat. They replace the "please send your name, address, pincode and preferred time" back-and-forth with proper fields, dropdowns, date pickers and validation.

Flows can be static or dynamic. A dynamic flow calls your endpoint (a data_exchange action) to fetch the next screen's data, such as available delivery slots for a pincode or stock for a size. Requests to your endpoint are encrypted, and your endpoint must respond within a few seconds, so cache slow lookups.

Good uses of Flows:

• Delivery address capture with pincode serviceability checks.
• Appointment or slot booking for services.
• Product customisation (size, colour, engraving text).
• Lead qualification and simple KYC details.
• Feedback and returns requests.

Pricing: what WhatsApp commerce costs

Since 1 July 2025, Meta charges per delivered template message rather than per 24-hour conversation. Rates depend on the recipient's country and the template category: marketing, utility or authentication. Replies within the 24-hour customer service window, which opens when the customer messages you, are free. Meta may update rates at the start of each quarter, and India has had rate changes since the switch, so check the current rate card before you build a cost model.

What this means for design:

• Customer-initiated conversations are cheap. Make it easy for customers to message you first: click-to-chat links, QR codes on packaging, ads that open WhatsApp.
• Order and delivery updates are utility messages. Keep them strictly transactional; promotional content in a utility template can lead Meta to recategorise it.
• Marketing messages cost the most and affect quality rating. Send them only to opted-in customers, segmented and capped.

Add your Business Solution Provider's fees (if you use one), payment gateway charges, and hosting and development costs to get the real total.

AI on WhatsApp: what is allowed in 2026

Meta changed the WhatsApp Business Solution terms so that general-purpose AI chatbots, assistants that answer open-ended questions on any topic, are no longer allowed on the Business Platform. The rule applied to new users from October 2025 and to all users from 15 January 2026; services such as ChatGPT and Copilot left the platform as a result.

Task-specific AI remains allowed: a bot that helps customers find products, track orders, book slots or resolve support issues for your business. In practice, that means:

• Scope the assistant to your catalogue, policies and order data.
• Refuse or hand off off-topic requests rather than answering them.
• Use retrieval over your own content, not open-ended generation.
• Hand off to a person for complaints, refunds and anything sensitive.

Our guide to AI customer support operations covers hand-off design and quality checks in more depth.

Architecture for WhatsApp order automation

A reliable setup has five parts:

1. Messaging layer: the WhatsApp Cloud API, directly or through a provider, receiving messages and sending replies.
2. Conversation service: your logic for menus, Flows, AI assistance and hand-off to agents.
3. Order service: creates orders with a unique reference ID, holds stock, calculates GST and delivery charges.
4. Payment integration: sends order_details, receives the gateway webhook, verifies signature and amount, marks paid.
5. Fulfilment and accounts: pushes paid orders to your ERP or accounting system, issues GST invoices (and e-invoices where required), triggers shipping and sends utility updates.

Everything between these parts should be event-driven, with idempotent handlers, because webhooks are delivered at least once and sometimes out of order. Our guide to webhook reliability explains the patterns, and e-invoicing automation covers the GST side.

Reconciliation: the part most setups skip

Payments that cannot be matched to orders create month-end pain. Build reconciliation in from day one:

• Use one reference ID across WhatsApp, the gateway and your ERP.
• Store the gateway's transaction ID and UTR against the order.
• Run a daily job that compares gateway settlements with orders marked paid.
• Flag partial payments, duplicate payments and refunds for review.
• Keep refunds in the same system that issued the charge.

Journeys that work well, by business type

For each journey, measure the funnel: conversations started, Flow completed, payment initiated, payment succeeded, order fulfilled. The biggest drop-off is usually between payment initiated and payment succeeded, and it is often fixable with clearer order summaries and a single, well-timed reminder.

Compliance and consent

• Opt-in: collect clear consent for WhatsApp marketing messages and honour opt-outs immediately.
• DPDP Act: names, phone numbers and addresses are personal data. Publish a notice, limit retention and secure your logs.
• Payments: card data should never touch your servers; let the gateway handle it.
• GST: issue proper tax invoices; for businesses above the e-invoicing threshold, B2B invoices need an IRN.

How to start

1. Pick one journey: reorders for existing customers are usually the easiest win.
2. Get access to the WhatsApp Business Platform with a verified business and display name.
3. Set up a payment gateway that supports WhatsApp payment configurations.
4. Build the order service and payment webhook handling first, then the chat experience.
5. Add one Flow for address or slot capture.
6. Launch to a small customer segment, monitor drop-offs and payment success, then expand.

Algon builds WhatsApp commerce and automation on top of workflow automation and web application development, with Node.js services handling webhooks and payments.

Conclusion

WhatsApp commerce in India is now a real channel with official building blocks: in-chat UPI payments, structured Flows, catalogues and per-message pricing that rewards customer-initiated conversations. The opportunity is large, but the work that decides success is unglamorous: verified payment webhooks, idempotent order handling, clean reconciliation and a tightly scoped assistant that hands off to people. Get those right, and chat becomes one of your most efficient sales channels.