> ## Documentation Index
> Fetch the complete documentation index at: https://razorpay.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Update Account Tests

> Test account updates on Onboarding APIs in Test Mode, including verification failure and field lock scenarios.

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](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration) for test credentials and headers.

## 1. Test Mode Coverage

### Test Mode Differences

The table below lists how updates behave in each mode:

| Behaviour | Live mode | Test mode |
| - | - | - |
| Checks on each value | Registries and banks check each value. | The value decides each outcome, from the [Test Values](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/test-values.md). |
| Codes | Real codes go to the user's phone and email, and to the mobile on the Central KYC Records Registry (CKYC) record. | No code reaches anyone. `000007` verifies the phone and email. Any 6 digits other than `000000` verify the CKYC code, and `000000` is a wrong code. |
| Failed checks | HTTP 200, with `rejected`, a `verification.error_code` and the requirement due again. | The same HTTP 200, with the same codes and descriptions. |
| The website check | The scan can take longer. Fetch the account, do not wait. | The check settles a few seconds after the response. |
| Ordering and locks | `step_not_due`, and `field_locked` after submission and on verified values. | The same rules as live mode. |
| Needs clarification | A reviewer flags points after submission. | Settlement account `000000000003` raises a clarification. See [Needs Clarification](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/needs-clarification.md). |

### What You Can Test

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

| Area | What to test | In test mode |
| - | - | - |
| Send what is due | Codes, PAN, CKYC code, bank account, category, website and statement descriptor | Available |
| Codes | Right and wrong `phone_otp` and `email_otp` codes, and right and wrong CKYC codes | Available |
| Failed checks | `rejected` with a `verification.error_code`, and the requirement due again | Available |
| The website check | A check that settles after the response | Available |
| Ordering and locks | `step_not_due`, and `field_locked` after submission and on verified values | Available |
| Needs clarification | `products.payment_gateway.clarification_responses` and `submit_clarification` | Available |

### Endpoint Coverage in Test Mode

The table below lists the endpoints this page uses:

