Skip to main content
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-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.
No registry or bank sits on the other end, so the value you send decides each check outcome. We match names for real, so take every value from one test business. For example, send PAN 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.com with Merchant Category Code (MCC) 5732.
  • Statement descriptor (statement_descriptor.value): any value.
  • Business-model questions: any option for each question.
To pick another outcome, send one of the outcome accounts as the settlement account instead.

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

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
1Activated end to end Coming soonTest business A, step by step
  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: individual, then the PAN ABCPD1234A at business_profile.authorized_person.identity_numbers.individual_pan.
  4. Confirm the PAN is verified with the name Rzp Test QA Merchant, and ckyc_fetch is due as send_ckyc_otp or skip_ckyc.
  5. Run send_ckyc_otp. Confirm its metadata has a request_id and its requirements list ckyc_otp and ckyc_request_id.
  6. Send any 6 digits other than 000000 as individual_ckyc.otp, with that request ID as individual_ckyc.request_id. Confirm individual_ckyc is verified and no proof of address is due.
  7. If requirements lists registered_address or operational_address, send them under business_profile.addresses. Each is all_of its lines, city, state, postal code and country. Otherwise a CKYC record, DigiLocker or a Goods and Services Tax (GST) record fills them.
  8. Send bank account 1234567890 with IFSC HDFC0123456 under bank_accounts.settlements_primary. Confirm it is verified.
  9. Send the category ecommerce with the subcategory computers_peripheral_equipment_software (MCC 5732) and a description.
  10. Send the website https://curlec.com and a statement descriptor at statement_descriptor.value.
  11. The test category, computers_peripheral_equipment_software, asks no business-model questions. To test them, see scenario 8 on Update an Account.
  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. Confirm the response is activated.
  14. Webhooks received: account.requirements.updated (as the website check settles), account.product.activated.
  15. Status changes: in_progress → activated.
2Create everything at once Coming soonTest business A in one account creation call
  1. Send the one-shot request on Create an Account. It uses the values of test business A.
  2. Confirm 201, with the PAN and the bank account verified and the website in_progress.
  3. Confirm requirements lists ckyc_fetch and accept_terms_of_service.
  4. Run send_ckyc_otp and send the code with its request ID. Answer the questions and accept the terms.
  5. Webhooks received: account.requirements.updated (as the website check settles), account.product.activated.
  6. Status changes: in_progress → activated.
3No CKYC record: video KYC Coming soonTest business B
  1. Run scenario 1 with PAN ABCPD7891B. Confirm ckyc_fetch is not due and proof_of_address_for_individual is.
  2. Send AADHAARCKYCCOMPLETE.jpg as both aadhaar_front and aadhaar_back in one update. poa_via_aadhaar_documents is an all_of pair, so the composite clears.
  3. Accept the terms. Confirm the response is edd_pending, with create_video_kyc_link due as an action.
  4. Run create_video_kyc_link. The link is in its response metadata, and the action stays due.
  5. Open the url and pick Approved.
  6. Fetch the account after 5 sec. Confirm activated.
  7. Webhooks received: account.requirements.updated (as the website check settles), account.product.edd_pending, account.requirements.updated, account.product.under_review, account.product.activated.
  8. Status changes: in_progress → edd_pending → under_review → activated.

3.2 Other Common Scenarios

The table below lists the other common scenarios:
#ScenarioTriggerWhat to confirm
4Fetch to follow the status (also on every business type) Coming soonSettlement account 000000000002
  1. Submit the account. Confirm the response is under_review.
  2. Poll GET /v1/accounts/{account_id} every 2 sec, for up to 60 sec.
  3. Confirm rejected arrives about 5 sec later, and that your code never treats under_review as final.
  4. Webhooks received: account.requirements.updated (as the website check settles), account.product.under_review, account.product.rejected.
  5. Status changes: under_review → rejected.
5Rejected (also on every business type) Coming soonSettlement account 000000000002
  1. Run scenario 1 with this settlement account.
  2. Confirm the response is under_review, then fetch the account after 5 sec. Confirm rejected.
  3. Confirm that later updates return 409 field_locked.
  4. Webhooks received: account.requirements.updated (as the website check settles), account.product.under_review, account.product.rejected.
  5. Status changes: under_review → rejected.
