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.

4 Confirm Identity ~30 seconds

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)

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)

Field	Source
Occupation	KRA record
Income Range	KRA / CKYC record
Net Worth	KRA / CKYC record
CKYC Number	CKYC Search result

First-time vs. existing KYC customers

If the customer has never opened a trading or demat account before, the KRA lookup will return empty and the CKYC search will find no record. In that case, the occupation and income fields will be blank and the customer will need to fill them in manually. This is the “new-to-market” path. For customers who already have a KYC record with another intermediary, these fields arrive pre-filled, saving them additional effort.

The only field the customer actually types on this screen is their email address.

User Input

Field	Validation	Notes
Email	Valid email format	Mobile already verified on Screen 1

Note

Mobile was already verified on Screen 1. Only email needs to be entered here. If KRA/CKYC returned an email, it can be pre-filled for the user to confirm.

Behind the scenes, this screen is also where your 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.

Vendor Comparison: KRA Integration

KRA Integration

Vendor	APIs	Key Features	Cost/txn
Digio Recommended	REST/JSON	All 5 KRAs via interoperability. PAN Status Check, Fetch Details, Upload/Update. IP whitelisting. 2-day integration.	Rs.3-5
CVL KRA Direct Alternate	SOAP/XML	GetPanStatus, InsertUpdateKYCRecord, bulk tilde-delimited files. Legacy but stable.	Rs.2-3
TrackWizz New	REST/JSON	KRA submission + CKYC upload + AML (Anti-Money Laundering) screening in one platform. Regulatory reporting bundle.	Rs.3-5

Full spec: KRA Integration

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. This dual upload — to both KRA and CKYC — has been mandatory since August 2024.

Vendor Comparison: CKYC Integration

CKYC Integration

Vendor	APIs	Key Features	Cost/txn
Decentro Recommended	Search + Download + Upload	REST API. Masked CKYC search (Jan 2025). Full download with identity match. Bulk upload.	Rs.3-10
Digio Alternate	Search + Download + Upload	FI code config, CKYC public key, keystore. Java 17 / Docker. GitHub SDK available.	Rs.3-10
TrackWizz New	Search + Upload	CKYC solution for reporting entities. Combined with AML screening.	Rs.5-10
Protean Direct Alternate	SFTP + API	Direct CERSAI integration. Batch and real-time. Official registry operator.	Contact

Full spec: CKYC Integration

Caution

CKYC Search now returns a masked CKYC number (since Jan 2025). A full Download call is needed to get the complete record for identity matching.

What the customer does not see

By the time the customer reviews and confirms their identity on this screen, the system has already evaluated PAN validity, checked KRA status, searched CKYC, and screened against AML/PEP (Politically Exposed Person) watchlists. None of these results are shown to the customer — they feed into the blocking gate at Screen 8. The customer simply sees a clean, pre-filled form.