> ## 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.

# Other Business Type Tests

> Test onboarding of other business types on Onboarding APIs in Test Mode, including LLP, trust and society scenarios.

Available in
🇮🇳 India

Every business type onboards through the same APIs, and only the requirements differ. This page covers the 9 types without a page of their own:

* Section 8 companies
* Limited Liability Partnerships (LLPs)
* Partnerships
* Trusts
* Societies
* Hindu Undivided Families (HUFs)
* Government bodies
* Judicial persons
* Local authorities

The page lists each type's requirements and test business. Use them to build and test each type's screens. For a Section 8 company, the authorised person's Central KYC Records Registry (CKYC) record decides whether video KYC is due.

Before you start, check that your test credentials and headers work. See [Test Your Integration](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration). Every request and response body is on the API test pages, starting with [Create an Account](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/create-account.md).

## 1. Test Mode Coverage

### Test Mode Differences

The table below compares live mode and test mode for these business types:

| Behaviour | Live mode | Test mode |
| - | - | - |
| Business PAN | The PAN registry confirms the PAN and returns the business name. The 4th character of the PAN must match the type. | The test business PAN in [2. Before You Begin](#2-before-you-begin) decides the outcome. Its name comes back as `business_name`. |
| Phone and email codes | We send a 6-digit code by SMS and email when you run `send_phone_otp` or `send_email_otp`. The sub-merchant types it into your form. | We send no SMS or email. The action responds as in live mode. The code `000007` verifies. Any other 6 digits is a wrong code. Test mode cannot show whether your sub-merchants receive the messages. |
| The CKYC code | If the person's PAN has a CKYC record, `send_ckyc_otp` sends a code to that record's mobile number. The code fetches the record. | The PAN in the test business decides whether a record exists. We do not send the code. Any 6 digits other than `000000` verifies it. |
| Review after submission | We activate most products at submission. Some go to a Razorpay reviewer, which can take hours or days. The product can stay `under_review` the whole time. | No reviewer is involved. The settlement account or a business name suffix picks the outcome. A review outcome lands about 5 sec after submission. A test value that holds the review takes 5 min. One that acts after activation takes 60 sec. Do not size your timeouts or sub-merchant messaging from these timings. |
| Video KYC | The sub-merchant joins a short video call with a Razorpay agent at the link that `create_video_kyc_link` returns. | The link opens a hosted test page where you pick the call outcome: **Approved**, **Rejected** or **Unable to verify**. No camera or agent is involved. |
| DigiLocker and the ₹1 UPI link | The sub-merchant shares their Aadhaar in DigiLocker at the link the action returns. For the UPI link, they pay ₹1 from the bank account. | The link opens a hosted test page where you pick the outcome. No sign-in or payment is involved. |
| Status webhooks | We send an event when a product moves to `under_review`, `edd_pending`, `needs_clarification`, `activated`, `rejected` or `suspended`. We also send one when requirements change without a call from you, such as an `in_progress` check that settles later. | The same events go to your test mode webhook URL with `mode: test`, a few seconds after each change. |

### What You Can Test

The table below lists what this page tests:

| Area | What to test |
| - | - |
| Activation | Each type's journey from account creation to `activated`: scenarios 1 to 9. |
| Requirements by type | What each type is asked for: the tables in [Requirements by Type](#requirements-by-type). |
| Review outcomes | Every outcome, with the outcome accounts: scenario 11. |
| Errors | Scenarios 12, 13 and 14. |

### Endpoint Coverage in Test Mode

The table below lists the endpoints these business types use:

| API | Endpoint | Available in test mode |
| - | - | - |
| Create an account | [`POST /v1/accounts`](https://razorpay.com/docs/api/partners/accounts/create) | Available |
| Fetch one account | [`GET /v1/accounts/{account_id}`](https://razorpay.com/docs/api/partners/accounts/fetch) | Available |
| Update an account | [`PATCH /v1/accounts/{account_id}`](https://razorpay.com/docs/api/partners/accounts/update) | Available |
| Send the phone and email codes | [`POST /v1/accounts/{account_id}/actions/send_phone_otp`](https://razorpay.com/docs/api/partners/accounts/run-action) and `…/send_email_otp` | Available |
| Send the CKYC code | [`POST /v1/accounts/{account_id}/actions/send_ckyc_otp`](https://razorpay.com/docs/api/partners/accounts/run-action) | Available |
| Create the video KYC link | [`POST /v1/accounts/{account_id}/actions/create_video_kyc_link`](https://razorpay.com/docs/api/partners/accounts/run-action) | Available |
| Create a DigiLocker link | [`POST /v1/accounts/{account_id}/actions/create_aadhaar_digilocker_link`](https://razorpay.com/docs/api/partners/accounts/run-action) | Available |
| Create a ₹1 UPI link | [`POST /v1/accounts/{account_id}/actions/create_upi_link`](https://razorpay.com/docs/api/partners/accounts/run-action) | Available |
| Upload a document | [`POST /v1/accounts/{account_id}/documents`](https://razorpay.com/docs/api/partners/accounts/upload-document) | Available |
| Accept the terms and submit | [`PATCH /v1/accounts/{account_id}`](https://razorpay.com/docs/api/partners/accounts/update) with `products.payment_gateway.terms_of_service_acceptance` | Available |

### Webhooks

An onboarding fires the events below. Test mode accounts send them to your test mode webhook URL.

The table below lists each webhook and what to do when it arrives:

| Webhook | Fires when and what to do | In test mode |
| - | - | - |
| `account.product.under_review` | A product was submitted, its video KYC call finished or it was resubmitted after a clarification. Lock the KYC details in your app. | Available |
| `account.product.edd_pending` | The product needs video KYC before review continues. Show the video KYC link. | Available |
| `account.product.needs_clarification` | A reviewer flagged points. Fetch the account and show only those points. | Available |
| `account.product.activated` | The product is live. Turn on payments for the shop. | Available |
| `account.product.rejected` | The application was not approved. Stop offering changes. | Available |
| `account.product.suspended` | An activated product was suspended, and `status_reason` says why. Stop payments and ask for what `requirements` lists. | Available |
| `account.requirements.updated` | Requirements changed without a call from you. A check finished after the response, or the sub-merchant completed a step at a link. Fetch the account and render the requirements again. | Available |
| `account.consent.withdrawn` | The sub-merchant withdrew your access through Razorpay. Stop calling the API for the account. | Available |

### Webhooks Each Scenario Fires

The table below lists the webhooks that key scenarios fire:

| Scenario | Webhooks | In test mode |
| - | - | - |
| 1 to 9: Activated | `account.requirements.updated` (as the website check settles), `account.product.activated` | Available |
| 11: Review outcomes | `account.requirements.updated` (as the website check settles), then the status event for each change. For example, `000000000002` fires `account.product.under_review`, then `account.product.rejected`. | Available |
| 14: A failed business PAN | None, because the response carries it | Available |

### Before You Trust a Webhook

Follow these rules before you act on any webhook:

* **Verify the signature** on the raw body with your webhook secret before you parse it. Reject anything that fails.
* **Expect repeats.** An event can arrive more than once. Use `X-Razorpay-Event-Id` to process each event once.
* **Expect events out of order.** Compare `payload.account.updated_at`, or fetch the account and act on its current status.
* **Do not wait on webhooks.** The payload carries only what changed: the complete product, with its status and requirements. Fetch the account for the rest, and fetch when an event is late.

### Product Statuses

Take payments only while the product is `activated`. Every status is reachable in test mode.

The table below lists the product statuses:

| Status | Means | Accepts payments | Webhook | Available in test mode |
| - | - | - | - | - |
| `created` | The product is on the account | No | None | Available |
| `in_progress` | Values are coming in. `requirements` lists what is left | No | None | Available |
| `under_review` | Submitted for Razorpay review | No | `account.product.under_review` | Available |
| `edd_pending` | Submitted with video KYC due | No | `account.product.edd_pending` | Available |
| `needs_clarification` | A reviewer flagged points to answer | No | `account.product.needs_clarification` | Available |
| `activated` | Live | Yes, in live mode | `account.product.activated` | Available |
| `rejected` | Not approved, with no further changes | No | `account.product.rejected` | Available |
| `suspended` | Stopped after being live | No | `account.product.suspended` | Available |

## 2. Before You Begin

Set up the following before you start:

* Generate your app's **test** key and secret pair on the Partner Dashboard. The test pair sends every request to test mode. Its key starts with `rzp_test_partner_`.
* Use the same endpoints and request bodies as in live mode. Only the key changes. Every write carries an `X-Idempotency-Key` header.
* Send each input's value at its `field_path`, in the order that `requirements` lists them.
* Subscribe a test mode webhook URL on the Partner Dashboard to receive each scenario's webhooks.

Keep these rules in mind when you pick values:

* **Use the test business for the type**, listed below.
* **Plan your screens from `requirements`.** Create the account, then render what it lists. The tables below list what each type is asked for.
* **Match the 4th character of the business PAN to the type.** Use `C` for a company, `F` for a firm or LLP and `T` for a trust. Use `A` for an association of persons or society, `H` for an HUF, `G` for government, `J` for a judicial person and `L` for a local authority.
* **Use `Rzp Test QA Merchant`** with PAN `ABCPD1234A` as the authorised person for every type below.

### Test Businesses

Every test business below uses the Indian Financial System Code (IFSC) `HDFC0123456` for its bank account.

The table below lists the test business for each type:

| Type | `business_type` | Business PAN | Proof of identity | Bank account | Number of requirements |
| - | - | - | - | - | - |
| Section 8 company | `section_8_company` | `ABCCD1260N` | The Corporate Identification Number (CIN) `U85300KA2019NPL123456`, with the date of incorporation `2019-04-15` | `000000000001` | 22 |
| LLP | `llp` | `DHKFP3456L` | The certificate of incorporation, file `COI_DHKFP3456L.pdf` | `210045678901` | 21 |
| Partnership | `partnership` | `DEFFT7777G` | The business PAN | `210045678903` | 20 |
| Trust | `trust` | `MNOTW1234J` | The business PAN | `210045678905` | 20 |
| Society | `society` | `ABCAD1239F` | The business PAN | `210045678908` | 20 |
| HUF | `huf` | `ABCHD1234A` | The business PAN | `000000000001` | 18 |
| Government | `government` | `ABCGD1234A` | The business PAN | `000000000001` | 18 |
| Judicial person | `judicial_person` | `ABCJD1234A` | The business PAN | `000000000001` | 18 |
| Local authority | `local_authority` | `ABCLD1234A` | The business PAN | `000000000001` | 18 |

Every other value, such as the category, website, codes and addresses, is the same as for any business type. See [Test Values](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/test-values.md). To pick a review outcome, use one of the [outcome accounts](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/test-values.md#3-after-submission) as the settlement account.

### Requirements by Type

Every type sends the requirements in the first table below. The second table lists the requirements that differ by type. A type sends a requirement only when its row names that type.

The table below lists the requirements every type shares:

<table>
  <colgroup>
    <col width="16%" />

    <col width="30%" />

    <col width="12%" />

    <col width="32%" />

    <col width="10%" />
  </colgroup>

  <thead><tr><th>Requirement</th><th>Send</th><th>When</th><th>Notes</th><th>Due</th></tr></thead>

  <tbody>
    <tr>
      <td>User's contact</td>
      <td>`user.email` + `user.phone` + `user.name`</td>
      <td>Always</td>
      <td>Verify both with the OTP actions in the next row.</td>
      <td>At creation</td>
    </tr>

    <tr>
      <td>Contact verification</td>
      <td>`send_phone_otp` + `phone_otp` + `send_email_otp` + `email_otp`</td>
      <td>Always</td>
      <td>Run each send action, and its response asks for the code.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Business type</td>
      <td>`business_profile.business_type`</td>
      <td>Always</td>
      <td>Decides every other row. Locked once the PAN is verified.</td>
      <td>At creation</td>
    </tr>

    <tr>
      <td>Payment channels</td>
      <td>`products.payment_gateway.payment_channels.website.primary` or `products.payment_gateway.payment_channels.app_android.url` or `products.payment_gateway.payment_channels.app_ios.url`</td>
      <td>Always</td>
      <td>The `payment_channels` composite requirement, `one_of`. Any one channel satisfies it: a website, an Android app or an iOS app.</td>
      <td>Optional</td>
    </tr>

    <tr>
      <td>Website</td>
      <td>`products.payment_gateway.payment_channels.website.primary`</td>
      <td>With a website channel</td>
      <td>Checked once sent. It must be the business's own storefront, live on HTTPS. Its `verification` goes `in_progress`, then `verified` or `rejected` with `website_unreachable`. In needs clarification, a reply also answers it.</td>
      <td>Optional</td>
    </tr>

    <tr>
      <td>Business category</td>
      <td>`business_profile.business_category.category` + `business_profile.business_category.subcategory` or `business_profile.business_category.mcc`</td>
      <td>Always</td>
      <td>Select the business category and send its subcategory with it. Alternatively, send the Merchant Category Code (MCC) alone.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Business description</td>
      <td>`business_profile.business_category.business_description`</td>
      <td>Always</td>
      <td>What the business sells, in up to 100 characters.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Name on statements</td>
      <td>`statement_descriptor.value`</td>
      <td>Always</td>
      <td>A text input.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Registered address</td>
      <td>`business_profile.addresses[type=registered_address].line1` + `business_profile.addresses[type=registered_address].line2` + `business_profile.addresses[type=registered_address].city` + `business_profile.addresses[type=registered_address].state` + `business_profile.addresses[type=registered_address].postal_code` + `business_profile.addresses[type=registered_address].country`</td>
      <td>Always</td>
      <td>Where the business is registered. The `registered_address` composite requirement, `all_of` its parts. `line2` is optional and `country` is `IN`.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Operational address</td>
      <td>`business_profile.addresses[type=operational_address].line1` + `business_profile.addresses[type=operational_address].line2` + `business_profile.addresses[type=operational_address].city` + `business_profile.addresses[type=operational_address].state` + `business_profile.addresses[type=operational_address].postal_code` + `business_profile.addresses[type=operational_address].country`</td>
      <td>Always</td>
      <td>Where the business runs day to day. The `operational_address` composite requirement, `all_of` its parts. `line2` is optional and `country` is `IN`.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Settlement bank account</td>
      <td>`bank_accounts.settlements_primary.account_number` + `bank_accounts.settlements_primary.routing_code` + `bank_accounts.settlements_primary.routing_code_type` or `create_upi_link`</td>
      <td>Always</td>
      <td>The account number, the IFSC and `routing_code_type` `IFSC`, checked by penny drop. The holder name must match the PAN name or the business name. Once a check fails, a ₹1 UPI payment from the account also answers it. In needs clarification, a reply does too.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Business-model questions</td>
      <td>`business_profile.business_category.business_model_clarifications.<question_id>.answer`</td>
      <td>When the category asks</td>
      <td>Once the category is known, the `business_model_clarifications` composite requirement lists one input per question for the subcategory. Its `requirement_code` is the question ID. Its `value_type` is `enum`, `multi_select` or `text`, with the question's options. Answer every one.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Business-model documents</td>
      <td>`business_profile.documents`</td>
      <td>When an answer asks for one</td>
      <td>A licence or agreement that an answer asks for.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Terms of service and submission</td>
      <td>`products.payment_gateway.terms_of_service_acceptance.ip` + `products.payment_gateway.terms_of_service_acceptance.device_fingerprint_id`</td>
      <td>Always</td>
      <td>Show Razorpay's terms of service to the sub-merchant for the `accept_terms_of_service` composite requirement. Once the sub-merchant accepts, send their `ip` and `device_fingerprint_id`. Accepting submits the product.</td>
      <td>Before submission</td>
    </tr>
  </tbody>
</table>

The table below lists the requirements that differ by type:

<table>
  <colgroup>
    <col width="14%" />

    <col width="14%" />

    <col width="26%" />

    <col width="12%" />

    <col width="26%" />

    <col width="8%" />
  </colgroup>

  <thead><tr><th>Requirement</th><th>Types</th><th>Send</th><th>When</th><th>Notes</th><th>Due</th></tr></thead>

  <tbody>
    <tr>
      <td>Business PAN</td>
      <td>Section 8 company and LLP</td>
      <td>`business_profile.identity_numbers.business_pan` or `business_profile.documents.business_pan`</td>
      <td>Always</td>
      <td>The `business_pan` composite requirement: the number or the card. The 4th character must match the business type.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Business PAN</td>
      <td>Partnership, trust, society, HUF, government, judicial person and local authority</td>
      <td>`business_profile.identity_numbers.business_pan` or `business_profile.documents.business_pan`</td>
      <td>Always</td>
      <td>The `business_pan` composite requirement: the number or the card. The 4th character must match the business type. The business PAN is also this type's proof of identity, so it sends no other identity document.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Date of incorporation</td>
      <td>Section 8 company</td>
      <td>`business_profile.date_of_establishment`</td>
      <td>Always</td>
      <td>The date the company was incorporated.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Proof of business identity</td>
      <td>Section 8 company</td>
      <td>`business_profile.identity_numbers.cin` or `business_profile.documents.certificate_of_incorporation`</td>
      <td>Always</td>
      <td>The `business_identity` composite requirement, the company's identity. Send the CIN or the certificate of incorporation. We check the CIN with the Ministry of Corporate Affairs (MCA) and match either to the business PAN name.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Proof of business identity</td>
      <td>LLP</td>
      <td>`business_profile.documents.certificate_of_incorporation`</td>
      <td>Always</td>
      <td>The LLP's certificate of incorporation, matched to the business PAN name.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Goods and Services Tax Identification Number (GSTIN)</td>
      <td>LLP, partnership, trust, society, HUF, government, judicial person and local authority</td>
      <td>`business_profile.identity_numbers.gstin`</td>
      <td>Needed if turnover is over ₹40,00,000 or the business sells across states</td>
      <td>Checked with the Goods and Services Tax (GST) registry. Its `requirement_level` is `conditional`.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Authorised person's name and PAN</td>
      <td>All 9 types</td>
      <td>`business_profile.authorized_person.name` + `business_profile.authorized_person.identity_numbers.individual_pan` or `business_profile.authorized_person.name` + `business_profile.authorized_person.documents.individual_pan_document`</td>
      <td>Always</td>
      <td>The `authorized_person` composite requirement, `all_of` the name plus the PAN or the PAN card. See [Who Signs](#who-signs-for-each-type).</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Authorised person's CKYC record</td>
      <td>Section 8 company</td>
      <td>`business_profile.authorized_person.identity_numbers.individual_ckyc.is_skipped` or `send_ckyc_otp` + `business_profile.authorized_person.identity_numbers.individual_ckyc.otp` + `business_profile.authorized_person.identity_numbers.individual_ckyc.request_id`</td>
      <td>When the authorised person's PAN has a CKYC record</td>
      <td>The `ckyc_fetch` composite requirement: the person's CKYC record, fetched with a code or skipped. Skip it with `is_skipped: true`, or run `send_ckyc_otp`. Then `ckyc_otp` and `ckyc_request_id` come due: send the code as `individual_ckyc.otp` and the `request_id` the action returned as `individual_ckyc.request_id`. The code goes to the mobile number on the CKYC record. Skipping makes the proof of address due. `metadata.ckyc_mobile` is optional. A number that is not the mobile number on the CKYC record returns `status: failed`.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Authorised person's proof of address</td>
      <td>Section 8 company</td>
      <td>`create_aadhaar_digilocker_link` or `business_profile.authorized_person.documents.aadhaar_front` + `business_profile.authorized_person.documents.aadhaar_back` or `business_profile.authorized_person.documents.passport_front` + `business_profile.authorized_person.documents.passport_back` or `business_profile.authorized_person.documents.voter_id_front` + `business_profile.authorized_person.documents.voter_id_back`</td>
      <td>When the authorised person skips CKYC or has no CKYC record</td>
      <td>The `proof_of_address_for_individual` composite requirement. Complete one option: DigiLocker or both sides of an Aadhaar, passport or voter ID. The name must match the PAN.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Authorised person's proof of address</td>
      <td>LLP, partnership, trust, society, HUF, government, judicial person and local authority</td>
      <td>`create_aadhaar_digilocker_link` or `business_profile.authorized_person.documents.aadhaar_front` + `business_profile.authorized_person.documents.aadhaar_back` or `business_profile.authorized_person.documents.passport_front` + `business_profile.authorized_person.documents.passport_back` or `business_profile.authorized_person.documents.voter_id_front` + `business_profile.authorized_person.documents.voter_id_back`</td>
      <td>Always</td>
      <td>The `proof_of_address_for_individual` composite requirement. Complete one option: DigiLocker or both sides of an Aadhaar, passport or voter ID. The name must match the PAN.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Beneficial owners</td>
      <td>Section 8 company, LLP, partnership and trust</td>
      <td>`business_profile.stakeholders`</td>
      <td>Always</td>
      <td>Everyone holding more than 10%: name, PAN and `percentage_ownership`.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Beneficial owners</td>
      <td>Society</td>
      <td>`business_profile.stakeholders`</td>
      <td>Always</td>
      <td>Everyone holding more than 15%: name, PAN and `percentage_ownership`.</td>
      <td>Before submission</td>
    </tr>

    <tr>
      <td>Video KYC</td>
      <td>Section 8 company</td>
      <td>`create_video_kyc_link`</td>
      <td>Without a CKYC record or when CKYC is skipped</td>
      <td>Enhanced due diligence while the product is `edd_pending`: a short video call at the link in the action's response `metadata`. The product then moves to `under_review`.</td>
      <td>After submission</td>
    </tr>

    <tr>
      <td>Video KYC</td>
      <td>LLP, partnership, trust and society</td>
      <td>`create_video_kyc_link`</td>
      <td>When Razorpay needs enhanced due diligence</td>
      <td>Enhanced due diligence while the product is `edd_pending`: a short video call at the link in the action's response `metadata`. The product then moves to `under_review`.</td>
      <td>After submission</td>
    </tr>
  </tbody>
</table>

HUF, government, judicial person and local authority accounts send no beneficial owners and no video KYC.

### Who Signs for Each Type

The table below lists who acts as the authorised person for each type:

| Type | Authorised person |
| - | - |
| Section 8 company | A director or another person who signs for the company |
| LLP | A designated partner or another person who signs for the LLP |
| Partnership | A partner or another person who signs for the firm |
| Trust | A trustee or another person who signs for the trust |
| Society | A member of the governing body or another person who signs for the society |
| HUF | The karta or another member who signs for the HUF |
| Government | The officer who signs for the body |
| Judicial person | The officer who signs for the body |
| Local authority | The officer who signs for the body |

## 3. Test Scenarios

This section lists every scenario to run against your integration for these business types before you go live. We group the scenarios by what each one proves. Work down the page in order to cover the integration end to end.

The scenarios fall into 3 groups:

* **Must-build**: The successful path and the outcomes you are almost certain to meet once live. Run these first.
* **Other common scenarios**: Scenarios shared with the other business types, so the same handling must work on every one.
* **Error scenarios**: Failed checks you trigger with a test value, so you check your handling without waiting for a real failure.

Each scenario's steps end with the webhooks it fires and the status it leaves. In test mode, the webhooks go to your test mode webhook URL.

### 3.1 Must-Build Scenarios

Run the journey for each type you offer.

**Live** scenarios work in test mode today. **Coming soon** scenarios are not available in test mode yet.

The table below lists the must-build scenarios:

<table>
  <colgroup>
    <col width="5%" />

    <col width="20%" />

    <col width="20%" />

    <col width="55%" />
  </colgroup>

  <thead><tr><th>#</th><th>Scenario</th><th>Trigger</th><th>What to confirm</th></tr></thead>

  <tbody>
    <tr>
      <td>1</td>
      <td>Section 8 company: account creation to activation Coming soon</td>
      <td>`business_type: section_8_company`, business PAN `ABCCD1260N`</td>

      <td>
        <ol>
          <li>Create the account with `country`, the user and `products: { "payment_gateway": { "payment_channels": {} } }`. See [Create an Account](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/create-account.md). Confirm `business_type`, `send_phone_otp` and `send_email_otp` are due.</li>
          <li>Run `send_phone_otp` and `send_email_otp`, then send `000007` as `phone_otp` and `email_otp`.</li>
          <li>Send `business_type: section_8_company` and the business PAN `ABCCD1260N` at `business_profile.identity_numbers.business_pan`.</li>
          <li>Confirm the PAN is `verified` and the PAN record's name comes back as `business_name`.</li>
          <li>Send the CIN `U85300KA2019NPL123456`. Confirm `business_identity` clears.</li>
          <li>Send `date_of_establishment` `2019-04-15`, the date of incorporation.</li>
          <li>Send the authorised person `Rzp Test QA Merchant` with PAN `ABCPD1234A`. This person has a CKYC record, so `ckyc_fetch` is due.</li>
          <li>Run `send_ckyc_otp`. Send any 6 digits other than `000000` as `individual_ckyc.otp`, with its request ID as `individual_ckyc.request_id`. Confirm `verified`, with no proof of address due.</li>
          <li>If `requirements` lists the beneficial owners, send `stakeholders`. Each owner has `name`, `identity_numbers.individual_pan` and `percentage_ownership`.</li>
          <li>Send `registered_address` and `operational_address` under `business_profile.addresses`. Each is `all_of` its lines, city, state, postal code and country. `line2` is optional.</li>
          <li>Send bank account `000000000001` with IFSC `HDFC0123456`. Confirm `verified`.</li>
          <li>Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.</li>
          <li>Show Razorpay's terms of service to the sub-merchant. Then send the sub-merchant's `ip` and `device_fingerprint_id` in `products.payment_gateway.terms_of_service_acceptance`. See [Terms and Submission](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/terms-and-submission.md).</li>
          <li>Webhooks received: `account.requirements.updated` (as the website check settles), `account.product.activated`.</li>
          <li>Status changes: `in_progress` → `activated`.</li>
        </ol>
      </td>
    </tr>

    <tr>
      <td>2</td>
      <td>LLP: account creation to activation Coming soon</td>
      <td>`business_type: llp`, business PAN `DHKFP3456L`</td>

      <td>
        <ol>
          <li>Create the account with `country`, the user and `products: { "payment_gateway": { "payment_channels": {} } }`. See [Create an Account](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/create-account.md). Confirm `business_type`, `send_phone_otp` and `send_email_otp` are due.</li>
          <li>Run `send_phone_otp` and `send_email_otp`, then send `000007` as `phone_otp` and `email_otp`.</li>
          <li>Send `business_type: llp` and the business PAN `DHKFP3456L` at `business_profile.identity_numbers.business_pan`.</li>
          <li>Confirm the PAN is `verified` and the PAN record's name comes back as `business_name`.</li>
          <li>Upload `COI_DHKFP3456L.pdf` and attach it at `business_profile.documents.certificate_of_incorporation`. Confirm `verified`.</li>
          <li>Send the authorised person `Rzp Test QA Merchant` with PAN `ABCPD1234A`.</li>
          <li>Send what else `requirements` lists for the type, such as the authorised person's proof of address and the beneficial owners.</li>
          <li>For the proof of address, send `AADHAARCKYCCOMPLETE.jpg` as the front and the back, in one update.</li>
          <li>For each beneficial owner in `stakeholders`, send `name`, `identity_numbers.individual_pan` and `percentage_ownership`.</li>
          <li>Send `registered_address` and `operational_address` under `business_profile.addresses`. Each is `all_of` its lines, city, state, postal code and country. `line2` is optional.</li>
          <li>Send bank account `210045678901` with IFSC `HDFC0123456`. Confirm `verified`.</li>
          <li>Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.</li>
          <li>Show Razorpay's terms of service to the sub-merchant. Then send the sub-merchant's `ip` and `device_fingerprint_id` in `products.payment_gateway.terms_of_service_acceptance`. See [Terms and Submission](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/terms-and-submission.md).</li>
          <li>Webhooks received: `account.requirements.updated` (as the website check settles), `account.product.activated`.</li>
          <li>Status changes: `in_progress` → `activated`.</li>
        </ol>
      </td>
    </tr>

    <tr>
      <td>3</td>
      <td>Partnership: account creation to activation Coming soon</td>
      <td>`business_type: partnership`, business PAN `DEFFT7777G`</td>

      <td>
        <ol>
          <li>Create the account with `country`, the user and `products: { "payment_gateway": { "payment_channels": {} } }`. See [Create an Account](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/create-account.md). Confirm `business_type`, `send_phone_otp` and `send_email_otp` are due.</li>
          <li>Run `send_phone_otp` and `send_email_otp`, then send `000007` as `phone_otp` and `email_otp`.</li>
          <li>Send `business_type: partnership` and the business PAN `DEFFT7777G` at `business_profile.identity_numbers.business_pan`.</li>
          <li>Confirm the PAN is `verified` and the PAN record's name comes back as `business_name`.</li>
          <li>Send the authorised person `Rzp Test QA Merchant` with PAN `ABCPD1234A`.</li>
          <li>Send what else `requirements` lists for the type, such as the authorised person's proof of address and the beneficial owners.</li>
          <li>For the proof of address, send `AADHAARCKYCCOMPLETE.jpg` as the front and the back, in one update.</li>
          <li>For each beneficial owner in `stakeholders`, send `name`, `identity_numbers.individual_pan` and `percentage_ownership`.</li>
          <li>Send `registered_address` and `operational_address` under `business_profile.addresses`. Each is `all_of` its lines, city, state, postal code and country. `line2` is optional.</li>
          <li>Send bank account `210045678903` with IFSC `HDFC0123456`. Confirm `verified`.</li>
          <li>Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.</li>
          <li>Show Razorpay's terms of service to the sub-merchant. Then send the sub-merchant's `ip` and `device_fingerprint_id` in `products.payment_gateway.terms_of_service_acceptance`. See [Terms and Submission](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/terms-and-submission.md).</li>
          <li>Webhooks received: `account.requirements.updated` (as the website check settles), `account.product.activated`.</li>
          <li>Status changes: `in_progress` → `activated`.</li>
        </ol>
      </td>
    </tr>

    <tr>
      <td>4</td>
      <td>Trust: account creation to activation Coming soon</td>
      <td>`business_type: trust`, business PAN `MNOTW1234J`</td>

      <td>
        <ol>
          <li>Create the account with `country`, the user and `products: { "payment_gateway": { "payment_channels": {} } }`. See [Create an Account](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/create-account.md). Confirm `business_type`, `send_phone_otp` and `send_email_otp` are due.</li>
          <li>Run `send_phone_otp` and `send_email_otp`, then send `000007` as `phone_otp` and `email_otp`.</li>
          <li>Send `business_type: trust` and the business PAN `MNOTW1234J` at `business_profile.identity_numbers.business_pan`.</li>
          <li>Confirm the PAN is `verified` and the PAN record's name comes back as `business_name`.</li>
          <li>Send the authorised person `Rzp Test QA Merchant` with PAN `ABCPD1234A`.</li>
          <li>Send what else `requirements` lists for the type, such as the authorised person's proof of address and the beneficial owners.</li>
          <li>For the proof of address, send `AADHAARCKYCCOMPLETE.jpg` as the front and the back, in one update.</li>
          <li>For each beneficial owner in `stakeholders`, send `name`, `identity_numbers.individual_pan` and `percentage_ownership`.</li>
          <li>Send `registered_address` and `operational_address` under `business_profile.addresses`. Each is `all_of` its lines, city, state, postal code and country. `line2` is optional.</li>
          <li>Send bank account `210045678905` with IFSC `HDFC0123456`. Confirm `verified`.</li>
          <li>Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.</li>
          <li>Show Razorpay's terms of service to the sub-merchant. Then send the sub-merchant's `ip` and `device_fingerprint_id` in `products.payment_gateway.terms_of_service_acceptance`. See [Terms and Submission](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/terms-and-submission.md).</li>
          <li>Webhooks received: `account.requirements.updated` (as the website check settles), `account.product.activated`.</li>
          <li>Status changes: `in_progress` → `activated`.</li>
        </ol>
      </td>
    </tr>

    <tr>
      <td>5</td>
      <td>Society: account creation to activation Coming soon</td>
      <td>`business_type: society`, business PAN `ABCAD1239F`</td>

      <td>
        <ol>
          <li>Create the account with `country`, the user and `products: { "payment_gateway": { "payment_channels": {} } }`. See [Create an Account](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/create-account.md). Confirm `business_type`, `send_phone_otp` and `send_email_otp` are due.</li>
          <li>Run `send_phone_otp` and `send_email_otp`, then send `000007` as `phone_otp` and `email_otp`.</li>
          <li>Send `business_type: society` and the business PAN `ABCAD1239F` at `business_profile.identity_numbers.business_pan`.</li>
          <li>Confirm the PAN is `verified` and the PAN record's name comes back as `business_name`.</li>
          <li>Send the authorised person `Rzp Test QA Merchant` with PAN `ABCPD1234A`.</li>
          <li>Send what else `requirements` lists for the type, such as the authorised person's proof of address and the beneficial owners.</li>
          <li>For the proof of address, send `AADHAARCKYCCOMPLETE.jpg` as the front and the back, in one update.</li>
          <li>For each beneficial owner in `stakeholders`, send `name`, `identity_numbers.individual_pan` and `percentage_ownership`.</li>
          <li>Send `registered_address` and `operational_address` under `business_profile.addresses`. Each is `all_of` its lines, city, state, postal code and country. `line2` is optional.</li>
          <li>Send bank account `210045678908` with IFSC `HDFC0123456`. Confirm `verified`.</li>
          <li>Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.</li>
          <li>Show Razorpay's terms of service to the sub-merchant. Then send the sub-merchant's `ip` and `device_fingerprint_id` in `products.payment_gateway.terms_of_service_acceptance`. See [Terms and Submission](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/terms-and-submission.md).</li>
          <li>Webhooks received: `account.requirements.updated` (as the website check settles), `account.product.activated`.</li>
          <li>Status changes: `in_progress` → `activated`.</li>
        </ol>
      </td>
    </tr>

    <tr>
      <td>6</td>
      <td>HUF: account creation to activation Coming soon</td>
      <td>`business_type: huf`, business PAN `ABCHD1234A`</td>

      <td>
        <ol>
          <li>Create the account with `country`, the user and `products: { "payment_gateway": { "payment_channels": {} } }`. See [Create an Account](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/create-account.md). Confirm `business_type`, `send_phone_otp` and `send_email_otp` are due.</li>
          <li>Run `send_phone_otp` and `send_email_otp`, then send `000007` as `phone_otp` and `email_otp`.</li>
          <li>Send `business_type: huf` and the business PAN `ABCHD1234A` at `business_profile.identity_numbers.business_pan`.</li>
          <li>Confirm the PAN is `verified` and the PAN record's name comes back as `business_name`.</li>
          <li>Send the authorised person `Rzp Test QA Merchant` with PAN `ABCPD1234A`.</li>
          <li>Send what else `requirements` lists for the type, such as the authorised person's proof of address. This type sends no beneficial owners.</li>
          <li>For the proof of address, send `AADHAARCKYCCOMPLETE.jpg` as the front and the back, in one update.</li>
          <li>Send `registered_address` and `operational_address` under `business_profile.addresses`. Each is `all_of` its lines, city, state, postal code and country. `line2` is optional.</li>
          <li>Send bank account `000000000001` with IFSC `HDFC0123456`. Confirm `verified`.</li>
          <li>Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.</li>
          <li>Show Razorpay's terms of service to the sub-merchant. Then send the sub-merchant's `ip` and `device_fingerprint_id` in `products.payment_gateway.terms_of_service_acceptance`. See [Terms and Submission](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/terms-and-submission.md).</li>
          <li>Webhooks received: `account.requirements.updated` (as the website check settles), `account.product.activated`.</li>
          <li>Status changes: `in_progress` → `activated`.</li>
        </ol>
      </td>
    </tr>

    <tr>
      <td>7</td>
      <td>Government: account creation to activation Coming soon</td>
      <td>`business_type: government`, business PAN `ABCGD1234A`</td>

      <td>
        <ol>
          <li>Create the account with `country`, the user and `products: { "payment_gateway": { "payment_channels": {} } }`. See [Create an Account](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/create-account.md). Confirm `business_type`, `send_phone_otp` and `send_email_otp` are due.</li>
          <li>Run `send_phone_otp` and `send_email_otp`, then send `000007` as `phone_otp` and `email_otp`.</li>
          <li>Send `business_type: government` and the business PAN `ABCGD1234A` at `business_profile.identity_numbers.business_pan`.</li>
          <li>Confirm the PAN is `verified` and the PAN record's name comes back as `business_name`.</li>
          <li>Send the authorised person `Rzp Test QA Merchant` with PAN `ABCPD1234A`.</li>
          <li>Send what else `requirements` lists for the type, such as the authorised person's proof of address. This type sends no beneficial owners.</li>
          <li>For the proof of address, send `AADHAARCKYCCOMPLETE.jpg` as the front and the back, in one update.</li>
          <li>Send `registered_address` and `operational_address` under `business_profile.addresses`. Each is `all_of` its lines, city, state, postal code and country. `line2` is optional.</li>
          <li>Send bank account `000000000001` with IFSC `HDFC0123456`. Confirm `verified`.</li>
          <li>Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.</li>
          <li>Show Razorpay's terms of service to the sub-merchant. Then send the sub-merchant's `ip` and `device_fingerprint_id` in `products.payment_gateway.terms_of_service_acceptance`. See [Terms and Submission](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/terms-and-submission.md).</li>
          <li>Webhooks received: `account.requirements.updated` (as the website check settles), `account.product.activated`.</li>
          <li>Status changes: `in_progress` → `activated`.</li>
        </ol>
      </td>
    </tr>

    <tr>
      <td>8</td>
      <td>Judicial person: account creation to activation Coming soon</td>
      <td>`business_type: judicial_person`, business PAN `ABCJD1234A`</td>

      <td>
        <ol>
          <li>Create the account with `country`, the user and `products: { "payment_gateway": { "payment_channels": {} } }`. See [Create an Account](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/create-account.md). Confirm `business_type`, `send_phone_otp` and `send_email_otp` are due.</li>
          <li>Run `send_phone_otp` and `send_email_otp`, then send `000007` as `phone_otp` and `email_otp`.</li>
          <li>Send `business_type: judicial_person` and the business PAN `ABCJD1234A` at `business_profile.identity_numbers.business_pan`.</li>
          <li>Confirm the PAN is `verified` and the PAN record's name comes back as `business_name`.</li>
          <li>Send the authorised person `Rzp Test QA Merchant` with PAN `ABCPD1234A`.</li>
          <li>Send what else `requirements` lists for the type, such as the authorised person's proof of address. This type sends no beneficial owners.</li>
          <li>For the proof of address, send `AADHAARCKYCCOMPLETE.jpg` as the front and the back, in one update.</li>
          <li>Send `registered_address` and `operational_address` under `business_profile.addresses`. Each is `all_of` its lines, city, state, postal code and country. `line2` is optional.</li>
          <li>Send bank account `000000000001` with IFSC `HDFC0123456`. Confirm `verified`.</li>
          <li>Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.</li>
          <li>Show Razorpay's terms of service to the sub-merchant. Then send the sub-merchant's `ip` and `device_fingerprint_id` in `products.payment_gateway.terms_of_service_acceptance`. See [Terms and Submission](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/terms-and-submission.md).</li>
          <li>Webhooks received: `account.requirements.updated` (as the website check settles), `account.product.activated`.</li>
          <li>Status changes: `in_progress` → `activated`.</li>
        </ol>
      </td>
    </tr>

    <tr>
      <td>9</td>
      <td>Local authority: account creation to activation Coming soon</td>
      <td>`business_type: local_authority`, business PAN `ABCLD1234A`</td>

      <td>
        <ol>
          <li>Create the account with `country`, the user and `products: { "payment_gateway": { "payment_channels": {} } }`. See [Create an Account](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/create-account.md). Confirm `business_type`, `send_phone_otp` and `send_email_otp` are due.</li>
          <li>Run `send_phone_otp` and `send_email_otp`, then send `000007` as `phone_otp` and `email_otp`.</li>
          <li>Send `business_type: local_authority` and the business PAN `ABCLD1234A` at `business_profile.identity_numbers.business_pan`.</li>
          <li>Confirm the PAN is `verified` and the PAN record's name comes back as `business_name`.</li>
          <li>Send the authorised person `Rzp Test QA Merchant` with PAN `ABCPD1234A`.</li>
          <li>Send what else `requirements` lists for the type, such as the authorised person's proof of address. This type sends no beneficial owners.</li>
          <li>For the proof of address, send `AADHAARCKYCCOMPLETE.jpg` as the front and the back, in one update.</li>
          <li>Send `registered_address` and `operational_address` under `business_profile.addresses`. Each is `all_of` its lines, city, state, postal code and country. `line2` is optional.</li>
          <li>Send bank account `000000000001` with IFSC `HDFC0123456`. Confirm `verified`.</li>
          <li>Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.</li>
          <li>Show Razorpay's terms of service to the sub-merchant. Then send the sub-merchant's `ip` and `device_fingerprint_id` in `products.payment_gateway.terms_of_service_acceptance`. See [Terms and Submission](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/terms-and-submission.md).</li>
          <li>Webhooks received: `account.requirements.updated` (as the website check settles), `account.product.activated`.</li>
          <li>Status changes: `in_progress` → `activated`.</li>
        </ol>
      </td>
    </tr>
  </tbody>
</table>

### 3.2 Other Common Scenarios

The table below lists the other common scenarios:

<table>
  <colgroup>
    <col width="5%" />

    <col width="20%" />

    <col width="20%" />

    <col width="55%" />
  </colgroup>

  <thead><tr><th>#</th><th>Scenario</th><th>Trigger</th><th>What to confirm</th></tr></thead>

  <tbody>
    <tr>
      <td>10</td>
      <td>Requirements follow the type (also on every business type) Coming soon</td>
      <td>Each type above</td>

      <td>
        <ol>
          <li>Create one test account per type you offer.</li>
          <li>Confirm the requirements match the type's rows in [Requirements by Type](#requirements-by-type).</li>
          <li>Webhooks received: none.</li>
          <li>Status changes: none.</li>
        </ol>
      </td>
    </tr>

    <tr>
      <td>11</td>
      <td>Review outcomes (also on every business type) Coming soon</td>
      <td>The outcome accounts `000000000002` to `000000000007`. Use `000000000004` only for Section 8 companies, LLPs, partnerships, trusts and societies.</td>

      <td>
        <ol>
          <li>Run any journey above with one of the outcome accounts as the settlement account.</li>
          <li>Confirm the outcome that the account names.</li>
          <li>Webhooks received: the status events for each change.</li>
          <li>Status changes: as the account names.</li>
        </ol>
      </td>
    </tr>
  </tbody>
</table>

### 3.3 Error Scenarios

We group the error scenarios by the check or request that fails.

**Request Errors**

The request itself was wrong, so nothing was saved and no webhook fires. Fix it in code, because retrying it unchanged fails again.

The table below lists the request error scenarios:

<table>
  <colgroup>
    <col width="5%" />

    <col width="17%" />

    <col width="16%" />

    <col width="25%" />

    <col width="37%" />
  </colgroup>

  <thead><tr><th>#</th><th>Scenario</th><th>Trigger</th><th>Error object</th><th>What to confirm</th></tr></thead>

  <tbody>
    <tr>
      <td>12</td>
      <td>A business type not in the list Live</td>
      <td>`business_type: "company"`</td>
      <td>HTTP `400`\
      `error.reason`: `invalid_option`\
      `error.field`: `business_profile.business_type`</td>

      <td>
        <ol>
          <li>Send the value.</li>
          <li>Confirm `400` with `metadata.allowed_values`.</li>
          <li>Webhooks received: none.</li>
          <li>Status changes: none.</li>
        </ol>
      </td>
    </tr>

    <tr>
      <td>13</td>
      <td>Changing the type after the PAN verifies Coming soon</td>
      <td>A new `business_type` on an account whose PAN is verified</td>
      <td>HTTP `409`\
      `error.reason`: `field_locked`\
      `error.field`: `business_profile.business_type`</td>

      <td>
        <ol>
          <li>Send the value.</li>
          <li>Confirm `409`.</li>
          <li>Webhooks received: none.</li>
          <li>Status changes: none.</li>
        </ol>
      </td>
    </tr>
  </tbody>
</table>

**Business PAN**

The PAN registry said no. The business PAN or its card clears `business_pan`. Each type has a failing PAN with its own 4th character.

The table below lists the business PAN scenario:

<table>
  <colgroup>
    <col width="5%" />

    <col width="17%" />

    <col width="16%" />

    <col width="25%" />

    <col width="37%" />
  </colgroup>

  <thead><tr><th>#</th><th>Scenario</th><th>Trigger</th><th>Error object</th><th>What to confirm</th></tr></thead>

  <tbody>
    <tr>
      <td>14</td>
      <td>A business PAN that fails its check Coming soon</td>
      <td>Section 8 company: `ABCCD1234B`\
      LLP: `ABCFD1234B`\
      Partnership: `ABCFD1234B`\
      Trust: `ABCTD1234B`\
      Society: `ABCAD1234B`\
      HUF: `ABCHD1234B`\
      Government: `ABCGD1234B`\
      Judicial person: `ABCJD1234B`\
      Local authority: `ABCLD1234B`</td>
      <td>`verification.status`: `rejected`\
      `verification.error_code`: `pan_not_found`\
      At: `business_profile.identity_numbers.business_pan`\
      Due again: `business_profile.identity_numbers.business_pan`, `business_profile.documents.business_pan`\
      Composite requirement: `business_pan`</td>

      <td>
        <ol>
          <li>Send the failing PAN for your type where it is due. Confirm the response is a `200`.</li>
          <li>Webhooks received: none, because the response carries the failure.</li>
          <li>Status changes: none.</li>
        </ol>
      </td>
    </tr>
  </tbody>
</table>

Every failure code, with its test value, is in the [Error Index](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/error-index.md).

## 4. Common Integration Gaps

These mistakes most often stall an onboarding or leave an account in the wrong state after go-live. **Test with** points to the scenario that proves you handled each one.

**Business Types**

The table below lists gaps in handling business types:

| Gap | What goes wrong in production | What to do | Test with |
| - | - | - | - |
| Hard-coding requirements per type | A type's requirements change and your form misses one. | Render `requirements` as returned. | Scenario 10 |
| Hiding types you have not tested | Sub-merchants pick the nearest type and fail verification. | Offer every type in the `options` of `business_type`. | Scenarios 1 to 9 |

## 5. Best Integration Practices

These practices apply to every onboarding integration. **On this page** says what each one means here. **Test it** points to the scenario that tests it.

The table below lists the best integration practice for this page:

| Topic | What to know | On this page | Test it | Read more |
| - | - | - | - | - |
| The 4th character of the business PAN | It must match the business type. | For example, `C` for a company, `F` for a firm or LLP and `T` for a trust. | Scenarios 1 to 9 | [Collect Requirements](https://razorpay.com/docs/partners/aggregators/onboarding-api/collect-requirements.md) |

### Related Information

* [Test Your Integration](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration)
* [Individual](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/individual.md)
* [Proprietorship](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/proprietorship.md)
* [Private Limited](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/private-limited.md)
* [Public Limited](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/public-limited.md)
* [Test Values](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/test-values.md)
* [Error Index](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/error-index.md)
* [Create an Account](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/create-account.md)
* [Fetch an Account](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/fetch-account.md)
* [Terms and Submission](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/terms-and-submission.md)
