Flow Summary

This page gives you the complete onboarding pipeline in a single view — from the customer’s first mobile OTP (One-Time Password) to the moment their account status changes to “ACTIVE” and they can place their first trade. If you are a new engineer, read this page after the Design Principles and before diving into the individual screen specifications. It will give you the end-to-end mental model that ties everything together: the 9-screen user journey (~6 minutes of customer time), the maker-checker review (internal quality gate), and the multi-agency batch processing (the 24-72 hours where the system registers the customer with every exchange and depository).

User Journey (9 Screens, ~6 Minutes)

The flow below shows each screen, the fields the customer provides, and the async operations that fire at each step. Notice how the async calls are strategically placed to complete before the data is needed.

Screen 1: Mobile / Email Registration (1 field: mobile + OTP)
    |--> ASYNC: Device Fingerprint [Bureau.id]

Screen 2: Enter PAN + DOB (2 fields)
    |--> ASYNC: PAN Verify, KRA Lookup, CKYC Search, AML Screen

Screen 3: DigiLocker Consent (redirect, 0 fields)
    |--> Harvests: Name, DOB, Gender, Photo, Address, Father's Name, PAN

Screen 4: Confirm Identity (1 field: email)
    |--> Mobile already verified from Screen 1

Screen 5: Bank Account (3 fields: account no, IFSC, type)
    |--> ASYNC: Penny Drop, IFSC Lookup, OCR

Screen 6: Trading Preferences (segment toggles)
    |--> ASYNC: Income verify (if F&O/Commodity)

Screen 7: Nominations (add nominee or opt-out)

Screen 8: Declarations (checkboxes) + BLOCKING GATE

Screen 9: Review + Face Match + Aadhaar OTP e-Sign

Note

User is done in ~6 minutes. Everything after Screen 9 is automatic.

Reading the flow diagram

Each ASYNC tag indicates a background operation that runs without blocking the customer. The results of these operations converge at Screen 8 (the blocking gate). If you are tracing a specific data point through the system — say, PAN (Permanent Account Number) verification status — follow it from Screen 2 where it fires, through DigiLocker (Government of India’s digital document platform) on Screen 3 where it completes in the background, to Screen 8 where it is evaluated.

Once the customer completes Screen 9, the application enters the internal review pipeline. The customer does not see or interact with this phase — they simply receive a notification when their account is active.

Maker-Checker Review

User Submits → Maker Review → Checker Approval → Batch Zone

• Maker (Step 10): Auto-approve if all checks pass; manual only for edge cases
• Checker (Step 11): Final approval before batch submission

Why maker-checker?

SEBI (Securities and Exchange Board of India) regulations require a dual-control review process for account opening. The maker reviews the application data and flags any discrepancies. The checker independently verifies and gives final approval. In the happy path (all async checks passed, no discrepancies), both steps can be semi-automated — the reviewer simply confirms what the system has already validated.

After the checker approves, the system triggers 8 independent batch pipelines. Each pipeline registers the customer with a different regulatory agency or exchange. They run in parallel because none of them depend on each other’s output.

Batch Zone (Parallel Agency Pipelines)

After checker approval, 8 pipelines run in parallel:

Pipeline	Submission	Processing	Result	Timeline
KRA	Submit	Under Process	Registered → Validated	2-3 days
CKYC	Upload	Queued → Validated	KIN Generated	4-5 days
NSE	UCC Submit	PAN Verify	Approved → Trading Active	Same day
BSE	UCC Submit	3-Param PAN Verify	Approved → Segments Live	Same day
MCX	UCC Submit	Income Verify	Approved	Next working day
CDSL	BO File	KYC Check → Bank Valid	Active	1-2 hrs (API)
NSDL	UDiFF Submit	CDS Process → DPM Update	Active	~15 days
Income	Perfios/AA verify	-	Confirmed	1-2 hrs

NSDL is the bottleneck

Notice that NSDL (National Securities Depository Limited) takes approximately 15 days — significantly longer than every other pipeline. This is because NSDL still uses the UDiFF batch format and has a longer processing cycle compared to CDSL (Central Depository Services Limited), which offers API-based BO (Beneficiary Owner) account opening with 1-2 hour turnaround. If your firm uses CDSL as the primary depository, the customer can typically start trading within 24 hours.

The final gate determines when the customer’s account status changes to “ACTIVE” and they receive the notification that they can trade.

Final Gate

KRA Registered → BO Active → UCC Approved → ACTIVE (Can Trade)

Total time to active: 24-72 hours (limited by KRA/NSDL processing)

Figure 1: Complete Onboarding Flow