Available in🇮🇳 India
An individual is an unregistered business. The owner’s PAN is the business identity, and the business name comes from the PAN. This page tests an individual’s onboarding from account creation to activation, including the Central KYC Records Registry (CKYC) fetch and video KYC.
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 this business type:What You Can Test
The table below lists what this page tests:Endpoint Coverage in Test Mode
The table below lists the endpoints this business type uses: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.
ABCPD1234A and it verifies with the name Rzp Test QA Merchant, with ckyc_fetch due. Send ABCPD1234K and the PAN verification is rejected with pan_not_found.
Keep these rules in mind when you pick values:
- To succeed, use test business A or C.
- To fail a check, send one of the values in 3.3 Error Scenarios.
- You need no real details. Nothing reaches a registry, a bank or the sub-merchant. Skip the real PAN, bank account, phone and video call.
- Any other value fails as if the registry or bank were down, so a typo looks like an outage.
Test Businesses
Every individual test business uses the Indian Financial System Code (IFSC)HDFC0123456 for its bank account.
The table below lists the individual test businesses:
Every individual also uses these values:
- Phone and email codes:
000007. - CKYC code: any 6 digits other than
000000. - Website:
https://curlec.comwith Merchant Category Code (MCC)5732. - Statement descriptor (
statement_descriptor.value): any value. - Business-model questions: any option for each question.
3. Test Scenarios
This section lists every scenario to run against your integration for this business type 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 4 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.
- Review, links and after activation: Outcomes that a reviewer, a hosted link or a later change decides. Test values and the hosted test pages force each one.
3.1 Must-Build Scenarios
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 | Activated end to end Coming soon | Test business A, step by step |
|
| 2 | Create everything at once Coming soon | Test business A in one account creation call |
|
| 3 | No CKYC record: video KYC Coming soon | Test business B |
|
3.2 Other Common Scenarios
The table below lists the other common scenarios:| # | Scenario | Trigger | What to confirm |
|---|---|---|---|
| 4 | Fetch to follow the status (also on every business type) Coming soon | Settlement account 000000000002 |
|
| 5 | Rejected (also on every business type) Coming soon | Settlement account 000000000002 |
|
| 6 | The PAN card instead of the number Coming soon | PERSONALPANFRONT.jpg |
|
| 7 | Wrong codes 3 times Coming soon | A wrong phone code, sent 3 times |
|
3.3 Error Scenarios
We group the error scenarios by the check or request that fails. In the error object,…authorized_person stands for business_profile.authorized_person. …website.primary stands for products.payment_gateway.payment_channels.website.primary.
PAN Registry
The PAN registry said no, or did not answer. Most failures bring back individual_pan or business_pan, meaning the number or the card. Nothing you send fixes an under-18 holder.
The table below lists the PAN registry scenarios:
| # | Scenario | Trigger | Error object | What to confirm |
|---|---|---|---|---|
| 8 | PAN: the PAN is invalid Coming soon | ABCPD1234K | verification.status: rejectedverification.error_code: pan_not_foundAt: …authorized_person.identity_numbers.individual_panDue again: …authorized_person.identity_numbers.individual_pan, …authorized_person.documents.individual_pan_documentComposite requirement: individual_pan |
|
| 9 | PAN: no record exists for the PAN Coming soon | ABCPD1234C | verification.status: rejectedverification.error_code: pan_not_foundAt: …authorized_person.identity_numbers.individual_panDue again: …authorized_person.identity_numbers.individual_pan, …authorized_person.documents.individual_pan_documentComposite requirement: individual_pan |
|
| 10 | PAN: the registry errored, but the PAN is fine Coming soon | ABCPD1234D | verification.status: rejectedverification.error_code: pan_check_unavailableAt: …authorized_person.identity_numbers.individual_panDue again: …authorized_person.identity_numbers.individual_pan, …authorized_person.documents.individual_pan_documentComposite requirement: individual_pan |
|
| 11 | PAN: the PAN holder is under 18 Coming soon | ABCPD1234M | verification.status: rejectedverification.error_code: promoter_underageAt: …authorized_person.identity_numbers.individual_pan |
|
| # | Scenario | Trigger | Error object | What to confirm |
|---|---|---|---|---|
| 12 | PAN card: the card reads ABCPD1234Z, not the PAN sent Coming soon | PERSONALPANMISMATCHFRONT.jpg | verification.status: rejectedverification.error_code: pan_card_mismatchAt: …authorized_person.documents.individual_pan_documentDue again: …authorized_person.documents.individual_pan_document |
|
| 13 | PAN card: the card carries another name Coming soon | PERSONALPANNAMEMISMATCHFRONT.jpg | verification.status: rejectedverification.error_code: pan_card_name_mismatchAt: …authorized_person.documents.individual_pan_documentDue again: …authorized_person.documents.individual_pan_document |
|
| 14 | PAN card: no name or number is readable on the card Coming soon | PERSONALPANUNREADABLEFRONT.jpg | verification.status: rejectedverification.error_code: pan_card_name_unreadableAt: …authorized_person.documents.individual_pan_documentDue again: …authorized_person.documents.individual_pan_document |
|
| 15 | PAN card: the file is not a PAN card Coming soon | WRONGFRONT.jpg | verification.status: rejectedverification.error_code: not_a_pan_cardAt: …authorized_person.documents.individual_pan_documentDue again: …authorized_person.documents.individual_pan_document |
|
| 16 | Proof of address: the Aadhaar is in another name Coming soon | AADHARMISMATCHFRONT.jpg | verification.status: rejectedverification.error_code: poa_name_mismatchAt: …authorized_person.documents.aadhaar_frontDue again: create_aadhaar_digilocker_link, …authorized_person.documents.aadhaar_front, …authorized_person.documents.aadhaar_back, …authorized_person.documents.passport_front, …authorized_person.documents.passport_back, …authorized_person.documents.voter_id_front, …authorized_person.documents.voter_id_backComposite requirement: proof_of_address_for_individual |
|
| 17 | Proof of address: the Aadhaar is unreadable Coming soon | AADHAARUNREADABLEFRONT.jpg | verification.status: rejectedverification.error_code: poa_unreadableAt: …authorized_person.documents.aadhaar_frontDue again: create_aadhaar_digilocker_link, …authorized_person.documents.aadhaar_front, …authorized_person.documents.aadhaar_back, …authorized_person.documents.passport_front, …authorized_person.documents.passport_back, …authorized_person.documents.voter_id_front, …authorized_person.documents.voter_id_backComposite requirement: proof_of_address_for_individual |
|
ckyc_otp and ckyc_request_id stay due. Send the right code with the same request ID. An expired code brings send_ckyc_otp back. A record that cannot be downloaded makes the proof of address due.
The table below lists the CKYC scenarios:
| # | Scenario | Trigger | Error object | What to confirm |
|---|---|---|---|---|
| 18 | CKYC record: the record cannot be downloaded Coming soon | PAN ABCPD1234X, then any code other than 000000 | verification.status: rejectedverification.error_code: ckyc_unavailableAt: …authorized_person.identity_numbers.individual_ckycDue again: create_aadhaar_digilocker_link, …authorized_person.documents.aadhaar_front, …authorized_person.documents.aadhaar_back, …authorized_person.documents.passport_front, …authorized_person.documents.passport_back, …authorized_person.documents.voter_id_front, …authorized_person.documents.voter_id_backComposite requirement: proof_of_address_for_individual |
|
| 19 | CKYC code: the code has expired Coming soon | PAN AICPD1234U, then any code other than 000000 | verification.status: rejectedverification.error_code: otp_expiredAt: …authorized_person.identity_numbers.individual_ckycDue again: send_ckyc_otp, …authorized_person.identity_numbers.individual_ckyc.is_skippedComposite requirement: ckyc_fetch |
|
| 20 | CKYC code: the code does not match the one sent Coming soon | PAN ABCPD1234A, then code 000000 | verification.status: rejectedverification.error_code: otp_invalidAt: …authorized_person.identity_numbers.individual_ckycDue again: …authorized_person.identity_numbers.individual_ckyc.otp, …authorized_person.identity_numbers.individual_ckyc.request_id |
|
bank_account comes back as one_of: the same or another account (settlement_bank_account), or the ₹1 UPI link (create_upi_link). Show them as one choice.
The table below lists the bank scenarios:
| # | Scenario | Trigger | Error object | What to confirm |
|---|---|---|---|---|
| 21 | Bank account: the holder name does not match Coming soon | 2100000011 | verification.status: rejectedverification.error_code: bank_name_mismatchAt: bank_accounts.settlements_primaryDue again: bank_accounts.settlements_primary, create_upi_linkComposite requirement: bank_account |
|
| 22 | Bank account: the holder name is close but under the match threshold Coming soon | 2100000012 | verification.status: rejectedverification.error_code: bank_name_mismatchAt: bank_accounts.settlements_primaryDue again: bank_accounts.settlements_primary, create_upi_linkComposite requirement: bank_account |
|
| 23 | Bank account: the IFSC is invalid Coming soon | 2100000040 | verification.status: rejectedverification.error_code: bank_details_incorrectAt: bank_accounts.settlements_primaryDue again: bank_accounts.settlements_primary, create_upi_linkComposite requirement: bank_account |
|
| 24 | Bank account: the account is closed Coming soon | 1234567892 | verification.status: rejectedverification.error_code: bank_account_unusableAt: bank_accounts.settlements_primaryDue again: bank_accounts.settlements_primary, create_upi_linkComposite requirement: bank_account |
|
| 25 | Bank account: the account is frozen Coming soon | 2100000005 | verification.status: rejectedverification.error_code: bank_account_unusableAt: bank_accounts.settlements_primaryDue again: bank_accounts.settlements_primary, create_upi_linkComposite requirement: bank_account |
|
| 26 | Bank account: a Non-Resident External (NRE) account cannot receive settlements Coming soon | 2100000006 | verification.status: rejectedverification.error_code: bank_account_unusableAt: bank_accounts.settlements_primaryDue again: bank_accounts.settlements_primary, create_upi_linkComposite requirement: bank_account |
|
| 27 | Bank account: the bank was unreachable, but the account is fine Coming soon | 2100000039 | verification.status: rejectedverification.error_code: bank_check_unavailableAt: bank_accounts.settlements_primaryDue again: bank_accounts.settlements_primary, create_upi_linkComposite requirement: bank_account |
|
| 28 | Bank account: the bank declined without a reason Coming soon | 2100000031 | verification.status: rejectedverification.error_code: bank_not_verifiedAt: bank_accounts.settlements_primaryDue again: bank_accounts.settlements_primary, create_upi_linkComposite requirement: bank_account |
|
| # | Scenario | Trigger | Error object | What to confirm |
|---|---|---|---|---|
| 29 | Website: the check fails a few seconds after the response Coming soon | https://www.kc-not-found.com | verification.status: rejectedverification.error_code: website_unreachableAt: …website.primaryDue again: …website.primary |
|
| # | Scenario | Trigger | Error object | What to confirm |
|---|---|---|---|---|
| 30 | Video KYC not approved (also on every business type) Coming soon | The hosted page’s Unable to verify, or Rejected | Still due: create_video_kyc_linkrequirement_type: action |
|
| # | Scenario | Trigger | Error object | What to confirm |
|---|---|---|---|---|
| 31 | Business name for an individual Live | business_name in an update | HTTP 400error.reason: invalid_requesterror.field: business_profile.business_name |
|
3.4 Review, Links and After Activation
A reviewer, a hosted link or a later change decides these outcomes. A test value or a hosted test page forces each one. The table below lists the scenarios that a review, a link or a later change decides:| # | Scenario | Trigger | What to confirm |
|---|---|---|---|
| 32 | Needs clarification (also on every business type) Coming soon | Settlement account 000000000003 |
|
| 33 | Held in review (also on every business type) Coming soon | Settlement account 000000000005 |
|
| 34 | Suspended after activation (also on every business type) Coming soon | Settlement account 000000000006 |
|
| 35 | A link expires before the sub-merchant finishes it (also on every business type) Coming soon | The hosted page’s Expire the link |
|
| 36 | DigiLocker for the proof of address Coming soon | The hosted page’s Share Aadhaar, then Decline |
|
| 37 | ₹1 UPI check of the bank account (also on every business type) Coming soon | The hosted page’s Pay ₹1, then Pay from another person’s account |
|
| 38 | Access withdrawn (also on every business type) Coming soon | Settlement account 000000000007 |
|
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. Requirements and Values The table below lists gaps in handling requirements and values:
Status and Webhooks
The table below lists gaps in handling status and webhooks:
Error Handling and Messaging
The table below lists gaps in error handling and messaging: