Available in🇮🇳 India
Fetching the account is always the source of truth. To avoid polling, subscribe to webhooks.
7.1 Fetch the Account
Fetch the account to see where it stands. The response shows:- The
business_profile, with itsstakeholders, and thebank_accountssubmitted so far, each with its verification - Each product in
products, with itsstatusandrequirements
GET /v1/accounts/{account_id}
Path Parameters
Path Parameters
account_id mandatory
: string The account ID, acc_-prefixed. For example, acc_TcdGEzmfKQzEl1.7.2 Product Status
Onboarding status lives on each product of the account. Activation needs the business’s KYC verified and the product’s own checks passed. These include the subcategory, and the website when one is sent. Razorpay checks the website again every year. An account takes payments once the product’sstatus is activated. You cannot set a product’s status through the API. Razorpay moves it as it reviews the product. Refer to Product States for every status and what to do in each.
7.3 Rejection and Suspension Reasons
Arejected or suspended product carries status_reason: a stable code to branch on and a description to show the sub-merchant. It is null in every other status. The wording of description can change, so branch only on code.
The table below lists the reasons:
A rejected product accepts no further changes. To try again, the sub-merchant starts a new account. A suspended product lists what would resolve it in its
requirements. Answer them like any other requirement.
7.4 Status Webhooks
Subscribe to webhooks on the Partner Dashboard, once per mode, with an https URL, a secret and the events to receive. A product event fires on every change tounder_review, edd_pending, needs_clarification, activated, rejected or suspended. This includes a change your own call caused, such as submitting. created and in_progress have no event.
Know more about webhooks and payloads.