Connect Razorpay through its Technology Partner OAuth flow.
Account eligibility, provider charges, OAuth approval, webhook verification, and a representative payment test remain part of production setup.
Create a hosted Razorpay Payment Link after a customer confirms an order, booking, or amount. Continue the workflow from the provider's verified outcome, not from a click or an unverified reply.
In one line
Waaru can create, read, and cancel Razorpay Payment Links; read one payment or refund; and continue from verified payment-link, payment, refund, or authorization events.
Capability review updated .
Maintained by the Waaru product team. Read our editorial and product-claim review method.
Platform free. AI features are paid separately.
The customer opens Razorpay's hosted payment page. A verified and deduplicated event returns the outcome needed for the next workflow step.
Order W-1842
Payment request
Operating boundary
An eligible merchant authorizes the connection through Razorpay's Technology Partner OAuth flow.
Read one connection-scoped Payment Link, payment, or refund.
Create or cancel one hosted Payment Link with a stable Waaru reference.
Selected Payment Link, payment, refund, and authorization outcomes can continue a workflow after verification.
Authorize the account, configure webhook delivery, and test paid, failed, expired, and cancelled outcomes.
No refund creation, subscriptions, recurring links, payouts, Route transfers, UPI QR codes, or broad phone-number search.
Webhook deliveries are verified and deduplicated. An uncertain financial result is reconciled against the specific provider record before another irreversible step.
Payment request
Set the amount, currency, description, expiry, and optional customer or internal reference. Waaru returns the Razorpay link ID, short URL, amount, expiry, and current status for use in the customer journey.
Verification
Payment Link paid, partially paid, expired, and cancelled events can continue a workflow. Payment captured or failed and refund processed or failed events are also supported. Ambiguous success is reconciled with Razorpay before an irreversible downstream action.
Available actions
Setup
The merchant authorises an eligible Razorpay account through the Technology Partner OAuth flow, so the setup does not ask them to paste API keys into Waaru. Configure the provider webhook path for the connected account and test create, paid, failed, expired, and cancelled outcomes before live customer traffic. The production handoff should record who owns reconciliation when a financial write or event result is uncertain.
Use-case library
A hotel deposit, assisted D2C order, and appointment deposit can use the same Payment Link actions, but they need different source records, expiry rules, confirmation messages, and recovery owners. The Razorpay use-case library documents each journey in operational detail so a team can review the payment boundary before building it.
Current boundary
The current connector does not create refunds, subscriptions, recurring links, payouts, Route transfers, or UPI QR codes. It also does not run broad payment searches by phone number. Payment completes on Razorpay's hosted page, not inside WhatsApp.
Yes. A workflow can create a hosted Razorpay Payment Link and send its URL in the relevant WhatsApp conversation.
No. The link opens Razorpay's hosted payment page. Waaru continues the workflow after it receives and verifies the provider event.
Yes. It verifies the Razorpay webhook and deduplicates the event. When local state is ambiguous, it fetches the provider record before an irreversible next step.
No. It can read one refund and receive refund events, but refund creation, subscriptions, and recurring payment links are outside the current release.
No. The connector uses a Razorpay Technology Partner OAuth application. The merchant authorizes the connection through Razorpay.
Research notes
Primary provider references for OAuth, Payment Links, and webhook verification.
Razorpay Technology Partners can onboard businesses through OAuth rather than collecting merchant API keys.
Razorpay documentation · Accessed 13 August 2026
Razorpay exposes Payment Link create, fetch, and cancel operations.
Razorpay API documentation · Accessed 13 August 2026
Razorpay documents raw-body webhook signature validation.
Razorpay webhook documentation · Accessed 13 August 2026
Razorpay documents Payment Link paid, partially paid, expired, and cancelled webhook events.
Razorpay webhook documentation · Accessed 13 August 2026
Ready to ship a WhatsApp flow that doesn't break?
Public signup is open. The platform is free. AI features are paid separately.
