WhatsApp Payments
WhatsApp Payments is the umbrella term for collecting money from a customer without them ever leaving the WhatsApp chat — whether that's a UPI intent, a saved card, netbanking, or a wallet. For an Indian business on the WhatsApp Business API, it turns a conversation into a checkout: the customer sees the product, asks a question, gets a quote, and pays in the same thread. This glossary entry defines the term precisely, separates the two very different mechanisms people lump together (native in-app payments versus gateway-backed payment links and flows), and flags the compliance and cost pitfalls that trip up first-time setups.
In one line
WhatsApp Payments means letting customers pay by UPI, card, or netbanking inside the WhatsApp chat — either through Meta's native in-app payments or through a payment gateway surfaced as a link, order-details message, or Flow. It shortens the path from conversation to conversion, but each route has different eligibility, settlement, and messaging-cost implications you should get right before you launch.What WhatsApp Payments actually means
WhatsApp Payments is not a single product — it's a category that covers every way a business collects money inside a WhatsApp conversation. At one end sits Meta's native in-app payments experience, where the customer taps to pay and completes a UPI or card transaction without opening a browser; the payment sheet is rendered by WhatsApp itself and backed by an integrated payment provider. At the other end sits the far more common gateway-backed approach, where your existing payment provider (a UPI PSP or an aggregator like Razorpay, Cashfree, PhonePe, or PayU) issues a payment link, an order-details message, or a WhatsApp Flow, and WhatsApp simply carries that link into the chat. Both feel seamless to the customer, but they differ in eligibility, who holds the merchant relationship, how settlement works, and how much engineering you need. The term 'WhatsApp Payments' should always be qualified by which of these two you actually mean.
- Native in-app payments: WhatsApp renders the payment sheet; requires an integrated payment partner and a payments-configured account
- Gateway payment link: your PSP generates a hosted checkout URL sent as a message or button
- Order-details / order-status messages: a structured message carrying line items and a total that opens a pay action
- WhatsApp Flow with a payment step: a multi-screen in-chat form that ends in a gateway checkout
Why it matters for Indian businesses
India runs on UPI, and the WhatsApp thread is where a huge share of small-business selling, catalogue browsing, and support already happens. Every extra tap — copying an order number, opening a browser, hunting for a card — is a place where a ready-to-pay customer drops off. Collecting the payment in-chat compresses that funnel to almost nothing, which is why it shines for order confirmations, digital invoices, deposit collection, subscription renewals, and abandoned-cart recovery. It also keeps the whole exchange auditable in one place: the quote, the customer's yes, and the paid receipt all sit in the same conversation. Getting the mechanics right early avoids the two classic failure modes — a checkout that looks native but silently breaks on certain devices, and a messaging setup that quietly costs more than it should because the wrong message category was used to deliver the pay link.
How the message that carries a payment is billed
A payment link or order-details message is delivered by a template, and templates are billed by category. Since Meta moved off per-conversation pricing on 1 July 2025, WhatsApp charges per delivered message according to its category — marketing, utility, or authentication —. A genuine transactional payment message (an invoice, an order confirmation, a renewal reminder tied to a specific purchase) is a utility-category template, which is priced lower than marketing. If you instead wrap the same pay link inside a promotional blast, it becomes a marketing message and is billed at the higher marketing rate for every recipient. The free 24-hour service window matters here too: it is a window during which you can reply to a customer-initiated message without a template, not a billing unit — so a customer who messages you first can often be sent the pay link as a free-form message within that window. InfiQ surfaces the correct category and the applicable ₹ rate before you send, with transparent ₹ pricing (ex-GST), so the cost of collecting a payment is never a surprise.
- Utility template: correct category for invoices, order confirmations, and renewal reminders tied to a purchase
- Marketing template: applies if the pay link rides inside a promotional message — priced higher
- Service window: reply free-form to a customer within 24 hours of their last message — no template fee
- Billing basis: per delivered message by category, not per conversation
Common mistakes to avoid
The most frequent mistake is treating WhatsApp Payments as one turnkey button when it is really an integration decision. Businesses assume native in-app payments are available and generally usable, then discover eligibility, device, and partner constraints and have to fall back to a gateway link anyway. A second mistake is category misuse: sending payment links as marketing broadcasts, which both raises cost and risks template rejection or quality-rating damage because payment content in a promotional template reads as spammy to reviewers. A third is compliance blind spots — reconciliation, refunds, chargebacks, and receipt records all still live with your payment provider and your books, not with WhatsApp; the chat is the delivery channel, not the ledger. Finally, teams forget that the merchant and settlement relationship stays with the gateway: WhatsApp does not hold your money, so KYC, settlement timelines, and dispute handling follow your PSP's rules, not Meta's.
- Assuming native payments will 'just work' everywhere instead of confirming eligibility first
- Delivering pay links inside marketing templates and paying the higher rate
- Forgetting refunds, reconciliation, and receipts sit with your gateway and accounting, not WhatsApp
- Not testing the checkout across devices before a live campaign