Razorpay logoPayments

Razorpay WhatsApp Integration

UPI, cards and netbanking collected inside the chat, in India.

Razorpay is how most Indian businesses take money online, and connecting it gives the chatbot builder a payment block that raises a Razorpay link for the amount the flow holds. The customer pays by UPI, card or netbanking without leaving WhatsApp, and the flow continues only once Razorpay confirms. For merchants in India, native WhatsApp Pay is available as a separate rail alongside it.

Libromi Connect

Libromi Connect

WhatsApp Business Platform

Razorpay logo

Razorpay

Two-way connection

Where it shows up

  • Payment block
  • Chatbot builder node
  • WhatsApp store & catalogue

A UPI screenshot is not a payment confirmation

Indian chat commerce runs on payment screenshots — a UPI reference pasted into the conversation that someone then has to verify by hand. It is slow, it is trivially faked, and it means the flow cannot do anything automatically after payment because nothing verified it.

What moves, and which way

Razorpay to WhatsApp

  • Verified payment

    Razorpay confirms the transaction and the flow proceeds — no screenshot, no manual check.

  • Failure handling

    Failed or abandoned payments take their own branch so the customer can retry cleanly.

  • Transaction reference

    The reference is available downstream for receipts, CRM writes or order records.

WhatsApp to Razorpay

  • Payment links

    The block raises a Razorpay link on your account for the amount the flow calculated.

  • Order and cart totals

    Totals from a connected store, including tax and delivery, set the amount.

  • Customer identity

    Contact details from the conversation travel with the payment request.

In India, native WhatsApp Pay is also available as a separate in-chat payment rail.

What you get

UPI, cards and netbanking

Customers pay with whatever they normally use, from a link raised inside the conversation.

Automatic verification

The flow waits for Razorpay's confirmation instead of trusting a screenshot.

Branches for every outcome

Paid, timed out and cancelled are separate paths, so a failed payment gets a retry rather than silence.

Alongside WhatsApp Pay

Indian merchants can offer native WhatsApp Pay as well, and use Razorpay for everything it does not cover.

What you can build with it

COD-to-prepaid conversion

Offer a small discount for paying now, raise the link in chat, and confirm the order on the paid branch.

Booking deposits

Hold the slot only after Razorpay confirms, so no-shows cost less.

Subscription and fee collection

Send the reminder and the link together, and mark the record paid automatically.

In practice

A D2C brand converting COD orders

Cash on delivery was over half of orders and a quarter of them were refused at the door. The team wanted prepaid orders but had no way to collect reliably inside the WhatsApp conversation where the order was placed.

The result

A meaningful share of COD orders become prepaid without pressuring anyone, and the flow handles both outcomes on its own.

  1. 1

    After the customer confirms the basket, the flow offers a discount for paying now.

  2. 2

    The payment block raises a Razorpay link for the discounted total.

  3. 3

    Razorpay confirms and the flow marks the order prepaid and sends the confirmation.

  4. 4

    If the customer does not pay, the timeout branch places the order as COD instead.

How to connect it

  1. 1

    Connect Razorpay

    Add your Razorpay key and secret in Libromi Connect to link your merchant account.

  2. 2

    Add the payment block

    Set the amount from a variable and give the payment a reference your team will recognise.

  3. 3

    Build both outcomes

    Decide what happens when payment succeeds and what happens when it does not.

Frequently asked questions

Collect properly, not by screenshot

Connect Razorpay and let the flow verify every payment.