Skip to main content
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. Every request and response body is on the API test pages, starting with Create an Account.

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-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:

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: 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:
RequirementSendWhenNotesDue
User’s contactuser.email + user.phone + user.nameAlwaysVerify both with the OTP actions in the next row.At creation
Contact verificationsend_phone_otp + phone_otp + send_email_otp + email_otpAlwaysRun each send action, and its response asks for the code.Before submission
Business typebusiness_profile.business_typeAlwaysDecides every other row. Locked once the PAN is verified.At creation
Payment channelsproducts.payment_gateway.payment_channels.website.primary or products.payment_gateway.payment_channels.app_android.url or products.payment_gateway.payment_channels.app_ios.urlAlwaysThe payment_channels composite requirement, one_of. Any one channel satisfies it: a website, an Android app or an iOS app.Optional
Websiteproducts.payment_gateway.payment_channels.website.primaryWith a website channelChecked 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 categorybusiness_profile.business_category.category + business_profile.business_category.subcategory or business_profile.business_category.mccAlwaysSelect the business category and send its subcategory with it. Alternatively, send the Merchant Category Code (MCC) alone.Before submission
Business descriptionbusiness_profile.business_category.business_descriptionAlwaysWhat the business sells, in up to 100 characters.Before submission
Name on statementsstatement_descriptor.valueAlwaysA text input.Before submission
Registered addressbusiness_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].countryAlwaysWhere the business is registered. The registered_address composite requirement, all_of its parts. line2 is optional and country is IN.Before submission
Operational addressbusiness_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].countryAlwaysWhere 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 accountbank_accounts.settlements_primary.account_number + bank_accounts.settlements_primary.routing_code + bank_accounts.settlements_primary.routing_code_type or create_upi_linkAlwaysThe 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 questionsbusiness_profile.business_category.business_model_clarifications.<question_id>.answerWhen the category asksOnce 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 documentsbusiness_profile.documentsWhen an answer asks for oneA licence or agreement that an answer asks for.Before submission
Terms of service and submissionproducts.payment_gateway.terms_of_service_acceptance.ip + products.payment_gateway.terms_of_service_acceptance.device_fingerprint_idAlwaysShow 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
The table below lists the requirements that differ by type:
RequirementTypesSendWhenNotesDue
Business PANSection 8 company and LLPbusiness_profile.identity_numbers.business_pan or business_profile.documents.business_panAlwaysThe business_pan composite requirement: the number or the card. The 4th character must match the business type.Before submission
Business PANPartnership, trust, society, HUF, government, judicial person and local authoritybusiness_profile.identity_numbers.business_pan or business_profile.documents.business_panAlwaysThe 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 incorporationSection 8 companybusiness_profile.date_of_establishmentAlwaysThe date the company was incorporated.Before submission
Proof of business identitySection 8 companybusiness_profile.identity_numbers.cin or business_profile.documents.certificate_of_incorporationAlwaysThe 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 identityLLPbusiness_profile.documents.certificate_of_incorporationAlwaysThe 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 authoritybusiness_profile.identity_numbers.gstinNeeded if turnover is over ₹40,00,000 or the business sells across statesChecked with the Goods and Services Tax (GST) registry. Its requirement_level is conditional.Before submission
Authorised person’s name and PANAll 9 typesbusiness_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_documentAlwaysThe authorized_person composite requirement, all_of the name plus the PAN or the PAN card. See Who Signs.Before submission
Authorised person’s CKYC recordSection 8 companybusiness_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_idWhen the authorised person’s PAN has a CKYC recordThe 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 addressSection 8 companycreate_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_backWhen the authorised person skips CKYC or has no CKYC recordThe 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 addressLLP, partnership, trust, society, HUF, government, judicial person and local authoritycreate_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_backAlwaysThe 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 ownersSection 8 company, LLP, partnership and trustbusiness_profile.stakeholdersAlwaysEveryone holding more than 10%: name, PAN and percentage_ownership.Before submission
Beneficial ownersSocietybusiness_profile.stakeholdersAlwaysEveryone holding more than 15%: name, PAN and percentage_ownership.Before submission
Video KYCSection 8 companycreate_video_kyc_linkWithout a CKYC record or when CKYC is skippedEnhanced 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 KYCLLP, partnership, trust and societycreate_video_kyc_linkWhen Razorpay needs enhanced due diligenceEnhanced 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
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:

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:
#ScenarioTriggerWhat to confirm
1Section 8 company: account creation to activation Coming soonbusiness_type: section_8_company, business PAN ABCCD1260N
  1. Create the account with country, the user and products: { "payment_gateway": { "payment_channels": {} } }. See Create an Account. Confirm business_type, send_phone_otp and send_email_otp are due.
  2. Run send_phone_otp and send_email_otp, then send 000007 as phone_otp and email_otp.
  3. Send business_type: section_8_company and the business PAN ABCCD1260N at business_profile.identity_numbers.business_pan.
  4. Confirm the PAN is verified and the PAN record’s name comes back as business_name.
  5. Send the CIN U85300KA2019NPL123456. Confirm business_identity clears.
  6. Send date_of_establishment 2019-04-15, the date of incorporation.
  7. Send the authorised person Rzp Test QA Merchant with PAN ABCPD1234A. This person has a CKYC record, so ckyc_fetch is due.
  8. 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.
  9. If requirements lists the beneficial owners, send stakeholders. Each owner has name, identity_numbers.individual_pan and percentage_ownership.
  10. 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.
  11. Send bank account 000000000001 with IFSC HDFC0123456. Confirm verified.
  12. Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.
  13. 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.
  14. Webhooks received: account.requirements.updated (as the website check settles), account.product.activated.
  15. Status changes: in_progress → activated.
