Skip to main content
Available in🇮🇳 India
A requirement is something Razorpay still needs about the account before it can activate an instrument. It is the same Requirement object the Onboarding APIs return, filtered to the instrument. There is no separate clarification object to track. A requirement describes the account. One requirement can appear on several instruments, and answering it once fulfils it for all of them.

3.1 Read the Requirements

Read requirements on the instrument. For a netbanking bank that needs onboarding:
Response

3.2 Answer Each Requirement

How you answer depends on requirement_type: Know more about the requirement object and how to collect requirements.

3.3 Confirm the Answer

Fetch its payment method again. An answered requirement shows status: fulfilled and the answer in response. Razorpay continues the onboarding on its own. There is no separate answer call, and nothing to resubmit or restart.

3.4 Answer a Clarification

When Razorpay or a bank asks for more, the instrument’s status is needs_clarification. requirements lists the flagged points, with the reviewer’s comment in requirement_reason. A flagged point is usually a one_of composite. Answer with a corrected value or document, or with a text reply where the point offers a reply input. Know more about handling needs clarification.
Watch Out!
  • A requirement can carry a due_at deadline, as a Unix timestamp in seconds. It is null when there is none.
  • Send a document that matches metadata.constraints: the accepted file types and the maximum size.
  • requirement_level can be mandatory, conditional or optional. A conditional requirement is needed only in some cases, such as the option you take in a one_of.

Next Step

Follow Onboarding
Last modified on November 18, 2026