WhatsApp Payments for SMBs: Collect Money Right in Chat

Here's a scenario I've watched play out dozens of times. A saree boutique owner in Jaipur closes a sale over WhatsApp. The customer's ready to pay. So the owner types out her UPI ID, the customer fumbles copying it, sends the wrong amount, then forgets to share the screenshot. Twenty messages later, half the payments go untracked and reconciliation at month-end becomes a nightmare. Multiply that across 200 orders and you've got a business bleeding time and money on something that should take ten seconds.

WhatsApp is where Indian commerce actually happens. Over 500 million Indians use it, and for a huge slice of SMBs it is the storefront, the catalogue, and the customer support desk all at once. What most owners don't realise is that you can now collect money and send GST-compliant invoices right inside that same chat window, without bouncing the customer to a separate payment link or a clunky website checkout. Meta rolled out payment features on the Business Platform in India, and combined with a good BSP (Business Solution Provider), you can build a proper in-chat payment flow.

In this post I'll walk you through how WhatsApp Business payments India actually works in practice, what it costs, how to set it up step by step, the mistakes I see teams make, and a real example of a small business that cut its checkout drop-off dramatically. This is the stuff I wish someone had handed me the first time I implemented this for a client.

Key Takeaways

• WhatsApp lets you send payment links, invoices, and even native in-chat checkout, cutting the friction of copy-pasting UPI IDs and chasing screenshots.
• You need the WhatsApp Business API (not the free app) plus a verified payment gateway like Razorpay, Cashfree, or PayU to collect money at scale.
• Realistic monthly cost for a small team starts around ₹2,000–₹5,000 in platform fees plus a 2% gateway cut on payments — often cheaper than the labour lost to manual reconciliation.
• Send proper GST invoices as PDF documents inside the same chat; keep your invoice numbering and HSN codes clean to stay audit-ready.
• Payment collection messages must be triggered inside the 24-hour service window or use an approved utility template, or Meta will block them.
• Start with payment links (fastest to deploy), then graduate to native flows once your volume justifies the setup effort.

Why collect payments inside WhatsApp instead of a website checkout?

The honest answer is drop-off. Every extra tap between "I want this" and "payment done" loses customers. When you send someone from a WhatsApp chat to a website, they have to switch apps, sometimes log in, re-enter details, and often abandon halfway. Industry data on general e-commerce checkout abandonment hovers around 70%, and for mobile-first Indian buyers on patchy 4G, that number gets worse.

Keeping the payment in-chat removes the context switch. The customer stays in the conversation they already trust. For a business that does most of its selling through conversation anyway, like a home baker in Pune or a B2B stationery supplier in Coimbatore, this is a natural fit rather than a bolt-on.

There's also the trust factor. Indian buyers are wary of random payment links forwarded on chat because of the fraud they've seen. When the payment request comes through your verified WhatsApp Business profile with the green tick and your business name, it reads as legitimate. That verification does real work in getting people to actually pay.

What do you actually need to accept WhatsApp Business payments in India?

Let me clear up the confusion first, because there are three different things people lump together.

The free WhatsApp Business app (the green one you download from the Play Store) does not support proper automated payment collection or invoicing at scale. You can share your UPI ID or a payment link manually, but that's the messy process I described at the top. Fine for five orders a day, painful beyond that.

The WhatsApp Business API (now called the WhatsApp Business Platform) is what you need for real payment workflows, automation, and templates. It runs through a BSP. If you're weighing the two, our guide on the WhatsApp Business API vs the Broadcast App breaks down exactly when each makes sense.

Here's the checklist of what you need to go live:

• A registered business with a GSTIN (needed for both API onboarding and for issuing compliant invoices).
• A Facebook Business Manager account and a verified business (Meta business verification, usually 2–7 working days).
• A dedicated phone number not currently tied to the WhatsApp app.
• A BSP partner such as Interakt, WATI, AiSensy, or Gupshup to provision the API.
• A payment gateway with UPI, cards, and netbanking enabled — Razorpay, Cashfree, or PayU are the common choices.
• A display name and profile that passes Meta's approval so you get that verified badge.

If the API onboarding sounds like a lot, that's because it genuinely has a few moving parts. This is where a partner earns their fee. The team at eDarpan handles the whole WhatsApp Business API setup including Meta verification, number provisioning, and gateway integration, so you're not stuck decoding developer documentation at 11pm.

How do the payment methods inside WhatsApp compare?

There isn't just one way to collect money in a WhatsApp chat. You have a few options, each with different setup effort and customer experience. Picking the right one depends on your order volume and how much engineering help you have.

Method	Setup effort	Customer experience	Best for	Typical cost
Manual UPI ID / QR share	None	Clunky, error-prone	Very low volume, under ~10 orders/day	Free (but high hidden labour cost)
Payment link via gateway	Low	One tap, opens gateway page	Most SMBs starting out	~2% per transaction
Interactive payment message (native)	Medium	Pay inside chat, minimal switch	Growing D2C brands	~2% + API/template fees
WhatsApp Flows checkout	High	Full catalogue + cart + pay in-chat	High-volume sellers, catalogue-driven	Gateway + dev + API fees

