Screen 4: Confirm Identity
The customer has just returned from DigiLocker (Government of India’s digital document platform). They land on a screen that already knows their name, date of birth, gender, father’s name, address, and photo. All of this was fetched from their Aadhaar XML during the DigiLocker consent. On top of that, the four async API calls from Screen 2 have now completed, so the system also has their KRA (KYC Registration Agency) record (occupation, income range, net worth) and CKYC (Central KYC) data if they exist. The customer sees a pre-filled form and only needs to type one thing: their email address. This is the payoff of the DigiLocker-first architecture.
Purpose: Present the pre-filled identity data for user confirmation. Only email needs to be entered.
This screen is where the customer first sees the power of the system working on their behalf. Instead of filling out a long form, they are reviewing data that the system has already gathered from three authoritative sources: DigiLocker, KRA, and CKYC.
Pre-filled Fields (Read-Only)
Section titled “Pre-filled Fields (Read-Only)”These fields come directly from DigiLocker and are displayed as read-only. The customer cannot edit them — they are government-verified.
| Field | Source |
|---|---|
| Name | DigiLocker (Aadhaar XML) |
| Date of Birth | DigiLocker (Aadhaar XML) |
| Gender | DigiLocker (Aadhaar XML) |
| Father’s Name | DigiLocker (Aadhaar XML) |
| Full Address | DigiLocker (Aadhaar XML) |
| Photo | DigiLocker (Aadhaar XML) |
| PAN (Permanent Account Number) | User input (Screen 2) |
If the customer has an existing KYC record with another broker, additional financial fields are also pre-filled. These come from the KRA lookup and CKYC search that fired on Screen 2.
Pre-filled from KRA / CKYC (if found)
Section titled “Pre-filled from KRA / CKYC (if found)”| Field | Source |
|---|---|
| Occupation | KRA record |
| Income Range | KRA / CKYC record |
| Net Worth | KRA / CKYC record |
| CKYC Number (KIN) | CKYC Search result |
The only field the customer actually types on this screen is their email address.
User Input
Section titled “User Input”| Field | Validation | Notes |
|---|---|---|
| Valid email format | Mobile already verified on Screen 1 |
Behind the scenes, this screen is also where the system assembles the identity record that will be used for all downstream operations — exchange registration, depository account opening, and regulatory filings. The data sources are stitched together with a clear priority: DigiLocker fields take precedence, followed by CKYC, then KRA.
KRA and CKYC Integration
Section titled “KRA and CKYC Integration”KRA integration supports all five KRAs (CVL, NDML, DOTEX, CAMS, KFintech) via interoperability. Key operations include PAN status check, fetch details, and upload/update. The CKYC integration serves a dual purpose: it provides pre-fill data now, and later (post-approval) the system will upload the customer’s complete KYC record back to the CKYC registry (CERSAI). This dual upload — to both KRA and CKYC — has been mandatory since August 2024 per SEBI circular.
For vendor implementation options for KRA and CKYC integration, see Vendor Integrations.