Run your entire commerce stack on WhatsApp — catalog, cart, checkout, payments, invoices and order tracking. Stripe, Razorpay, Cashfree, PayU and UPI supported out of the box.
Upload products with images, price, variants and stock. Customers browse a beautiful in-chat catalog — no third-party app.
Add to cart, change quantities, apply discount codes and review the order — all inside the WhatsApp conversation.
Stripe, Razorpay, Cashfree, PayU, PayPal, Paytm — plus UPI deep-links for one-tap pay on Indian numbers.
Generate branded invoices and payment receipts as PDF, sent right after the order is confirmed.
Customers ask 'where is my order?' and the chatbot replies with the live tracking link from Shiprocket, Delhivery, FedEx or any carrier.
If a customer drops off mid-checkout, an automated nudge with a 1-tap pay link recovers 30–60% of carts.
Live GMV, AOV, conversion rate and revenue per campaign. Export to CSV, Sheets or your warehouse.
The chatbot suggests products from your catalog based on the customer's preferences, past orders and current cart.
Bulk-upload from CSV, sync from Shopify/WooCommerce or paste a Google Sheet — variants, stock and images included.
Bot or human shares the catalog, customer scrolls, picks variants and adds to cart — inside WhatsApp.
Customer taps the payment link (Razorpay, Stripe, UPI…), pays, and an instant webhook fires.
Order goes to Shopify/your OMS, invoice + tracking are sent on WhatsApp, support is on the same thread.
Run an entire D2C brand from WhatsApp — catalog, cart, payments, tracking, support.
Share the menu in chat, take the order, collect UPI/Stripe payment and notify the kitchen automatically.
Frequent customers reorder their last purchase with a single 'Reorder' button — paid via UPI in seconds.
Salons, clinics and studios collect a deposit on WhatsApp before locking the slot — no-shows drop.
Meta verification, WhatsApp Business API, catalog upload, Stripe/Razorpay/UPI integration and your first checkout flow — done-for-you.
Modern buyers don't want to leave the chat to checkout. Every redirect to a payment page leaks conversion — to load time, to second-guessing, to a competing tab. WhatsApp catalog plus in-chat payments compresses the entire purchase into a single thread: browse, ask, decide, pay, confirm.
LandinChat ties your product catalog, your payment gateway and your fulfilment system together so an order placed in chat updates Shopify, charges via Razorpay or Stripe, and pings the warehouse — without anyone copying an order number into a spreadsheet.
Native 2-way sync with Shopify, WooCommerce, Magento and Zoho Commerce keeps stock, price and product info live in your WhatsApp catalog. When a SKU goes out of stock on Shopify, it stops showing in chat. When pricing changes, chat reflects it within minutes — no manual upload, no stale catalog burning trust.
LandinChat doesn't replace your payment stack — it plugs into Stripe, Razorpay, Cashfree, PayU, PayPal, Paytm and UPI. Customers pay with the gateway they already trust at the rates you've already negotiated. Successful payments fire a webhook back into the chat so the bot can confirm the order in real time.
For COD-friendly markets, the pre-delivery COD-to-prepaid step alone usually pays for the platform — converting 25–40% of COD orders to prepaid and slashing RTO costs in half.
Every cart event triggers a recovery flow timed across 72 hours; every paid order triggers a post-purchase NPS, review request and replenishment reminder timed to the product's natural repeat cycle. The same WhatsApp thread that took the first order takes the second, the third and the fifth — without you ever buying a new email subscription.
“Our WhatsApp store does 22% of total revenue now. The COD-to-prepaid flow alone paid for the platform in the first month.”
Last updated: June 2026
Yes. With LandinChat you upload a product catalog, customers browse and add to cart inside the chat, the chatbot generates an order summary, collects the payment via Stripe/Razorpay/UPI and confirms the order — without ever leaving WhatsApp.
Stripe, Razorpay, Cashfree, PayU, PayPal, Paytm and UPI (Google Pay, PhonePe, BHIM). Use any combination — customers see your branded checkout link inside the chat.
Yes. Native 2-way sync with Shopify, WooCommerce, Magento and Zoho Commerce. Stock, price and product info stay live — no manual upload.
No. Your WhatsApp catalog + LandinChat is enough to take orders and payments. You can still link it to your website if you have one.
The chatbot generates a UPI deep-link or payment-link from your provider. The customer pays with one tap, you get an instant webhook, the chatbot confirms the order and shares tracking — all inside the same WhatsApp thread.
Yes. LandinChat is an Official Meta Tech Partner and uses only the official WhatsApp Business API and Meta Commerce policies. Your number stays safe and green-tick intact.
No. LandinChat charges a flat platform fee. Payment-gateway fees go to your provider (Stripe, Razorpay, Cashfree, PayU, UPI) at their published rates — we don't add a per-order markup.
Yes. One catalog can power multiple WhatsApp Business numbers in the same workspace — useful for multi-region or multi-brand setups.
Cart events trigger a multi-step recovery flow: a soft reminder at 1 hour, an offer or social proof at 24 hours, and a final nudge at 72 hours. Typical recovery is 8–14% of abandoned WhatsApp carts.
Yes — payment flows support partial payments, deposits and pre-orders. Useful for high-ticket items, custom orders and bookings where a small upfront payment confirms intent.
Yes. Customers can choose COD or prepaid inside the chat. We strongly recommend a COD-to-prepaid confirmation step, which typically converts 25–40% of COD orders to prepaid and cuts RTO in half.
Join 500+ businesses worldwide using LandinChat to reply faster, sell more, and never miss a customer on WhatsApp.
Every product below is built on the official WhatsApp Business Cloud API and works with the rest of the LandinChat stack — CRM, broadcast, chatbot, automation and analytics — out of the box.
Catalog & Payments solves a different operating problem than a generic WhatsApp inbox. This page focuses on the triggers, reports, agent workflows, integrations and account-health decisions that buyers evaluate before choosing this exact product area.
Look for official WhatsApp API provisioning, opt-in capture, template governance, CRM context, handoff rules, role-based access and exportable analytics. A strong catalog & payments setup should improve reply speed without creating more manual admin work.
The early signal is not message volume. It is higher qualified replies, cleaner assignment, faster resolution and clearer revenue attribution. Mature teams use catalog & payments as a repeatable operating system, not a one-off campaign tool.
We build on top of official documentation from Meta and recognised industry bodies. Use these references to verify policies, pricing and compliance details directly at the source.
See how teams in your sector deploy LandinChat end-to-end.
The full loop: shopper messages your number → bot / agent shares a product list message pulled from your Meta catalog → shopper adds items to an in-chat cart → payment request sent as a native WhatsApp Payments message (India / Brazil / Singapore) or a payment link (rest of world) → confirmation and order-status updates flow back through the 24h service window. Zero app installs, zero browser handoff.
| Step | Where | Gotcha |
|---|---|---|
| Create a Meta Commerce catalog | Commerce Manager | Cannot reuse Instagram Shopping catalog if currencies differ |
| Attach catalog to WABA | WhatsApp Manager | One catalog per WABA — plan multi-brand accordingly |
| Upload products | Feed / API / manual | SKU IDs must be stable — changing them breaks past chats |
| Approve for WhatsApp | Commerce policy review | Alcohol, supplements, digital services often rejected |
| Test in prod number | WhatsApp Manager | Sandbox catalog does not surface to shoppers |
| Country | Native WhatsApp Pay | Recommended fallback |
|---|---|---|
| India | Live (NPCI / UPI) | Razorpay payment link |
| Brazil | Live (Cielo, Mercado Pago) | Pix link |
| Singapore | Live (Stripe) | PayNow link |
| UAE / KSA | Not native | Tabby / Tamara link |
| US / EU | Not native | Stripe / payment link |
Meta's Commerce Policy is stricter than its Advertising Policy. Prohibited: prescription drugs, live animals, weapons, real currency, adult products, digital-only services (Netflix codes, subscriptions), event tickets in some markets. Restricted (case-by-case): alcohol, supplements, cosmetics with medical claims, financial services. A catalog rejection freezes the whole WABA's shopping surface — get pre-approval before publishing.
| Metric | Median | Top decile |
|---|---|---|
| Product-list open rate | 62% | 84% |
| Add-to-cart rate | 18% | 34% |
| Checkout completion | 41% | 68% |
| Order value uplift vs web | +22% | +58% |
Related: WhatsApp Commerce · WhatsApp Catalog · Shopify integration.
WhatsApp Catalog Payments is one of those topics where the surface answer ("use WhatsApp Business API") hides the real work. The rest of this page unpacks what actually moves the needle for growth teams teams: template strategy, opt-in hygiene, human handoff, and the compliance guardrails that keep the account alive.
WhatsApp’s open rate — 85–98% inside 15 minutes — is only valuable if the platform underneath it treats the channel as a workflow surface, not a broadcast megaphone. For growth teams teams evaluating WhatsApp Catalog Payments, the questions to ask are: does the vendor own green-tick submission end-to-end, are templates reviewed for approval-risk before you send them, is pricing flat or does it add per-message markup on top of Meta’s own rate, and can a live agent take over a conversation without losing context.
The three levers that consistently produce measurable lift are: (1) segmenting broadcasts by recency and spend tier instead of blasting the entire list; (2) capturing opt-in at every surface — website, checkout, in-store QR — so future utility templates approve first-attempt; and (3) routing any reply containing intent signals to a human within five minutes. Everything else — chatbot flows, catalog integration, payment links — is downstream of those three.
LandinChat ships all of the above as defaults, with the data model pre-wired. That is why customers who move onto LandinChat typically see reply-rate lift within the first 30 days and full ROI within one billing cycle.
A high-quality WhatsApp Catalog Payments page should not stop at a feature list. Buyers need to know how the topic behaves in the real WhatsApp Business API environment: what happens when templates are rejected, how agent ownership is preserved after a bot handoff, how opt-in is captured, what reports prove revenue, and where a team should avoid over-automation. The practical evaluation lens is workflow fit, compliance, automation depth, reporting quality, and handoff speed. If any of those areas are vague, the implementation usually becomes slower, more expensive, and harder to scale.
Start WhatsApp Catalog Payments with one narrow, measurable journey: capture the opt-in, send one approved utility or marketing template, route replies to the correct owner, and tag the outcome. Once the first journey produces clean data, duplicate the structure for adjacent segments. This protects account quality because every template has a clear purpose, every reply has an owner, and every campaign has a measurable next step.
For growth teams teams, the strongest pages combine strategic context, setup detail, operational risks, pricing expectations, compliance notes, and real use cases. That is why this page covers the decision criteria around WhatsApp Catalog Payments rather than repeating the same generic WhatsApp API explanation used on every software page.
Ask whether the platform supports official WhatsApp Business API onboarding, segmented broadcasts, a shared team inbox, CRM history, flow automation, live analytics, template review, and clean exports. The right answer for WhatsApp Catalog Payments is rarely the tool with the longest feature grid; it is the one your operators can run every week without needing developers for routine changes.
The most common mistake is launching WhatsApp Catalog Payments as one large broadcast or one oversized chatbot flow. Strong teams launch smaller journeys, inspect the conversations, then expand. That gives WhatsApp better engagement signals, gives agents cleaner context, and gives leadership a clearer view of revenue impact.