2LLP: account creation to activation Coming soonbusiness_type: llp, business PAN DHKFP3456L
  1. Create the account with country, the user and products: { "payment_gateway": { "payment_channels": {} } }. See Create an Account. Confirm business_type, send_phone_otp and send_email_otp are due.
  2. Run send_phone_otp and send_email_otp, then send 000007 as phone_otp and email_otp.
  3. Send business_type: llp and the business PAN DHKFP3456L at business_profile.identity_numbers.business_pan.
  4. Confirm the PAN is verified and the PAN record’s name comes back as business_name.
  5. Upload COI_DHKFP3456L.pdf and attach it at business_profile.documents.certificate_of_incorporation. Confirm verified.
  6. Send the authorised person Rzp Test QA Merchant with PAN ABCPD1234A.
  7. Send what else requirements lists for the type, such as the authorised person’s proof of address and the beneficial owners.
  8. For the proof of address, send AADHAARCKYCCOMPLETE.jpg as the front and the back, in one update.
  9. For each beneficial owner in stakeholders, send name, identity_numbers.individual_pan and percentage_ownership.
  10. 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.
  11. Send bank account 210045678901 with IFSC HDFC0123456. Confirm verified.
  12. Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.
  13. 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.
  14. Webhooks received: account.requirements.updated (as the website check settles), account.product.activated.
  15. Status changes: in_progress → activated.
3Partnership: account creation to activation Coming soonbusiness_type: partnership, business PAN DEFFT7777G
  1. Create the account with country, the user and products: { "payment_gateway": { "payment_channels": {} } }. See Create an Account. Confirm business_type, send_phone_otp and send_email_otp are due.
  2. Run send_phone_otp and send_email_otp, then send 000007 as phone_otp and email_otp.
  3. Send business_type: partnership and the business PAN DEFFT7777G at business_profile.identity_numbers.business_pan.
  4. Confirm the PAN is verified and the PAN record’s name comes back as business_name.
  5. Send the authorised person Rzp Test QA Merchant with PAN ABCPD1234A.
  6. Send what else requirements lists for the type, such as the authorised person’s proof of address and the beneficial owners.
  7. For the proof of address, send AADHAARCKYCCOMPLETE.jpg as the front and the back, in one update.
  8. For each beneficial owner in stakeholders, send name, identity_numbers.individual_pan and percentage_ownership.
  9. 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.
  10. Send bank account 210045678903 with IFSC HDFC0123456. Confirm verified.
  11. Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.
  12. 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.
  13. Webhooks received: account.requirements.updated (as the website check settles), account.product.activated.
  14. Status changes: in_progress → activated.
