Razorpay / PayU Payment Links Inside WhatsApp Flows

Operators search Razorpay WhatsApp payment link when they want the customer to tap Pay now in chat and finish UPI or card without a fragile PDF.

On official Cloud API that tap is one of these product-real paths — not a grey “UPI on WhatsApp Web” plugin:

Path	What the customer sees	Gateway truth on WatsBerry
Razorpay Payment Link	WhatsApp Pay now URL button (UPI / card / netbanking on Razorpay’s hosted page)	Generated from Razorpay (shop UPI Intent fallback, or a WhatsApp Form that creates a payment link)
Razorpay UPI Intent / QR	In-chat UPI when Meta can fetch the QR	Razorpay keys on WhatsApp Orders → Payments. If QR fails, we fall back to a Payment Link
Meta Review & Pay	Native WhatsApp invoice (UPI apps + card)	Razorpay, PayU, BillDesk, or Zaakpay linked in WhatsApp Manager. WatsBerry keeps the Meta configuration name — we do not store those PG secrets for this mode
Manual UPI	Your VPA / QR	You mark Paid. No auto-capture

We do not claim a PayU or BillDesk Payment Link API inside WatsBerry. Those brands are accurate on the Meta Payments (India) Review & Pay path and on the public marketing logos. Zaakpay is the other Meta-supported PG we list in Payments settings.

WatsBerry is not the merchant of record for shop checkout. Invite-only beta — join the waitlist.

WhatsApp Forms are Meta-native in-chat forms (WhatsApp Flows). A shipped Service Payment template collects name, service type, reference, and amount due, then can send a Razorpay Pay now link and a PDF receipt after payment.

A sane India sequence:

1. Customer is already in the customer-care window (they messaged you, tapped CTWA, or submitted a form) — or you send an approved template that is allowed to carry the pay CTA.
2. They complete the form (or you already have an order total from catalogue commerce).
3. WatsBerry creates the Razorpay payment link for that amount and sends Pay now.
4. On success: webhook / callback / Orders Sync marks Paid; optional receipt.

Campaign / automation flows can sit around the same job: keyword or order trigger → reminder → pay CTA. Integrations copy also describes Razorpay-powered links and COD confirmation on flows when Razorpay is connected. Use that for an amount you can defend (fee, invoice, unpaid catalogue order) — not a cold list blast.

Template category: a pay link for an already created order or a stated due is usually utility if Meta approves it that way. “Complete your cart / festive offer” is usually marketing. See marketing vs utility.

Do not mix the two desks in your head.

Catalogue / WhatsApp Orders — browse, address, Pay now / COD, fulfilment. Choose one checkout mode (catalogue playbook). Review & Pay is the native invoice. Razorpay Payment Link is the fallback when you are on UPI Intent and QR is not usable in WhatsApp.

Standalone form / flow link — dues, retainers, workshop fees, a draft-order balance. There is no cart SKU required. Still send one amount and one button.

Shopify cart recovery is a third path: checkout URL on Shopify, not a catalogue invoice. You can mention prepaid vs COD and still use Razorpay on the site. Playbook: Shopify cart recovery.

Webhooks (do not swap these)

• Shop Razorpay: merchant dashboard → payment_link.paid / payment.captured on the shop callback URL (tenant keys).
• WatsBerry Billing Razorpay: plans and wallet top-ups. Wrong webhook = Paid never flips on the order.

Opening WhatsApp Orders also polls unpaid plink_ / qr_ rows. A cron retries. Agents can tap Sync payment status.

Accurate to the marketing site and the Payments UI:

• Logos and copy: collect in-chat with WhatsApp Payments (India) via Razorpay, PayU, BillDesk, or Zaakpay.
• Meta setup: create the merchant account at the PG → WhatsApp Manager → Payment configurations (India) → authorize → paste the exact configuration name into WatsBerry → enable in-chat invoices.
• UPI Intent + generated Payment Links: Razorpay only today.
• Form Pay now links: Razorpay payment-link path.

We will not claim:

• That WatsBerry is a RBI-regulated payment aggregator.
• That PayU/BillDesk payment-link APIs are wired the same as Razorpay’s payment_links.
• Official Meta message rates for “pay now” taps — those are conversation/template fees, verify on Meta’s card.
• A made-up success rate or testimonial.

GST, MDR, and refunds live on your PG dashboard. WatsBerry dual billing is plan + wallet vs Meta’s WhatsApp invoice.

• Official WABA — not WhatsApp Web (official vs unofficial).
• One payment mode enabled; test with a small live or test amount.
• Address-before-pay on physical catalogue goods.
• Chatbot pause during checkout.
• Correct Razorpay shop webhook if you use Payment Links.
• Template category that matches the job.
• Meta payment method and WatsBerry wallet funded.

Public pricing lists Payment Gateway on the comparison table (Razorpay on plans that include the integration). Entitlements are confirmed when you are invited.

Next: catalogue commerce, features, solutions. Ready to collect on official WhatsApp? Join the beta waitlist.

Does WatsBerry generate PayU payment links the same way as Razorpay?

No. Razorpay Payment Links (and UPI Intent fallback) are the generated-link path. PayU, BillDesk, and Zaakpay appear on the Meta WhatsApp Payments Review & Pay configuration — we store the Meta configuration name, not PayU/BillDesk API keys.

Where does the money settle?

Shop / catalogue checkout settles in your Razorpay, PayU, BillDesk, or Zaakpay merchant account (or your bank on manual UPI) — not in WatsBerry Billing. WatsBerry still bills the platform plan and wallet; Meta bills conversation/template usage separately.

Can I put a Razorpay link in a marketing broadcast?

A payment request should follow a real amount (form, order, or invoice). Cold “pay now” blasts are a policy and trust problem. After the 24-hour window, use an approved template in the right category — usually utility for an existing order, marketing if you are promoting.

Is this available during beta?

WatsBerry is invite-only beta. Public pricing lists Payment Gateway on the comparison table; exact entitlements are confirmed at invite. Request access on /waitlist.