6The PAN card instead of the number Coming soonPERSONALPANFRONT.jpg
  1. Upload the file with type: individual_pan_document. See Documents.
  2. Attach its id at business_profile.authorized_person.documents.individual_pan_document.
  3. Confirm the card is verified and individual_pan cleared.
  4. Webhooks received: none.
  5. Status changes: none. The product stays in_progress.
7Wrong codes 3 times Coming soonA wrong phone code, sent 3 times
  1. Send a wrong phone_otp 3 times.
  2. Confirm send_phone_otp is due again as an action.
  3. Run it again and send the new code.
  4. Webhooks received: none.
  5. Status changes: none.

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:
#ScenarioTriggerError objectWhat to confirm
8PAN: the PAN is invalid Coming soonABCPD1234Kverification.status: rejected
verification.error_code: pan_not_found
At: …authorized_person.identity_numbers.individual_pan
Due again: …authorized_person.identity_numbers.individual_pan, …authorized_person.documents.individual_pan_document
Composite requirement: individual_pan
  1. Send the value where it is due. Confirm the response is a 200.
  2. Webhooks received: none, because the response carries the failure.
  3. Status changes: none. The product stays in_progress.
9PAN: no record exists for the PAN Coming soonABCPD1234Cverification.status: rejected
verification.error_code: pan_not_found
At: …authorized_person.identity_numbers.individual_pan
Due again: …authorized_person.identity_numbers.individual_pan, …authorized_person.documents.individual_pan_document
Composite requirement: individual_pan
  1. Send the value where it is due. Confirm the response is a 200.
  2. Webhooks received: none, because the response carries the failure.
  3. Status changes: none. The product stays in_progress.
10PAN: the registry errored, but the PAN is fine Coming soonABCPD1234Dverification.status: rejected
verification.error_code: pan_check_unavailable
At: …authorized_person.identity_numbers.individual_pan
Due again: …authorized_person.identity_numbers.individual_pan, …authorized_person.documents.individual_pan_document
Composite requirement: individual_pan
  1. Send the value where it is due. Confirm the response is a 200.
  2. Webhooks received: none, because the response carries the failure.
  3. Status changes: none. The product stays in_progress.
11PAN: the PAN holder is under 18 Coming soonABCPD1234Mverification.status: rejected
verification.error_code: promoter_underage
At: …authorized_person.identity_numbers.individual_pan
  1. Send the value where it is due. Confirm the response is a 200.
  2. Webhooks received: none, because the response carries the failure.
  3. Status changes: none. The product stays in_progress.
Documents The file was unreadable, or did not match what was sent. Ask for the right file. The table below lists the document scenarios:
#ScenarioTriggerError objectWhat to confirm
12PAN card: the card reads ABCPD1234Z, not the PAN sent Coming soonPERSONALPANMISMATCHFRONT.jpgverification.status: rejected
verification.error_code: pan_card_mismatch
At: …authorized_person.documents.individual_pan_document
Due again: …authorized_person.documents.individual_pan_document
  1. Upload the file with its type and attach its id where it is due.
  2. Confirm the response is a 200.
  3. Webhooks received: none, because the response carries the failure.
  4. Status changes: none. The product stays in_progress.
13PAN card: the card carries another name Coming soonPERSONALPANNAMEMISMATCHFRONT.jpgverification.status: rejected
verification.error_code: pan_card_name_mismatch
At: …authorized_person.documents.individual_pan_document
Due again: …authorized_person.documents.individual_pan_document
  1. Upload the file with its type and attach its id where it is due.
  2. Confirm the response is a 200.
  3. Webhooks received: none, because the response carries the failure.
  4. Status changes: none. The product stays in_progress.
14PAN card: no name or number is readable on the card Coming soonPERSONALPANUNREADABLEFRONT.jpgverification.status: rejected
verification.error_code: pan_card_name_unreadable
At: …authorized_person.documents.individual_pan_document
Due again: …authorized_person.documents.individual_pan_document
  1. Upload the file with its type and attach its id where it is due.
  2. Confirm the response is a 200.
  3. Webhooks received: none, because the response carries the failure.
  4. Status changes: none. The product stays in_progress.
