Skip to main content
Available in🇮🇳 India
Razorpay sends these events as a clarification moves through its statuses. Each event carries the whole requirement it is about, at products.payment_gateway.requirements. Know more about subscribing to and handling webhooks. Each event is named after the status the requirement moved to. Know more about statuses.

Requirement Needs Clarification

Triggered when Razorpay raises a requirement after a risk review, and again when Razorpay asks again after reviewing your responses. Show each input requirement to the sub-merchant and answer them in one update before due_at. The product’s status does not change. The sample below shows a new requirement.
Payload

Requirement Under Review

Triggered when you submit your responses, from needs_clarification or overdue. Razorpay is reviewing them. The sample below shows the requirement after you sent every response.
Payload

Requirement Overdue

Triggered when due_at passes with responses still due. The requirement moves to overdue. The sample below shows the alternative path, where due_at passes before you submit, so it is not a step after the under_review sample above. Razorpay reviews the account and may disable payments, put settlement on hold or suspend the product, each with its own event. You can still respond. Your submit moves the requirement to under_review.
Payload

Requirement Resolved

Triggered when Razorpay resolves the requirement, after its review or, in exceptional cases, without your responses. If an action pointed to it, the action’s own event follows when Razorpay reverses it, or account.product.payment_gateway.suspended follows if Razorpay escalates. A resolved requirement no longer appears in requirements when you fetch the account.
Payload
Last modified on November 20, 2026