> ## Documentation Index
> Fetch the complete documentation index at: https://razorpay.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# 2. Collect Requirements

> Collect the KYC details a sub-merchant account needs using Razorpay Onboarding APIs.

Available in
🇮🇳 India

Each product's `requirements` list what is still due, in any status and in journey order. A requirement disappears once it is satisfied, and its data then lives on the account. The list is empty when nothing is due. Build your forms from this list, not from hard-coded rules.

## 2.1 Read a Requirement

The table below lists the attributes of a requirement:

| Attribute | Use |
| - | - |
| `id` | The unique ID of this requirement node, `req_`-prefixed. |
| `requirement_code` | The requirement's code, from a closed list, such as `individual_pan`, `ckyc_fetch` or `proof_of_address_for_individual`. For an action, it is the action's name, such as `send_ckyc_otp`. Codes are unique within one composite. The top-level list can hold the same code twice, once for each of 2 people. For example, the authorised person and a stakeholder can each owe a proof of address. The inputs' `field_path` tells them apart. |
| `requirement_level` | `mandatory`: needed before submission. `optional`: not needed to submit, such as an address's second line. `conditional`: needed only under a condition. |
| `requirement_type` | `input`: send a value or document at `field_path`. `action`: run the action named in `requirement_code`. Its response lists what is due next. `composite`: several requirements that answer one point, as its `fulfillment_criteria` says. |
| `description` | A sentence to show the sub-merchant. |
| `requirement_reason` | Why the requirement was raised, such as a reviewer's reason in `needs_clarification` or a failed check. Shown only when a review or a check raised the requirement. |
| `field_path` | Inputs only. Where to send the value in an update, as a dot path. For example, `business_profile.authorized_person.identity_numbers.individual_pan`. The path names the person it is about, such as `business_profile.stakeholders.<stakeholder_id>.identity_numbers.individual_pan` for a stakeholder. |
| `value_type` | Inputs only. `text` for a value, `enum` for one of `options`, `multi_select` for one or more of `options`, `boolean` for `true` or `false` and `document` for a file. |
| `response` | Inputs only, once answered. The response submitted for this requirement. It holds `text` for a `text` input and `documents` for a `document` input. It also carries `created_at`, `updated_at` and `metadata`. |
| `options` | `enum` or `multi_select` inputs only. The label and value pairs to choose from. |
| `fulfillment_criteria` | Composites only. `one_of`: answer any one of its sub-requirements. `any_of`: answer one or more of them. `all_of`: answer every one, apart from an optional one. |
| `sub_requirements` | Composites only. The requirements that answer it. Each is a full requirement and can itself be a composite. |
| `status` | Where the requirement stands: `created`, `needs_clarification`, `under_review`, `resolved`, `overdue`, `rejected`, `expired` or `cancelled`. Know more about [requirement status](https://razorpay.com/docs/api/partners/accounts/requirement-entity.md). |
| `due_at` | The deadline to fulfil the requirement, as a Unix timestamp in seconds. Shown only when the requirement has a deadline. |
| `metadata` | Any requirement, only when it has any. More context or configuration, such as what an action needs. See [Requirement Metadata](#2-1-1-requirement-metadata). A link an action mints is in the action's response. |

Every sub-requirement of a `one_of` is `conditional`, needed only if it is the option chosen. Some requirements depend on the business, such as a Goods and Services Tax Identification Number (GSTIN). These are `conditional`, with the condition in the description.

A document input takes a pre-signed `{ "url" }` or an uploaded document's `{ "id" }`. Know more about [uploading documents](https://razorpay.com/docs/partners/aggregators/onboarding-api/submit-information.md#3-6-upload-documents).

### 2.1.1 Requirement Metadata

`metadata` is an optional, free-form object of key-value pairs for extensibility on any requirement. It carries more context or configuration, such as what an action needs on an action requirement, without changing the requirement schema.

### 2.1.2 Requirement Keys

A requirement carries only the keys its `requirement_type` uses:

* **Every requirement:** `id`, `requirement_code`, `requirement_level`, `requirement_type`, `description` and `status`. It adds `requirement_reason` when a review or a check raised it, and `due_at` when it has a deadline.
* **An input:** Adds `field_path` and `value_type`. It also carries `response` once answered, `options` for an `enum` or `multi_select` and `metadata` when it has any.
* **A composite:** Adds `fulfillment_criteria` and `sub_requirements`, with `metadata` when it has any.
* **An action:** Adds `metadata` when it has any.

Every other object the API returns has every declared property present, with `null` when it does not apply. Maps list only the entries that exist.

Why a value failed sits on the element itself, in its `verification.error_code`, with the requirement due again. See [Failed-Check Codes](#2-3-failed-check-codes).

Refer to the [Requirement Entity](https://razorpay.com/docs/api/partners/accounts/requirement-entity.md) for every attribute.

## 2.2 Composite Requirements

A point answered in more than one way, or with several values, is one requirement of `requirement_type` `composite`. Its `sub_requirements` answer it, as its `fulfillment_criteria` says:

* **`one_of`:** Answer any one sub-requirement. Each is `conditional`, so offer them as one choice. Sending one clears the composite.
* **`any_of`:** Answer one or more sub-requirements.
* **`all_of`:** Answer every sub-requirement. Each is `mandatory`, or `optional` when it can be left out, such as an address's `address_line2`.

The composite's `requirement_code` names the point. A sub-requirement can itself be a composite. The person a requirement is about is in its inputs' `field_path`.

> [tab] CKYC Fetch
>
> Razorpay fetches the Central KYC Records Registry (CKYC) record with a code, or the sub-merchant skips it:
>
> ```json ckyc_fetch theme={null}
> {
>   "id": "req_hocykxcAkjCdtB",
>   "requirement_code": "ckyc_fetch",
>   "requirement_level": "mandatory",
>   "requirement_type": "composite",
>   "description": "The person's CKYC record, fetched with a code or skipped.",
>   "fulfillment_criteria": "one_of",
>   "sub_requirements": [
>     {
>       "id": "req_2KRiIGIhuAPNW6",
>       "requirement_code": "skip_ckyc",
>       "requirement_level": "conditional",
>       "requirement_type": "input",
>       "description": "Skip CKYC.",
>       "field_path": "business_profile.authorized_person.identity_numbers.individual_ckyc.is_skipped",
>       "value_type": "boolean",
>       "status": "created"
>     },
>     {
>       "id": "req_L3rskP8gX6YVHh",
>       "requirement_code": "send_ckyc_otp",
>       "requirement_level": "conditional",
>       "requirement_type": "action",
>       "description": "A Central KYC record was found for your PAN. Get a code on the mobile on your CKYC record to fetch it.",
>       "status": "created"
>     }
>   ],
>   "status": "created"
> }
> ```

> [tab] Proof of Address
>
> The proof of address nests 2 levels. The sub-merchant uses DigiLocker or uploads both sides of one document:
>
> ```json proof_of_address_for_individual theme={null}
> {
>   "id": "req_63ayeHknvAqF3b",
>   "requirement_code": "proof_of_address_for_individual",
>   "requirement_level": "mandatory",
>   "requirement_type": "composite",
>   "description": "Verify the proof of address for an individual. It can be done through one of the multiple ways.",
>   "fulfillment_criteria": "one_of",
>   "sub_requirements": [
>     {
>       "id": "req_8Z7cOzH9RmInpe",
>       "requirement_code": "create_aadhaar_digilocker_link",
>       "requirement_level": "conditional",
>       "requirement_type": "action",
>       "description": "Share your Aadhaar from DigiLocker to verify your address.",
>       "status": "created"
>     },
>     {
>       "id": "req_ZldFJm6xUdiytV",
>       "requirement_code": "poa_via_document_upload",
>       "requirement_level": "conditional",
>       "requirement_type": "composite",
>       "description": "Upload both sides of the proof of address document.",
>       "fulfillment_criteria": "one_of",
>       "sub_requirements": [
>         {
>           "id": "req_TAi3IfSrpQ1saS",
>           "requirement_code": "poa_via_aadhaar_documents",
>           "requirement_level": "conditional",
>           "requirement_type": "composite",
>           "description": "Aadhaar: front and back.",
>           "fulfillment_criteria": "all_of",
>           "sub_requirements": [
>             {
>               "id": "req_3cewYYSLf1kdD3",
>               "requirement_code": "poa_aadhaar_front",
>               "requirement_level": "mandatory",
>               "requirement_type": "input",
>               "description": "Front side of Aadhaar.",
>               "field_path": "business_profile.authorized_person.documents.aadhaar_front",
>               "value_type": "document",
>               "status": "created"
>             },
>             {
>               "id": "req_h0bDEfO2nsiz11",
>               "requirement_code": "poa_aadhaar_back",
>               "requirement_level": "mandatory",
>               "requirement_type": "input",
>               "description": "Back side of Aadhaar.",
>               "field_path": "business_profile.authorized_person.documents.aadhaar_back",
>               "value_type": "document",
>               "status": "created"
>             }
>           ],
>           "status": "created"
>         },
>         {
>           "id": "req_NLtTxBNkCbhnO5",
>           "requirement_code": "poa_via_passport_documents",
>           "requirement_level": "conditional",
>           "requirement_type": "composite",
>           "description": "Passport: front and back.",
>           "fulfillment_criteria": "all_of",
>           "sub_requirements": [
>             {
>               "id": "req_fNrgaH4kj0U0xo",
>               "requirement_code": "poa_passport_front",
>               "requirement_level": "mandatory",
>               "requirement_type": "input",
>               "description": "Front side of the passport.",
>               "field_path": "business_profile.authorized_person.documents.passport_front",
>               "value_type": "document",
>               "status": "created"
>             },
>             {
>               "id": "req_wa2RY80UNI5xz8",
>               "requirement_code": "poa_passport_back",
>               "requirement_level": "mandatory",
>               "requirement_type": "input",
>               "description": "Back side of the passport.",
>               "field_path": "business_profile.authorized_person.documents.passport_back",
>               "value_type": "document",
>               "status": "created"
>             }
>           ],
>           "status": "created"
>         },
>         {
>           "id": "req_LbhXMBnfvBDfU5",
>           "requirement_code": "poa_via_voter_id_documents",
>           "requirement_level": "conditional",
>           "requirement_type": "composite",
>           "description": "Voter ID: front and back.",
>           "fulfillment_criteria": "all_of",
>           "sub_requirements": [
>             {
>               "id": "req_hQpfCIgX1EPiJV",
>               "requirement_code": "poa_voter_id_front",
>               "requirement_level": "mandatory",
>               "requirement_type": "input",
>               "description": "Front side of the voter ID.",
>               "field_path": "business_profile.authorized_person.documents.voter_id_front",
>               "value_type": "document",
>               "status": "created"
>             },
>             {
>               "id": "req_6bWvV57FbjHh6b",
>               "requirement_code": "poa_voter_id_back",
>               "requirement_level": "mandatory",
>               "requirement_type": "input",
>               "description": "Back side of the voter ID.",
>               "field_path": "business_profile.authorized_person.documents.voter_id_back",
>               "value_type": "document",
>               "status": "created"
>             }
>           ],
>           "status": "created"
>         }
>       ],
>       "status": "created"
>     }
>   ],
>   "status": "created"
> }
> ```

The table below lists the composite requirements:

| `requirement_code` | Point | `fulfillment_criteria` | `sub_requirements` |
| - | - | - | - |
| `ckyc_fetch` | `The person's CKYC record, fetched with a code or skipped.` | `one_of` | `skip_ckyc`, `send_ckyc_otp` |
| `individual_pan` | `The person's PAN: the number, or the PAN card.` | `one_of` | `individual_pan_number`, `individual_pan_card` |
| `business_pan` | `The business PAN: the number, or the PAN card.` | `one_of` | `business_pan_number`, `business_pan_card` |
| `proof_of_address_for_individual` | `Verify the proof of address for an individual. It can be done through one of the multiple ways.` | `one_of` | `create_aadhaar_digilocker_link`, `poa_via_document_upload` (`one_of`: `poa_via_aadhaar_documents` (`all_of`: `poa_aadhaar_front`, `poa_aadhaar_back`), `poa_via_passport_documents` (`all_of`: `poa_passport_front`, `poa_passport_back`), `poa_via_voter_id_documents` (`all_of`: `poa_voter_id_front`, `poa_voter_id_back`)) |
| `business_identity` | `The company's identity: the CIN or the certificate of incorporation.` | `one_of` | `cin`, `certificate_of_incorporation` |
| `proof_of_business` | `Proof that your business exists: one registration document and one registration number.` | `all_of` | `proof_of_business_document` (`one_of`: `gst_certificate`, `udyam_registration_certificate`, `shop_establishment`), `proof_of_business_number` (`one_of`: `gstin`, `udyam_registration`) |
| `bank_account` | `Your settlement bank account.` | `one_of` | `settlement_bank_account` (`all_of`: `bank_account_number`, `bank_routing_code`, `bank_routing_code_type`), `create_upi_link`, `clarify_bank_account` |
| `settlement_bank_account` | `The bank account that receives settlements, in the name on your PAN.` | `all_of` | `bank_account_number`, `bank_routing_code`, `bank_routing_code_type` |
| `website` | `Your website.` | `one_of` | `website_url`, `clarify_website` |
| `payment_channels` | `Where you take payments: a website, an Android app or an iOS app. Any one is enough.` | `one_of` | `website_url`, `app_android_url`, `app_ios_url` |
| `accept_terms_of_service` | `Show the sub-merchant Razorpay's terms of service and record their acceptance.` | `all_of` | `acceptance_ip`, `acceptance_device_fingerprint_id` |
| `business_model_clarifications` | `Answer the questions about your business model.` | `all_of` | `<question_id>` |
| `registered_address` | `Your business's registered address.` | `all_of` | `address_line1`, `address_line2`, `address_city`, `address_state`, `address_postal_code`, `address_country` |
| `operational_address` | `The address your business operates from.` | `all_of` | `address_line1`, `address_line2`, `address_city`, `address_state`, `address_postal_code`, `address_country` |
| `authorized_person` | `The authorized person: their name and PAN.` | `all_of` | `authorized_person_name`, `individual_pan` (`one_of`: `individual_pan_number`, `individual_pan_card`) |

Some composites apply only in certain cases:

* **`business_identity`:** For a private limited, public limited or Section 8 company. The Corporate Identification Number (CIN) or the certificate of incorporation answers it.
* **`proof_of_business`:** For a proprietorship.
* **`bank_account`:** Listed only after a failed check or in `needs_clarification`. Otherwise, it is listed as `settlement_bank_account`. Its `clarify_bank_account` option appears only in `needs_clarification`.
* **`website`:** Listed only in `needs_clarification`. Otherwise, it is listed as `website_url`.
* **`payment_channels`:** Optional. Any one channel answers it.
* **`accept_terms_of_service`:** Sending it submits the product.
* **`business_model_clarifications`:** One input per question, coded by the question's ID, with the question's `options`. Its `value_type` follows the question's `bmc_input_type`: `single_select` becomes `enum`, `multi_select` stays `multi_select` and `free_text` becomes `text`. Know more about the [business model questions](https://razorpay.com/docs/api/partners/accounts/business-model-questions.md) for each subcategory.

### 2.2.1 Input Paths

The [Requirement Entity](https://razorpay.com/docs/api/partners/accounts/requirement-entity.md) lists each input's `value_type` and `field_path`. Input paths follow the account:

* **A person:** Under `business_profile.authorized_person`, or `business_profile.stakeholders.<stakeholder_id>` for a stakeholder.
* **A business identifier or document:** Under `business_profile.identity_numbers` or `business_profile.documents`.
* **An address:** Its parts in the `business_profile.addresses` item of that `type`, such as `business_profile.addresses[type=registered_address].line1`.
* **The bank account:** Under `bank_accounts.settlements_primary`.
* **A reply:** Under `products.<product_type>.clarification_responses`, such as `products.payment_gateway.clarification_responses`.

### 2.2.2 How Composites Collapse

A document with 2 sides is an `all_of` pair. Both sides are due together, and a request can send them at once or one at a time. A satisfied requirement drops out, and a composite drops out once it is satisfied.

A composite left with one sub-requirement is returned as that sub-requirement, at the composite's `requirement_level`:

* Before any bank check has failed, `bank_account` comes back as `settlement_bank_account`.
* Outside `needs_clarification`, `website` comes back as `website_url`.

The exception is `ckyc_fetch`, which always comes back whole.

Send the bank account's 3 inputs together in one update, under `bank_accounts.settlements_primary`.

A GSTIN asked for on its own, for a business type other than a proprietorship, is `conditional`. The condition is in its description, for example: `Your GSTIN. Needed if your turnover is over ₹40 lakh or you sell across states.`

## 2.3 Failed-Check Codes

A failed check is a `200`, not an error. The element's `verification.status` is `rejected`, with the code in `verification.error_code`. Its requirement comes back due, with a `requirement_reason`. Branch on the code and show `verification.error_description` to the sub-merchant.

Some checks behave differently:

* **Link codes:** `link_expired`, `video_kyc_failed`, `digilocker_failed` and `upi_payment_failed` have no element to carry them. The action comes back due, without a link.
* **Phone or email One-Time Password (OTP):** Carries no error code. A wrong code leaves the code due. An expired code, or 3 wrong tries, brings the send action back.

The tables below list every code a failed check can carry, grouped by check:

> [accordion] PAN and PAN Card
>
> | Error Code | Check | When | `error_description` | What Is Due Next |
> | - | - | - | - | - |
> | `pan_not_found` | PAN | The PAN registry has no such PAN or rejected it as invalid. | `We couldn't find this PAN. Check the number, or upload the PAN card.` | `The PAN again, or the PAN card, as the options of one composite requirement.` |
> | `pan_name_mismatch` | PAN | The PAN exists, but its holder is not the authorised person named for the company. | `This PAN belongs to someone other than the signatory. Send the signatory's own PAN.` | `The signatory's name and PAN again.` |
> | `pan_check_unavailable` | PAN | The PAN registry did not answer or returned an error. Nothing is wrong with the PAN. | `We couldn't check this PAN at the moment. Upload the PAN card instead.` | `The PAN card; or send the PAN again later.` |
> | `promoter_underage` | PAN | The PAN holder is under 18. | `Based on the date of birth linked to this PAN, you must be 18 years or older to register with Razorpay. If you believe this is an error, contact Razorpay support.` | `Nothing the platform can send clears it; the sub-merchant contacts Razorpay.` |
> | `pan_card_mismatch` | PAN card | The PAN printed on the card is not the PAN sent. | `The PAN on this card doesn't match the PAN you entered. Upload the card for that PAN.` | `The PAN card again.` |
> | `pan_card_name_mismatch` | PAN card | The name on the card is not the owner's or the authorised person's. | `The name on this PAN card doesn't match. Upload your own PAN card.` | `The PAN card again.` |
> | `pan_card_name_unreadable` | PAN card | Razorpay could not read a name or number off the card. | `We couldn't read this PAN card. Upload a clear photo or scan of the front.` | `The PAN card again.` |
> | `not_a_pan_card` | PAN card | The file is not a PAN card. | `This doesn't look like a PAN card. Upload the front of your PAN card.` | `The PAN card again.` |

> [accordion] CKYC and Proof of Address
>
> | Error Code | Check | When | `error_description` | What Is Due Next |
> | - | - | - | - | - |
> | `otp_invalid` | CKYC code | The CKYC code does not match the one sent. | `The code didn't match. Try again, or request a new code.` | `The corrected code, with the same request ID: ckyc_otp and ckyc_request_id stay due.` |
> | `otp_expired` | CKYC code | The CKYC code was right but expired. This also applies after 3 wrong tries. | `This code has expired. Request a new code.` | `send_ckyc_otp again, for a new code: the send action is due again.` |
> | `ckyc_unavailable` | CKYC | Razorpay could not download the CKYC record, for a system reason. | `We couldn't fetch your KYC record. Upload a proof of address instead.` | `The proof of address (Aadhaar, passport or voter ID).` |
> | `poa_name_mismatch` | Proof of address | The address proof is not in the person's name. | `The name on this document doesn't match. Upload an address proof in your own name.` | `The proof of address again.` |
> | `poa_unreadable` | Proof of address | Razorpay could not read the address proof. | `We couldn't read this document. Upload a clear photo or scan.` | `The proof of address again.` |

> [accordion] Bank Account
>
> | Error Code | Check | When | `error_description` | What Is Due Next |
> | - | - | - | - | - |
> | `bank_name_mismatch` | Bank account | The account holder's name does not match the PAN name or the business name. | `The account must be in the name of your business. Please use a different account.` | `Another account, or a ₹1 UPI payment from it, as the options of one composite requirement.` |
> | `bank_details_incorrect` | Bank account | The account number or Indian Financial System Code (IFSC) is wrong. | `The account number or IFSC is incorrect. Check the details and try again.` | `The account again, or a ₹1 UPI payment from it.` |
> | `bank_account_unusable` | Bank account | The bank reported the account as frozen, blocked, closed or Non-Resident External (NRE). | `This account cannot receive payments. Please use a different bank account.` | `A different account, or a ₹1 UPI payment from one.` |
> | `bank_check_unavailable` | Bank account | Razorpay could not reach the bank. Nothing is wrong with the account. | `We could not reach your bank to verify the account. Verify it with a ₹1 UPI payment from the account.` | `The bank_account composite requirement again: the account, or a ₹1 UPI payment from it.` |
> | `bank_not_verified` | Bank account | Any other failure. Razorpay does not say why. | `We could not verify this account. Check the details and try again.` | `The account again, or a ₹1 UPI payment from it.` |

> [accordion] GSTIN and Udyam Number
>
> | Error Code | Check | When | `error_description` | What Is Due Next |
> | - | - | - | - | - |
> | `gstin_name_mismatch` | GSTIN | The GSTIN is registered to another business. | `This GSTIN is registered to a different business. Check the GSTIN, or send your Udyam number instead.` | `The GSTIN again, or the Udyam number.` |
> | `gstin_not_found` | GSTIN | The Goods and Services Tax (GST) registry has no such GSTIN or lists it as cancelled. | `We couldn't find this GSTIN. Check the number, or send your Udyam number instead.` | `The GSTIN again, or the Udyam number.` |
> | `udyam_name_mismatch` | Udyam number | The Udyam registration is in another business's name. | `This Udyam number is registered to a different business. Check the number, or send your GSTIN instead.` | `The Udyam number again, or the GSTIN.` |
> | `udyam_not_found` | Udyam number | The Udyam registry has no such number. | `We couldn't find this Udyam number. Check the number, or send your GSTIN instead.` | `The Udyam number again, or the GSTIN.` |

> [accordion] Website
>
> | Error Code | Check | When | `error_description` | What Is Due Next |
> | - | - | - | - | - |
> | `website_unreachable` | Website | Razorpay could not open the website, or the website is not live. | `We couldn't open your website. Check that it's live, or share another one.` | `The website again.` |

> [accordion] Links
>
> | Error Code | Check | When | `error_description` | What Is Due Next |
> | - | - | - | - | - |
> | `link_expired` | Link | The sub-merchant did not complete the step before `metadata.expires_at`. | `This link has expired. Run the action again for a new link.` | `The action is due again: run it for a new link.` |
> | `video_kyc_failed` | Video KYC | The agent could not verify the person on the call. For example, the face did not match the PAN photo or the call dropped. | `We couldn't complete your video KYC. Start a new call when you're ready.` | `The action is due again: run it for a new call.` |
> | `digilocker_failed` | DigiLocker | The sub-merchant declined to share the Aadhaar in DigiLocker or DigiLocker returned no Aadhaar. | `We didn't get your Aadhaar from DigiLocker. Try again, or upload a proof of address.` | `The action is due again: run it for a new link, or send a proof-of-address document, another option of the same composite requirement.` |
> | `upi_payment_failed` | UPI ₹1 payment | The ₹1 payment failed or did not come from an account in the business's or owner's name. | `We couldn't verify the account from this payment. Pay from an account in your business's name, or share the account details.` | `The action is due again: run it for a new link, or send the account.` |

## 2.4 Review Reasons

In `needs_clarification`, a reviewer's flag comes back on the flagged point's requirements, with the reviewer's reason in `requirement_reason`. Know more about [handling clarifications](https://razorpay.com/docs/partners/aggregators/onboarding-api/needs-clarification.md).

The table below lists the reasons a reviewer can give:

| Reason | Composite Requirement | When | What the Sub-Merchant Sees |
| - | - | - | - |
| `bank_account_ownership_unconfirmed` | `bank_account` | The reviewer could not confirm that the business or its owner holds the settlement account. | `A reviewer couldn't confirm that the payout account is held in your name. Share an account in your name, pay ₹1 from it, or reply.` |
| `website_no_products` | `website` | The website does not list products or prices. | `The website doesn't list any products or prices yet. Share a website with your products and prices, or explain how customers will buy from you.` |
| `website_policies_missing` | `website` | The website has no refund, cancellation or contact policy. | `The website needs refund, cancellation and contact details. Add them, or explain how customers reach you.` |
| `business_proof_unclear` | `proof_of_business` | The registration document is unreadable, expired or in another name. | `We couldn't confirm your business from this document. Upload a clear, current registration in the business's name.` |
| `address_proof_unclear` | `proof_of_address_for_individual` | The proof of address is unreadable, cropped or in another name. | `We couldn't read your proof of address. Upload both sides of an Aadhaar, voter ID or passport in your name, or use DigiLocker.` |
| `category_mismatch` | None | What the business sells does not match its category. | `What your business sells doesn't match the category you chose. Pick the category that fits.` |

## 2.5 Build Your Forms

Arrange requirements into steps the sub-merchant recognises, such as business details, identity, bank account and website. Render each one by its `requirement_type`, with a label and help text from `description`. Mark the optional ones.

> [card] Input
>
> Show a control that matches its `value_type`. Use a text box for `text`. Use a picker for `enum`, a multi-pick for `multi_select`, a toggle for `boolean` and a file picker for `document`.

> [card] Action
>
> Show a button that [runs the action](https://razorpay.com/docs/api/partners/accounts/run-action.md). Then show what its response returns: a box for the code it sent, or the link to open.

> [card] Composite
>
> Render its `sub_requirements` the same way, by `fulfillment_criteria`. Offer one choice between them for `one_of`, one or more for `any_of` and every one for `all_of`.

> [!NOTE]
>
> **Handy Tips**
>
> New requirements can appear. Render an unknown `requirement_code` generically from its `requirement_type` and `value_type` rather than failing.

## Next Step

[Submit Information](https://razorpay.com/docs/partners/aggregators/onboarding-api/submit-information.md)