15PAN card: the file is not a PAN card Coming soonWRONGFRONT.jpgverification.status: rejected
verification.error_code: not_a_pan_card
At: …authorized_person.documents.individual_pan_document
Due again: …authorized_person.documents.individual_pan_document
  1. Upload the file with its type and attach its id where it is due.
  2. Confirm the response is a 200.
  3. Webhooks received: none, because the response carries the failure.
  4. Status changes: none. The product stays in_progress.
16Proof of address: the Aadhaar is in another name Coming soonAADHARMISMATCHFRONT.jpgverification.status: rejected
verification.error_code: poa_name_mismatch
At: …authorized_person.documents.aadhaar_front
Due 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_back
Composite requirement: proof_of_address_for_individual
  1. Upload the file with its type and attach its id where it is due.
  2. Confirm the response is a 200.
  3. Webhooks received: none, because the response carries the failure.
  4. Status changes: none. The product stays in_progress.
17Proof of address: the Aadhaar is unreadable Coming soonAADHAARUNREADABLEFRONT.jpgverification.status: rejected
verification.error_code: poa_unreadable
At: …authorized_person.documents.aadhaar_front
Due 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_back
Composite requirement: proof_of_address_for_individual
  1. Upload the file with its type and attach its id where it is due.
  2. Confirm the response is a 200.
  3. Webhooks received: none, because the response carries the failure.
  4. Status changes: none. The product stays in_progress.
CKYC The CKYC record did not come through. After a wrong code, 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:
#ScenarioTriggerError objectWhat to confirm
18CKYC record: the record cannot be downloaded Coming soonPAN ABCPD1234X, then any code other than 000000verification.status: rejected
verification.error_code: ckyc_unavailable
At: …authorized_person.identity_numbers.individual_ckyc
Due 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_back
Composite requirement: proof_of_address_for_individual
  1. Send the PAN, run send_ckyc_otp and send the code shown.
  2. Confirm the response is a 200.
  3. Webhooks received: none, because the response carries the failure.
  4. Status changes: none. The product stays in_progress.
19CKYC code: the code has expired Coming soonPAN AICPD1234U, then any code other than 000000verification.status: rejected
verification.error_code: otp_expired
At: …authorized_person.identity_numbers.individual_ckyc
Due again: send_ckyc_otp, …authorized_person.identity_numbers.individual_ckyc.is_skipped
Composite requirement: ckyc_fetch
  1. Send the PAN, run send_ckyc_otp and send the code shown.
  2. Confirm the response is a 200.
  3. Webhooks received: none, because the response carries the failure.
  4. Status changes: none. The product stays in_progress.
20CKYC code: the code does not match the one sent Coming soonPAN ABCPD1234A, then code 000000verification.status: rejected
verification.error_code: otp_invalid
At: …authorized_person.identity_numbers.individual_ckyc
Due again: …authorized_person.identity_numbers.individual_ckyc.otp, …authorized_person.identity_numbers.individual_ckyc.request_id
  1. Send the PAN, run send_ckyc_otp and send the code shown.
  2. Confirm the response is a 200.
  3. Webhooks received: none, because the response carries the failure.
  4. Status changes: none. The product stays in_progress.
Bank The bank check failed. 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:
#ScenarioTriggerError objectWhat to confirm
21Bank account: the holder name does not match Coming soon2100000011verification.status: rejected
verification.error_code: bank_name_mismatch
At: bank_accounts.settlements_primary
Due again: bank_accounts.settlements_primary, create_upi_link
Composite requirement: bank_account
  1. Send the value where it is due. Confirm the response is a 200.
  2. Webhooks received: none, because the response carries the failure.
  3. Status changes: none. The product stays in_progress.
