Available in🇮🇳 India
The Onboarding APIs let partner platforms create and manage sub-merchant accounts. These webhook events tell your server when something changes on an account, so you do not need to poll. Subscribe to them on the Partner Dashboard, once for each mode. Know more about the Onboarding APIs.
List of Onboarding APIs Webhook Events
The table below lists the webhook events available for the Onboarding APIs:Sample Payloads
Each event carries what changed, not the whole account.payload.account has the account’s id and updated_at, plus each part that changed. A product event carries the complete product, with its status and requirements.
Account Product Under Review
Razorpay sendsaccount.product.under_review when the update that accepts the terms of service submits a product, or when submit_clarification resubmits it after a clarification. It also fires when the product’s video KYC call finishes. The KYC details stay locked from submission on. Changing one returns 409 field_locked. Tell the sub-merchant that Razorpay is reviewing their details. Nothing is due from them. Most products skip this state and go straight to account.product.activated.
account.product.under_review
Account Product EDD Pending
Razorpay sendsaccount.product.edd_pending when it needs enhanced due diligence (EDD) after submission before it can activate the product. This usually happens because the sub-merchant has no Central KYC Records Registry (CKYC) record. The product’s requirements hold one item, create_video_kyc_link, an action. Run it and show the sub-merchant the link. Know more about video KYC.
account.product.edd_pending
Account Product Needs Clarification
Razorpay sendsaccount.product.needs_clarification when a reviewer needs more information before the product can be activated. The product’s requirements list only the flagged points. Each is usually a composite requirement with fulfillment_criteria: one_of, with the reviewer’s reason in its requirement_reason. Show them to the sub-merchant and send the answers with an update. Once every flagged point is answered, send products.<product_type>.submit_clarification: true in its own call. Know more about clarifications.
account.product.needs_clarification
Account Product Activated
Razorpay sendsaccount.product.activated when the product is live and the account takes payments. From then on, the KYC details are locked. A few details can still change after a manual review. Know more about account management.
account.product.activated
Account Product Rejected
Razorpay sendsaccount.product.rejected when it turns the product down. The product’s status_reason says why. The product accepts no further changes. To try again, the sub-merchant starts a new account.
account.product.rejected
Account Product Suspended
Razorpay sendsaccount.product.suspended when it suspends an activated product, for example when the yearly website check fails and the sub-merchant does not resolve it. Payments stop until the sub-merchant resolves it. The product’s status_reason says why, and what would resolve it is in its requirements. Answer them like any other requirement.
account.product.suspended
Account Requirements Updated
Razorpay sendsaccount.requirements.updated when a product’s requirements change without a call from you. For example:
account.requirements.updated
Account Consent Withdrawn
Razorpay sendsaccount.consent.withdrawn when the sub-merchant withdraws, through Razorpay, your permission to act on its account, or asks Razorpay to delete its data. From then on, every call you make on the account returns 403 consent_withdrawn. Stop acting on the account and delete what you still hold about it. The payload carries only the account’s id and updated_at. product is null.
account.consent.withdrawn