The WatEase Razorpay integration lets an Indian business collect payment inside a WhatsApp conversation — cards, UPI, netbanking, and wallets — without pushing the buyer out to an external checkout page. It is a first-party connector shipped in the product today: no Zapier middleman, no copy-paste glue code, no per-action usage fee. The connector handles its own webhook registration, retry and backoff policy, and reconciliation cadence, so a misbehaving upstream never silently drops an order.
Refunds, partial refunds, and dispute evidence flow back into the WatEase order timeline automatically, so the person answering the chat sees payment state in the same place they see the conversation. Razorpay then settles captured payments to your bank account on its standard settlement cycle — typically T+1.
How the Razorpay integration works
Connect in minutes with a guided key flow
There is no developer project to schedule. Setup is a guided API-key paste flow: you bring your Razorpay credentials, WatEase stores them encrypted at rest with AES-256-GCM, isolated per tenant in ap-south-1 (Mumbai). The connector registers the webhooks it needs and verifies the signature on every inbound Razorpay event before acting on it — a forged payment notification never updates an order. Setup typically takes 3–5 minutes, and credential rotation is supported from the dashboard; rotating a key re-issues all dependent webhooks automatically.
UPI-first checkout, with cards and netbanking behind it
Indian buyers expect UPI as a first-class option, with cards and netbanking second — and the integration is built in that order. WatEase wires UPI deep-links directly, so a customer taps once and pays from PhonePe, Google Pay, Paytm, or BHIM without ever leaving WhatsApp. Razorpay covers the cards, netbanking, and wallet rails on the same checkout, and supports recurring payments for subscription-style billing. Stripe and PayPal are intentionally not part of the WatEase stack: their Indian rates are non-competitive and the merchant-of-record model conflicts with Indian GST invoicing.
Refunds and disputes stay in the order timeline
When a buyer asks for their money back, the agent does not tab-switch into a gateway dashboard. Refunds and partial refunds are handled against the order, and dispute evidence flows back into the order timeline automatically — payment history, conversation history, and fulfilment history read as one record. That single timeline is what makes WhatsApp viable as a real sales channel rather than a lead-capture form in front of one.
Built to survive upstream failure
Payment infrastructure is judged on its worst day. The connector respects Retry-After headers and applies exponential backoff to Razorpay calls; 429 and 503 responses are queued and retried automatically, and persistent failures surface in the integration health dashboard with the upstream error code — so you act before customers notice. Outbound events for your own systems (order.created, payment.captured, and the rest) are HMAC-signed with a per-tenant secret, carry idempotency keys, and retry on 5xx.
What businesses use Razorpay + WhatsApp for
Catalog order checkout in chat
A buyer picks products over WhatsApp and pays by UPI, card, or netbanking in the same thread — no website redirect, no abandoned external cart.
Tap-once UPI collection
UPI deep-links open the buyer’s own payment app — PhonePe, Google Pay, Paytm, or BHIM — pre-filled, so payment is one tap, not a form.
Refunds without tab-switching
Full and partial refunds run against the order, and dispute evidence lands in the same timeline the support agent already has open.
Subscription-style billing
Recurring payments through Razorpay cover repeat-billing businesses — the same connector, the same encrypted credentials.
Frequently asked questions
Do I need a developer to connect Razorpay to WatEase?
No. The Razorpay connector uses a guided API-key paste flow — you bring your Razorpay credentials, WatEase stores them encrypted (AES-256-GCM, isolated per tenant in Mumbai), and the connector registers and signature-verifies its own webhooks. Setup typically takes 3–5 minutes. Technical teams that want event-level control can additionally use the outbound webhook API, which emits every order and payment event with HMAC signatures and idempotency keys.
Which payment methods work through the Razorpay integration?
Cards, UPI, netbanking, wallets, and recurring payments. UPI is wired as deep-links, so the customer taps once and pays from PhonePe, Google Pay, Paytm, or BHIM without leaving WhatsApp; Razorpay carries the card, netbanking, and wallet rails on the same checkout.
How do refunds and disputes work?
Refunds, partial refunds, and dispute evidence flow back into the WatEase order timeline automatically. The agent handling the conversation sees payment state, refund state, and dispute evidence next to the chat itself — no separate gateway dashboard required for routine cases.
Is the Razorpay integration available on the free plan?
Yes. The Free Forever plan supports payment and WhatsApp integrations, and integrations carry no extra per-action charge on any plan. The only separate cost is Meta’s standard per-conversation WhatsApp charges, which apply regardless of provider.
Explore the rest of the stack
More integrations: PhonePe + WhatsAppPaytm + WhatsAppShiprocket + WhatsApp