| API | Endpoint | Available in test mode |
| - | - | - |
| [Update an Account](https://razorpay.com/docs/api/partners/accounts/update.md) | `PATCH /v1/accounts/{account_id}` | Available |
| [Run an Action](https://razorpay.com/docs/api/partners/accounts/run-action.md) | `POST /v1/accounts/{account_id}/actions/{action}` | Available |
| [Fetch Accounts](https://razorpay.com/docs/api/partners/accounts/fetch.md) | `GET /v1/accounts/{account_id}` | Available |

## 2. Before You Begin

Prepare the following before you run the scenarios:

* Create an account, as in scenario 1 on [Create an Account](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/create-account.md).
* 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.

```bash Curl theme={null}
curl -X PATCH https://api.razorpay.com/v1/accounts/acc_TcdGEzmfKQzEl1 \
-u rzp_test_partner_[CLIENT_ID]:[CLIENT_SECRET] \
-H "Content-Type: application/json" \
-H "X-Idempotency-Key: [UNIQUE_KEY]" \
-d '{
  "business_profile": {
    "business_type": "individual",
    "authorized_person": {
      "identity_numbers": {
        "individual_pan": {
          "value": "ABCPD1234A"
        }
      }
    }
  }
}'
```

Know more about the [request parameters](https://razorpay.com/docs/api/partners/accounts/update.md).

### Sample Response

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

> [accordion] Response: HTTP 200
>
> ```json Response theme={null}
> {
>   "id": "acc_TcdGEzmfKQzEl1",
>   "country": "IN",
>   "statement_descriptor": null,
>   "is_mfa_enabled": false,
>   "user": {
>     "role": "owner",
>     "email": "test.owner@example.com",
>     "phone": "+919876543210",
>     "name": "Rzp Test QA Merchant",
>     "is_email_verified": true,
>     "is_phone_verified": true
>   },
>   "business_profile": {
>     "business_type": "individual",
>     "business_name": "Rzp Test QA Merchant",
>     "date_of_establishment": null,
>     "identity_numbers": {},
>     "documents": {},
>     "business_category": null,
>     "authorized_person": {
>       "name": "Rzp Test QA Merchant",
>       "identity_numbers": {
>         "individual_pan": {
>           "type": "individual_pan",
>           "value": "ABCPD1234A",
>           "verification": {
>             "status": "verified",
>             "error_code": null,
>             "error_description": null,
>             "verified_at": 1793164860,
>             "metadata": {},
>             "created_at": 1793164858
>           },
>           "metadata": {},
>           "is_skipped": false,
>           "created_at": 1793164858,
>           "updated_at": 1793164860
>         }
>       },
>       "documents": {},
>       "address": null,
>       "date_of_birth": null,
>       "additional_data": {},
>       "created_at": 1793164858,
>       "updated_at": 1793164860
>     },
>     "stakeholders": {},
>     "addresses": [],
>     "metadata": {}
>   },
>   "bank_accounts": {},
>   "products": {
>     "payment_gateway": {
>       "type": "payment_gateway",
>       "status": "in_progress",
>       "status_reason": null,
>       "created_at": 1793164800,
>       "updated_at": 1793164860,
>       "requirements": [
>         {
>           "id": "req_hocykxcAkjCdtB",
>           "requirement_code": "ckyc_fetch",
>           "requirement_level": "mandatory",
>           "requirement_type": "composite",
>           "description": "The person's CKYC record, fetched with a code or skipped.",
>           "fulfillment_criteria": "one_of",
>           "sub_requirements": [
>             {
>               "id": "req_2KRiIGIhuAPNW6",
>               "requirement_code": "skip_ckyc",
>               "requirement_level": "conditional",
>               "requirement_type": "input",
>               "description": "Skip CKYC.",
>               "field_path": "business_profile.authorized_person.identity_numbers.individual_ckyc.is_skipped",
>               "value_type": "boolean",
>               "status": "created"
>             },
>             {
>               "id": "req_L3rskP8gX6YVHh",
>               "requirement_code": "send_ckyc_otp",
>               "requirement_level": "conditional",
>               "requirement_type": "action",
>               "description": "A Central KYC record was found for your PAN. Get a code on the mobile on your CKYC record to fetch it.",
>               "status": "created"
>             }
>           ],
>           "status": "created"
>         },
>         {
>           "id": "req_VgRHb7QJNtMyj2",
>           "requirement_code": "settlement_bank_account",
>           "requirement_level": "mandatory",
>           "requirement_type": "composite",
>           "description": "The bank account that receives settlements, in the name on your PAN.",
>           "fulfillment_criteria": "all_of",
>           "sub_requirements": [
>             {
>               "id": "req_4rY5OIDnOHtA2z",
>               "requirement_code": "bank_account_number",
>               "requirement_level": "mandatory",
>               "requirement_type": "input",
>               "description": "The account number.",
>               "field_path": "bank_accounts.settlements_primary.account_number",
>               "value_type": "text",
>               "status": "created"
>             },
>             {
>               "id": "req_mOTextgE1uJfFK",
>               "requirement_code": "bank_routing_code",
>               "requirement_level": "mandatory",
>               "requirement_type": "input",
>               "description": "The bank's IFSC.",
>               "field_path": "bank_accounts.settlements_primary.routing_code",
>               "value_type": "text",
>               "status": "created"
>             },
>             {
>               "id": "req_GNDdQcckulAU4g",
>               "requirement_code": "bank_routing_code_type",
>               "requirement_level": "mandatory",
>               "requirement_type": "input",
>               "description": "The kind of routing code.",
>               "field_path": "bank_accounts.settlements_primary.routing_code_type",
>               "value_type": "enum",
>               "options": [
>                 {
>                   "label": "IFSC",
>                   "value": "IFSC"
>                 }
>               ],
>               "status": "created"
>             }
>           ],
>           "status": "created"
>         },
>         {
>           "id": "req_A0YsNfe8Ldgifp",
>           "requirement_code": "payment_channels",
>           "requirement_level": "optional",
>           "requirement_type": "composite",
>           "description": "Where you take payments: a website, an Android app or an iOS app. Any one is enough.",
>           "fulfillment_criteria": "one_of",
>           "sub_requirements": [
>             {
>               "id": "req_N0fo3L9LVzHpZQ",
>               "requirement_code": "website_url",
>               "requirement_level": "conditional",
>               "requirement_type": "input",
>               "description": "Your website's address.",
>               "field_path": "products.payment_gateway.payment_channels.website.primary",
>               "value_type": "text",
>               "status": "created"
>             },
>             {
>               "id": "req_LaWQWFJKitHAow",
>               "requirement_code": "app_android_url",
>               "requirement_level": "conditional",
>               "requirement_type": "input",
>               "description": "Your Android app's link.",
>               "field_path": "products.payment_gateway.payment_channels.app_android.url",
>               "value_type": "text",
>               "status": "created"
>             },
>             {
>               "id": "req_y4V5UfDpr3azhi",
>               "requirement_code": "app_ios_url",
>               "requirement_level": "conditional",
>               "requirement_type": "input",
>               "description": "Your iOS app's link.",
>               "field_path": "products.payment_gateway.payment_channels.app_ios.url",
>               "value_type": "text",
>               "status": "created"
>             }
>           ],
>           "status": "created"
>         },
>         {
>           "id": "req_7zAE2YmS5MDUhG",
>           "requirement_code": "business_category",
>           "requirement_level": "mandatory",
>           "requirement_type": "input",
>           "description": "Select your business category, and send its subcategory with it.",
>           "field_path": "business_profile.business_category.category",
>           "value_type": "enum",
>           "options": [
>             {
>               "label": "Ecommerce",
>               "value": "ecommerce"
>             },
>             {
>               "label": "Food and beverage",
>               "value": "food"
>             }
>           ],
>           "status": "created"
>         },
>         {
>           "id": "req_bNeyy5msL1HUKX",
>           "requirement_code": "business_description",
>           "requirement_level": "mandatory",
>           "requirement_type": "input",
>           "description": "What your business sells, in under 100 characters.",
>           "field_path": "business_profile.business_category.business_description",
>           "value_type": "text",
>           "status": "created"
>         },
>         {
>           "id": "req_yD8JfNtIoWXmu4",
>           "requirement_code": "statement_descriptor",
>           "requirement_level": "mandatory",
>           "requirement_type": "input",
>           "description": "The name shown on customers' receipts and statements.",
>           "field_path": "statement_descriptor.value",
>           "value_type": "text",
>           "status": "created"
>         },
>         {
>           "id": "req_0HAQYzBrDRNnEM",
>           "requirement_code": "accept_terms_of_service",
>           "requirement_level": "mandatory",
>           "requirement_type": "composite",
>           "description": "Show the sub-merchant Razorpay's terms of service and record their acceptance.",
>           "fulfillment_criteria": "all_of",
>           "sub_requirements": [
>             {
>               "id": "req_CTW6xxsQmygIDU",
>               "requirement_code": "acceptance_ip",
>               "requirement_level": "mandatory",
>               "requirement_type": "input",
>               "description": "The IP address the terms were accepted from.",
>               "field_path": "products.payment_gateway.terms_of_service_acceptance.ip",
>               "value_type": "text",
>               "status": "created"
>             },
>             {
>               "id": "req_gXg6igx2STKrZA",
>               "requirement_code": "acceptance_device_fingerprint_id",
>               "requirement_level": "mandatory",
>               "requirement_type": "input",
>               "description": "The device fingerprint of the device the terms were accepted on.",
>               "field_path": "products.payment_gateway.terms_of_service_acceptance.device_fingerprint_id",
>               "value_type": "text",
>               "status": "created"
>             }
>           ],
>           "status": "created"
>         }
>       ],
>       "terms_of_service_acceptance": null,
>       "payment_channels": null
>     }
>   },
>   "notes": {
>     "shop_id": "60291847"
>   },
>   "created_at": 1793164800,
>   "updated_at": 1793164860
> }
> ```

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

<table>
  <colgroup>
    <col width="6%" />

    <col width="22%" />

    <col width="24%" />

    <col width="48%" />
  </colgroup>

  <thead><tr><th>#</th><th>Scenario</th><th>Trigger</th><th>What to confirm</th></tr></thead>

  <tbody>
    <tr><td>1</td><td>Send the business type Live</td><td>`individual`</td><td>Send it. Confirm the requirements change to those of an individual.</td></tr>
    <tr><td>2</td><td>Verify the phone and email Coming soon</td><td>`000007`</td><td>Run `send_phone_otp` and `send_email_otp`, as on [Actions](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/actions.md). Each response lists the code to send. Send `phone_otp` and `email_otp`. Confirm both contacts are verified.</td></tr>
    <tr><td>3</td><td>A wrong code Coming soon</td><td>`123456`</td><td>Send it as `phone_otp`. Confirm HTTP 200, and that `phone_otp` is still due.</td></tr>
    <tr><td>4</td><td>PAN verified Coming soon</td><td>`ABCPD1234A`</td><td>Send the PAN, as in the [sample request](#sample-request). Confirm `verified`, the name and `ckyc_fetch` due.</td></tr>
    <tr><td>5</td><td>The CKYC code Coming soon</td><td>Any 6 digits other than `000000`</td><td>Run `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](#3-2-scenario-details). Confirm `individual_ckyc` is verified with `value: null`, and no proof of address is due.</td></tr>
    <tr><td>6</td><td>Bank account verified Coming soon</td><td>`1234567890` with `HDFC0123456`</td><td>Send it under `bank_accounts.settlements_primary`. Confirm `verified`, and the account number returned in full.</td></tr>
    <tr><td>7</td><td>Bank name mismatch Coming soon</td><td>`2100000011`</td><td>Send it. Confirm `verification.status: rejected` with `error_code: bank_name_mismatch`, and `bank_account` due again. Send `1234567890` to clear it.</td></tr>
    <tr><td>8</td><td>Category and business-model questions Coming soon</td><td>Subcategory `fashion_and_lifestyle`</td><td>Send 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](https://razorpay.com/docs/api/partners/accounts/business-model-questions.md).</td></tr>
    <tr><td>9</td><td>A check that settles later Coming soon</td><td>`https://curlec.com`</td><td>Send it. Confirm `in_progress`, then `verified` on a fetch. Confirm Razorpay sends `account.requirements.updated` when the check settles.</td></tr>
    <tr><td>10</td><td>Name on statements Live</td><td>A name, such as `Rzp Test Store`</td><td>Send it as `statement_descriptor.value`.</td></tr>
    <tr><td>11</td><td>A value before it is due Live</td><td>A bank account before the business type</td><td>Confirm `400 step_not_due` with `metadata.due`.</td></tr>
    <tr><td>12</td><td>A read-only or unknown key Coming soon</td><td>`bank_accounts.settlements_primary.verification` or `"bussiness_profile"`</td><td>Confirm `400 invalid_request`.</td></tr>
    <tr><td>13</td><td>A code in the wrong format Live</td><td>`12345`</td><td>Confirm `400 invalid_format`. A wrong 6-digit code returns HTTP 200 instead (#3).</td></tr>
    <tr><td>14</td><td>A document ID that is not this account's Live</td><td>A `file_` ID from another account, or a deleted one</td><td>Confirm `404 not_found` with the path of the document.</td></tr>
    <tr><td>15</td><td>Change KYC after submission Coming soon</td><td>A new bank account while `edd_pending`</td><td>Submit an account without a CKYC record, as in scenario 4 on [Terms and Submission](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/terms-and-submission.md). Send a bank account. Confirm `409 field_locked` with `metadata.status: edd_pending`.</td></tr>
    <tr><td>16</td><td>Change a verified value Coming soon</td><td>`business_type` after the PAN verifies, or a verified phone</td><td>Confirm `409 field_locked`.</td></tr>
    <tr><td>17</td><td>Empty body Live</td><td>`{}`</td><td>Confirm `400 invalid_request`.</td></tr>
    <tr><td>18</td><td>Retry an update Live</td><td>The same key and body</td><td>Confirm the same response, and that the value applied once.</td></tr>
    <tr><td>19</td><td>Answer a reviewer Coming soon</td><td>A product in `needs_clarification` (settlement account `000000000003`)</td><td>Follow [Needs Clarification](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/needs-clarification.md). Confirm only the flagged points can change.</td></tr>
    <tr><td>20</td><td>Change the bank account after activation Coming soon</td><td>An activated account, then settlement account `000000000001`</td><td>Send 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.</td></tr>
  </tbody>
</table>

### 3.2 Scenario Details

The details below expand the scenarios that need more than one step:

> [accordion] 2. Verify the Phone and Email
>
> **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:
>
> ```json theme={null}
> {
>   "phone_otp": "000007",
>   "email_otp": "000007"
> }
> ```
>
> **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.

> [accordion] 3. A Wrong Code
>
> **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.

> [accordion] 4. PAN Verified
>
> **How to test:** Send the [sample request](#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.

> [accordion] 5. The CKYC Code
>
> **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](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/actions.md). Its `metadata` has the `request_id`.
> 2. Send the code as `otp` and the request ID as `request_id`, both on `individual_ckyc`:
>
> ```json theme={null}
> {
>   "business_profile": {
>     "authorized_person": {
>       "identity_numbers": {
>         "individual_ckyc": {
>           "otp": "123456",
>           "request_id": "CKYCREQ20261115000123"
>         }
>       }
>     }
>   }
> }
> ```
>
> **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.

> [accordion] 7. Bank Name Mismatch
>
> **How to test:** Send the bank account:
>
> ```json theme={null}
> {
>   "bank_accounts": {
>     "settlements_primary": {
>       "account_number": "2100000011",
>       "routing_code": "HDFC0123456",
>       "routing_code_type": "IFSC"
>     }
>   }
> }
> ```
>
> **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](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/fetch-account.md).
>
> **Your integration should:** Show its sub-requirements as 1 choice. Send `1234567890` to clear it in test mode.

> [accordion] 11. A Value Before It Is Due
>
> **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.

> [accordion] 15. Change KYC After Submission
>
> **Before you begin:** Get an account to `edd_pending`, as in scenario 4 on [Terms and Submission](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/terms-and-submission.md).
>
> **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](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration) lists the errors every operation shares.

The table below lists the errors this endpoint returns:

| Trigger | HTTP | `error.reason` | `error.field` |
| - | - | - | - |
| An empty body, `business_name` for an individual or a read-only key such as `verification` | 400 | `invalid_request` | The key |
| A code of 5 digits, or a bad Indian Financial System Code (IFSC), PIN code or date | 400 | `invalid_format` | The key |
| A business-model answer that is not an option, or a document key that is not a type | 400 | `invalid_option` | The key |
| A bank account before the business type, or `phone_otp` for a verified phone | 400 | `step_not_due` | The key, with `metadata.due` |
| A document `url` that cannot be fetched | 400 | `invalid_document_url` | The path of the document |
| A document `id` that is not this account's | 404 | `not_found` | The path of the document |
| KYC changes while `under_review` or `edd_pending`, or `business_type` after the PAN verifies | 409 | `field_locked` | The key, with `metadata.status` |

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

| Gap | What goes wrong in production | What to do | Test with |
| - | - | - | - |
| Sending everything you have in every update | Values not yet due fail with `step_not_due`, and the order matters. | Send what is due. Values earlier in the body are saved. | #11 |
| Treating a wrong code as an error | You show a generic failure and the sub-merchant cannot retry. | Treat a wrong code as HTTP 200, with the code still due. | #3 |
| A new value for every failure | A sub-merchant with a name mismatch is asked only for a new account, though a ₹1 UPI payment would do. | Offer every sub-requirement of the `one_of`. | #7 |

**After submission**

The table below lists the gaps after submission:

| Gap | What goes wrong in production | What to do | Test with |
| - | - | - | - |
| Editable KYC after submission | The sub-merchant edits a field and the call fails with HTTP 409. They think the change was saved. | Lock the fields in your UI by status. | #15 |

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

| Topic | What to know | On this page | Test it | Read more |
| - | - | - | - | - |
| One input, one value | Send each input's value at its `field_path`. The inputs of an `all_of` can go in 1 update, such as the bank account's number, IFSC and routing code type. | The bank account goes under `settlements_primary`. | #6 | [Collect Requirements](https://razorpay.com/docs/partners/aggregators/onboarding-api/collect-requirements.md) |
| 3-second answer | Each update answers within 3 sec. A slow check is `in_progress`, so fetch it later. | The website settles later. | #9, and #3 on [Fetch an Account](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/fetch-account.md) | [Fetch an Account](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/fetch-account.md) |
| Concurrent updates | 2 updates to 1 account apply one at a time, in arrival order. Do not rely on the order of parallel calls. | Send 1 update at a time per account. | Not applicable | Not applicable |

### Related Information

* [Test Your Integration](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration)
* [Create an Account](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/create-account.md)
* [Fetch an Account](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/fetch-account.md)
* [Actions](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/actions.md)
* [Documents](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/documents.md)
* [Terms and Submission](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/terms-and-submission.md)
* [Needs Clarification](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/needs-clarification.md)
* [Webhooks](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/webhooks.md)
* [Test Values](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/test-values.md)
* [Error Index](https://razorpay.com/docs/partners/aggregators/onboarding-api/test-integration/error-index.md)