4Trust: account creation to activation Coming soonbusiness_type: trust, business PAN MNOTW1234J
  1. Create the account with country, the user and products: { "payment_gateway": { "payment_channels": {} } }. See Create an Account. Confirm business_type, send_phone_otp and send_email_otp are due.
  2. Run send_phone_otp and send_email_otp, then send 000007 as phone_otp and email_otp.
  3. Send business_type: trust and the business PAN MNOTW1234J at business_profile.identity_numbers.business_pan.
  4. Confirm the PAN is verified and the PAN record’s name comes back as business_name.
  5. Send the authorised person Rzp Test QA Merchant with PAN ABCPD1234A.
  6. Send what else requirements lists for the type, such as the authorised person’s proof of address and the beneficial owners.
  7. For the proof of address, send AADHAARCKYCCOMPLETE.jpg as the front and the back, in one update.
  8. For each beneficial owner in stakeholders, send name, identity_numbers.individual_pan and percentage_ownership.
  9. 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.
  10. Send bank account 210045678905 with IFSC HDFC0123456. Confirm verified.
  11. Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.
  12. 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.
  13. Webhooks received: account.requirements.updated (as the website check settles), account.product.activated.
  14. Status changes: in_progress → activated.
5Society: account creation to activation Coming soonbusiness_type: society, business PAN ABCAD1239F
  1. Create the account with country, the user and products: { "payment_gateway": { "payment_channels": {} } }. See Create an Account. Confirm business_type, send_phone_otp and send_email_otp are due.
  2. Run send_phone_otp and send_email_otp, then send 000007 as phone_otp and email_otp.
  3. Send business_type: society and the business PAN ABCAD1239F at business_profile.identity_numbers.business_pan.
  4. Confirm the PAN is verified and the PAN record’s name comes back as business_name.
  5. Send the authorised person Rzp Test QA Merchant with PAN ABCPD1234A.
  6. Send what else requirements lists for the type, such as the authorised person’s proof of address and the beneficial owners.
  7. For the proof of address, send AADHAARCKYCCOMPLETE.jpg as the front and the back, in one update.
  8. For each beneficial owner in stakeholders, send name, identity_numbers.individual_pan and percentage_ownership.
  9. 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.
  10. Send bank account 210045678908 with IFSC HDFC0123456. Confirm verified.
  11. Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.
  12. 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.
  13. Webhooks received: account.requirements.updated (as the website check settles), account.product.activated.
  14. Status changes: in_progress → activated.
6HUF: account creation to activation Coming soonbusiness_type: huf, business PAN ABCHD1234A
  1. Create the account with country, the user and products: { "payment_gateway": { "payment_channels": {} } }. See Create an Account. Confirm business_type, send_phone_otp and send_email_otp are due.
  2. Run send_phone_otp and send_email_otp, then send 000007 as phone_otp and email_otp.
  3. Send business_type: huf and the business PAN ABCHD1234A at business_profile.identity_numbers.business_pan.
  4. Confirm the PAN is verified and the PAN record’s name comes back as business_name.
  5. Send the authorised person Rzp Test QA Merchant with PAN ABCPD1234A.
  6. Send what else requirements lists for the type, such as the authorised person’s proof of address. This type sends no beneficial owners.
  7. For the proof of address, send AADHAARCKYCCOMPLETE.jpg as the front and the back, in one update.
  8. 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.
  9. Send bank account 000000000001 with IFSC HDFC0123456. Confirm verified.
  10. Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.
  11. 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.
  12. Webhooks received: account.requirements.updated (as the website check settles), account.product.activated.
  13. Status changes: in_progress → activated.
7Government: account creation to activation Coming soonbusiness_type: government, business PAN ABCGD1234A
  1. Create the account with country, the user and products: { "payment_gateway": { "payment_channels": {} } }. See Create an Account. Confirm business_type, send_phone_otp and send_email_otp are due.
  2. Run send_phone_otp and send_email_otp, then send 000007 as phone_otp and email_otp.
  3. Send business_type: government and the business PAN ABCGD1234A at business_profile.identity_numbers.business_pan.
  4. Confirm the PAN is verified and the PAN record’s name comes back as business_name.
  5. Send the authorised person Rzp Test QA Merchant with PAN ABCPD1234A.
  6. Send what else requirements lists for the type, such as the authorised person’s proof of address. This type sends no beneficial owners.
  7. For the proof of address, send AADHAARCKYCCOMPLETE.jpg as the front and the back, in one update.
  8. 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.
  9. Send bank account 000000000001 with IFSC HDFC0123456. Confirm verified.
  10. Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.
  11. 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.
  12. Webhooks received: account.requirements.updated (as the website check settles), account.product.activated.
  13. Status changes: in_progress → activated.
