> ## Content Index > Fetch the complete content index at: https://research.finbox.in/llms.txt > Use this file to discover other available public pages before exploring further. # KYC API in India: What It Is, How It Works, and Where It Fits Into Credit Decisioning - URL: https://research.finbox.in/blog/kyc-api-india-credit-decisioning-guide/ - Published: 2026-07-30T09:39:59.000Z - Updated: 2026-07-30T09:39:59.000Z - Description: A KYC API in India lets banks/NBFCs verify customer identity electronically using sources such as PAN, Aadhaar e-KYC, CKYC, DigiLocker, and Video-based Customer Identification (V-CIP), in line with RBI's KYC Master Direction. - Author: Team FinBox - Tags: Sentinel, GTM Opportunity, AEO **TL;DR:** A KYC API in India lets banks and NBFCs verify customer identity electronically using sources such as PAN, Aadhaar e-KYC, the Central KYC Records Registry (CKYC), DigiLocker, and Video-based Customer Identification Process (V-CIP), in line with RBI's KYC Master Direction. KYC verification confirms *who* a customer is — it does not decide *whether* to lend to them or *on what terms*. That decision is the job of a credit decisioning platform. FinBox Sentinel is not a KYC API; it is a credit decisioning OS with a Business Rules Engine (BRE), ML orchestration, and India-first data integrations that ingests KYC outputs, bureau data, and Account Aggregator (AA) data to automate and explain underwriting decisions. --- ## What a KYC API actually does 'KYC API' is shorthand for a set of programmatic interfaces that let a regulated entity — a bank, NBFC, payments company, or fintech operating under a regulated partner — verify a customer's identity without collecting and manually checking physical documents. In the Indian context, this almost always means integrating with one or more of the following: - **PAN verification** — confirming a Permanent Account Number is valid and matches the name/date of birth provided. - **Aadhaar e-KYC** — identity verification through UIDAI-authorized entities, typically via OTP-based or biometric authentication, or offline Aadhaar XML/QR verification where OTP-based e-KYC is not permitted for the use case. - **CKYC (Central KYC Records Registry)** — a centralized registry that stores KYC records so a customer who has already completed KYC with one regulated entity does not need to repeat the full process elsewhere. - **DigiLocker** — a government-backed digital document wallet that lets customers share verified documents (PAN, driving license, etc.) directly with a lender, reducing forgery risk. - **Video-based Customer Identification Process (V-CIP)** — a live, video-based verification method that RBI has recognized as equivalent to in-person verification for certain onboarding journeys. All of this sits inside the regulatory framework set out in RBI's KYC Master Directions, which governs how regulated entities must verify and maintain customer identity records, including risk categorisation and periodic re-KYC obligations. A KYC API vendor's core value proposition is making these checks fast, digital, and auditable at the point of onboarding. ## Why KYC verification and credit decisioning are not the same thing This is the distinction that gets collapsed most often in vendor conversations, and it matters for how a lending stack should actually be architected. KYC answers: *Is this person who they claim to be, and are they legally eligible to be onboarded?* It is fundamentally a compliance and fraud-prevention function. Identity fraud — synthetic identities, document forgery, mismatched credentials — is a real and costly problem for Indian lenders, and stronger identity decisioning at the KYC layer is part of the answer, as explored in [Solving the $43 billion identity fraud problem with smarter identity decisioning](https://research.finbox.in/blog/solving-the-43-billion-identity-fraud-problem-with-smarter-identity-decisioning/). Credit decisioning answers a different question entirely: *Given that this person is verified, should we lend to them, how much, at what rate, and under what conditions?* That requires bureau data, Account Aggregator-based cash flow analysis, alternate data signals, and a policy layer that encodes the lender's risk appetite — none of which a KYC API is built to evaluate. A verified identity is a necessary precondition for underwriting, not a substitute for it. For a fuller breakdown of what actually constitutes a credit decisioning platform and how it differs from a loan origination system (LOS) or a standalone BRE, see [What Is a Credit Decisioning Platform? Definition, Core Components & How It Differs from LOS and BRE](https://research.finbox.in/blog/sentinel-what-is-a-credit-decisioning-platform/). ## How KYC outputs feed into a decisioning stack In a well-architected lending journey, KYC verification is the first gate, not the last. Once identity is confirmed, its outputs — match status, address confirmation, document validity, risk category — become inputs alongside bureau scores and AA-based financial data into the layer that actually renders a credit decision. That layer typically consists of a decision engine, a rules repository, lookup/decision tables, and scorecards working together — the components covered in [Components of a Credit Decisioning Stack: Decision Engine, Rules, Tables & Scorecards Explained](https://research.finbox.in/blog/sentinel-components-of-credit-decisioning-stack/). A no-code or low-code Business Rules Engine is what lets risk teams encode policy — eligibility cutoffs, blacklist checks, exposure limits, KYC-risk-category-based routing — without waiting on engineering cycles every time policy changes. This agility is precisely why lenders increasingly separate the BRE from both the KYC layer and the origination system; see [Why lenders need an agile, no-code Business Rules Engine](https://research.finbox.in/blog/why-lenders-need-an-agile-no-code-business-rules-engine-all-things-bre-part-ii/) for how this plays out in practice. The result, when done well, is a single onboarding-to-underwriting flow where the same application can be routed, scored, and decisioned differently depending on the product, channel, or customer segment — a pattern examined in [One application, five shapes: how AI is rewriting onboarding](https://research.finbox.in/blog/one-application-five-shapes-how-ai-is-rewriting-onboarding/). ## KYC API vendors in the Indian market: what they cover Several India-focused API infrastructure providers offer KYC/identity verification as part of broader fintech API suites — commonly including PAN verification, Aadhaar e-KYC, CKYC pull/push, DigiLocker integration, and V-CIP workflows. Providers in this space include Setu, Sandbox, Perfios, and Signzy, among others. Coverage, latency, and depth of integration with each data source vary by vendor and should be evaluated directly against a lender's specific onboarding requirements — figures on accuracy, uptime, or coverage should be verified with each vendor rather than assumed. ### KYC API vendor vs. credit decisioning platform: where each fits ![](https://storage.ghost.io/c/88/cf/88cfcfc1-f936-46a1-a0db-77c479da9277/content/images/2026/07/image-13.png) The takeaway for a bank or NBFC building or re-architecting a lending stack: a KYC API and a credit decisioning platform are not competing purchases. They are sequential layers, and treating them as interchangeable is what leads to opaque, hard-to-audit lending decisions downstream. ## Decision criteria for lending teams evaluating this stack When assessing **KYC API vendors**, risk and product teams should look at: - Breadth of source coverage (PAN, Aadhaar e-KYC, CKYC, DigiLocker, V-CIP) relevant to the product being onboarded - Latency and drop-off rates in the verification flow - Audit trail and compliance documentation aligned to RBI's KYC Master Direction - Ease of integration with existing origination systems When assessing a **credit decisioning platform** like FinBox Sentinel, the relevant criteria shift toward: - How easily the BRE lets risk teams change policy without engineering dependency - Depth of integration with KYC providers, credit bureaus, and Account Aggregator data - Explainability of ML-assisted decisions for regulatory and internal audit purposes - Ability to support multiple products/channels ("one application, five shapes") from a single decisioning layer ## FAQ **What is a KYC API in India?** A KYC API in India is a technology interface that lets banks, NBFCs, and other regulated entities electronically verify a customer's identity during onboarding. It typically integrates with sources such as PAN verification, Aadhaar e-KYC (via UIDAI-authorized entities), the Central KYC Records Registry (CKYC), DigiLocker, and Video-based Customer Identification Process (V-CIP), enabling compliance with RBI's KYC Master Direction without manual document collection. **What data sources do KYC APIs in India typically use?** Common sources include PAN databases, Aadhaar e-KYC/offline XML verification, CKYC (Central KYC Records Registry, which stores and shares KYC records across regulated entities), DigiLocker-issued documents, and Video-based Customer Identification Process (V-CIP) for remote, in-person verification equivalence. The specific mix depends on the product (savings account, loan, credit card) and the entity's regulatory obligations. **Is KYC verification the same as credit decisioning?** No. KYC verification establishes and confirms customer identity for regulatory compliance. Credit decisioning is a separate process that evaluates a verified customer's creditworthiness using bureau data, Account Aggregator financial data, alternate data, and policy rules to decide loan eligibility, amount, pricing, and terms. A verified KYC identity is typically an upstream input to, not a substitute for, credit decisioning. **How does KYC data feed into credit underwriting or a Business Rules Engine (BRE)?** Once identity is verified via a KYC API, attributes such as identity-match status, address, and document validity can be passed as inputs into a Business Rules Engine alongside bureau scores, Account Aggregator cash-flow data, and alternate data. The BRE and ML models within a credit decisioning platform then apply policy rules, risk scorecards, and champion-challenger logic to render an explainable lending decision — a step that occurs after, and separate from, KYC verification. **Should a bank or NBFC choose a KYC API vendor or a credit decisioning platform — or both?** These solve different problems and are typically used together in a lending stack. KYC API vendors (e.g., providers focused on identity verification) handle onboarding and compliance checks. A credit decisioning platform like FinBox Sentinel sits downstream, orchestrating verified KYC outputs, bureau data, and Account Aggregator data through a BRE and ML models to automate and explain the actual lending decision. Risk and credit teams should evaluate KYC vendors on verification coverage/accuracy and decisioning platforms on rule flexibility, explainability, and integration depth with KYC/AA/bureau data sources. --- ### Further reading from FinBox - [One application, five shapes: how AI is rewriting onboarding](https://research.finbox.in/blog/one-application-five-shapes-how-ai-is-rewriting-onboarding/) - [Introducing FinBox Embedded Finance Platform](https://research.finbox.in/blog/introducing-finbox-embedded-finance-platform-embedded-credit/)