My practical advice for most small teams: start with payment links through a gateway. They deploy in a day, work reliably, and remove 80% of the manual pain. Once you're processing a few hundred orders a month and the maths justifies it, move to interactive payment messages or Flows. Don't over-engineer on day one.

Which WhatsApp Business API and payment provider should you choose?

The BSP you pick matters because it shapes your pricing, your dashboard, and how easily payments plug in. Below is a comparison of providers Indian SMBs actually use. Note that Meta's per-conversation charges are separate and change periodically, so treat the platform fee as the recurring subscription each BSP charges on top.

Provider	Approx. starting plan	Payment integration	Good for
Interakt	~₹2,000/month	Razorpay, catalogue payments	Small retail & D2C
AiSensy	~₹999–₹2,400/month	Razorpay payment links	Budget-conscious SMBs
WATI	~₹2,499/month	Razorpay, Stripe, custom APIs	Teams needing shared inbox
Gupshup	Custom / usage-based	Multiple gateways, enterprise	Higher volume, custom builds

On the gateway side, Razorpay has the widest BSP compatibility in India, which is why it shows up in almost every plan above. Cashfree and PayU are strong alternatives, and if you're already using one of them for your website, keep it for consistency in reconciliation.

Pro Tip: Don't pick the cheapest BSP purely on the monthly headline price. Check the per-conversation markup and whether template message support is throttled on the lowest tier. I've seen a client save ₹500 a month on the plan and then lose that ten times over in per-message charges once campaigns scaled. Read our breakdown of WhatsApp messaging limits and warm-up before you commit.

Step-by-step: setting up WhatsApp in-chat payments

Here's the actual sequence I follow when deploying this for a client. You can hand this to your vendor as a brief, or work through it yourself.