22Bank account: the holder name is close but under the match threshold Coming soon2100000012verification.status: rejected
verification.error_code: bank_name_mismatch
At: bank_accounts.settlements_primary
Due again: bank_accounts.settlements_primary, create_upi_link
Composite requirement: bank_account
  1. Send the value where it is due. Confirm the response is a 200.
  2. Webhooks received: none, because the response carries the failure.
  3. Status changes: none. The product stays in_progress.
23Bank account: the IFSC is invalid Coming soon2100000040verification.status: rejected
verification.error_code: bank_details_incorrect
At: bank_accounts.settlements_primary
Due again: bank_accounts.settlements_primary, create_upi_link
Composite requirement: bank_account
  1. Send the value where it is due. Confirm the response is a 200.
  2. Webhooks received: none, because the response carries the failure.
  3. Status changes: none. The product stays in_progress.
24Bank account: the account is closed Coming soon1234567892verification.status: rejected
verification.error_code: bank_account_unusable
At: bank_accounts.settlements_primary
Due again: bank_accounts.settlements_primary, create_upi_link
Composite requirement: bank_account
  1. Send the value where it is due. Confirm the response is a 200.
  2. Webhooks received: none, because the response carries the failure.
  3. Status changes: none. The product stays in_progress.
25Bank account: the account is frozen Coming soon2100000005verification.status: rejected
verification.error_code: bank_account_unusable
At: bank_accounts.settlements_primary
Due again: bank_accounts.settlements_primary, create_upi_link
Composite requirement: bank_account
  1. Send the value where it is due. Confirm the response is a 200.
  2. Webhooks received: none, because the response carries the failure.
  3. Status changes: none. The product stays in_progress.
26Bank account: a Non-Resident External (NRE) account cannot receive settlements Coming soon2100000006verification.status: rejected
verification.error_code: bank_account_unusable
At: bank_accounts.settlements_primary
Due again: bank_accounts.settlements_primary, create_upi_link
Composite requirement: bank_account
  1. Send the value where it is due. Confirm the response is a 200.
  2. Webhooks received: none, because the response carries the failure.
  3. Status changes: none. The product stays in_progress.
27Bank account: the bank was unreachable, but the account is fine Coming soon2100000039verification.status: rejected
verification.error_code: bank_check_unavailable
At: bank_accounts.settlements_primary
Due again: bank_accounts.settlements_primary, create_upi_link
Composite requirement: bank_account
  1. Send the value where it is due. Confirm the response is a 200.
  2. Webhooks received: none, because the response carries the failure.
  3. Status changes: none. The product stays in_progress.
28Bank account: the bank declined without a reason Coming soon2100000031verification.status: rejected
verification.error_code: bank_not_verified
At: bank_accounts.settlements_primary
Due again: bank_accounts.settlements_primary, create_upi_link
Composite requirement: bank_account
  1. Send the value where it is due. Confirm the response is a 200.
  2. Webhooks received: none, because the response carries the failure.
  3. Status changes: none. The product stays in_progress.
Website The website check runs after the response, so the failure shows on the next fetch. Send the website again, or another one. The table below lists the website scenario:
#ScenarioTriggerError objectWhat to confirm
29Website: the check fails a few seconds after the response Coming soonhttps://www.kc-not-found.comverification.status: rejected
verification.error_code: website_unreachable
At: …website.primary
Due again: …website.primary
  1. Send the website where it is due, and fetch the account after 5 sec.
  2. Webhooks received: account.requirements.updated.
  3. Status changes: none. The product stays in_progress.
Video KYC The call did not verify the person. The action is due again, so let the sub-merchant start a new call. The table below lists the video KYC scenario:
#ScenarioTriggerError objectWhat to confirm
30Video KYC not approved (also on every business type) Coming soonThe hosted page’s Unable to verify, or RejectedStill due: create_video_kyc_link
requirement_type: action
  1. Submit a test business without a CKYC record, run create_video_kyc_link and open the url.
  2. Pick Unable to verify.
  3. Fetch the account. Confirm create_video_kyc_link is still due, and run it again for a new call.
  4. Pick Rejected on a new link instead. Confirm the product ends rejected.
  5. Webhooks received: none for Unable to verify, because the requirements do not change. For Rejected, account.product.under_review then account.product.rejected.
  6. Status changes: the product stays edd_pending, or moves under_review → rejected.
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
31Business name for an individual Livebusiness_name in an updateHTTP 400
error.reason: invalid_request
error.field: business_profile.business_name
  1. Send the update.
  2. Confirm 400, because an individual’s name comes from the PAN.
  3. Webhooks received: none.
  4. Status changes: none.