8Judicial person: account creation to activation Coming soonbusiness_type: judicial_person, business PAN ABCJD1234A
  1. Create the account with country, the user and products: { "payment_gateway": { "payment_channels": {} } }. See Create an Account. Confirm business_type, send_phone_otp and send_email_otp are due.
  2. Run send_phone_otp and send_email_otp, then send 000007 as phone_otp and email_otp.
  3. Send business_type: judicial_person and the business PAN ABCJD1234A at business_profile.identity_numbers.business_pan.
  4. Confirm the PAN is verified and the PAN record’s name comes back as business_name.
  5. Send the authorised person Rzp Test QA Merchant with PAN ABCPD1234A.
  6. Send what else requirements lists for the type, such as the authorised person’s proof of address. This type sends no beneficial owners.
  7. For the proof of address, send AADHAARCKYCCOMPLETE.jpg as the front and the back, in one update.
  8. 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.
  9. Send bank account 000000000001 with IFSC HDFC0123456. Confirm verified.
  10. Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.
  11. 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.
  12. Webhooks received: account.requirements.updated (as the website check settles), account.product.activated.
  13. Status changes: in_progress → activated.
9Local authority: account creation to activation Coming soonbusiness_type: local_authority, business PAN ABCLD1234A
  1. Create the account with country, the user and products: { "payment_gateway": { "payment_channels": {} } }. See Create an Account. Confirm business_type, send_phone_otp and send_email_otp are due.
  2. Run send_phone_otp and send_email_otp, then send 000007 as phone_otp and email_otp.
  3. Send business_type: local_authority and the business PAN ABCLD1234A at business_profile.identity_numbers.business_pan.
  4. Confirm the PAN is verified and the PAN record’s name comes back as business_name.
  5. Send the authorised person Rzp Test QA Merchant with PAN ABCPD1234A.
  6. Send what else requirements lists for the type, such as the authorised person’s proof of address. This type sends no beneficial owners.
  7. For the proof of address, send AADHAARCKYCCOMPLETE.jpg as the front and the back, in one update.
  8. 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.
  9. Send bank account 000000000001 with IFSC HDFC0123456. Confirm verified.
  10. Send the category, website and statement descriptor as for any type. Answer any business-model questions the subcategory asks.
  11. 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.
  12. Webhooks received: account.requirements.updated (as the website check settles), account.product.activated.
  13. Status changes: in_progress → activated.

3.2 Other Common Scenarios

The table below lists the other common scenarios:
#ScenarioTriggerWhat to confirm
10Requirements follow the type (also on every business type) Coming soonEach type above
  1. Create one test account per type you offer.
  2. Confirm the requirements match the type’s rows in Requirements by Type.
  3. Webhooks received: none.
  4. Status changes: none.
11Review outcomes (also on every business type) Coming soonThe outcome accounts 000000000002 to 000000000007. Use 000000000004 only for Section 8 companies, LLPs, partnerships, trusts and societies.
  1. Run any journey above with one of the outcome accounts as the settlement account.
  2. Confirm the outcome that the account names.
  3. Webhooks received: the status events for each change.
  4. Status changes: as the account names.

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:
#ScenarioTriggerError objectWhat to confirm
12A business type not in the list Livebusiness_type: "company"HTTP 400
error.reason: invalid_option
error.field: business_profile.business_type
  1. Send the value.
  2. Confirm 400 with metadata.allowed_values.
  3. Webhooks received: none.
  4. Status changes: none.
13Changing the type after the PAN verifies Coming soonA new business_type on an account whose PAN is verifiedHTTP 409
error.reason: field_locked
error.field: business_profile.business_type
  1. Send the value.
  2. Confirm 409.
  3. Webhooks received: none.
  4. Status changes: none.
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:
#ScenarioTriggerError objectWhat to confirm
14A business PAN that fails its check Coming soonSection 8 company: ABCCD1234B
LLP: ABCFD1234B
Partnership: ABCFD1234B
Trust: ABCTD1234B
Society: ABCAD1234B
HUF: ABCHD1234B
Government: ABCGD1234B
Judicial person: ABCJD1234B
Local authority: ABCLD1234B
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
  1. Send the failing PAN for your type where it is due. Confirm the response is a 200.
  2. Webhooks received: none, because the response carries the failure.
  3. Status changes: none.
Every failure code, with its test value, is in the Error Index.

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:

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:
Last modified on November 18, 2026