Skip to main content
Available in🇮🇳 India
Accept Razorpay’s terms of service on a test account, submit the product and force every outcome after submission before you go live. The sub-merchant accepts Razorpay’s terms of service in your UI. You submit by sending the acceptance. The product’s outcome follows, in the same response for most products. Start with the overview for test credentials and headers.

1. Test Mode Coverage

Test Mode Differences

The table below lists how submission behaves in each mode:

What You Can Test

The table below lists the areas to test for submission:

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:
  • Meet every requirement except accept_terms_of_service.
  • Pick the outcome you want to test with the settlement bank account, from the table below.

Outcomes After Submission

Pick the outcome with the settlement bank account number. Each of these accounts verifies whatever the holder’s name, so it works with every business type. Any other verified account gives the default: activated in the response, or edd_pending without a Central KYC Records Registry (CKYC) record. The table below lists the settlement accounts that force each outcome: Registered business types can use a business-name suffix instead. _REJECT (such as SUNRISE ENTERPRISES_REJECT) rejects the product, and _EDD asks for video KYC. The suffix does not affect the name matches.

Sample Request

Submission is the last update. Show the sub-merchant Razorpay’s terms of service for the accept_terms_of_service requirement. Once they accept in your UI, send their ip and device_fingerprint_id in the product’s terms_of_service_acceptance.
Curl
The table below lists the fields of terms_of_service_acceptance: Know more about the request parameters.

Sample Response

Razorpay records the acceptance and submits the product. The response carries the acceptance’s accepted_at. Most products come back activated in this response, as below.
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 14 scenarios. 2 are live and 12 are coming soon:
#ScenarioTriggerWhat to confirm
1Accept the terms and submit Coming soonIndividual A, with every requirement but the terms metShow Razorpay’s terms of service to the sub-merchant, who accepts. Send their ip and device_fingerprint_id, as in the sample request. Confirm activated, with accepted_at on the acceptance.
2Submit with something still due LiveThe acceptance before the bank accountConfirm 400 step_not_due with metadata.due.
3A missing field LiveNo device_fingerprint_idConfirm 400 invalid_request, with field naming it.
4No CKYC record: video KYC Coming soonPAN ABCPD7891BSubmit. Confirm edd_pending in the response, and create_video_kyc_link due as an action.
5Video KYC approved Coming soon#4, then Approved on the hosted test pageRun create_video_kyc_link. The link is in the response’s metadata. Open the url and pick Approved. Confirm under_review, then activated about 5 sec later.
6Video KYC rejected Coming soon#4, then Rejected on the hosted test pagePick Rejected. Confirm under_review, then rejected about 5 sec later.
7Video KYC unable to verify Coming soon#4, then Unable to verify on the hosted test pagePick Unable to verify. Confirm the product stays edd_pending, and create_video_kyc_link is still due. Run it again for a new call.
8Rejected Coming soonSettlement account 000000000002, or business_name ending _REJECTSubmit. Confirm under_review in the response, then rejected about 5 sec later.
9Video KYC by value Coming soonSettlement account 000000000004, or business_name ending _EDDSubmit. Confirm edd_pending in the response.
10Needs clarification Coming soonSettlement account 000000000003Submit. Confirm under_review, then needs_clarification about 5 sec later. Answer it, as on Needs Clarification.
11Held in review Coming soonSettlement account 000000000005Send it. Its verification is deferred, and bank_account clears. Submit and confirm under_review. Confirm it stays under_review, then turns activated after 5 min.
12Locked after submission Coming soon#4, then a new bank accountConfirm 409 field_locked with metadata.status: edd_pending.
13A rejected product Coming soon#8, then any update or actionConfirm 409 field_locked on updates and 400 step_not_due on actions.
14Suspended after activation Coming soonSettlement account 000000000006Submit and confirm activated. Confirm suspended about 60 sec later, with status_reason.code: website_review_failed and the website due again. Send https://curlec.com, and the product is activated again.

3.2 Scenario Details

The details below expand the scenarios that need more than one step:
Before you begin: Meet every requirement, so only accept_terms_of_service is due.How to test:
  1. Show Razorpay’s terms of service to the sub-merchant, unchanged.
  2. When they accept in your UI, record their IP address and your device fingerprint for the session.
  3. Send both values, as in the sample request.
Expected result: HTTP 200, as in the sample response. The product is activated and requirements is empty. The acceptance carries ip, device_fingerprint_id and accepted_at.Webhooks: account.product.activated.Your integration should: Send the acceptance only after the sub-merchant accepts, with their own ip. Keep the accepted_at time Razorpay returns.
How to test: Send terms_of_service_acceptance with only ip.Expected result: HTTP 400 with reason: invalid_request and field: products.payment_gateway.terms_of_service_acceptance.device_fingerprint_id. Nothing is recorded.Your integration should: Collect both values before you send, because both are required.
Before you begin: Use Individual B (PAN ABCPD7891B) with everything else sent. See Individual.How to test: Submit, as in #1.Expected result: edd_pending in the response, with 1 requirement: create_video_kyc_link, requirement_type: action. The KYC details are locked.Webhooks: account.product.edd_pending.Your integration should: Show the sub-merchant why a call is needed, and show the link (#5). Do not report the outcome of the call yourself.
Before you begin: Complete #4.How to test:
  1. Run create_video_kyc_link. The link is in the response’s metadata, as in scenario 10 on Actions.
  2. Open the url. The hosted test page shows the outcomes.
  3. Pick Approved.
  4. Fetch the account.
Expected result: The action clears by itself. The product moves to under_review, then activated about 5 sec later.Webhooks: account.requirements.updated, account.product.under_review, then account.product.activated.Your integration should: Open the link inside your product. The link expires and works only for this account.
Before you begin: Use any test business with settlement account 000000000002. Or use Proprietorship A with business_name set to SUNRISE ENTERPRISES_REJECT. See Proprietorship.How to test:
  1. Submit.
  2. Fetch after 5 sec.
Expected result: under_review in the response, then rejected, with requirements empty. No further changes are accepted.Webhooks: account.product.under_review, then account.product.rejected.Your integration should: Tell the sub-merchant the application was not approved, and stop offering changes.
Before you begin: Get an account ready to submit.How to test:
  1. Send settlement account 000000000005. Its verification.status is deferred, error_code is null and bank_account clears.
  2. Submit.
Expected result: under_review in the response. The product stays there for 5 min while a reviewer decides, then moves to activated.Webhooks: account.product.under_review, then account.product.activated.Your integration should: Show under_review as waiting, never as live or failed. No timeout in your code should move the sub-merchant to a failure state.

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 submission 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. Terms The table below lists the gaps in handling the terms: 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 submission:
Last modified on November 18, 2026