AsyncAPI channel · Razorpay
· Razorpay Webhooks
webhook
Single inbound channel that receives every subscribed Razorpay event. The specific event is identified by the `event` field of the payload and mirrored in the `X-Razorpay-Event-Id` delivery header.
Channel address
webhook
Operations
subscribe
receiveRazorpayEvent
Receive Razorpay webhook events.
Messages
payment.authorized
A customer payment moved to the `authorized` state and is awaiting capture.
Content-Type:
application/jsonpayment.captured
An authorized payment was captured (funds will move to settlement).
Content-Type:
application/jsonpayment.failed
A payment attempt failed.
Content-Type:
application/jsonpayment.downtime.started
A payment method (UPI/cards/netbanking/etc.) is experiencing reduced success rates.
Content-Type:
application/jsonpayment.downtime.updated
An ongoing payment downtime advisory was updated.
Content-Type:
application/jsonpayment.downtime.resolved
A previously reported payment downtime has been resolved.
Content-Type:
application/jsonpayment.dispute.created
A customer or issuing bank raised a dispute on a payment.
Content-Type:
application/jsonpayment.dispute.won
Merchant evidence prevailed; the dispute was resolved in merchant's favor.
Content-Type:
application/jsonpayment.dispute.lost
The dispute was resolved against the merchant.
Content-Type:
application/jsonpayment.dispute.closed
The dispute lifecycle has been closed.
Content-Type:
application/jsonpayment.dispute.under_review
Submitted dispute evidence is being evaluated.
Content-Type:
application/jsonpayment.dispute.action_required
Merchant action is needed to respond to the dispute.
Content-Type:
application/jsonorder.paid
An order has been fully paid; fires alongside `payment.captured`.
Content-Type:
application/jsonrefund.created
A refund has been initiated against a payment.
Content-Type:
application/jsonrefund.processed
A refund was successfully processed.
Content-Type:
application/jsonrefund.failed
A refund attempt failed.
Content-Type:
application/jsonrefund.speed_changed
The processing speed for a refund (normal vs optimum) changed.
Content-Type:
application/jsonsubscription.authenticated
A subscription mandate was authenticated by the customer.
Content-Type:
application/jsonsubscription.activated
The first charge succeeded and the subscription is now active.
Content-Type:
application/jsonsubscription.charged
A scheduled subscription charge succeeded.
Content-Type:
application/jsonsubscription.completed
All scheduled subscription cycles have completed.
Content-Type:
application/jsonsubscription.updated
Subscription details (plan, quantity, addons) were modified.
Content-Type:
application/jsonsubscription.pending
A charge attempt failed; subscription is in retry/pending state.
Content-Type:
application/jsonsubscription.halted
Retries are exhausted; subscription has been halted.
Content-Type:
application/jsonsubscription.paused
Subscription has been paused by the merchant or customer.
Content-Type:
application/jsonsubscription.resumed
A paused subscription has resumed.
Content-Type:
application/jsonsubscription.cancelled
Subscription has been cancelled.
Content-Type:
application/jsoninvoice.paid
An invoice has been paid in full.
Content-Type:
application/jsoninvoice.partially_paid
An invoice has received a partial payment.
Content-Type:
application/jsoninvoice.expired
An invoice expired without being paid.
Content-Type:
application/jsonsettlement.processed
A settlement payout was processed to the merchant's (or sub-merchant's) bank account.
Content-Type:
application/jsonvirtual_account.created
A Smart Collect virtual account / UPI ID was created.
Content-Type:
application/jsonvirtual_account.credited
Funds were received into a virtual account via bank transfer or UPI.
Content-Type:
application/jsonvirtual_account.closed
A virtual account was closed.
Content-Type:
application/jsonpayment_link.paid
A payment link received a full payment.
Content-Type:
application/jsonpayment_link.partially_paid
A payment link received a partial payment.
Content-Type:
application/jsonpayment_link.cancelled
A payment link was cancelled.
Content-Type:
application/jsonpayment_link.expired
A payment link expired without being paid.
Content-Type:
application/jsontransfer.processed
A Razorpay Route transfer to a linked account completed.
Content-Type:
application/jsontransfer.failed
A Razorpay Route transfer to a linked account failed.
Content-Type:
application/jsonproduct.route.activated
Razorpay Route has been activated for the account.
Content-Type:
application/jsonproduct.route.under_review
Razorpay Route activation is pending review.
Content-Type:
application/jsonproduct.route.needs_clarification
Razorpay Route activation requires additional information.
Content-Type:
application/jsonAbout AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.
Work with this as data
Every channel here is available over the APIs.io API and to AI agents over MCP.