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
1. Test Mode Coverage
Test Mode Differences
The table below compares live mode and test mode for these business types:What You Can Test
The table below lists what this page tests:Endpoint Coverage in Test Mode
The table below lists the endpoints these business types use: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:Webhooks Each Scenario Fires
The table below lists the webhooks that key scenarios fire: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-Idto 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 isactivated. Every status is reachable in test mode.
The table below lists the product statuses:
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-Keyheader. - Send each input’s value at its
field_path, in the order thatrequirementslists them. - Subscribe a test mode webhook URL on the Partner Dashboard to receive each scenario’s webhooks.
- 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
Cfor a company,Ffor a firm or LLP andTfor a trust. UseAfor an association of persons or society,Hfor an HUF,Gfor government,Jfor a judicial person andLfor a local authority. - Use
Rzp Test QA Merchantwith PANABCPD1234Aas 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:
Every other value, such as the category, website, codes and addresses, is the same as for any business type. See Test Values. To pick a review outcome, use one of the outcome accounts 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:| Requirement | Send | When | Notes | Due |
|---|---|---|---|---|
| User’s contact | user.email + user.phone + user.name | Always | Verify both with the OTP actions in the next row. | At creation |
| Contact verification | send_phone_otp + phone_otp + send_email_otp + email_otp | Always | Run each send action, and its response asks for the code. | Before submission |
| Business type | business_profile.business_type | Always | Decides every other row. Locked once the PAN is verified. | At creation |
| Payment channels | 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 | Always | The payment_channels composite requirement, one_of. Any one channel satisfies it: a website, an Android app or an iOS app. | Optional |
| Website | products.payment_gateway.payment_channels.website.primary | With a website channel | 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. | Optional |
| Business category | business_profile.business_category.category + business_profile.business_category.subcategory or business_profile.business_category.mcc | Always | Select the business category and send its subcategory with it. Alternatively, send the Merchant Category Code (MCC) alone. | Before submission |
| Business description | business_profile.business_category.business_description | Always | What the business sells, in up to 100 characters. | Before submission |
| Name on statements | statement_descriptor.value | Always | A text input. | Before submission |
| Registered address | 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 | Always | Where the business is registered. The registered_address composite requirement, all_of its parts. line2 is optional and country is IN. | Before submission |
| Operational address | 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 | Always | Where the business runs day to day. The operational_address composite requirement, all_of its parts. line2 is optional and country is IN. | Before submission |
| Settlement bank account | bank_accounts.settlements_primary.account_number + bank_accounts.settlements_primary.routing_code + bank_accounts.settlements_primary.routing_code_type or create_upi_link | Always | 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. | Before submission |
| Business-model questions | business_profile.business_category.business_model_clarifications.<question_id>.answer | When the category asks | 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. | Before submission |
| Business-model documents | business_profile.documents | When an answer asks for one | A licence or agreement that an answer asks for. | Before submission |
| Terms of service and submission | products.payment_gateway.terms_of_service_acceptance.ip + products.payment_gateway.terms_of_service_acceptance.device_fingerprint_id | Always | 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. | Before submission |
| Requirement | Types | Send | When | Notes | Due |
|---|---|---|---|---|---|
| Business PAN | Section 8 company and LLP | business_profile.identity_numbers.business_pan or business_profile.documents.business_pan | Always | The business_pan composite requirement: the number or the card. The 4th character must match the business type. | Before submission |
| Business PAN | Partnership, trust, society, HUF, government, judicial person and local authority | business_profile.identity_numbers.business_pan or business_profile.documents.business_pan | Always | 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. | Before submission |
| Date of incorporation | Section 8 company | business_profile.date_of_establishment | Always | The date the company was incorporated. | Before submission |
| Proof of business identity | Section 8 company | business_profile.identity_numbers.cin or business_profile.documents.certificate_of_incorporation | Always | 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. | Before submission |
| Proof of business identity | LLP | business_profile.documents.certificate_of_incorporation | Always | The LLP’s certificate of incorporation, matched to the business PAN name. | Before submission |
| Goods and Services Tax Identification Number (GSTIN) | LLP, partnership, trust, society, HUF, government, judicial person and local authority | business_profile.identity_numbers.gstin | Needed if turnover is over ₹40,00,000 or the business sells across states | Checked with the Goods and Services Tax (GST) registry. Its requirement_level is conditional. | Before submission |
| Authorised person’s name and PAN | All 9 types | 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 | Always | The authorized_person composite requirement, all_of the name plus the PAN or the PAN card. See Who Signs. | Before submission |
| Authorised person’s CKYC record | Section 8 company | 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 | When the authorised person’s PAN has a CKYC record | 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. | Before submission |
| Authorised person’s proof of address | Section 8 company | 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 | When the authorised person skips CKYC or has no CKYC record | 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. | Before submission |
| Authorised person’s proof of address | LLP, partnership, trust, society, HUF, government, judicial person and local authority | 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 | Always | 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. | Before submission |
| Beneficial owners | Section 8 company, LLP, partnership and trust | business_profile.stakeholders | Always | Everyone holding more than 10%: name, PAN and percentage_ownership. | Before submission |
| Beneficial owners | Society | business_profile.stakeholders | Always | Everyone holding more than 15%: name, PAN and percentage_ownership. | Before submission |
| Video KYC | Section 8 company | create_video_kyc_link | Without a CKYC record or when CKYC is skipped | 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. | After submission |
| Video KYC | LLP, partnership, trust and society | create_video_kyc_link | When Razorpay needs enhanced due diligence | 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. | After submission |
Who Signs for Each Type
The table below lists who acts as the authorised person for each type: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.
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:| # | Scenario | Trigger | What to confirm |
|---|---|---|---|
| 1 | Section 8 company: account creation to activation Coming soon | business_type: section_8_company, business PAN ABCCD1260N |
|
| 2 | LLP: account creation to activation Coming soon | business_type: llp, business PAN DHKFP3456L |
|
| 3 | Partnership: account creation to activation Coming soon | business_type: partnership, business PAN DEFFT7777G |
|
| 4 | Trust: account creation to activation Coming soon | business_type: trust, business PAN MNOTW1234J |
|
| 5 | Society: account creation to activation Coming soon | business_type: society, business PAN ABCAD1239F |
|
| 6 | HUF: account creation to activation Coming soon | business_type: huf, business PAN ABCHD1234A |
|
| 7 | Government: account creation to activation Coming soon | business_type: government, business PAN ABCGD1234A |
|
| 8 | Judicial person: account creation to activation Coming soon | business_type: judicial_person, business PAN ABCJD1234A |
|
| 9 | Local authority: account creation to activation Coming soon | business_type: local_authority, business PAN ABCLD1234A |
|
3.2 Other Common Scenarios
The table below lists the other common scenarios:| # | Scenario | Trigger | What to confirm |
|---|---|---|---|
| 10 | Requirements follow the type (also on every business type) Coming soon | Each type above |
|
| 11 | Review outcomes (also on every business type) Coming soon | The outcome accounts 000000000002 to 000000000007. Use 000000000004 only for Section 8 companies, LLPs, partnerships, trusts and societies. |
|
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:| # | Scenario | Trigger | Error object | What to confirm |
|---|---|---|---|---|
| 12 | A business type not in the list Live | business_type: "company" | HTTP 400error.reason: invalid_optionerror.field: business_profile.business_type |
|
| 13 | Changing the type after the PAN verifies Coming soon | A new business_type on an account whose PAN is verified | HTTP 409error.reason: field_lockederror.field: business_profile.business_type |
|
business_pan. Each type has a failing PAN with its own 4th character.
The table below lists the business PAN scenario:
| # | Scenario | Trigger | Error object | What to confirm |
|---|---|---|---|---|
| 14 | A business PAN that fails its check Coming soon | Section 8 company: ABCCD1234BLLP: ABCFD1234BPartnership: ABCFD1234BTrust: ABCTD1234BSociety: ABCAD1234BHUF: ABCHD1234BGovernment: ABCGD1234BJudicial person: ABCJD1234BLocal authority: ABCLD1234B | verification.status: rejectedverification.error_code: pan_not_foundAt: business_profile.identity_numbers.business_panDue again: business_profile.identity_numbers.business_pan, business_profile.documents.business_panComposite requirement: business_pan |
|