1. Get business verification done first. Create or clean up your Facebook Business Manager, upload your GST certificate and business proof, and submit for Meta business verification. This gates everything else, so start it early. Budget 2–7 working days.
2. Provision the API through your BSP. Choose a dedicated number (a fresh number is cleanest). Your BSP registers it on the WhatsApp Business Platform and sets up your display name for approval.
3. Connect your payment gateway. Complete KYC on Razorpay or Cashfree, enable UPI, cards, and netbanking, and generate your API keys. Link these inside your BSP dashboard.
4. Build your invoice and payment templates. Create a utility message template for order confirmation with the payment link, and a document template to attach the GST invoice PDF. Submit these to Meta for approval (usually a few hours to a day).
5. Set up the trigger logic. Decide when a payment request fires. Common triggers: after a customer confirms an order in chat, or when your team clicks "collect payment" in the shared inbox. Wire this to auto-generate the gateway link with the correct amount.
6. Automate the invoice. On successful payment, have the system generate a GST invoice PDF with correct invoice number, HSN/SAC code, GST split (CGST/SGST or IGST), and send it back into the same chat as a document.
7. Test end to end with a ₹1 transaction. Run a real payment through, confirm the invoice generates correctly, and check the money lands in your settlement account. Never skip this.
8. Reconcile. Connect gateway settlements to your accounting tool (Zoho Books, Tally, or a Google Sheet if you're small) so payments auto-match to orders.

If step 6 sounds like it needs a developer, it often does for the invoice automation piece. That's a small custom software job that pays for itself fast when you're issuing 300 invoices a month by hand.

A real example: a Nagpur home-decor seller cuts checkout friction

Let me make this concrete. A home-decor and gifting business in Nagpur, run by a husband-wife team with two part-time helpers, was doing roughly 250 orders a month entirely over WhatsApp. Their process: share UPI ID, wait for screenshot, manually note the payment in a notebook, and issue invoices only when a customer specifically asked.

The problems piled up. Around 15% of chats went cold at the payment stage because customers got confused or distracted. Reconciliation ate one full evening every week. And at GST filing time, they were scrambling to reconstruct invoices, which meant their CA charged extra for the cleanup.

We moved them onto the WhatsApp Business API through a BSP at ₹2,400/month and integrated Razorpay payment links. Order confirmation now auto-sends a payment link inside the chat. On payment, a GST invoice PDF with proper numbering lands back in the same thread. Here's what shifted over three months:

• Payment-stage drop-off fell from ~15% to under 5%, recovering roughly 25 orders a month that were previously lost.
• Weekly reconciliation went from ~4 hours to about 30 minutes, since every payment auto-matched.
• Every sale now generates a compliant invoice automatically, ending the GST-season panic.
• Total monthly cost: ₹2,400 platform + ~2% gateway fee. On their volume, that was a clear net gain against recovered orders and saved hours.

The lesson isn't the specific numbers. It's that for a conversation-driven business, removing payment friction directly recovers revenue you were already losing silently.

Staying GST-compliant and on the right side of Meta's rules

Two areas trip people up here, and both can hurt you.

GST invoicing done right

If you're GST-registered, every taxable sale needs a proper tax invoice. When you automate invoices through WhatsApp, make sure each one carries a unique sequential invoice number, your GSTIN, the customer's GSTIN if it's a B2B sale, the correct HSN or SAC code, and the tax split. For intra-state sales you show CGST and SGST; for inter-state, IGST. Getting the numbering sequence and tax type right is what keeps you audit-ready.

If you don't yet have a registered business address for GST, a virtual office address for GST and company registration is a legitimate, low-cost way to get compliant before you scale your payment flows.

Meta's messaging rules

You cannot spam payment requests. WhatsApp enforces a 24-hour customer service window: you can send free-form messages, including payment links, within 24 hours of the customer's last message. Outside that window you must use a pre-approved template. Send an unsolicited payment link to a cold contact and you risk your number being flagged or blocked.

Common Mistake: Businesses grab a customer's number from an old order and blast a payment reminder outside the 24-hour window using a marketing-style message. Meta's systems catch this fast, quality rating drops, and suddenly your template messages stop delivering. Always use an approved utility template for payment nudges, and keep an eye on WhatsApp's evolving policy changes so a rule update doesn't break your flow overnight. If you run any automation, also review the chatbot policy rules before you go live.

How does this fit into a larger customer engagement stack?

Payments are one piece. The businesses that get real leverage treat WhatsApp as their whole conversational commerce channel: catalogue, ordering, payment, support, and re-engagement. Layer in order-status updates, abandoned-cart nudges within the service window, and post-purchase feedback requests, and the same channel that closes the sale also drives repeat business.

For higher-volume promotional reach, some businesses pair WhatsApp with bulk SMS for OTPs and transactional alerts, since SMS still has near-universal reach. And if a big chunk of your support is repetitive queries, an AI voicebot can offload the phone calls while WhatsApp handles the chat. If you're exploring AI-driven marketing more broadly, our playbook on Gemini ad tools for Indian SMBs is worth a read.

The point is to design the flow around how your customers already behave rather than forcing them into your convenience. That's exactly the kind of thinking our IT consulting team brings when we map a client's commerce journey end to end. You can see the full range of what we support on our services overview.

Frequently asked questions

Can I accept payments on the free WhatsApp Business app in India?

Only manually, by sharing a UPI ID, QR code, or payment link and confirming payment yourself. There's no automated invoicing or scaled payment collection on the free app. For anything beyond a handful of orders a day, you'll want the WhatsApp Business API through a BSP.

How much does it cost to set up WhatsApp Business payments for a small business?

Expect roughly ₹2,000–₹5,000 per month in BSP platform fees, plus around 2% per transaction charged by your payment gateway, plus Meta's per-conversation charges which vary. Many SMBs find this cheaper than the labour lost to manual payment tracking and reconciliation.

Do I need a GST number to collect payments on WhatsApp?

You need a GSTIN if your turnover crosses the registration threshold or you're already registered, and you must issue compliant tax invoices in that case. It's also required for smooth API onboarding and gateway KYC. If you're not yet registered, a virtual office address can help you get a GSTIN before scaling.

Which payment gateway works best with WhatsApp in India?

Razorpay has the widest compatibility across BSPs like Interakt, WATI, and AiSensy, which is why it's the most common choice. Cashfree and PayU are solid alternatives, especially if you already use one on your website and want consistent reconciliation.

Can I send an invoice automatically after a customer pays?

Yes. With the API you can trigger a GST invoice PDF to generate on successful payment and send it straight back into the same chat as a document. This usually needs a small custom integration between your gateway, accounting tool, and BSP.

Will Meta block me for sending payment links?

Not if you follow the rules. Send payment links within the 24-hour service window after a customer messages you, or use an approved utility template outside it. Blasting unsolicited payment requests to cold contacts is what gets numbers flagged and quality ratings dropped.

How long does it take to go live with WhatsApp payments?

If your business verification is clean, you can typically be live in 5–10 working days: 2–7 days for Meta verification, plus a day or two for API provisioning, gateway KYC, and template approval. Invoice automation may add a bit more depending on your accounting setup.

Getting started

The gap between businesses that thrive on WhatsApp and those that just tolerate it usually comes down to friction. Every UPI ID you type by hand, every screenshot you chase, every invoice you scramble to reconstruct at filing time is friction you can engineer away. Setting up WhatsApp Business payments India the right way turns your busiest sales channel into a clean, trackable, compliant revenue engine.

Start small with payment links, keep your GST invoicing tidy, respect Meta's messaging windows, and grow into native flows as your volume earns it. If you'd rather not wrestle with Meta verification, BSP selection, gateway KYC, and invoice automation on your own, that's exactly what we do. Talk to the eDarpan team about setting up your WhatsApp payment and invoicing flow, and get selling in chat without the reconciliation headache. You can also learn more about how we work with Indian SMBs.

Image credit: Market by Mike Knell via flickr (BY-SA 2.0), sourced through Openverse.