WhatsApp Pay — checkout inside the chat
Send payment links, render product catalogues and accept UPI, card and wallet payments inside WhatsApp itself. Powered by your payment gateway, orchestrated by LandinChat.
- UPI, cards, wallets
- Razorpay, Stripe, PayU, Paddle
- Auto order confirmations
- PCI-DSS handled by gateway
Key things to know
Native UPI payments (India)
Accept UPI directly inside WhatsApp where Meta's native rail is live.
Catalogue checkout
Show products in WhatsApp's catalogue, let customers add to cart and pay inline.
Payment links
Generate one-tap pay-now links from broadcasts, flows or 1-to-1 conversations.
Gateway-grade security
All card and account data flows through PCI-DSS L1 gateways — never via LandinChat.
People also ask
Q.What is WhatsApp Pay?
WhatsApp Pay refers to Meta's native in-chat payment surfaces — including UPI-powered WhatsApp Payments in India, and the broader WhatsApp Business Platform payments API that lets customers complete checkout inside a chat using cards, UPI, Razorpay, Stripe or PayU rails.
Q.Is WhatsApp Pay available outside India?
Native UPI WhatsApp Pay is India-first. Outside India, brands accept payments inside WhatsApp via the Payments API — payment links, embedded checkout and webhook-confirmed orders powered by Stripe, PayPal, Razorpay, PayU, Paddle and others.
Q.How does LandinChat enable WhatsApp payments?
We integrate your payment provider (Razorpay, Stripe, PayU, Cashfree, Paddle, PayPal) and let you trigger payment requests, product catalogue checkouts and order confirmations from broadcasts, flows, chatbot replies or click-to-WhatsApp ads.
Q.Is WhatsApp Pay PCI-compliant and secure?
Yes. All card and UPI data is handled by the underlying PCI-DSS L1 payment gateway — never by WhatsApp or LandinChat. Settlement, refunds and chargebacks happen inside your existing payment provider dashboard.
Q.What are the fees?
WhatsApp charges its standard conversation rate for the message that contains the payment. The payment provider charges its standard MDR. There's no extra surcharge from LandinChat. See the pricing page for plans.
Q.Can I refund from WhatsApp itself?
Refunds are issued from your payment gateway and the customer is notified inside the same WhatsApp thread via an automated template message.
What WhatsApp Pay really means in 2026
There are two things people mean by WhatsApp Pay. First, Meta's native UPI-powered consumer payments product available in India (and rolling out gradually in select markets). Second, the broader WhatsApp Business Platform payments capability — in-chat payment requests, embedded checkout, catalogue purchases — powered by partner payment gateways.
For most growth teams, what actually moves the needle is the second one: surfacing a paid checkout right inside the chat where your customer already trusts the brand. Conversion rates on in-chat checkout are dramatically higher than redirecting to a web checkout — especially on mobile-first markets.
LandinChat connects to Razorpay, Stripe, PayU, Cashfree, Paddle, PayPal and others. You trigger payment requests from broadcasts, flows, chatbot replies or click-to-WhatsApp ads. Settlement, refunds and reconciliation happen in your existing payment dashboard — nothing changes for finance.
Built for serious growth teams
Native UPI payments (India)
Accept UPI directly inside WhatsApp where Meta's native rail is live.
Catalogue checkout
Show products in WhatsApp's catalogue, let customers add to cart and pay inline.
Payment links
Generate one-tap pay-now links from broadcasts, flows or 1-to-1 conversations.
Gateway-grade security
All card and account data flows through PCI-DSS L1 gateways — never via LandinChat.
Auto receipts & invoices
Trigger receipt template messages and GST-compliant invoices on every successful payment.
Global gateway network
Razorpay, Stripe, PayU, Cashfree, Paddle, PayPal — match your country and currency.
Get live in days, not months
- 1
Connect your gateway
OAuth into Razorpay / Stripe / PayU / Cashfree / Paddle — under 2 minutes.
- 2
Upload your catalogue
Sync products from Shopify, WooCommerce or upload CSV. Auto-mirrors to WhatsApp catalogue.
- 3
Build a pay flow
Use the Flow Builder to design address + checkout screens, or send pure pay-now links.
- 4
Trigger from anywhere
Launch from broadcasts, click-to-WhatsApp ads, chatbot intents or 1-to-1 chats.
- 5
Reconcile in your gateway
Refunds, payouts and disputes happen in your existing payment dashboard.
What teams ship with this
Abandoned cart recovery
Resend cart with one-tap pay link — most brands see 8–15% recovered revenue.
COD-to-prepaid conversion
Offer 2–5% discount on prepaid via WhatsApp before dispatch to cut RTO.
Subscription renewals
Trigger renewal pay links 7 days before expiry with smart reminder cadence.
Event ticketing
Sell tickets inside chat with auto QR delivery on successful payment.
Service bookings
Salons, clinics, consults — slot + pay in one chat session.
Donations & fundraising
Frictionless one-tap donation flows for NGOs and creators.
Frequently asked questions
Why WhatsApp Pay — checkout inside the chat is the highest-leverage move for growth teams
WhatsApp is where growth teams customers actually reply. Open rates sit at 85–98% inside 15 minutes versus 18–22% on email and sub-2% on SMS, and the medium is conversational — a customer can ask a follow-up, share a photo, or pay without leaving the thread. That is the entire premise behind whatsapp pay — checkout inside the chat: stop losing the conversation to slow channels and let intent convert while it is warm.
Most growth teams teams treat WhatsApp as a broadcast megaphone. The teams that win treat it as a workflow surface — every notification is also a decision point where the customer can act. The capabilities below are wired to do exactly that: each one collapses a multi-step off-platform detour into a single in-thread reply.
The impact numbers on this page — 3.4x higher checkout completion, <45s average pay flow time, 100% pci handled by gateway, 10+ payment providers — are pulled from LandinChat customers running this workflow for at least 90 days. They are directional; your mileage depends on list quality, template approval speed, and how aggressively you route qualified conversations to a live agent.
Each capability, in plain terms
Native UPI payments (India)
Accept UPI directly inside WhatsApp where Meta's native rail is live. In practice this means the growth teams operator running whatsapp pay — checkout inside the chat does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Catalogue checkout
Show products in WhatsApp's catalogue, let customers add to cart and pay inline. In practice this means the growth teams operator running whatsapp pay — checkout inside the chat does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Payment links
Generate one-tap pay-now links from broadcasts, flows or 1-to-1 conversations. In practice this means the growth teams operator running whatsapp pay — checkout inside the chat does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Gateway-grade security
All card and account data flows through PCI-DSS L1 gateways — never via LandinChat. In practice this means the growth teams operator running whatsapp pay — checkout inside the chat does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Auto receipts & invoices
Trigger receipt template messages and GST-compliant invoices on every successful payment. In practice this means the growth teams operator running whatsapp pay — checkout inside the chat does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Global gateway network
Razorpay, Stripe, PayU, Cashfree, Paddle, PayPal — match your country and currency. In practice this means the growth teams operator running whatsapp pay — checkout inside the chat does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
How this actually rolls out
Step 1. Connect your gateway
OAuth into Razorpay / Stripe / PayU / Cashfree / Paddle — under 2 minutes. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
Step 2. Upload your catalogue
Sync products from Shopify, WooCommerce or upload CSV. Auto-mirrors to WhatsApp catalogue. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
Step 3. Build a pay flow
Use the Flow Builder to design address + checkout screens, or send pure pay-now links. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
Step 4. Trigger from anywhere
Launch from broadcasts, click-to-WhatsApp ads, chatbot intents or 1-to-1 chats. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
Step 5. Reconcile in your gateway
Refunds, payouts and disputes happen in your existing payment dashboard. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
How different teams put this to work
Abandoned cart recovery
Resend cart with one-tap pay link — most brands see 8–15% recovered revenue. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
COD-to-prepaid conversion
Offer 2–5% discount on prepaid via WhatsApp before dispatch to cut RTO. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
Subscription renewals
Trigger renewal pay links 7 days before expiry with smart reminder cadence. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
Event ticketing
Sell tickets inside chat with auto QR delivery on successful payment. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
Service bookings
Salons, clinics, consults — slot + pay in one chat session. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
Donations & fundraising
Frictionless one-tap donation flows for NGOs and creators. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
Buyer’s checklist
- • Official Meta Tech Partner — templates approve faster and account is not at ban risk.
- • Native growth teams data model — no glue-code to import contacts, orders, or bookings.
- • Green-tick support with a clear submission checklist and Meta-side follow-up.
- • Conversation-based pricing that matches WhatsApp’s own billing model, not per-message surcharges.
- • Human handoff with unread routing, so qualified replies never sit in a bot loop.
- • Audit log & role-based access — required for regulated enterprise buyers.
Common pitfalls
- • Broadcasting cold lists — quickest way to a quality-rating downgrade and eventually a template ban.
- • Skipping opt-in capture — makes every future utility template harder to approve.
- • Treating WhatsApp as a one-way channel — the platform penalises accounts with low reply-rate.
- • Running only one template variant — you leave 20–40% of lift on the table.
- • Not routing hot conversations to a human within 5 minutes — kills conversion by up to half.
What to measure after launching whatsapp pay — checkout inside the chat
Week 1 signal
Track template approval time, first-reply latency, delivered-rate, and the first 100 customer replies. For growth teams, the fastest warning sign is not low opens; it is customers replying with confusion because the trigger, offer, or handoff promise was not specific enough.
Month 1 signal
Compare reply quality across Native UPI payments (India), Catalogue checkout, Payment links, Gateway-grade security. The best-performing growth teams teams keep the highest-intent replies visible to managers, then rewrite templates around real customer language instead of internal terminology.
Scale signal
Once Connect your gateway → Upload your catalogue → Build a pay flow → Trigger from anywhere is stable, scale by segment rather than volume. Add new audiences only when opt-in source, template intent, agent ownership, and conversion tracking are all mapped.
Search-quality notes for this workflow
This page is intentionally built around whatsapp pay — checkout inside the chat rather than a generic WhatsApp marketing overview. The content references the actual workflow, the growth teams audience, implementation steps such as Connect your gateway, Upload your catalogue, Build a pay flow, Trigger from anywhere, and use cases like Abandoned cart recovery, COD-to-prepaid conversion, Subscription renewals, Event ticketing. That specificity helps buyers, internal teams, and search engines understand why this page deserves to exist separately from broader WhatsApp CRM, broadcast, chatbot, and automation pages.
Ready to ship on WhatsApp?
Talk to our team about plans, onboarding and how LandinChat fits your stack.