Skip to main content
Available in🇮🇳 India
Send what is due on a test account and check each verification outcome. Test the ordering rules and locks before you go live. PATCH /v1/accounts/{account_id} sends what is due. Values apply in the order sent. Concurrent updates to 1 account apply one at a time. Start with the overview for test credentials and headers.

1. Test Mode Coverage

Test Mode Differences

The table below lists how updates behave in each mode:

What You Can Test

The table below lists the areas to test on this endpoint:

Endpoint Coverage in Test Mode

The table below lists the endpoints this page uses:

2. Before You Begin

Prepare the following before you run the scenarios:
  • Create an account, as in scenario 1 on Create an Account.
  • Send each input’s field_path as a path in the body.
  • Send the phone and email codes (phone_otp, email_otp) at the top level of the body.

Sample Request

The request below sends the PAN of test business Individual A. The response is the whole account, within 3 sec. A slow check stays in_progress and settles later.
Curl
Know more about the request parameters.

Sample Response

The PAN comes back verified, and ckyc_fetch is due next.
Response

3. Test Scenarios

Work through these scenarios in order. Each row gives the trigger to send and what to confirm in the response.

3.1 Scenarios

Live scenarios work in test mode today. Coming soon scenarios are not available in test mode yet. The table below lists 20 scenarios. 7 are live and 13 are coming soon:
#ScenarioTriggerWhat to confirm
1Send the business type LiveindividualSend it. Confirm the requirements change to those of an individual.
2Verify the phone and email Coming soon000007Run send_phone_otp and send_email_otp, as on Actions. Each response lists the code to send. Send phone_otp and email_otp. Confirm both contacts are verified.
3A wrong code Coming soon123456Send it as phone_otp. Confirm HTTP 200, and that phone_otp is still due.
4PAN verified Coming soonABCPD1234ASend the PAN, as in the sample request. Confirm verified, the name and ckyc_fetch due.
5The CKYC code Coming soonAny 6 digits other than 000000Run send_ckyc_otp. Its response lists ckyc_otp and ckyc_request_id. Send the code as individual_ckyc.otp and its request ID as individual_ckyc.request_id, as in the scenario details. Confirm individual_ckyc is verified with value: null, and no proof of address is due.
6Bank account verified Coming soon1234567890 with HDFC0123456Send it under bank_accounts.settlements_primary. Confirm verified, and the account number returned in full.
7Bank name mismatch Coming soon2100000011Send it. Confirm verification.status: rejected with error_code: bank_name_mismatch, and bank_account due again. Send 1234567890 to clear it.
8Category and business-model questions Coming soonSubcategory fashion_and_lifestyleSend the category ecommerce with this subcategory. Confirm business_model_clarifications lists bmc_question_2. Answer it with one of its options. Know more about business model questions.
9A check that settles later Coming soonhttps://curlec.comSend it. Confirm in_progress, then verified on a fetch. Confirm Razorpay sends account.requirements.updated when the check settles.
10Name on statements LiveA name, such as Rzp Test StoreSend it as statement_descriptor.value.
11A value before it is due LiveA bank account before the business typeConfirm 400 step_not_due with metadata.due.
12A read-only or unknown key Coming soonbank_accounts.settlements_primary.verification or "bussiness_profile"Confirm 400 invalid_request.
13A code in the wrong format Live12345Confirm 400 invalid_format. A wrong 6-digit code returns HTTP 200 instead (#3).
14A document ID that is not this account’s LiveA file_ ID from another account, or a deleted oneConfirm 404 not_found with the path of the document.
15Change KYC after submission Coming soonA new bank account while edd_pendingSubmit an account without a CKYC record, as in scenario 4 on Terms and Submission. Send a bank account. Confirm 409 field_locked with metadata.status: edd_pending.
16Change a verified value Coming soonbusiness_type after the PAN verifies, or a verified phoneConfirm 409 field_locked.
17Empty body Live{}Confirm 400 invalid_request.
18Retry an update LiveThe same key and bodyConfirm the same response, and that the value applied once.
19Answer a reviewer Coming soonA product in needs_clarification (settlement account 000000000003)Follow Needs Clarification. Confirm only the flagged points can change.
20Change the bank account after activation Coming soonAn activated account, then settlement account 000000000001Send the new account under bank_accounts.settlements_primary. Confirm HTTP 200, the new account checked and verified and the product still activated. Settlements move to the new account once it is verified.

3.2 Scenario Details

The details below expand the scenarios that need more than one step:
Before you begin: Create an account without marking the user’s contacts verified.How to test:
  1. Call POST /v1/accounts/{account_id}/actions/send_phone_otp and POST /v1/accounts/{account_id}/actions/send_email_otp. Each response’s requirements lists phone_otp or email_otp.
  2. Send both codes in an update:
Expected result: HTTP 200. user.is_phone_verified and is_email_verified are true, and neither code is due.Your integration should: Collect the code in your form and send it as is. Offer a resend through the action, up to 5 an hour.
How to test: Send "phone_otp": "123456".Expected result: HTTP 200, not an error, because the code was well-formed but wrong. phone_otp is still due. After 3 wrong codes, or once the code expires, send_phone_otp is due again as an action.Your integration should: Tell the sub-merchant the code did not match, and let them retry or resend.
How to test: Send the sample request.Expected result: HTTP 200, as in the sample response. The response shows the following:
  • The PAN is verified, and the authorised person’s name is Rzp Test QA Merchant.
  • ckyc_fetch is due as a one_of: send_ckyc_otp or skip_ckyc.
  • The bank account is due as settlement_bank_account. It is an all_of of account_number, routing_code and routing_code_type under bank_accounts.settlements_primary.
  • The ₹1 UPI link is offered only after a failed check.
  • business_category, business_description and statement_descriptor are due.
  • The optional payment_channels composite is listed, as a one_of of a website or an app.
Your integration should: Read the name from the response to prefill the statement descriptor. Never ask for it again.
Before you begin: Complete scenario 4, so ckyc_fetch is due.How to test:
  1. Run send_ckyc_otp, as in scenario 4 on Actions. Its metadata has the request_id.
  2. Send the code as otp and the request ID as request_id, both on individual_ckyc:
Expected result: HTTP 200. business_profile.authorized_person.identity_numbers.individual_ckyc is verified with value: null. Its metadata has ckyc_mobile. The response never shows otp or request_id, because they are request-only. The proof of address comes from the CKYC record, so no Aadhaar is due.Your integration should: Send the code with the request ID the latest send_ckyc_otp returned. A resend replaces the open code and its request ID. Sending skip_ckyc instead makes proof_of_address_for_individual due.
How to test: Send the bank account:
Expected result: HTTP 200. The bank account’s verification is rejected with error_code: bank_name_mismatch. bank_account is due again as a one_of: the account again (settlement_bank_account) or the ₹1 UPI link (create_upi_link). See the complete body on Fetch an Account.Your integration should: Show its sub-requirements as 1 choice. Send 1234567890 to clear it in test mode.
How to test: On a new account, send a bank account before business_type.Expected result: HTTP 400 with reason: step_not_due. metadata.due lists what is due now. Values earlier in the body are saved.Your integration should: Send only what requirements lists.
Before you begin: Get an account to edd_pending, as in scenario 4 on Terms and Submission.How to test: Send a new bank account.Expected result: HTTP 409 with reason: field_locked, field: bank_accounts.settlements_primary and metadata.status: edd_pending.Your integration should: Make the KYC details read-only in your UI while a product is under_review or edd_pending, and after activation. Keep statement_descriptor and a new settlement bank account editable after activation (#20).

3.3 Errors to Handle

Every error returns the same object. Branch on error.reason and error.field, because the description can change. The overview lists the errors every operation shares. The table below lists the errors this endpoint returns:

4. Common Integration Gaps

These mistakes most often stall an onboarding or leave an account in the wrong state after go-live. The Test with column points to the scenario that proves you have handled each one. Sending values The table below lists the gaps when sending values: After submission The table below lists the gaps after submission:

5. Best Integration Practices

These practices apply to every onboarding integration. The On this page column says what each one means here. The table below lists the practices for updates:
Last modified on November 18, 2026