How to Set Up Razorpay Webhook Notifications with Webhookify

Razorpay is India's leading payment gateway platform, enabling businesses to accept, process, and disburse payments through a comprehensive suite of products including payment links, subscriptions, invoices, and smart collect. Used by millions of businesses across India and internationally, Razorpay processes payments via UPI, credit/debit cards, net banking, wallets, and more. Razorpay's webhook system sends real-time HTTP notifications when payment events occur in your account -- successful payments, failed transactions, subscription renewals, refunds, and disputes. With Webhookify, you can capture every Razorpay event and receive instant, AI-powered notifications on Telegram, Discord, Slack, Email, or mobile push with a cash register sound for every successful payment. Whether you run an e-commerce store, a SaaS product, or a marketplace, real-time payment visibility is essential.

This guide shows you how to connect Razorpay webhooks to Webhookify so you never miss a payment, refund, or subscription event again.

Why Monitor Razorpay Webhooks with Webhookify?

• Instant Payment Alerts with Cash Sound: Hear a cash register sound on your phone every time a payment is captured through Razorpay. Whether it is a UPI payment, card transaction, or net banking transfer, Webhookify notifies you the instant funds are collected.

• Failed Payment Detection: Payment failures can result in lost revenue and poor customer experience. Webhookify sends you an immediate alert when a payment fails, including the failure reason, so you can follow up with the customer or investigate technical issues.

• Subscription Lifecycle Monitoring: Track the complete subscription lifecycle from activation to cancellation. Get Slack or Discord alerts for subscription renewals, failed charges, and cancellations, enabling your team to manage churn proactively.

• AI-Powered INR Summaries: Razorpay payloads contain amounts in paisa (smallest currency unit), entity IDs, method details, and bank references. Webhookify's AI converts these into human-readable summaries like "Payment of Rs. 2,499 captured via UPI (john@okaxis) for Order #12345."

• Dispute and Refund Awareness: Get notified immediately when a customer raises a dispute (chargeback) or when a refund is processed. Timely awareness of disputes gives you a better chance of resolving them within the response window.

Prerequisites

1. A Razorpay account (Test or Live mode). Sign up at razorpay.com if you do not have one.
2. Razorpay API keys generated for your account.
3. A Webhookify account. Sign up for free at webhookify.app.
4. A notification channel configured in Webhookify (Telegram bot, Discord webhook, Slack workspace, or Email address).
5. Access to the Razorpay Dashboard with permissions to manage webhook settings.

Step-by-Step Setup Guide

https://hook.webhookify.app/w/your-unique-endpoint-id

Razorpay Webhook Events You Can Monitor

Complete reference of Razorpay webhook events that Webhookify captures:

Payments:

• payment.authorized -- Payment authorized, funds held
• payment.captured -- Payment captured, funds collected
• payment.failed -- Payment attempt failed
• payment.dispute.created -- Chargeback/dispute raised
• payment.dispute.won -- Dispute resolved in merchant's favor
• payment.dispute.lost -- Dispute resolved in customer's favor
• payment.downtime.started -- Payment method experiencing issues
• payment.downtime.resolved -- Payment method restored

Subscriptions:

• subscription.activated -- New subscription activated
• subscription.charged -- Subscription renewal charged
• subscription.completed -- All billing cycles completed
• subscription.updated -- Subscription modified
• subscription.pending -- Charge pending
• subscription.halted -- Subscription halted (payment failures)
• subscription.cancelled -- Subscription cancelled
• subscription.paused -- Subscription paused
• subscription.resumed -- Subscription resumed

Refunds:

• refund.created -- Refund initiated
• refund.processed -- Refund completed
• refund.failed -- Refund failed
• refund.speed_changed -- Refund speed changed

Orders:

• order.paid -- Order fully paid

Invoices:

• invoice.paid -- Invoice paid in full
• invoice.partially_paid -- Invoice partially paid
• invoice.expired -- Invoice expired

Settlements:

• settlement.processed -- Settlement processed to bank account

Virtual Accounts:

• virtual_account.credited -- Virtual account received funds
• virtual_account.closed -- Virtual account closed

Each payload includes the entity ID, amount (in paisa), currency, method (UPI, card, netbanking, wallet), customer details, and timestamps.

Real-World Use Cases

• D2C Brand Sales Tracking: Set up mobile push notifications with cash sound for every payment.captured event. Whether customers pay via UPI, credit card, or COD prepayment, you will hear the sale the instant it happens. Many Indian D2C founders keep a daily tally just by counting notification sounds.

• SaaS Subscription Management: Route subscription.activated, subscription.halted, and subscription.cancelled events to a Slack channel. Your customer success team can see when new users subscribe, when payments fail (halted), and when customers cancel, enabling timely intervention.

• Refund and Dispute Monitoring: Forward refund.created and payment.dispute.created events to your operations team via Discord or email. Disputes have a limited response window in India, so instant awareness is critical for protecting your revenue.

• Payment Downtime Awareness: Monitor payment.downtime.started and payment.downtime.resolved events to know when specific payment methods (UPI, net banking, specific banks) are experiencing issues. This helps you proactively communicate with customers and reduce failed transaction frustration.

Example Notification

When a payment is captured in Razorpay, Webhookify delivers a notification like this:

{
  "entity": "event",
  "account_id": "acc_BFQ7uQEaa7j2P5",
  "event": "payment.captured",
  "contains": ["payment"],
  "payload": {
    "payment": {
      "entity": {
        "id": "pay_FgR7UNaVoM3qEP",
        "entity": "payment",
        "amount": 249900,
        "currency": "INR",
        "status": "captured",
        "order_id": "order_FgR7MNOP8a2b3c",
        "method": "upi",
        "vpa": "john@okaxis",
        "description": "Pro Plan - Annual Subscription",
        "email": "john@example.com",
        "contact": "+919876543210",
        "created_at": 1740148320
      }
    }
  },
  "created_at": 1740148325
}

Webhookify's AI summary would display:

Razorpay Payment Captured: Rs. 2,499.00 INR via UPI (john@okaxis). Description: "Pro Plan - Annual Subscription." Customer: john@example.com (+919876543210). Order: order_FgR7MNOP8a2b3c.

If you have the cash sound enabled, you will hear a "cha-ching" along with this notification.

Troubleshooting

1. No webhook events received after creating the webhook: Verify you are in the correct mode (Test vs. Live) in the Razorpay Dashboard. Webhooks created in Test Mode only fire for test transactions, and vice versa. Also confirm you selected at least one event type.

2. "payment.authorized" event received but not "payment.captured": If you have auto-capture disabled in your Razorpay settings, payments are authorized but not automatically captured. You need to manually capture the payment (or configure auto-capture) for the payment.captured event to fire.

3. Webhook shows "Failed" status in Razorpay Dashboard: Check the webhook URL for typos or extra characters. Razorpay requires HTTPS endpoints (which Webhookify provides). If the URL is correct, try deleting and re-creating the webhook.

4. Amounts appear in paisa instead of rupees: Razorpay sends all amounts in the smallest currency unit (paisa for INR, cents for USD). An amount of 249900 means Rs. 2,499.00. Webhookify's AI automatically converts these to human-readable amounts in the notification summary.

5. Duplicate webhook events: Razorpay retries webhook delivery up to 24 times if it does not receive a successful response. Webhookify responds instantly, but network issues could occasionally cause retries. Each event has a unique event ID and payload.payment.entity.id that you can use to identify duplicates.

Related Articles

• Webhook Security Best Practices
• How to Receive Webhook Notifications on Telegram
• Real-Time Payment Failure Alerts with Webhooks
• Revenue Monitoring for Indie Hackers & Solo Founders
• How to Set Up Stripe Webhook Notifications
• How to Set Up Square Webhook Notifications