Process Flow & Field Reference
Prepared from the supplied Individual workflow configuration. This document describes the configured journey at a functional level; conditional visibility and validation rules are summarized where they are defined in the file.
1. Journey Overview
- Applicant enters and verifies mobile number through OTP.
- Applicant enters and verifies email address; Google sign-in and branch/reference details are available.
- Applicant selects trading segments and applicable tariff/DP plan details.
- PAN and date of birth are captured, with an option to fetch KRA details.
- KRA details are reviewed; Aadhaar/DigiLocker and PAN verification/document steps are conditionally used.
- Applicant completes personal, account, nominee and nominee-percentage details.
- Applicant verifies the nominee contact mobile number through OTP.
- Applicant enters bank details and uploads supporting documents as required.
- Applicant uploads signature and completes live image capture where applicable.
- PDF generation and e-sign steps are configured, followed by KRA New, CDSL, Back Office, NSE and BSE integrations.
2. Detailed Journey Steps
1. Mobile Number
Applicant enters mobile number and selects the applicable dependency. The configured mobile OTP step is used for verification.
| Field | Input Type | Requirement |
| Mobile number | number | Required |
| Select Dependency | select | Required |
| form_number | text | Optional / system field |
2. Mobile OTP Verification
Applicant enters the OTP received on the registered mobile number. A change-mobile option is also configured.
| Field | Input Type | Requirement |
| Mobile OTP | number | Required |
| change_mobile | text | Optional / system field |
3. Email Details
Applicant signs in with Google or enters an email ID. Branch/reference code and branch code fields are available.
| Field | Input Type | Requirement |
| Sign in with Google | button | Optional / system field |
| Email ID | Required | |
| Select Dependency | select | Optional / system field |
| Branch/Reference Code | text | Optional / system field |
| Branch Code | select | Optional / system field |
| branch_code_value | text | Optional / system field |
4. Email OTP Verification
Applicant enters the email OTP. A change-email option is configured.
| Field | Input Type | Requirement |
| OTP | number | Required |
| change_email | text | Optional / system field |
5. Trading Segments & Tariff
Applicant selects applicable exchange/segment options (NSE/BSE cash, F&O, currency and MCX) and relevant brokerage/DP tariff details. Some segment selections are mutually synchronized; F&O selection can trigger income-proof requirements.
| Field | Input Type | Requirement |
| NSE CASH | checkbox | Required |
| BSE CASH | checkbox | Required |
| NSE FO | checkbox | Optional / system field |
| BSE FO | checkbox | Optional / system field |
| BSE CURRENCY | checkbox | Optional / system field |
| NSE CURRENCY | checkbox | Optional / system field |
| MCX | checkbox | Optional / system field |
| Brokerage Plan | button | Optional / system field |
| BOID | select | Optional / system field |
| clientcode | text | Optional / system field |
| equity_intraday | text | Optional / system field |
| equity_delivery | text | Optional / system field |
| future | text | Optional / system field |
| options | text | Optional / system field |
| commo_future | text | Optional / system field |
| commo_options | text | Optional / system field |
| applicationcode | text | Optional / system field |
| DP tariff plan | button | Required |
| admin_pen_status | text | Optional / system field |
| admin_pen_message | text | Optional / system field |
| equity_sip | radioButton | Optional / system field |
| dp_charges_link_first | text | Required |
| dp_agreement_first | checkbox | Required |
| segement_selected | number | Optional / system field |
| nse_bse_cash_select | select | Optional / system field |
| nse_bse_fo_select | select | Optional / system field |
| nse_currency_select | select | Optional / system field |
| bse_currency_select | select | Optional / system field |
| mcx_select | select | Optional / system field |
6. PAN & KRA Fetch Choice
Applicant enters PAN and date of birth and chooses whether to fetch details from KRA. If KRA fetch is declined, the KRA fetch/detail modules are hidden.
| Field | Input Type | Requirement |
| Pan Number | text | Required |
| Date of Birth | date | Required |
| Do you want to fetch details from kra? | select | Required |
7. KRA Fetch
System fetches available KRA information, including identity and address data. If KRA verification is unsuccessful, the KRA details step may be hidden.
| Field | Input Type | Requirement |
| AADHAR_NO | text | Optional / system field |
| FATHER_NAME | text | Optional / system field |
| GENDER | text | Optional / system field |
| KRA_NAME | text | Optional / system field |
| PER_ADD1 | text | Optional / system field |
| PER_ADD2 | text | Optional / system field |
| PER_ADD3 | text | Optional / system field |
| PER_CITY | text | Optional / system field |
| PER_PINCD | text | Optional / system field |
| PER_STATE | text | Optional / system field |
| dob_for_kra_fetch | text | Optional / system field |
| kra_verify | text | Optional / system field |
| pan_for_kra_fetch | text | Optional / system field |
8. KRA Details Review
Applicant reviews the fetched KRA details and indicates whether to continue with them. Depending on the response and Aadhaar availability, DigiLocker/PAN steps are shown or hidden.
| Field | Input Type | Requirement |
| Gender | text | Optional / system field |
| Aadhaar number | text | Optional / system field |
| Address 1 | text | Optional / system field |
| Address 2 | text | Optional / system field |
| Pincode | text | Optional / system field |
| State | text | Optional / system field |
| Do You Want to continue with KRA details ? | select | Required |
| kraname | text | Optional / system field |
| Date of birth | date | Optional / system field |
| kra_add_line1 | text | Optional / system field |
| kra_add_line2 | text | Optional / system field |
9. DigiLocker / Aadhaar
Configured fields capture Aadhaar/DigiLocker identity, demographic and document data. PAN-related steps may be skipped when Aadhaar seeding or PAN retrieval conditions are met.
| Field | Input Type | Requirement |
| aadhar_address | text | Optional / system field |
| aadhar_country | text | Optional / system field |
| aadhar_dist | text | Optional / system field |
| aadhar_dob | text | Optional / system field |
| aadhar_fathername | text | Optional / system field |
| aadhar_file | image | Optional / system field |
| aadhar_gender | text | Optional / system field |
| aadhar_house | text | Optional / system field |
| aadhar_image | image | Optional / system field |
| aadhar_name | text | Optional / system field |
| aadhar_no | text | Optional / system field |
| aadhar_pincode | text | Optional / system field |
| aadhar_state | text | Optional / system field |
| clienttoken | text | Optional / system field |
| digitrans | text | Optional / system field |
| locality | text | Optional / system field |
| pan_from_digilocker | text | Optional / system field |
| panname_for_digilocker | text | Optional / system field |
| panno_for_digilocker | text | Optional / system field |
| state | text | Optional / system field |
| uploadPAN | image | Optional / system field |
10. PAN Verification
PAN number and name are captured/verified where required. PAN status can affect the journey path.
| Field | Input Type | Requirement |
| aadhar_seeding_status | text | Optional / system field |
| Pan Number | text | Required |
| Name on the PAN | text | Required |
| pan_status | text | Optional / system field |
11. Personal & Account Details
Applicant provides personal, occupation, income, trading experience, tax residency, communication preferences, DP instructions and related declarations. Spouse name visibility depends on marital status; DDPI selection controls related declaration/stamp fields.
| Field | Input Type | Requirement |
| Father’s Name | text | Required |
| Mother’s Name | text | Required |
| Gender | select | Required |
| Marital Status | select | Required |
| Spouse Name | text | Optional / system field |
| Education | select | Required |
| Occupation | select | Required |
| Annual Income | select | Required |
| Trading Experience (in years) | number | Required |
| Politically Exposed | select | Required |
| Are you a citizen of India ? | select | Required |
| Do you wish to execute DDPI ? (Demat Debit Pledge Instructions) | select | Optional / system field |
| Tax Residency outside India | select | Required |
| How frequently do you want to receive your holding cum Transaction statement? | select | Required |
| I request you to send Electronic Transaction Cum-Holding statement on my Email ID | select | Required |
| How would you like to receive your annual report? | select | Required |
| How would you like to receive your contract note? | select | Required |
| I wish to receive dividend/interest directly into my bank account | select | Required |
| I instruct the DP to receive each and every credit in my account | select | Required |
| I would like to share email ID with RTA | select | Required |
| I would like to instruct the DP to accept all the pledge instructions in my account without any other further instruction from my end | select | Optional / system field |
| I do not have any past actions from SEBI/Exchange in last 3 years | select | Required |
| I/We hereby authorize auto-debit from my/our registered bank account to clear any debit balance in my/our trading account. | select | Required |
| I have read and understood the contents pertaining to the DP Standing Instructions and Tariff Structure details. I hereby agree and give my consent to the same. | checkbox | Optional / system field |
| Trading & Demat | select | Required |
| ddpi_yes_name | checkbox | Optional / system field |
| ddpi_no_name | checkbox | Optional / system field |
| ddpi_yes_stamp | checkbox | Optional / system field |
| ddpi_no_stamp | checkbox | Optional / system field |
| Disability | select | Required |
| I/We would like to instruct the DP to accept all the pledge instructions in my / our account without any other further instruction from my / our end | select | Required |
| I/We wish to receive dividend / interest directly into my bank account as given above through ECS | select | Required |
| I/We instruct the DP to receive each and every credit automatically in my account | select | Required |
| I/We would like to share the email id to the RTA | select | Required |
| Running Account Authorisation | select | Required |
| get_gender | text | Optional / system field |
12–21. Nominee Details
The configuration contains nominee modules for up to ten nominees. These capture nominee identity, contact, relationship, date of birth, address, proof and upload details; guardian details are available where applicable. Opt-in/opt-out declarations and supporting stamps/dates are also configured.
22. Nominee Percentage Allocation
Configured fields capture nominee names and percentage allocation. Conditional rules show or hide allocation rows according to the selected nominee count.
| Field | Input Type | Requirement |
| nominee_1_name | text | Optional / system field |
| nominee_1_percentage | number | Optional / system field |
| nominee_2_name | text | Optional / system field |
| nominee_2_percentage | number | Optional / system field |
| nominee_3_name | text | Optional / system field |
| nominee_3_percentage | number | Optional / system field |
| nominee_4_name | text | Optional / system field |
| nominee_4_percentage | number | Optional / system field |
| nominee_5_name | text | Optional / system field |
| nominee_5_percentage | number | Optional / system field |
| nominee_6_name | text | Optional / system field |
| nominee_6_percentage | number | Optional / system field |
| nominee_7_name | text | Optional / system field |
| nominee_7_percentage | number | Optional / system field |
| nominee_8_name | text | Optional / system field |
| nominee_8_percentage | number | Optional / system field |
| nominee_9_name | text | Optional / system field |
| nominee_9_percentage | text | Optional / system field |
| nominee_10_name | text | Optional / system field |
| nominee_10_percentage | number | Optional / system field |
| nominee_count | text | Optional / system field |
| get_number_of_nominee | text | Optional / system field |
23–24. Nominee Mobile & OTP
A holder mobile number is captured and verified through OTP as a separate nominee-related verification step.
| Field | Input Type | Requirement |
| Holder Mobile No | number | Required |
25. Bank Details
Applicant enters account number, confirms account number, IFSC and account type. Bank verification/penny-drop response fields are configured. Bank proof upload visibility depends on verification outcome.
| Field | Input Type | Requirement |
| activestatus | text | Optional / system field |
| bankAddress | text | Optional / system field |
| bankName | text | Optional / system field |
| bank_city | text | Optional / system field |
| bank_district | text | Optional / system field |
| bank_pincode | text | Optional / system field |
| bank_state | text | Optional / system field |
| bankverify | text | Optional / system field |
| branchName | text | Optional / system field |
| micr | text | Required |
| pennydrop_accountholder_name | text | Optional / system field |
| pennydrop_mobile | text | Optional / system field |
| pennydrop_name | text | Optional / system field |
| pennydrop_verify | text | Optional / system field |
| pennydrop_verify_time | text | Optional / system field |
| Account Number | password | Required |
| Confirm Account Number | number | Required |
| IFSC | text | Required |
| MICR | number | Optional / system field |
| Account Type | select | Required |
| Bank Address | text | Optional / system field |
26. Bank Proof Upload
Bank proof document upload is available when the bank verification flow requires supporting proof.
| Field | Input Type | Requirement |
| Upload Bank Proof | file | Required |
27. Income Proof Upload
Income proof upload is configured and can be made mandatory/visible based on selected trading segments and account-aggregator conditions.
| Field | Input Type | Requirement |
| Upload Income Proof | file | Required |
| reject_reason_upload_income_proof | text | Optional / system field |
| rejected_by_upload_income_proof | text | Optional / system field |
| rejected_timestamp_upload_income_proof | text | Optional / system field |
28. PAN Document Upload
PAN document upload is available when required by the PAN/DigiLocker verification path.
| Field | Input Type | Requirement |
| Pan upload | file | Required |
| reject_reason_pan_upload | text | Optional / system field |
| rejected_by_pan_upload | text | Optional / system field |
| rejected_timestamp_pan_upload | text | Optional / system field |
29. Signature Upload
Applicant uploads signature. A BOID selection field is also configured in this step.
| Field | Input Type | Requirement |
| Signature Upload | file | Required |
| reject_reason_signature_upload | text | Optional / system field |
| rejected_by_signature_upload | text | Optional / system field |
| rejected_timestamp_signature_upload | text | Optional / system field |
| boid | select | Optional / system field |
30. Live Image Capture
Live applicant image capture and location coordinates are configured, with rejection reason/audit fields.
| Field | Input Type | Requirement |
| clientimage | file | Optional / system field |
| latitude | text | Optional / system field |
| location | text | Optional / system field |
| longitude | text | Optional / system field |
| reject_reason_clientimage | text | Optional / system field |
| rejected_by_clientimage | text | Optional / system field |
| rejected_timestamp_clientimage | text | Optional / system field |
31–34. PDF Generation & E-sign
Two PDF-generation steps and two e-sign steps are configured. The e-sign steps store signer name, timestamp and transaction ID.
| Field | Input Type | Requirement |
| NA | image | Optional / system field |
| current_date | text | Optional / system field |
| current_day | text | Optional / system field |
| current_month | text | Optional / system field |
| current_year | text | Optional / system field |
35. KRA New Submission
KRA New integration step is configured after the document/PDF/e-sign stages.
36. CDSL Upload
CDSL upload integration step is configured.
37. Back Office
Back-office integration step is configured for account processing.
38. NSE
NSE integration step is configured.
39. BSE
BSE integration step is configured.
3. Key Conditional Rules
Branch/segment selection: NSE Cash and BSE Cash selections are synchronized. NSE/BSE F&O and currency selections also have linked behavior. Selecting F&O can display the income-proof upload step.
KRA path: Choosing not to fetch KRA details hides the KRA fetch and KRA review steps. KRA verification outcome and Aadhaar availability determine whether DigiLocker and PAN steps are displayed.
Personal details: Spouse name is hidden for Single and shown for Married. DDPI Yes/No controls the related name and stamp fields.
Nomination: Selecting No for nominee appointment switches to the opt-out declaration path and hides nominee-entry fields. Selecting nominees allows nominee details and percentage allocation to be captured. Percentage rows are controlled by nominee count.
Bank proof: Bank proof upload is hidden when penny-drop verification succeeds and shown when it does not.
Income proof: Income proof visibility is controlled by segment selection and account-aggregator verification conditions.
4. Downstream Integrations
| Integration | Configured Purpose |
| KRA New | Submit KYC data to KRA New |
| CDSL Upload | Submit demat/account data to CDSL |
| Back Office | Push account data to the back-office system |
| NSE | Exchange onboarding/push |
| BSE | Exchange onboarding/push |
5. Notes & Scope
- The supplied file is a workflow configuration export, not a complete business requirements document. The journey order is interpreted from the configured node sequence and positions.
- Some modules contain internal/system fields that are not applicant-facing; these have been omitted from the field tables for readability.
- Detailed API payloads, credentials, secrets and implementation code are intentionally excluded.
- Conditional rules are summarized; the full configuration may contain additional field-level behavior and validation not reproduced here.