Every failure code, with its test value, is in the Error Index. 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:
#ScenarioTriggerWhat to confirm
32Needs clarification (also on every business type) Coming soonSettlement account 000000000003
  1. Run scenario 1 with this settlement account, and submit.
  2. Fetch the account after 5 sec. Confirm needs_clarification, with only bank_account due.
  3. Answer the point. When submit_clarification is due, send submit_clarification: true in its own call. See Needs Clarification.
  4. Webhooks received: account.requirements.updated (as the website check settles), account.product.under_review, account.product.needs_clarification, account.product.under_review, account.product.activated.
  5. Status changes: under_review → needs_clarification → under_review → activated.
33Held in review (also on every business type) Coming soonSettlement account 000000000005
  1. Send the account. Confirm its verification is deferred and bank_account clears.
  2. Submit. Confirm the response is under_review.
  3. Confirm it stays under_review for 5 min, then becomes activated.
  4. Assert that no timeout in your code moves the sub-merchant to a failure state.
  5. Webhooks received: account.requirements.updated (as the website check settles), account.product.under_review, account.product.activated.
  6. Status changes: under_review → activated.
34Suspended after activation (also on every business type) Coming soonSettlement account 000000000006
  1. Run scenario 1 with this settlement account. Confirm the response is activated.
  2. About 60 sec later, confirm suspended, with status_reason.code: website_review_failed and the website due again.
  3. Stop payments, show the reason and ask for what is listed.
  4. Send https://curlec.com. Confirm the product is activated again.
  5. Webhooks received: account.requirements.updated (as the website check settles), account.product.activated, account.product.suspended. After the website, account.requirements.updated and account.product.activated.
  6. Status changes: activated → suspended → activated.
35A link expires before the sub-merchant finishes it (also on every business type) Coming soonThe hosted page’s Expire the link
  1. Run any link action (video KYC, DigiLocker or ₹1 UPI) and open its url.
  2. Pick Expire the link.
  3. Fetch the account. Confirm the action is still due.
  4. Show a fresh Start again that runs the action again for a new link. Never reuse an expired url.
  5. Webhooks received: none, because the requirements do not change.
  6. Status changes: none.
36DigiLocker for the proof of address Coming soonThe hosted page’s Share Aadhaar, then Decline
  1. With proof_of_address_for_individual due, run create_aadhaar_digilocker_link with your return_url. Open the url in its response.
  2. Pick Share Aadhaar. Confirm proof_of_address_for_individual clears and the page returns to your return_url.
  3. On another account, pick Decline. Confirm proof_of_address_for_individual stays due, with the action and the document uploads.
  4. Run the action again, or upload a document.
  5. Webhooks received: account.requirements.updated when the Aadhaar is shared. None after Decline.
  6. Status changes: none.
37₹1 UPI check of the bank account (also on every business type) Coming soonThe hosted page’s Pay ₹1, then Pay from another person’s account
  1. With bank_account due after a failed bank check, run create_upi_link. Open the url in its response.
  2. Pick Pay ₹1. Confirm bank_account clears and the account is verified.
  3. On another account, pick Pay from another person’s account. Confirm bank_account stays due.
  4. Run the action again, or send the account.
  5. Webhooks received: account.requirements.updated when the payment verifies the account. None after a failed payment.
  6. Status changes: none.
38Access withdrawn (also on every business type) Coming soonSettlement account 000000000007
  1. Run scenario 1 with this settlement account.
  2. About 60 sec after activation, confirm account.consent.withdrawn arrives.
  3. Stop calling the API for the account. Confirm later calls return 403 consent_withdrawn.
  4. Webhooks received: account.requirements.updated (as the website check settles), account.product.activated, account.consent.withdrawn.
  5. Status changes: none after activated.

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:

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