Customer Onboarding Process in Banking: The KYC-to-LOS Hand-off, Step by Step
How Indian banks and NBFCs run customer onboarding: CKYC, Aadhaar e-KYC, PAN, penny drop, mule screening, and the LOS hand-off under RBI KYC rules.

In Indian banking and lending, the customer onboarding process runs identity, tax, bank-account, deduplication, and risk checks before sending one verified record to a Loan Origination System (LOS), the software that tracks loan applications. Under the RBI’s 2025 KYC Directions for commercial banks, the regulator sets what checks a lender must finish, not the API order or webhook format. The sequence below is an illustrative engineering blueprint.
Where things stand (November 2026)
- •On 28 November 2025, the RBI repealed its 2016 KYC Master Direction and issued entity-wise Directions. Commercial banks and Non-Banking Financial Companies (NBFCs) follow separate 2025 Directions with different paragraph numbers.
- •These Directions set mandatory Know Your Customer (KYC) and Customer Due Diligence (CDD) rules, not a fixed API order or LOS schema.
- •The API sequence, webhook payload, and retry loop below are an illustrative engineering design, not a vendor specification.
Core Regulatory Rules Before Any Check Runs
Before running any API check, a bank or NBFC must ensure it can complete Customer Due Diligence (CDD), the required identity, address, and background checks at relationship start.
Under the RBI’s 2025 KYC Directions (Commercial Banks version), a bank cannot open an anonymous or fictitious account. It also cannot open an account where it cannot apply CDD. Both the Commercial Banks version and the RBI’s 2025 KYC Directions for NBFCs (NBFC version) require allotting a Unique Customer Identification Code (UCIC), one internal ID per person across the lender.
CDD applies at the UCIC level. An existing KYC-compliant customer opening another account or taking another product from the same lender does not need fresh identification. Under the Commercial Banks version, a bank also cannot reject an application without applying its mind, and the officer must record the reason.
Illustrative KYC-to-LOS Onboarding Sequence
This illustrative blueprint breaks the sequence into seven steps from initial lookup to the LOS hand-off.
Step 1: CKYC Lookup and Consent
Ask the customer for their 14-digit KYC Identifier or search the Central KYC Records Registry (CKYCR), the central KYC registry. Under both the Commercial Banks and NBFC versions of the 2025 Directions, a lender must download records online from CKYCR with explicit customer consent. It must not ask for the same KYC documents again unless one of four exceptions applies:
- •The customer's information in CKYCR has changed.
- •The retrieved record is incomplete or fails current KYC norms.
- •The validity period of downloaded documents has lapsed.
- •The lender needs to verify identity or address, run Enhanced Due Diligence (EDD, deeper checks for higher-risk customers), or build a risk profile.
Under a 29 December 2025 amendment to both versions, the entity that last uploaded or updated the CKYCR record is responsible for verifying identity and address. A downloading lender using current, Prevention of Money Laundering Act (PMLA)-compliant CKYCR records need not re-verify identity or address, though other CDD duties remain. For new customers, the lender must upload records to CKYCR within 10 days, share the KYC Identifier, and send updates within seven days.
Per Decentro’s CKYC Download API documentation, downloading a record takes the 14-digit CKYC identifier plus an auth factor (date of birth, 6-digit pincode and birth year, Aadhaar-linked mobile, or address pincode) or a mobile OTP. It returns personalDetails and identityDetails. For registry updates, see our Central KYC 2.0 guide.
Step 2: Aadhaar e-KYC, Offline Verification, or OVD
When CKYCR has no record or an exception triggers, collect fresh KYC. Under the Commercial Banks version, Aadhaar is voluntary unless the customer seeks a Section 7 benefit or subsidy. Customers can use Aadhaar for Aadhaar e-KYC, share offline Aadhaar proof (with the Aadhaar number redacted when authentication is not needed), or submit an Officially Valid Document (OVD) via Digital KYC.
Digital KYC under the Commercial Banks version uses an authenticated bank app. It captures a live photo of the customer and original OVD, watermarked with Customer Application Form (CAF) number, GPS, officer name or code, and timestamp. It supports QR auto-fill and validates an OTP on the customer’s own mobile number.
If a bank or NBFC opens an account remotely using Aadhaar OTP-based e-KYC, both 2025 Directions enforce strict rules:
- •Consent and alerts: Get specific consent, send OTPs only to the Aadhaar-registered mobile, and collect a declaration that no other OTP-based remote account exists or will be opened.
- •Account caps: Deposit accounts are capped at ₹1 lakh balance and ₹2 lakh annual credits. Borrowal accounts are capped at ₹60,000 in term loans per year.
- •One-year limit: Accounts cannot run past one year without full CDD or Video-based Customer Identification Process (V-CIP). Otherwise, deposit accounts must close immediately and borrowal accounts allow no further debits.
For V-CIP under both 2025 Directions, Aadhaar XML or Secure QR files cannot be older than three working days. The video call must also happen within three working days of downloading CKYCR or Aadhaar records.
Step 3: PAN Verification and Link Status
Under the Commercial Banks version, a bank must collect a Permanent Account Number (PAN), its e-document equivalent, or Form No. 60 (for customers without a PAN). Any PAN obtained must be verified via the issuing authority’s facility. See our PAN verification guide.
Per the Income Tax Department’s Link Aadhaar FAQ, PANs not linked with Aadhaar by 30 June 2023 became inoperative from 1 July 2023 unless exempt (residents of Assam, Jammu & Kashmir, and Meghalaya, non-residents, people aged 80+, and non-citizens). Reactivation takes a ₹1,000 fee and Aadhaar intimation, and the issuing authority’s facility reflects PAN status.
Step 4: Bank Account Proof (Penny Drop)
The RBI’s 2025 KYC Directions do not mandate a penny-drop API call as a standalone KYC step. In an illustrative workflow, it can be included as an operational bank-account verification step (see our penny drop verification guide).
Step 5: Document OCR, Dedupe, Sanctions, and Mule Screening
Next, Optical Character Recognition (OCR) reads uploaded documents. Digital KYC permits QR auto-fill, while exact OCR confidence or name-match thresholds are engineering choices.
Three regulatory screens follow:
- •UCIC deduplication: Match internal records to assign or reuse the customer’s UCIC.
- •Sanctions screening: Under the Commercial Banks version, confirm the customer does not match Chapter IX sanctions lists.
- •Money Mule controls: Under both 2025 Directions, follow account-opening and monitoring rules to curb Money Mule accounts, third-party accounts used to launder fraud proceeds. Establishing a Money Mule account without filing a Suspicious Transaction Report (STR) with India’s Financial Intelligence Unit (FIU-IND) is non-compliant. See our mule account detection guide.
Step 6: Risk Categorisation and Confidentiality
Under the Commercial Banks version, a bank must rate each customer as low, medium, or high risk. Factors include identity, financial status, business nature, geography, products, delivery channel, and transaction types.
The bank must keep the risk rating and its reasons confidential. Revealing them to the customer is barred to prevent tipping off.
Step 7: Webhook Hand-off to the LOS (Illustrative Pattern)
Once checks pass, the verification layer pushes a signed-off record to the LOS. Because no RBI or industry standard defines an LOS webhook schema, the table below is an illustrative engineering pattern:
| Event (Illustrative) | Trigger | Example fields (Illustrative) | LOS action |
|---|---|---|---|
| kyc.verified | All KYC, PAN, dedupe, and risk checks pass | app_id, ucic_status, kyc_mode, risk_tier | Move to underwriting; hide risk reasons |
| kyc.action_needed | CKYC exception, OTP cap, or OCR mismatch | app_id, failed_step, reason_code | Route to manual queue or V-CIP link |
| kyc.rejected | Sanctions match or unresolved failure | app_id, rejection_reason, officer_id | Close application; log officer reason |
In an illustrative pattern, teams can pair webhooks with an idempotency key so duplicate deliveries of an already verified record succeed cleanly. On timeout, the verification layer can retry with backoff, route persistent failures to a manual review queue, and flag stale data before V-CIP’s three-working-day limit expires.
“The RBI's 2025 KYC Directions prescribe what checks a lender must complete, not the API call order or webhook schema between your verification layer and LOS.”
The illustrative diagram below maps this sequence across the applicant app, verification layer, and LOS.
- 01
CKYC lookup
Submit 14-digit KYC Identifier with consent and download CKYCR record.
Not found or exception: Go to Step 2
- 02
Aadhaar e-KYC or OVD
Run voluntary Aadhaar e-KYC, offline Aadhaar, or Digital KYC with OVD.
- 03
PAN check
Verify PAN or Form 60 through the issuing authority facility.
- 04
Bank penny drop (operational)
Run operational bank-account verification step.
- 05
OCR, dedupe, and mule screen
Extract document fields, match UCIC, and screen sanctions and Money Mules.
- 06
Risk categorisation
Assign confidential low, medium, or high risk tier internally.
- 07
Webhook to LOS
Push verified status to LOS; retry timeouts, then route to manual queue.
Timeout: Retry with backoff, then manual queue
Failure and Fallback Patterns (Illustrative)
These fallback steps are illustrative operational patterns, subject to recording officer reasons for any rejection.
| Step | What it checks | Failure condition | Illustrative fallback |
|---|---|---|---|
| CKYC lookup | personalDetails and identityDetails | Missing record or 4 exceptions | Prompt for Aadhaar e-KYC or OVD |
| Aadhaar OTP e-KYC | Aadhaar e-KYC authentication | OTP fails or loan over ₹60,000/year | Switch to V-CIP or Digital KYC |
| PAN check | Issuing authority PAN status | Mismatch, inoperative, or missing | Check Form 60 or ask user to resolve |
| Penny drop | Bank-account verification | Verification failure (illustrative) | Retry or request alternate bank proof |
| OCR and dedupe | Extracted fields and UCIC | Low OCR score or sanctions/mule hit | Manual compliance review; log reason |
| LOS webhook | Signed-off KYC payload | LOS timeout or server error | Retry with backoff, then manual queue |
Automating the KYC-to-LOS Hand-off
Teams wanting a single API for CKYC, Aadhaar, PAN, bank checks, and screening can explore KYCKART’s customer onboarding solution or read our guide to customer onboarding software for banks and NBFCs.
How KYCKART Helps
KYCKART orchestrates CKYC retrieval, Aadhaar e-KYC and V-CIP, PAN verification, penny-drop checks, and mule screening through one integration layer before handing a structured, audit-ready onboarding record to your LOS.
What This Means for Banking and NBFC Teams
Read together, the 2025 RBI KYC Directions and API rules point to three practical steps for product, risk, and engineering teams:
Key Takeaways
- •Plan for CKYCR fallbacks early. Lenders can rely on current CKYCR records without re-verifying identity or address, but four exceptions still require fresh documents. The practical implication is that your app should route users smoothly into Digital KYC or V-CIP without restarting the journey.
- •Match ticket size to KYC mode. Non-face-to-face Aadhaar OTP e-KYC caps term loans at ₹60,000 per year and blocks debits after one year without full CDD or V-CIP. Product teams building larger loans should route applicants to V-CIP or Digital KYC from the start.
- •Strip risk reasons from user messages. Under the Commercial Banks Directions, risk tiers and reasons stay confidential. Engineering teams should keep risk-reason fields internal to the LOS while still logging officer rejection reasons.
Frequently Asked Questions
Author: Bhanujeet Choudhary, Head of Compliance, KYCKART
Published: 8 November 2026
Disclaimer: This article is for informational purposes only and does not constitute legal, regulatory, tax, or compliance advice. Institutions should consult qualified legal or compliance counsel before establishing customer onboarding, KYC, or loan origination policies.
KYCKART Intelligence
Automate Your KYC-to-LOS Customer Onboarding Flow
Run CKYC lookups, Aadhaar e-KYC, PAN checks, penny drop, and mule screening through one API before handing a verified record to your LOS.
Explore Onboarding Solutionsarrow_forward