# FastKYC - full text > Real-time identity, banking, business and document verification APIs for India, verified against official records and available through a single API key. The body copy of every page on fastkyc.com, in one file: 148 verification APIs across 9 categories, 12 industry pages and 15 articles. The index version of this file, with links but no body copy, is at https://fastkyc.com/llms.txt. --- # Banking ## Banking overview URL: https://fastkyc.com/apis/banking/ Bank account verification APIs for India: penny drop, penny-less and hybrid checks, IFSC search and UPI lookups for safer payouts and onboarding. ## Bank Verification Hybrid API URL: https://fastkyc.com/apis/bank-verification-hybrid/ Verify any Indian bank account with automatic routing between penny-drop and penny-less checks, so you get the fastest valid result every time. Bank Verification Hybrid takes an account number and IFSC and decides for itself how to verify them. It attempts a penny-less lookup first, and falls back to a penny drop only when the account cannot be confirmed from network data. You get one endpoint and one response shape instead of two integrations and your own routing logic. Because the cheaper path is tried first, average cost per verification falls well below a penny-drop-only setup while the success rate stays close to it. The response returns the account holder name as recorded by the bank, along with branch details, so you can run your own name-match before releasing a payout. Use cases: - Validating payout accounts during merchant or vendor onboarding - Confirming beneficiary details before a first disbursement - Reducing verification spend where penny-less coverage is already high - Cutting failed transfers caused by mistyped account numbers Q: How does it decide which method to use? A: It tries the penny-less route first, since it is faster and cheaper. If the account cannot be confirmed that way, it automatically falls back to a penny drop. You do not need to specify a preference. Q: Will a rupee be debited from my account? A: Only when the request falls back to a penny drop. Penny-less verifications move no money at all, which is why they are attempted first. Q: Does it return the account holder's name? A: Yes. The response carries the name as held by the beneficiary bank, which you can compare against your own record before releasing funds. ## Bank Verification Penny Drop API URL: https://fastkyc.com/apis/bank-verification-penny-drop/ Confirm an Indian bank account is live and correctly owned by depositing one rupee and reading back the account holder name from the bank. Penny drop is the most reliable way to prove a bank account exists and can receive money. The API credits a token amount, usually one rupee, to the account number and IFSC you supply. The receiving bank returns the registered account holder name along with the transaction result. Because the check involves a real transfer, it proves far more than a format validation ever could: the account is open, it is not frozen, and it accepts credits. That makes it the standard pre-payout check for lenders, insurers and marketplaces settling money to customers. Use cases: - Verifying a borrower's account before loan disbursal - Onboarding sellers who will receive marketplace settlements - Validating refund and insurance claim accounts - Meeting internal controls that require proof an account accepts credits Q: Who pays the one rupee? A: The transfer originates from FastKYC's pooled account, not yours. You are billed per verification, not per rupee transferred. Q: What happens if the account is closed or frozen? A: The credit fails and the API returns the failure reason from the bank, which is itself a useful signal: the account is not fit to receive a payout. Q: How is this different from penny-less verification? A: Penny drop moves money and so proves the account can actually receive funds. Penny-less confirms the account exists using network data without a transfer, which is faster and cheaper but slightly narrower in coverage. ## Bank Verification Pennyless API URL: https://fastkyc.com/apis/bank-verification-pennyless/ Validate an Indian bank account and fetch the account holder name without transferring any money, using real-time banking network data. Penny-less verification confirms an account number and IFSC without moving a single rupee. Instead of depositing a token amount, it queries banking network records directly and returns the registered account holder name and branch details. The absence of a transfer makes it faster and cheaper than a penny drop, and it avoids leaving small credits scattered across customer statements. It is the better default for high-volume onboarding, with penny drop reserved for the accounts it cannot confirm. Use cases: - High-volume account validation during customer sign-up - Pre-screening accounts before committing to a penny drop - Verifying accounts where a stray credit would confuse the customer - Bulk cleaning of an existing beneficiary database Q: Is it as accurate as a penny drop? A: For accounts it can resolve, the name it returns comes from the same banking records. The difference is coverage: some accounts cannot be confirmed without an actual transfer, and those need a penny drop. Q: Does the customer see anything? A: No. Nothing is credited or debited, so nothing appears on their statement. Q: Can I use it for payouts? A: Yes, though it does not prove the account currently accepts credits. Where that matters, such as a first high-value disbursement, a penny drop is the stronger check. ## IFSC Search API URL: https://fastkyc.com/apis/ifsc-search/ Look up any Indian bank branch by IFSC code and get the bank name, branch, address, city and supported payment rails in one call. IFSC Search resolves an eleven-character IFSC code into full branch details: bank name, branch name, postal address, city, district and state, along with which payment systems the branch supports. It is most useful as a front-end aid. Resolving the IFSC as soon as a customer types it lets you show the branch name back to them for confirmation, which catches transposed characters before they turn into a failed transfer. Use cases: - Auto-filling branch details on a bank account form - Confirming the branch back to the user before they submit - Validating IFSC codes in a bulk beneficiary upload - Checking whether a branch supports NEFT, RTGS or IMPS Q: Does this verify the account itself? A: No. It resolves the branch behind an IFSC code only. Use bank account verification to confirm a specific account number and its holder. Q: How current is the branch data? A: It is sourced from the central IFSC directory, so branch merges and renames are reflected as the registry is updated. Q: What happens with an invalid code? A: The API returns a not-found result rather than a guess, which you can surface as an inline validation error on the form. ## Mobile to Bank API URL: https://fastkyc.com/apis/mobile-to-bank/ Find the bank accounts linked to an Indian mobile number, so customers can confirm an existing account instead of typing one in. Mobile to Bank returns the bank accounts associated with a given mobile number, drawing on records that link phone numbers to banking relationships. It turns a long, error-prone form field into a confirmation step. This shortens onboarding noticeably. Rather than asking a customer to find their cheque book and type a sixteen-digit account number, you present the account you already resolved and ask them to confirm it. Use cases: - Pre-filling bank details during digital lending journeys - Reducing drop-off on account entry in mobile-first flows - Cross-checking a declared account against ones already linked to the customer - Detecting when an applicant supplies an account with no history against their number Q: Do I need the customer's consent? A: Yes. This returns financial information tied to an individual, so collect and record explicit consent before you query it. Q: Will it always find an account? A: No. Coverage depends on the number being linked in the source records. Treat a nil result as inconclusive rather than as evidence the customer has no bank account. Q: Does it confirm the account is active? A: Not on its own. Follow it with a penny-drop or penny-less verification if you intend to send money to the account. ## Penny Drop Initialize API URL: https://fastkyc.com/apis/penny-drop-initialize/ Start an asynchronous penny-drop verification and receive a reference ID you can poll, built for bulk and queue-based account checks. Penny Drop Initialize begins a verification without waiting for the bank to respond. You submit the account number, IFSC, expected holder name and amount, and immediately receive a reference ID. Splitting initiation from the result suits batch processing: you can queue thousands of accounts without holding open connections, then collect outcomes with Penny Drop Verify as they settle. Interbank transfers can take time, and this pattern stops that latency blocking your own workers. Use cases: - Queueing overnight verification of a large beneficiary file - Verifying accounts from a background worker rather than a web request - Handling banks whose responses are too slow for a synchronous call - Building a retry-safe verification pipeline Q: How long should I wait before checking the result? A: Most verifications settle within seconds, but interbank timing varies. Poll with a short backoff rather than a fixed delay, and treat pending as a normal intermediate state. Q: How long is the reference ID valid? A: Long enough to cover any realistic settlement window. Store it against your own record so a result is never orphaned. Q: Can I use the synchronous version instead? A: Yes. Bank Verification Penny Drop performs the same check in a single call and suits interactive flows where the customer is waiting. ## Penny Drop Verify API URL: https://fastkyc.com/apis/penny-drop-verify/ Fetch the outcome of an asynchronous penny drop using its reference ID and get the verification result with the account holder name. Penny Drop Verify completes the asynchronous flow. You supply the reference ID returned by Penny Drop Initialize, along with the amount, and receive the settled result: whether the credit succeeded and the account holder name as recorded by the bank. Results are idempotent, so polling the same reference more than once is safe and returns the same outcome. That makes the pairing straightforward to build a reliable, retry-tolerant pipeline around. Use cases: - Collecting results for a batch of queued verifications - Reconciling verification outcomes against your own records - Driving a webhook or state machine from settled results - Auditing which accounts passed name-match before disbursal Q: What if the result is still pending? A: The API says so explicitly. Keep polling with a backoff; a pending state means the bank has not settled the credit yet, not that the account has failed. Q: Is it safe to call more than once? A: Yes. The call is read-only against a settled verification and returns the same result each time, so retries cannot trigger a second transfer. Q: Does it perform the name match for me? A: It returns the bank's recorded name. Comparing that against your own record is your decision, since acceptable tolerance for initials and spelling varies by policy. ## VPA to Account Details API URL: https://fastkyc.com/apis/vpa-to-account/ Resolve a UPI VPA to its underlying bank account and holder name, verifying a payment address before you settle money to it. VPA to Account Details takes a UPI virtual payment address, such as name@bank, and returns the bank account behind it along with the registered holder name. For any business paying out over UPI, this closes a real gap. A VPA is easy to mistype and gives no visual clue about who owns it, so resolving it to a named account before the first payout prevents money reaching the wrong person. Use cases: - Verifying a UPI handle before a first payout - Matching a VPA owner against a customer record you already hold - Validating collected VPAs in bulk before a settlement run - Detecting handles that no longer resolve to an active account Q: Does resolving a VPA move any money? A: No. It is a lookup against UPI records and involves no transaction. Q: What if the VPA does not exist? A: The API returns a not-found result, which is a strong signal the handle was mistyped or has been deactivated. Q: Can I go the other way, from a mobile number to a VPA? A: Yes. Mobile to VPA maps a number to its associated UPI handle and account holder name. --- # Employment ## Employment overview URL: https://fastkyc.com/apis/employment/ Employment verification APIs built on EPFO records: UAN lookups, full employment history and current employer checks for lenders and HR teams. ## Current Employment Details API URL: https://fastkyc.com/apis/current-employment-details/ Confirm where someone works right now, including employer name, role, employment type and length of service, from provident fund records. Current Employment Details answers the question underwriters ask first: is this applicant employed, and by whom. It returns the present employer, the role on record, the employment type and how long the person has been in the job. Because it draws on provident fund filings rather than documents the applicant supplies, it is resistant to the forged offer letters and edited payslips that turn up regularly in lending applications. Use cases: - Confirming employment before approving a salaried loan - Checking job stability and tenure in credit decisioning - Screening candidates during background verification - Validating a declared employer against an independent source Q: How current is the data? A: It reflects the most recent provident fund filing, so it lags by up to a monthly cycle. Someone who started a job days ago may not appear yet. Q: Does it cover everyone who is employed? A: No. It covers employees whose employers file provident fund contributions. Contractors, gig workers and staff at very small firms often will not appear. Q: Does it show salary? A: Not directly. It returns employment facts; contribution amounts visible through the passbook endpoints give an indirect signal of salary band. ## EPFO Advanced Details API URL: https://fastkyc.com/apis/epfo-init-status/ Fetch detailed EPF passbook data by UAN without an OTP, including employer contribution history, service records and personal details. EPFO Advanced Details returns the substance of an employee's provident fund record: the UAN-linked profile, contribution history across employers, personal details and service records, all without requiring an OTP round trip. Skipping the OTP removes the main source of drop-off in employment verification, since it does not depend on the applicant still controlling their EPFO-registered mobile number. Confirm your consent model supports it before you rely on it in production. Use cases: - Verifying employment where OTP-based consent causes drop-off - Pulling contribution history for income assessment - Reconstructing service records during background checks - Cross-checking declared salary against contribution levels Q: How is this different from the OTP flow? A: It returns comparable data without the OTP step. The trade-off is the consent trail: the OTP flow proves the individual authorised the lookup at that moment. Q: Do I still need consent? A: Yes. This is personal financial data. Collect and record consent through your own flow even though the API does not enforce an OTP. Q: What do contributions tell me about salary? A: Provident fund contributions are a fixed proportion of basic pay, so they give a reliable signal of salary band, though not an exact figure. ## EPFO Basic Search API URL: https://fastkyc.com/apis/epfo-basic-search/ Look up an EPFO establishment by its ID and get organisation details plus a month-by-month summary of provident fund contributions. EPFO Basic Search examines the employer rather than the employee. Given an establishment ID, it returns the organisation's registered details and a monthly summary of its provident fund transactions over a period you choose. The contribution trend is the useful signal. A steadily filing establishment with a stable headcount looks very different from one whose contributions stopped abruptly, and that difference matters when you are lending to a business or verifying that an employer genuinely operates. Use cases: - Assessing an employer's health during business lending - Estimating headcount and payroll trend from contribution data - Confirming an establishment actively files provident fund returns - Screening an employer named on a salaried loan application Q: How many months can I request? A: You specify the window, so you can pull a short recent view or a longer run to see the trend. Q: Does it identify individual employees? A: No. It reports at establishment level. Use the employee endpoints, with consent, for individual records. Q: Can I search by company name instead? A: Use EPFO Name Search to check whether a named individual works at a given company. This endpoint keys on the establishment ID. ## EPFO Generate OTP API URL: https://fastkyc.com/apis/epfo-generate-otp/ Send an OTP to the employee's EPFO-registered mobile number to begin a consented provident fund verification of their employment and UAN details. This is the first step of a consent-based EPFO check. It sends a one-time password to the mobile number the employee has registered with the Employees' Provident Fund Organisation, establishing that the person authorising the lookup controls that number. Consent matters here because provident fund records reveal employment and salary history. Pair this with EPFO Submit OTP to complete authentication before pulling any passbook data. Use cases: - Starting a consented employment check during loan underwriting - Verifying an employee's own EPFO record in a self-service portal - Establishing mobile ownership before releasing salary history Q: Which number receives the OTP? A: The mobile number registered against the employee's UAN with EPFO. If they no longer control that number, the check cannot proceed and they must update it with EPFO first. Q: How long is the OTP valid? A: It expires after a few minutes, following EPFO's own rules. Generate a fresh one rather than retrying an expired code. Q: Is there a way to check EPFO without an OTP? A: Yes. EPFO Advanced Details returns passbook information without OTP verification, where your use case and consent model allow it. ## EPFO Name Search API URL: https://fastkyc.com/apis/epfo-name-search/ Check whether a named individual is employed at a specific company using EPFO provident fund filings, without needing their UAN. EPFO Name Search answers a narrow but common question: does this person actually work at the company they say they do. It checks the name against provident fund filings for that employer. The advantage is that it needs neither a UAN nor an OTP, just a name and an employer. That makes it usable at the top of a screening funnel, where you want a quick signal before deciding whether a deeper, consented check is worth running. Use cases: - Quickly testing an employment claim during screening - Flagging applications that name an employer with no matching record - Pre-qualifying applicants before a full employment check - Verifying employment where the applicant does not know their UAN Q: How exact does the name have to be? A: Matching tolerates ordinary variation, but records filed under a different spelling or a maiden name may not match. Treat a nil result as inconclusive, not as proof of a false claim. Q: Does it return salary or dates? A: No. It confirms the employment relationship. Use Employment History or Current Employment Details for dates and depth. Q: Is consent required? A: You are querying an individual's employment status, so follow your usual consent and notice obligations even though no OTP is involved. ## EPFO Submit OTP API URL: https://fastkyc.com/apis/epfo-submit-otp/ Validate the EPFO one-time password and complete authentication, unlocking access to the employee's provident fund records. This completes the consented EPFO flow. Submit the OTP the employee received and the API confirms whether authentication succeeded. A successful response is your audit trail: it records that the person holding the registered mobile number authorised the lookup, which is the evidence you want on file if the employment check is later questioned. Use cases: - Completing consent capture before pulling provident fund data - Recording proof of authorisation for an audit trail - Gating salary history behind verified mobile ownership Q: What if the employee enters the wrong OTP? A: The API returns a failure and the flow does not proceed. Allow a retry, and generate a new OTP if the original has expired. Q: Does this return the provident fund data itself? A: No. It confirms authentication. Fetch records with the employment history or EPFO detail endpoints once authentication has succeeded. Q: How long does authentication stay valid? A: Treat it as valid for the immediate session only. Re-authenticate for a later lookup rather than reusing an old consent. ## Employment History API URL: https://fastkyc.com/apis/employment-history/ Retrieve an individual's full employment history from their UAN, with every employer, joining date and exit date on provident fund record. Employment History returns the sequence of jobs recorded against a Universal Account Number: each employer, the dates of joining and leaving, and the member details filed alongside them. The value is in the pattern rather than any single row. Gaps, very short stints and overlapping employers are all visible at a glance, and all of them are things a self-declared CV can quietly omit. Use cases: - Verifying a candidate's claimed career history - Assessing job stability for a credit decision - Spotting undisclosed gaps or overlapping employment - Confirming length of service for a loan eligibility rule Q: What is a UAN? A: The Universal Account Number is the permanent identifier EPFO issues to an employee. It stays with the person across employers, which is what makes a continuous history possible. Q: What if I only have a mobile number? A: Use Mobile to UAN first to resolve the number to a UAN, then call this endpoint. Q: Are jobs without provident fund coverage shown? A: No. Employment that never generated a provident fund filing leaves no record here, so the absence of a period is not proof the person was unemployed. ## Mobile to UAN API URL: https://fastkyc.com/apis/mobile-to-uan/ Find the Universal Account Numbers linked to an Indian mobile number, so an employment check can start from a phone number alone. Mobile to UAN resolves a mobile number to the Universal Account Numbers associated with it in EPFO and employment registry data. Most applicants do not know their UAN, and asking for it stalls the journey. Starting from the mobile number you already collected removes that step and lets the rest of the employment verification chain run. Use cases: - Starting an employment check without asking for a UAN - Resolving the identifier needed for employment history lookups - Detecting when an applicant has multiple UANs from past employers - Reducing form friction in salaried lending journeys Q: Can one person have several UANs? A: It happens, usually when an employer issues a new UAN instead of linking the existing one. The API returns what it finds, and multiple results are worth investigating. Q: What if no UAN is found? A: The number may not be the one registered with EPFO, or the person may never have had provident fund coverage. Treat it as inconclusive. Q: What comes next? A: Pass the UAN to Employment History for the full record, or to Current Employment Details for the present employer. --- # Finance ## Finance overview URL: https://fastkyc.com/apis/finance/ Financial verification APIs for lenders: CIBIL, Experian and CRIF credit reports, ITR and Form 26AS downloads, CKYC records and tax compliance checks. ## Bank Statement Analyzer API URL: https://fastkyc.com/apis/bank-statement-analyzer/ Analyse bank statements to extract financial insights, transaction patterns, balance trends and risk indicators automatically. Bank Statement Analyzer goes beyond extraction. It reads a statement and returns analysis: income patterns, expense behaviour, balance trends, and risk indicators such as bounced payments or circular transfers. This is what turns statement data into an underwriting decision. Identifying which credits are genuine recurring salary, and which are transfers dressed up to look like income, is precisely the judgement that manual review does slowly and inconsistently. Use cases: - Automated income assessment for lending - Detecting manipulated or artificially inflated statements - Cash-flow analysis for small business credit - Identifying bounced payments and financial stress signals Q: How does it differ from Bank Statement OCR? A: OCR extracts transactions as data. The analyzer interprets them, classifying income, flagging patterns and surfacing risk indicators. Q: Can it detect a doctored statement? A: It flags patterns consistent with manipulation, such as circular transfers or inconsistent balances. Treat those as signals for review, not conclusions. Q: Which risk indicators does it surface? A: Things like bounced payments, irregular income, sudden balance changes and transfer patterns that inflate apparent income. ## CKYC Download via OTP API URL: https://fastkyc.com/apis/ckyc-download/ Download a customer's complete Central KYC record after OTP consent, including verified identity and address data, to onboard without re-collecting documents. CKYC Download via OTP retrieves the full Central KYC record once the customer has authorised release through an OTP, returning verified identity details, address and associated document information. The data arrives already verified by whichever regulated institution originally performed the KYC. That is the whole point of the registry: verification work done once is reusable across the sector. Use cases: - Onboarding with pre-verified KYC data - Eliminating document upload for existing CKYC holders - Populating customer records from registry data - Reducing KYC processing cost and turnaround Q: How current is the record? A: It reflects the last update by the institution that maintains it. Long-standing records may carry a stale address. Q: Can I download without an OTP? A: No. Customer authorisation through OTP is required by the registry before release. Q: Does this replace my own KYC? A: It supplies verified data, but your own regulatory obligations and risk policy still determine what is sufficient. ## CKYC Generate OTP API URL: https://fastkyc.com/apis/ckyc-generate-otp/ Send an OTP to the customer's CKYC-registered mobile number to authorise download of their Central KYC record, the first step of a consented CKYC fetch. CKYC Generate OTP sends a one-time password to the mobile number registered against the customer's CKYC record, beginning the consent step required before the full record can be downloaded. The OTP is not a formality. CKYC records contain verified identity data, and the registry requires proof that the customer authorised its release before any institution can retrieve it. Use cases: - Capturing customer consent before a CKYC download - Meeting registry authorisation requirements - Verifying the customer controls the registered mobile number Q: Which number receives it? A: The mobile number recorded against the customer's CKYC record, which may differ from the one they just gave you. Q: What if the customer no longer has that number? A: They cannot complete the download and will need to update their record with the institution that created it. Fall back to standard document KYC. Q: What comes next? A: Pass the verified OTP to CKYC Download via OTP to retrieve the full record. ## CKYC Search API URL: https://fastkyc.com/apis/ckyc-search/ Search the Central KYC registry with an identity document and retrieve the customer's existing CKYC record, so returning customers skip repeat KYC. CKYC Search queries India's Central KYC Records Registry using a supported identity document and returns the customer's CKYC details where a record exists. A customer who has completed KYC with any regulated institution already has a CKYC record. Finding it means you can reuse verified data rather than repeating document collection, which is faster for you and considerably less irritating for them. Use cases: - Reusing existing KYC instead of collecting documents again - Speeding up onboarding for customers already in the system - Checking whether a customer holds a CKYC identifier - Reducing document handling and storage obligations Q: What is CKYC? A: The Central KYC Records Registry, a shared repository where regulated financial institutions record verified customer KYC so it can be reused across the sector. Q: Which documents can I search with? A: The supported identity documents accepted by the registry. PAN is the most commonly used starting point. Q: What if no record exists? A: The customer has not completed KYC with a participating institution, so you will need to collect and verify documents yourself. ## Credit Report CIBIL API URL: https://fastkyc.com/apis/credit-report-cibil/ Fetch a customer's CIBIL credit score and full credit report using their PAN and mobile number, for instant lending decisions. Credit Report CIBIL returns a borrower's TransUnion CIBIL score along with the detailed report behind it: existing loans and cards, repayment history, outstanding balances and recent enquiries. CIBIL is the most widely referenced bureau in Indian retail lending, and the score alone rarely tells the whole story. The account-level detail is what shows whether a thin file reflects a new borrower or a rebuilt one, and whether recent enquiries suggest someone shopping widely for credit. Use cases: - Instant credit decisioning in digital lending - Assessing existing obligations before approving a loan - Detecting credit-hungry behaviour from enquiry patterns - Periodic portfolio monitoring of existing borrowers Q: Does pulling a report affect the customer's score? A: Consented lending enquiries are recorded as hard enquiries and can have a small effect. Pull only when you have a genuine decision to make. Q: What consent is required? A: Explicit borrower consent, recorded and retrievable. Bureau access without it is a serious compliance breach. Q: Which bureau should I use? A: Coverage differs between CIBIL, CRIF and Experian, particularly for thin-file borrowers. Many lenders check more than one before declining. ## Credit Report Crif API URL: https://fastkyc.com/apis/credit-report-crif/ Retrieve a comprehensive CRIF credit report with score, loan accounts, enquiry history and personal details for risk assessment. Credit Report Crif returns a CRIF High Mark report: the credit score, individual loan accounts with repayment history, enquiry records and the personal details held on the borrower. CRIF is notably strong in microfinance and rural lending, where borrowers often have limited presence in other bureaus. For lenders serving those segments it frequently surfaces obligations that would otherwise go unseen. Use cases: - Credit assessment in microfinance and rural lending - Cross-checking a thin file against a second bureau - Identifying group lending exposure - Building a fuller obligations picture before approval Q: When is CRIF the better choice? A: Where borrowers are likely to have microfinance or rural credit history, CRIF often has deeper coverage than the alternatives. Q: Should I check more than one bureau? A: For borderline or thin-file applications, yes. Bureaus do not see identical data, and a second pull can change the decision. Q: What does the enquiry history show? A: Recent applications for credit. A cluster of enquiries in a short window suggests the borrower is seeking credit from several lenders at once. ## Credit Report Experian API URL: https://fastkyc.com/apis/credit-report-experian/ Get a complete Experian credit report and score with account history, enquiries, employment information and derived attributes. Credit Report Experian returns the borrower's Experian score alongside personal details, account history, enquiry records, employment information and a set of derived credit attributes. The derived attributes are what set this report apart. Rather than leaving you to compute utilisation trends and delinquency patterns from raw accounts, it supplies them ready to feed into a scorecard. Use cases: - Credit decisioning with pre-computed risk attributes - Feeding derived variables into an underwriting model - Cross-bureau verification on borderline applications - Monitoring portfolio risk over time Q: What are derived attributes? A: Computed indicators such as utilisation trends and delinquency patterns, supplied alongside the raw accounts so your scorecard does not have to derive them. Q: How does it differ from V2? A: Credit Report Experian V2 is the newer implementation of the same report. Prefer V2 for new integrations. Q: Is employment information included? A: Where the bureau holds it, though it reflects what lenders reported and can be dated. Verify separately if it matters to the decision. ## Credit Report Experian V2 API URL: https://fastkyc.com/apis/credit-report-experian-v2/ The current Experian credit report endpoint for lenders, returning credit score, account history, enquiries and derived attributes for loan underwriting. Credit Report Experian V2 is the current implementation of the Experian report, returning the score, personal details, account history, enquiry records, employment information and derived credit attributes. Functionally it matches the original endpoint. New integrations should use this version, and existing ones should plan to move, since it is where ongoing improvements land. Use cases: - New lending integrations requiring Experian data - Migrating from the original Experian endpoint - Credit decisioning with derived risk attributes - Cross-bureau checks on marginal applications Q: Should I use V2 or the original? A: V2 for anything new. The original remains available for existing integrations but V2 is the version being maintained. Q: Is the response shape identical? A: Comparable but not guaranteed identical. Test against V2 rather than assuming your existing parser works unchanged. Q: Does it need separate consent? A: The same borrower consent obligations apply. Switching version does not change what you owe the customer. ## ITR Compliance API URL: https://fastkyc.com/apis/itr-compliance/ Check PAN-based tax compliance including Aadhaar linkage, PAN status and Section 206AB classification for TDS decisions. ITR Compliance returns the compliance position attached to a PAN: whether it is linked to Aadhaar, its current status, and its classification under Section 206AB. The 206AB classification carries direct financial consequences. Non-filers attract TDS at a higher rate, and deducting at the wrong rate leaves the deductor exposed, which makes this a routine pre-payment check. Use cases: - Determining the correct TDS rate before a payment - Checking PAN-Aadhaar linkage for compliance - Screening vendors for non-filer status - Avoiding short-deduction notices Q: What is Section 206AB? A: A provision requiring higher TDS rates for specified persons who have not filed returns. The classification tells you which rate applies. Q: Why does Aadhaar linkage matter? A: An unlinked PAN can become inoperative, which affects transactions and TDS treatment. Q: How often should I check? A: Before significant payments, and periodically across your vendor base, since status changes as filings are made. ## ITR Download API URL: https://fastkyc.com/apis/itr-file-download/ Retrieve a taxpayer's income tax return information, including filing history, status and secure document links, to verify income for lending. ITR Download returns detailed income tax return information for a client: which returns have been filed, their status, and secure links to the documents themselves. For income verification this is considerably stronger than a payslip. Returns are filed with the tax authority under penalty for misstatement, which makes them far harder to fabricate than a document an employer prints. Use cases: - Verifying declared income for a loan application - Assessing self-employed and business income - Confirming filing history during underwriting - Collecting return documents for a credit file Q: Does this need the taxpayer's consent? A: Yes. Tax records are sensitive personal financial data; obtain and record explicit consent. Q: Which years are available? A: Filing history across assessment years, subject to what the tax portal holds for that taxpayer. Q: Why prefer ITR over payslips? A: Returns are filed with the tax authority and carry legal consequences for misstatement. Payslips are produced by the employer and are trivially forged. ## ITR Download Form 26as API URL: https://fastkyc.com/apis/itr-download-26as/ Fetch Form 26AS tax credit statements across assessment years with secure download links for each TDS record, to verify a borrower's declared income. ITR Download Form 26as retrieves a taxpayer's Form 26AS across assessment years, with download links for each record. Form 26AS is the consolidated tax credit statement showing tax deducted at source, advance tax and high-value transactions reported against the PAN. Because the entries come from deductors rather than the taxpayer, it independently corroborates declared income. Use cases: - Corroborating declared income against TDS records - Identifying income sources the applicant did not disclose - Verifying tax credits during underwriting - Building an independent income picture Q: What does 26AS contain? A: Tax deducted at source by employers and others, advance tax paid, refunds, and certain high-value transactions reported against the PAN. Q: Why is it useful for lending? A: The entries are reported by third parties, so it can reveal income streams a borrower omitted from their application. Q: How does it compare to AIS? A: AIS is broader, covering a wider set of reported financial transactions. 26AS centres on tax credits. ## ITR File Download V API URL: https://fastkyc.com/apis/itr-file-download-v/ Retrieve a taxpayer's filing history with downloadable ITR-V acknowledgement documents for each assessment year, as proof of income tax filing. ITR File Download V returns the client's filing history along with downloadable ITR-V documents for each assessment year. The ITR-V is the acknowledgement the tax department issues on filing. It is the standard document lenders ask for as proof of income, and having it retrievable directly removes a back-and-forth with the applicant. Use cases: - Collecting ITR-V acknowledgements for a loan file - Documenting income proof in an audit trail - Verifying returns were actually filed and acknowledged - Gathering multi-year income documentation Q: What is an ITR-V? A: The acknowledgement generated when a return is filed. It confirms the filing took place and summarises what was declared. Q: How does this differ from ITR Download? A: This focuses on ITR-V acknowledgement documents per assessment year. ITR Download returns broader filing information. Q: Is an ITR-V proof of income? A: It evidences what was declared and acknowledged, which is what lenders generally require. ## ITR get AIS API URL: https://fastkyc.com/apis/itr-get-ais/ Retrieve Annual Information Statement documents with year-wise PDF links, showing the financial transactions reported against a taxpayer's PAN. ITR get AIS returns Annual Information Statement documents with year-wise links. The AIS consolidates financial transactions reported to the tax department against a taxpayer. It reaches considerably wider than Form 26AS, taking in interest income, dividends, securities transactions and high-value purchases. For assessing someone's true financial position it is among the most complete single sources available. Use cases: - Comprehensive income verification for lending - Identifying undisclosed income sources - Assessing investment activity and net worth signals - Cross-checking declared finances against reported transactions Q: What does AIS include beyond 26AS? A: Interest income, dividends, securities transactions, high-value purchases and other reported financial activity, not just tax credits. Q: Is it always accurate? A: Entries are reported by third parties and taxpayers can dispute them, so treat individual lines as indicative rather than definitive. Q: What consent is needed? A: Explicit consent. AIS is among the most revealing financial documents available about an individual. ## ITR get Profile Details API URL: https://fastkyc.com/apis/itr-get-profile-details/ Fetch a taxpayer's profile from the income tax portal, including PAN details, contact information, address and jurisdiction. ITR get Profile Details returns the profile the tax department holds for a taxpayer: PAN information, registered contact details, address and assessing jurisdiction. Because these details are maintained with the tax authority rather than self-declared on your form, they make a useful independent cross-check on the identity and address a customer has given you. Use cases: - Cross-checking declared address against tax records - Confirming contact details from an independent source - Verifying PAN details during onboarding - Identifying the assessing jurisdiction for tax matters Q: How current is the profile? A: It reflects what the taxpayer maintains on the portal, which can lag reality if they have not updated after moving. Q: Is the address reliable as proof? A: It is a useful corroboration rather than primary proof, since it is maintained by the taxpayer themselves. Q: What is jurisdiction used for? A: It identifies the assessing officer and circle handling the taxpayer, which matters for tax correspondence. ## ITR get TIS API URL: https://fastkyc.com/apis/itr-get-tis/ Retrieve Taxpayer Information Summary documents with year-wise PDF links, summarising a taxpayer's reported income by category for income checks. ITR get TIS returns Taxpayer Information Summary documents year by year. The TIS is the condensed companion to the AIS, aggregating reported information into income categories. Where the AIS lists every reported transaction, the TIS gives the totals. For underwriting that needs an income picture rather than a transaction ledger, it is the faster read. Use cases: - Getting a summarised income view for underwriting - Comparing category totals against declared income - Faster income assessment where transaction detail is unnecessary - Supporting documentation in a credit file Q: How does TIS differ from AIS? A: TIS aggregates into income categories; AIS lists the underlying reported transactions. TIS is the summary view. Q: Which should I use? A: TIS when you need totals quickly, AIS when the composition of income matters or you are investigating. Q: Is it consent-based? A: Yes, with the same obligations as any other tax record. ## Mobile to GST API URL: https://fastkyc.com/apis/mobile-to-gst/ Find GST identification numbers linked to a mobile number, validated across government and financial registration databases. Mobile to GST resolves a mobile number to any GSTINs registered against it, checking government and financial registration records. For merchant onboarding this removes a form field that customers routinely get wrong. It also surfaces registrations a merchant did not mention, which is worth knowing before you set a credit limit. Use cases: - Onboarding merchants without asking for a GSTIN - Discovering undisclosed business registrations - Pre-filling business details from a phone number - Cross-checking a declared GSTIN against the merchant's number Q: What if no GSTIN is found? A: The number may not be registered against any GST record, or the business may not be registered at all. Treat it as inconclusive. Q: Can one number return several GSTINs? A: Yes, where the business operates in multiple states, since GST registration is state-wise. Q: How do I verify the GSTIN itself? A: Pass it to GST Verification or GST Advanced for registration status and compliance detail. ## SEBI Debarr Verify API URL: https://fastkyc.com/apis/sebi-records/ Fetch SEBI and NSE regulatory records for a PAN, checking whether an individual is debarred from securities markets before onboarding or investing. SEBI Debarr Verify checks a PAN against SEBI and NSE regulatory records and reports any debarment or regulatory action associated with it. For any business dealing in securities this is a mandatory screen. Onboarding a debarred individual is a regulatory breach in itself, quite apart from the risk the debarment was intended to signal. Use cases: - Screening clients before broking or investment onboarding - Checking directors and promoters for regulatory action - Meeting compliance obligations in securities businesses - Periodic re-screening of an existing client base Q: What does a hit mean? A: The PAN is associated with regulatory action or debarment. Treat it as blocking pending compliance review. Q: Who should be screened? A: Clients in securities-related businesses, and typically the directors and promoters of corporate clients too. Q: How often should screening run? A: At onboarding and periodically thereafter, since regulatory actions arise after a relationship begins. ## Search ISIN Record API URL: https://fastkyc.com/apis/isin-record/ Validate an ISIN and retrieve the security's current status and details, for securities, demat and investment workflows that depend on the right instrument. Search ISIN Record validates an International Securities Identification Number and returns the security's details and current status. The ISIN uniquely identifies a security globally, which makes it the right key for confirming that an instrument being traded, pledged or held is the one everyone believes it to be. Use cases: - Validating securities in a trading or custody workflow - Confirming instrument details before a pledge - Checking whether a security is active or suspended - Reconciling holdings against instrument records Q: What is an ISIN? A: A twelve-character code that uniquely identifies a security internationally, covering equities, bonds and other instruments. Q: Does it give a price? A: No. It returns identification and status. Market data comes from a separate feed. Q: Why does status matter? A: Suspended or delisted securities cannot be traded or pledged normally, so status changes what actions are valid. ## Tan Validation Basic API URL: https://fastkyc.com/apis/tan-validation-basic/ Validate a TAN and retrieve the associated taxpayer details, confirming an entity is authorised to deduct tax at source. Tan Validation Basic checks a Tax Deduction and Collection Account Number and returns the taxpayer details registered against it. Any entity deducting tax at source must hold a valid TAN, and it appears on every TDS certificate they issue. Verifying it confirms the deductor is genuine and that the certificates they provide are meaningful. Use cases: - Verifying a deductor before accepting TDS certificates - Confirming an employer's TAN during employment checks - Validating vendor tax registration details - Reconciling TDS entries against the deducting entity Q: What is a TAN? A: A ten-character identifier required for anyone deducting or collecting tax at source. It differs from PAN, which identifies the taxpayer. Q: How does this differ from TAN Validation? A: Both validate a TAN and return taxpayer details. Choose based on the response depth your workflow needs. Q: Why verify a TAN? A: An invalid or fabricated TAN means any TDS certificate carrying it is worthless, and the deduction may never have reached the tax department. --- # Identity ## Identity overview URL: https://fastkyc.com/apis/identity/ Identity verification APIs for India: PAN, Aadhaar, passport, driving licence, voter ID and vehicle RC checks, plus mobile, email and court record lookups. ## Aadhaar Validation API URL: https://fastkyc.com/apis/aadhaar-validation/ Verify an Indian Aadhaar number instantly and confirm it is valid and in use, with essential identity insights for faster, safer customer onboarding. Aadhaar Validation checks an Aadhaar number and returns the identity insights available against it, confirming the number is well-formed and recognised. Aadhaar is the most widely held identity credential in India, which makes it the natural anchor for onboarding. Validating the number before the rest of your flow depends on it prevents effort being spent on a typo or a fabricated digit string. Use cases: - Validating Aadhaar at the start of a KYC journey - Confirming a number before running document verification - Screening for fabricated Aadhaar numbers - Cleaning Aadhaar data in an existing customer base Q: Does this expose the full Aadhaar details? A: It returns essential insights, not a full demographic dump. UIDAI restricts what can be shared, and full eKYC requires a different, consent-based route. Q: What are my storage obligations? A: Avoid storing full Aadhaar numbers without a lawful basis. Use Aadhaar Masking so only the last four digits are retained. Q: How do I get a cryptographically verifiable check? A: Use Aadhaar XML Verification, which validates UIDAI's digital signature on an offline eKYC file. ## Aadhaar XML Verification API URL: https://fastkyc.com/apis/aadhaar-xml-verification/ Verify an offline Aadhaar eKYC XML by validating UIDAI's digital signature and extracting identity, address and photograph. Aadhaar XML Verification takes a UIDAI offline eKYC file, validates the digital signature on it, and extracts the identity details, address and embedded photograph it contains. This is the strongest Aadhaar check available without connecting to UIDAI directly. Because the signature is cryptographic, a tampered file fails verification outright, which no amount of image editing can get around. Use cases: - High-assurance Aadhaar verification without a document photo - Extracting a verified photograph for face matching - Capturing a cryptographically proven address - Onboarding where document forgery is a real concern Q: Where does the customer get the XML file? A: They download it from the UIDAI portal, choosing a share code that protects the file. They provide both to you. Q: What does signature validation prove? A: That the file was issued by UIDAI and has not been altered since. It is far stronger evidence than a photograph of a card. Q: Can I use the photograph for face match? A: Yes, and it is a good source since it comes from a signed file rather than a resubmitted image. ## Blank Paper Validation API URL: https://fastkyc.com/apis/blank-paper-validation/ Detect whether an uploaded image is blank paper rather than a real document, catching failed captures before processing. Blank Paper Validation examines an uploaded image and reports whether it is plain blank paper rather than an actual document. It sounds trivial and it is quietly valuable. Blank or near-blank uploads are common, whether accidental or deliberate, and catching them at capture is far cheaper than letting them fail deep inside a verification pipeline. Use cases: - Rejecting empty uploads before OCR processing - Giving customers immediate feedback on a bad capture - Filtering junk submissions from a document queue - Reducing wasted processing on unusable images Q: Why is this needed? A: Blank uploads happen constantly, from misfires and from users trying to move past a mandatory step. Catching them at capture avoids confusing downstream failures. Q: Does it identify the document type? A: No. Use the KYC Document Classifier for that. This answers only whether there is a document present at all. Q: Where should it run? A: Immediately on upload, so the customer can retake the photo while they are still in the flow. ## Contact Details by GST API URL: https://fastkyc.com/apis/gst-to-contact-details/ Fetch the mobile number and email address registered against a GST number, giving you verified contact details for a business you are onboarding. Contact Details by GST returns the mobile number and email address registered against a GSTIN. These are the contact details the business gave the tax authority, which makes them more reliable than whatever appears on a website or was typed into your form. For merchant verification that difference matters. Use cases: - Obtaining verified contact details for a merchant - Cross-checking declared contacts against GST records - Reaching a business through registered channels - Detecting mismatches in merchant onboarding Q: Why trust these over declared details? A: They were registered with the tax authority, which carries consequences for misstatement, unlike a form field. Q: What does a mismatch indicate? A: The person onboarding may not be authorised to act for the business. Worth verifying before proceeding. Q: What consent applies? A: These are business contact details, but treat them under your normal purpose limitation and use them only for legitimate business contact. ## DIN Basic API URL: https://fastkyc.com/apis/din-basic/ Validate a Director Identification Number and retrieve the director's profile details from MCA records, confirming who actually runs a company. DIN Basic validates a Director Identification Number and returns the director profile registered against it. Every company director in India must hold a DIN, and it stays with the individual across appointments. That makes it the reliable key for confirming someone genuinely holds the directorship they claim. Use cases: - Verifying directorship claims during corporate onboarding - Confirming director identity for KYC - Screening directors before a business relationship - Validating DINs supplied in company documentation Q: What is a DIN? A: A unique identifier the Ministry of Corporate Affairs assigns to every individual appointed as a company director. It persists across companies. Q: How does this differ from DIN Verify? A: DIN Verify returns fuller information including linked entities, and accepts PAN or KID as well as DIN. Q: Can a DIN be disqualified? A: Yes. Directors can be disqualified under the Companies Act, which is exactly why the status is worth checking. ## DIN Verify API URL: https://fastkyc.com/apis/din-verify/ Retrieve detailed director information including personal details, DIN status and linked entities, using PAN, DIN or KID. DIN Verify returns a fuller director record: personal details, the current status of the DIN, and the entities the individual is linked to. It accepts a PAN, DIN or KID as the lookup key. The linked entities view is what makes this valuable for due diligence. Seeing every company an individual is involved with exposes group structures and conflicts that a single-company check would never reveal. Use cases: - Mapping an individual's full set of directorships - Identifying group structures behind a borrower - Checking DIN status for disqualification - Screening directors flexibly from PAN or DIN Q: Which identifier should I use? A: Whichever you have. PAN is often easiest since it is collected anyway; DIN is the most direct. Q: Why do linked entities matter? A: They expose the wider corporate group and any conflicts of interest that a single-company view would hide. Q: What does a disqualified status mean? A: The individual is barred from acting as a director. Treat it as a blocking finding pending compliance review. ## DIN to PAN API URL: https://fastkyc.com/apis/din-to-pan/ Find the PAN associated with a Director Identification Number, linking a director's corporate roles to their tax identity for KYB and due diligence. DIN to PAN resolves a Director Identification Number to the PAN of the individual holding it. It bridges the corporate registry and the tax world. Once you have the PAN behind a director, everything built on PAN becomes available: credit history, tax compliance and further identity verification. Use cases: - Linking a directorship to an individual's tax identity - Enabling credit checks on company directors - Cross-referencing corporate and personal records - Verifying a director's declared PAN Q: Why link DIN to PAN? A: It unlocks the PAN-based checks, from credit reports to tax compliance, for someone you have identified through the corporate registry. Q: Can I search the other way? A: Yes. PAN to DIN reveals the directorships held by an individual. Q: What consent applies? A: This links corporate and personal identity, so apply your usual consent and purpose limitation. ## DL Advanced API URL: https://fastkyc.com/apis/dl-advanced/ Extract complete driving licence data, including personal details, vehicle entitlements, validity and endorsements, for driver onboarding and KYC. DL Advanced returns the full driving licence record: personal details, every vehicle class held, validity periods and any endorsements recorded against the licence. Endorsements are the field that matters for commercial operators. They record hazardous goods permissions and similar authorisations, and assigning a driver work they are not endorsed for is a genuine liability. Use cases: - Full driver verification for commercial fleets - Checking hazardous goods and special endorsements - Comprehensive licence due diligence - Confirming complete vehicle entitlements before assignment Q: What are endorsements? A: Additional authorisations recorded on a licence, such as permission to carry hazardous goods. They matter for commercial assignment. Q: When should I use this over DL Basic? A: When entitlements and endorsements affect what work the person may legally do. Basic suffices for identity confirmation. Q: Does it show violation history? A: No. Use E-Challan Details for traffic violations, which are recorded against the vehicle. ## DL Basic API URL: https://fastkyc.com/apis/dl-basic/ Fetch driving licence status, holder name, vehicle classes and transport validity in one lightweight call, ideal for quick driver and customer checks. DL Basic returns the essentials of a driving licence: current status, holder name, the vehicle classes covered and the validity of both transport and non-transport entitlements. Separate transport and non-transport validity matters more than it might appear. A licence valid for private driving can be expired for commercial use, and only the transport validity tells you whether someone may legally drive for hire. Use cases: - Checking commercial driving entitlement for gig platforms - Confirming licence status quickly at onboarding - Verifying vehicle class before assigning work - Periodic re-checking of driver licences Q: What is transport versus non-transport validity? A: Non-transport covers private driving; transport covers commercial. They expire on different schedules, and only transport validity permits driving for hire. Q: How does this differ from DL Advanced? A: Advanced returns the complete record including endorsements. Basic covers status, name, classes and validity. Q: Do I need the date of birth? A: The Driving License endpoint uses date of birth as a second factor. Choose based on what your flow can collect. ## DigiLocker Download Docs API URL: https://fastkyc.com/apis/digilocker-download-docs/ Fetch verified documents from a customer's DigiLocker with their consent, for secure retrieval, verification and seamless KYC and onboarding integration. The DigiLocker Download Documents API enables businesses to securely download documents from a user's DigiLocker account after the required authorization. It provides access to eligible digital documents in the required format, making it easier to use them directly in KYC, onboarding, verification, and other document-based workflows. Use cases: - Collecting digital documents for loan and financial applications - Retrieving documents as part of KYC and customer onboarding - Supporting document verification and compliance workflows - Retrieving certificates and records for education and employment verification Q: Which documents and formats are supported? A: Depending on the document, it may be available in formats such as PDF or XML or JSON Q: Can I download a document immediately after the user completes authorization? A: Yes. Once the user completes the required authorization, the eligible document can be downloaded in real time. Q: Is authorization required for every document? A: No. Once the user completes the required authorization, the requested document can be downloaded within the authorized flow. ## Driving License API URL: https://fastkyc.com/apis/dl-text/ Verify an Indian driving licence using the licence number and date of birth, returning authenticated holder details for KYC and driver onboarding. Driving License verifies a licence number against transport department records, using the holder's date of birth as a second factor, and returns the authenticated details. Requiring the date of birth is a deliberate safeguard. It stops someone verifying a licence number they merely happen to know, which matters when the licence is being used as identity proof. Use cases: - Verifying identity using a driving licence - Onboarding drivers for fleet and delivery work - Confirming a licence is genuine and current - Using licence details as address proof Q: Why is date of birth required? A: It acts as a second factor, preventing lookups by someone who knows only the licence number. Q: Does it show vehicle classes? A: The authenticated record includes the entitlements held. DL Advanced returns the fullest breakdown. Q: What if the licence is expired? A: Validity dates come back with the record, so expiry is visible and can be handled by your policy. ## E-Aadhaar Verify API URL: https://fastkyc.com/apis/eaadhaar-upload/ Extract and verify Aadhaar details from an uploaded e-Aadhaar document, combining extraction with validation in one step. E-Aadhaar Verify accepts an uploaded e-Aadhaar document, extracts the identity details from it and verifies them. It suits flows where customers download their e-Aadhaar PDF rather than photographing a physical card, which is increasingly the norm and produces a much cleaner input than a phone camera. Use cases: - Onboarding customers who upload an e-Aadhaar PDF - Combining extraction and verification in one call - Avoiding the quality problems of card photographs - Processing e-Aadhaar documents already on file Q: How does this differ from OCR Aadhaar? A: OCR reads a card image and stops there. This handles the e-Aadhaar document and verifies the details as well as extracting them. Q: Is the e-Aadhaar password protected? A: Typically yes, using a scheme based on name and year of birth. Handle that before or during upload. Q: Which is strongest? A: Aadhaar XML Verification, because it validates a cryptographic signature rather than reading a rendered document. ## Ecourt CNR Search API URL: https://fastkyc.com/apis/ecourt-cnr-search/ Retrieve detailed court case information from an eCourt CNR number, covering case status, parties and hearing history, for litigation and risk checks. Ecourt CNR Search returns the case record behind a Case Number Record identifier: parties, current status and hearing history from the eCourts system. Litigation is a material risk factor that rarely surfaces voluntarily. For lending and corporate diligence, pending cases against a borrower or counterparty change the picture in ways their application will not mention. Use cases: - Checking litigation exposure during due diligence - Monitoring the progress of a known case - Screening counterparties for legal disputes - Assessing legal risk before extending credit Q: What is a CNR number? A: The Case Number Record, a unique identifier assigned to a case in the eCourts system that stays constant across hearings. Q: Does it cover High Courts? A: Use High Court Search for High Court cases. This endpoint targets the eCourts district system. Q: Does a pending case imply wrongdoing? A: No. It records that proceedings exist. Treat it as a factor for review, never as a finding. ## Email Check API URL: https://fastkyc.com/apis/email-check/ Verify an email address is legitimate and deliverable, filtering out disposable, invalid and undeliverable addresses before they enter your database. Email Check tests whether an email address is genuine and able to receive mail, identifying invalid, undeliverable and disposable addresses. Catching this at the point of entry prevents a compounding problem. An address that never receives your verification mail leaves the customer stuck and your database holding a record you can never reach. Use cases: - Validating email at sign-up before sending anything - Blocking disposable addresses in onboarding - Cleaning an existing mailing database - Protecting sender reputation from bounces Q: Does it prove the customer owns the address? A: No. It confirms the address is valid and deliverable. Ownership requires a confirmation link or OTP. Q: Why block disposable addresses? A: They expire quickly, so any account tied to one becomes unrecoverable, and they correlate with throwaway and fraudulent sign-ups. Q: How does it help deliverability? A: Repeated bounces damage sender reputation. Filtering bad addresses before sending protects your ability to reach real customers. ## Email Verification Send OTP API URL: https://fastkyc.com/apis/send-email-otp/ Send a one-time password to an email address to begin verifying the customer controls that inbox, the first step of email ownership verification. Email Verification Send OTP delivers a one-time password to the email address supplied, starting the verification of that address. Sending an OTP proves more than a format check ever could. It establishes that the address exists, accepts mail, and is being read by whoever is completing your flow. Use cases: - Verifying an email address at sign-up - Confirming an address change on an account - Establishing a reliable channel before sending statements Q: How long is the OTP valid? A: A short window. Generate a fresh one rather than asking the user to retry an expired code. Q: Should I check the address first? A: Yes. Email Check filters invalid and disposable addresses before you spend a send on them. Q: What comes next? A: Validate Email OTP confirms the code and completes verification. ## Esign Download Document API URL: https://fastkyc.com/apis/esign-download-docs/ Download completed Aadhaar eSign documents in Base64 format by document ID once every signature is collected, ready to store with the application. Esign Download Document retrieves the signed documents once execution is complete, returning them in Base64 form for storage or onward delivery. The signed document is the artefact that matters. It carries the signature certificates that make it legally enforceable, so retrieving and archiving it properly is the step that gives the whole flow its value. Use cases: - Archiving executed agreements - Delivering signed copies to customers - Storing signed mandates for compliance - Feeding executed documents into a document system Q: When can I download? A: Once signing is complete. Check with Esign Status Check before attempting retrieval. Q: What format is returned? A: Base64-encoded, which you decode and store in your own document repository. Q: How long should I retain it? A: For as long as the underlying agreement and your regulatory retention rules require. The signed copy is your evidence of execution. ## Esign Status Check API URL: https://fastkyc.com/apis/esign-status-check/ Check the live status of an Aadhaar eSign request and retrieve document and recipient signing details, so you know exactly who has signed and who hasn't. Esign Status Check reports where an eSign request has reached, including which recipients have signed and which are still outstanding. In multi-party signing this is what drives the process forward. Knowing precisely who has not yet signed lets you chase the right person rather than reminding everyone. Use cases: - Tracking signature progress on an agreement - Identifying which recipients still need to sign - Driving reminder workflows automatically - Reporting on pending documents Q: How often should I poll? A: Poll at a sensible interval, or drive your workflow from status transitions rather than a tight loop. Q: Can I see individual recipients? A: Yes. Recipient-level detail shows exactly who has signed and who has not. Q: What happens if someone never signs? A: The request stays incomplete. Handle expiry and cancellation in your own workflow policy. ## FASTAG History Verification API URL: https://fastkyc.com/apis/fastag-history/ Retrieve a vehicle's recent toll plaza activity from FASTag, giving a reliable snapshot of its movements over the past 72 hours for fleet and fraud checks. FASTAG History Verification returns the toll plazas a vehicle has passed through recently, covering roughly a 72-hour window. This is a genuine movement record rather than a claim. For logistics disputes, insurance claims and fleet monitoring, knowing where a vehicle actually was, and when, settles questions that paperwork cannot. Use cases: - Verifying vehicle movement in a logistics dispute - Corroborating location claims in an insurance claim - Monitoring fleet routes and utilisation - Confirming a consignment travelled the route claimed Q: How far back does it go? A: Around 72 hours, so it answers recent movement questions rather than providing a long-term history. Q: How precise is the location? A: It records toll plaza crossings, which gives points along a route rather than continuous tracking. Q: What are the privacy considerations? A: This is vehicle movement data. Use it for a legitimate documented purpose, with an appropriate basis where an individual is involved. ## Farmer Verification API URL: https://fastkyc.com/apis/farmer-verification/ Verify a farmer's identity and registration status using their Aadhaar number and state code, for agri lending, subsidies and rural onboarding. Farmer Verification confirms an individual's registration as a farmer using their Aadhaar number and state code, returning the registration status held on record. Agricultural credit, subsidies and insurance schemes all depend on this status. Verifying it against records rather than accepting a declaration is what keeps benefits reaching the people they were designed for. Use cases: - Verifying eligibility for agricultural credit - Confirming farmer status for subsidy schemes - Onboarding for crop insurance - Validating registration in agri-lending Q: Why is the state code needed? A: Farmer registration is maintained state-wise, so the code directs the lookup to the correct records. Q: What does verification confirm? A: That the individual is registered as a farmer in that state's records, which is the basis for scheme eligibility. Q: What if a farmer is not registered? A: They may still farm but cannot access registration-linked benefits. Treat it as an eligibility answer, not an identity failure. ## Fastag Lookup API URL: https://fastkyc.com/apis/fastag-lookup/ Retrieve FASTag information for a vehicle, including tag status and the details registered against it, for vehicle verification and fleet onboarding. Fastag Lookup returns the FASTag information held for a vehicle, including the tag's current status and registration details. For fleet operators this is operational rather than investigative. A blacklisted or inactive tag causes delays and penalties at toll plazas, and catching it before dispatch is considerably cheaper than dealing with it en route. Use cases: - Checking tag status before dispatching a vehicle - Managing FASTag across a commercial fleet - Verifying tag registration during vehicle onboarding - Identifying blacklisted or inactive tags Q: What does a blacklisted tag mean? A: The tag cannot be used for toll payment, commonly due to insufficient balance or a registration issue. It causes delays and penalties. Q: How does this differ from Fastag To RC? A: That endpoint maps a tag to a vehicle. This returns tag information for a vehicle. Q: Can I see toll history? A: Use FASTAG History Verification for recent toll plaza activity. ## Fastag To RC API URL: https://fastkyc.com/apis/fastag-to-rc/ Map a FASTag ID to its vehicle registration and return FASTag status alongside the vehicle details, linking a tag to the vehicle it is issued for. Fastag To RC resolves a FASTag identifier to the vehicle it is issued against, returning both the tag status and the vehicle's registration details. FASTag is mandatory for toll payment, so nearly every vehicle on a highway carries one. That makes the tag a practical secondary identifier when you need to confirm a vehicle from something other than its plate. Use cases: - Identifying a vehicle from its FASTag - Checking tag status alongside vehicle details - Verifying vehicle identity in fleet operations - Cross-checking a tag against the claimed vehicle Q: What is a FASTag? A: The RFID tag used for electronic toll collection on Indian highways. It is mandatory for most vehicles. Q: Does it show the account balance? A: It returns tag status and vehicle details. Fastag Lookup covers tag information more directly. Q: What does a mismatch mean? A: A tag registered to a different vehicle than claimed suggests a transferred tag or a misrepresented vehicle. Worth investigating. ## Generate E-Invoice API URL: https://fastkyc.com/apis/generate-e-invoice/ Generate a GST-compliant e-Invoice and receive the IRN, acknowledgement, signed invoice and QR code in one call, straight from your billing system. Generate E-Invoice creates a GST-compliant electronic invoice and returns the Invoice Reference Number, acknowledgement details, the digitally signed invoice and its signed QR code. Businesses above the turnover threshold must issue e-invoices, and an invoice without a valid IRN is not compliant. That has a direct consequence for the recipient: their input tax credit depends on it. Use cases: - Automating e-invoice generation in billing - Meeting GST e-invoicing obligations - Embedding compliance into an ERP workflow - Generating signed invoices with QR codes at scale Q: Who must issue e-invoices? A: Businesses above the prescribed turnover threshold, which has been lowered progressively. Check the current threshold against your turnover. Q: What is the IRN? A: The Invoice Reference Number, the unique identifier assigned when an invoice is registered. Without it the invoice is not compliant. Q: Why does the QR code matter? A: It carries the signed invoice details and allows verification of authenticity. ## Get 1A data API URL: https://fastkyc.com/apis/get-1a-data/ Retrieve GSTR-1A B2B invoice details for a GSTIN and return period, giving your GST reconciliation workflow the amendments a supplier has filed. Get 1A data returns the B2B invoice details filed under GSTR-1A for a given GSTIN and return period. GSTR-1A captures amendments to outward supplies. Pulling it into reconciliation catches corrections a supplier made after their original filing, which is exactly the sort of change that otherwise causes an unexplained mismatch. Use cases: - Reconciling amended supplier invoices - Tracking corrections to outward supply filings - Investigating mismatches in GST reconciliation - Automating input tax credit checks Q: What is GSTR-1A? A: The return capturing amendments to outward supplies previously reported. It records what changed after the original filing. Q: Why does it matter for reconciliation? A: Amendments explain differences between what you recorded and what the supplier ultimately reported. Q: What do I need to query it? A: The GSTIN and the return period. ## Get 2A Data API URL: https://fastkyc.com/apis/get-2a-data/ Retrieve GSTR-2A B2B invoice details by GSTIN and return period to reconcile input tax credit against what your suppliers have actually filed. Get 2A Data returns the GSTR-2A B2B invoice details for a GSTIN and return period. GSTR-2A is the auto-populated statement of inward supplies, built from what your suppliers filed. Reconciling purchases against 2A is how businesses protect their input tax credit. Where a supplier has not filed, the credit is at risk, and finding that early leaves time to chase them. Use cases: - Reconciling purchase records against supplier filings - Identifying suppliers who have not filed - Protecting input tax credit claims - Automating monthly GST reconciliation Q: What is GSTR-2A? A: An auto-populated statement of inward supplies, generated from the returns your suppliers filed. Q: How does it differ from 2B? A: 2A is dynamic and updates as suppliers file. 2B is a static monthly statement, which makes it the better basis for a fixed reconciliation. Q: What if an invoice is missing? A: The supplier has probably not filed it. Your input tax credit on that invoice is at risk until they do. ## Get 2B Data API URL: https://fastkyc.com/apis/get-2b-data/ Retrieve GSTR-2B ITC and reversal document details by GSTIN and return period, for accurate input tax credit computation and GST reconciliation. Get 2B Data returns GSTR-2B ITC reversal details for a GSTIN and return period. GSTR-2B is the static monthly statement used to determine eligible input tax credit. Because 2B is fixed for the period rather than updating continuously, it is what most businesses reconcile against. The reversal details matter because credit claimed and later reversed still affects the final position. Use cases: - Computing eligible input tax credit for a period - Tracking ITC reversals in reconciliation - Reconciling against a stable monthly statement - Automating credit computation in accounting Q: Why use 2B rather than 2A? A: 2B is static for the period, so reconciliation against it is reproducible. 2A keeps changing as suppliers file. Q: What is an ITC reversal? A: Credit previously claimed that must be reversed under the GST rules, which changes the net position for the period. Q: How often should I reconcile? A: Monthly, aligned to the return cycle, so problems surface while there is still time to act. ## Get 3B Data API URL: https://fastkyc.com/apis/get-3b-data/ Retrieve GSTR-3B summary return details for a GSTIN and return period, showing declared tax liability and credit for compliance and credit checks. Get 3B Data returns the GSTR-3B details filed for a GSTIN and return period. GSTR-3B is the summary return declaring tax liability and input tax credit claimed. Filing behaviour on 3B is a strong business health signal. A business that files consistently is operating and organised; extended gaps suggest distress, which is directly relevant if you are lending to them. Use cases: - Assessing a business borrower's filing consistency - Verifying declared turnover against filings - Reconciling summary returns against detailed records - Monitoring compliance across a supplier base Q: What is GSTR-3B? A: The monthly summary return in which a business declares its tax liability and the input tax credit it is claiming. Q: What does filing history reveal? A: Consistency of operations. Regular filings suggest an active business; gaps suggest distress or dormancy. Q: How does it relate to GST Advanced? A: GST Advanced summarises compliance behaviour. This returns the specific return data for a period. ## Get Company Details API URL: https://fastkyc.com/apis/cin-advance/ Get a company's full MCA profile including charges, compliance status and director details from its Corporate Identity Number. Get Company Details returns the Ministry of Corporate Affairs record behind a CIN: the company profile, registered charges, compliance status and the directors on record. Registered charges are the field most worth attention. They reveal existing security over the company's assets, which directly affects what any new lender can actually claim if things go wrong. Use cases: - Corporate due diligence before lending or partnership - Checking existing charges before taking security - Identifying directors and their other appointments - Confirming a company is compliant and active Q: What is a registered charge? A: Security created over company assets in favour of a lender. Existing charges limit what a new lender can claim, so they matter before extending credit. Q: Does it show whether the company is struck off? A: Yes, the status reflects the current registry position including struck-off and dormant companies. Q: How do I find the CIN? A: Company Name to CIN searches the registry by name if the customer does not have it. ## Get PAN Essentials API URL: https://fastkyc.com/apis/get-pan-essentials/ Retrieve a PAN holder's essential details, including name, date of birth and gender, to match a customer's identity against their PAN in seconds. Get PAN Essentials returns the core identity attributes held against a PAN: name, date of birth and gender. Date of birth is the field that makes this more useful than a name lookup. Names repeat constantly in India, and a name-plus-date-of-birth match is a far stronger identity assertion than either alone. Use cases: - Matching identity on name and date of birth together - Verifying age eligibility during onboarding - Cross-checking declared details against tax records - Reducing false matches on common names Q: Why include date of birth? A: It disambiguates common names. Name-only matching produces false positives at scale in a way that name plus date of birth does not. Q: Can I verify age with this? A: Yes, the date of birth supports age-based eligibility checks. Q: How does it differ from PAN Lite? A: PAN Lite returns the name alone. This adds date of birth and gender. ## High Court Search API URL: https://fastkyc.com/apis/high-court-search/ Retrieve High Court case details using an eCourt CNR number, covering parties, case status and hearing history, for litigation and due diligence checks. High Court Search returns case information from the High Court eCourts system using a CNR number, including the parties involved, current status and hearing history. High Court matters typically involve higher stakes than district cases, whether in value or in the seriousness of the issue, which makes them particularly relevant to corporate diligence and large credit decisions. Use cases: - Checking High Court litigation in corporate diligence - Monitoring significant cases involving a counterparty - Assessing legal exposure before a large transaction - Screening for appeals and writ petitions Q: How does this differ from Ecourt CNR Search? A: This targets High Court records; the other covers the district eCourts system. Which you need depends on where the case sits. Q: How complete is coverage? A: It follows what the eCourts system publishes, and completeness varies between High Courts. Q: Can I search without a CNR? A: The CNR is the lookup key here. Obtain it from case documents or the eCourts portal. ## I4C Check API URL: https://fastkyc.com/apis/i4c-check/ Check whether a mobile number is flagged as suspicious in the I4C cybercrime database, screening applicants for known fraud before you onboard them. I4C Check tests a mobile number against the Indian Cybercrime Coordination Centre database and reports whether it has been flagged in connection with cybercrime. This is one of the few checks that draws on actual reported crime rather than inference. A flagged number has featured in cybercrime complaints, which is a materially stronger signal than any behavioural heuristic. Use cases: - Screening numbers against reported cybercrime - Blocking known fraud numbers at onboarding - Adding a crime-reported signal to a risk engine - Investigating suspicious activity on an account Q: What does a flag mean? A: The number appears in cybercrime complaints recorded by I4C. It is a strong signal warranting rejection or escalation. Q: Should a flag block automatically? A: Most institutions treat it as blocking pending review. Decide deliberately and document the policy. Q: Does a clean result mean safe? A: No. It means the number has not been reported. Absence of a complaint is not evidence of good faith. ## ICSI Membership Verification API URL: https://fastkyc.com/apis/icsi-verify/ Verify an ICSI membership number and retrieve the company secretary's registered member details, confirming a CS is who they say they are. ICSI Membership Verification checks a membership number issued by the Institute of Company Secretaries of India and returns the registered member details. Company secretaries certify statutory filings and corporate compliance documents. Confirming that the person signing genuinely holds current membership is a basic control on documents you are relying upon. Use cases: - Verifying a company secretary's credentials - Confirming professional membership before engagement - Validating certification on statutory documents - Screening professionals in corporate services Q: Who is ICSI? A: The Institute of Company Secretaries of India, the statutory body governing company secretaries. Q: Why verify membership? A: Company secretaries certify statutory filings. A certification from someone without valid membership is worthless. Q: Does it show membership status? A: Yes, the registered member details include current standing. ## IP Quality Check API URL: https://fastkyc.com/apis/ip-quality-check/ Assess an IP address for risk, returning ASN, ISP, geographic location and indicators of malicious activity such as proxies, VPNs and abuse. IP Quality Check evaluates an IP address and returns its Autonomous System Number, ISP, geographic location and any indicators of malicious activity associated with it. The risk indicators are the operative output. An address associated with a VPN, proxy, hosting provider or known abuse is a meaningful signal, particularly when a customer's stated location contradicts where the connection appears to originate. Use cases: - Fraud screening at login and sign-up - Detecting VPN and proxy usage in onboarding - Flagging connections from hosting infrastructure - Adding network risk to a decision engine Q: Why does hosting infrastructure matter? A: Genuine consumers connect from residential or mobile networks. A connection from a data centre usually means automation or an anonymising service. Q: Should VPN use block a customer? A: Not on its own; plenty of people use VPNs legitimately. Weigh it with other signals rather than treating it as decisive. Q: How accurate is the location? A: Good at country level, approximate below that. Treat it as a signal, not proof. ## Indian Post Tracking API URL: https://fastkyc.com/apis/postal-tracking/ Track an India Post shipment by article number and get booking details, transit history and delivery status, for document and card delivery flows. Indian Post Tracking returns the current status of an India Post shipment along with its booking details and transit history. Where documents, cards or instruments are dispatched by post, delivery status becomes part of the onboarding record. Knowing an item reached the customer closes the loop on a step that otherwise sits unresolved. Use cases: - Tracking dispatched cards, cheque books and documents - Confirming delivery of physical KYC documents - Providing tracking visibility to customers - Investigating delayed or lost dispatches Q: What is the article number? A: The tracking identifier issued when the item is booked with India Post. Q: How current is the status? A: It reflects India Post's own scan records, which update as the item passes through their network. Q: Does delivery prove the customer received it? A: It confirms delivery to the address. Whether the intended person received it is a separate question. ## Initiate Esign Flow API URL: https://fastkyc.com/apis/initiate-esign/ Start an Aadhaar-based eSign flow by submitting documents and recipient details, so customers sign loan agreements and forms electronically. Initiate Esign Flow begins electronic signing. You submit the documents and the recipients who must sign, and the flow is created and sent for signature. Aadhaar-based eSign carries the same legal standing as a handwritten signature under the Information Technology Act. That is what allows loan agreements and mandates to be executed entirely remotely. Use cases: - Executing loan agreements without paper - Collecting signed mandates during onboarding - Remote signing of insurance proposals - Digitising any workflow that ends in a signature Q: Is an eSign legally valid? A: Aadhaar-based eSign is recognised under the Information Technology Act and carries the same standing as a handwritten signature. Q: How does the signer authenticate? A: Through Aadhaar-based authentication, which is what binds the signature to a verified identity. Q: What comes next? A: Track progress with Esign Status Check and retrieve the executed documents with Esign Download Document. ## MNV Without OTP API URL: https://fastkyc.com/apis/mnv-without-otp/ Verify an Indian mobile number and get subscriber and network details without sending an OTP, so customers are never interrupted during onboarding. MNV Without OTP returns subscriber and network details for a mobile number without sending a message or requiring any user action. The trade-off is explicit. You lose proof that the person is holding the phone, but you gain a silent check that adds no friction, which suits background screening and validating numbers already on file. Use cases: - Silent validation of numbers in an existing database - Background fraud screening without user interaction - Checking a number before sending an OTP - Enriching records with network and subscriber details Q: How does this compare to OTP verification? A: OTP proves the customer controls the SIM. This confirms the number's details without proving possession, so it is weaker but frictionless. Q: When should I still use an OTP? A: Any time possession matters: account creation, high-value actions, or credential recovery. Q: What is the basic variant? A: MNV Without OTP Basic returns a lighter response for the same silent check. ## MNV Without OTP Basic API URL: https://fastkyc.com/apis/mnv-without-otp-basic/ Get essential subscriber and network details for a mobile number without an OTP, in a lightweight verification call built for high-volume checks. MNV Without OTP Basic performs the same silent mobile check in a lighter form, returning the essential subscriber and network details. It suits high-volume screening where you need a quick signal on many numbers and the fuller response would be more data than the decision uses. Use cases: - Bulk screening of a contact database - Lightweight number validation at scale - Quick network checks before messaging - Cost-efficient verification in high-volume flows Q: What is the difference from the full version? A: Response depth. Basic returns the essentials; the standard endpoint returns fuller subscriber and network detail. Q: Does it prove the customer holds the number? A: No. Only OTP verification establishes possession. Q: When does the lighter response matter? A: At volume, where cost and data minimisation both favour returning only what you will use. ## Mobile to Address API URL: https://fastkyc.com/apis/mobile-to-address/ Retrieve address details linked to a mobile number, aggregated from telecom, utility and financial data sources, to prefill and verify customer addresses. Mobile to Address returns the addresses associated with a mobile number, aggregating records from telecom, utility and financial sources. Addresses are the hardest field to collect accurately and the easiest to falsify. Having independently sourced addresses to compare against a declared one turns an unverifiable claim into something you can actually assess. Use cases: - Corroborating a declared address during onboarding - Pre-filling address fields to reduce drop-off - Detecting address mismatches in fraud screening - Supporting field verification decisions Q: How current are the addresses? A: They reflect what the source records hold, which can lag a recent move. Multiple addresses often represent a genuine history. Q: Is this address proof? A: It is corroboration, not proof. For formal KYC address proof you still need an accepted document. Q: What are the privacy obligations? A: Address data is personal data. Collect explicit consent, state the purpose, and restrict internal access. ## Mobile to Name API URL: https://fastkyc.com/apis/mobile-to-name/ Retrieve the registered full name for an Indian mobile number using telecom and banking-grade sources, to match a customer's name to their phone. Mobile to Name returns the full name registered against a mobile number, drawn from telecom and banking-grade sources. As a fraud signal this is quietly effective. When the name on the number does not resemble the name on the application, you have a discrepancy worth resolving before anything else proceeds. Use cases: - Verifying a customer's name against their phone number - Fraud screening at the start of onboarding - Pre-filling name fields to reduce typing - Flagging applications using someone else's number Q: How reliable is the name? A: It reflects the registered subscriber. Family-held connections are common, so a mismatch is a signal to investigate rather than proof of fraud. Q: Does it prove the customer holds the phone? A: No. Use OTP-based mobile verification to establish control of the number. Q: What consent is required? A: This returns personal data tied to an individual, so obtain and record consent. ## Mobile to PAN API URL: https://fastkyc.com/apis/mobile-to-pan/ Find the PAN linked to a mobile number and name, validated against trusted telecom and financial sources, so customers don't have to type their PAN. Mobile to PAN resolves a mobile number, together with a name, to the PAN associated with it across telecom and financial records. Requiring the name alongside the number is an intentional constraint. It prevents bulk harvesting of PANs from phone numbers alone, while still letting a genuine onboarding flow skip a field the customer often gets wrong. Use cases: - Pre-filling PAN during onboarding - Reducing form friction in mobile-first journeys - Cross-checking a declared PAN against the customer's number - Detecting mismatches between name, number and PAN Q: Why is the name required? A: It guards against bulk lookups. Requiring both means you must already know who you are asking about. Q: What consent applies? A: PAN is sensitive financial identity data. Obtain and record explicit consent before querying. Q: What if nothing is found? A: Treat it as inconclusive. The number may not be the one on record against that PAN. ## Mobile to RC API URL: https://fastkyc.com/apis/mobile-to-rc/ Find the vehicle registration numbers linked to a mobile number, validated against transport and insurance databases, for vehicle loans and insurance. Mobile to RC returns the vehicle registrations linked to a mobile number, checked against transport and insurance-linked records. Vehicle ownership is a useful asset signal, and it is also a fast way to establish whether someone applying for vehicle finance or motor insurance already owns what they claim. Use cases: - Identifying vehicles owned by an applicant - Pre-filling vehicle details in an insurance quote - Assessing asset ownership for credit decisions - Cross-checking a declared vehicle against the customer's number Q: How complete is the coverage? A: It depends on the number appearing in transport and insurance records. A nil result does not prove the person owns no vehicle. Q: Does it give full vehicle details? A: It returns registration numbers. Pass those to Vehicle RC or RC V2 for the full record. Q: What consent applies? A: This links personal identity to asset ownership, so explicit recorded consent is required. ## Mobile to VPA API URL: https://fastkyc.com/apis/mobile-to-vpa/ Map a mobile number to its UPI virtual payment address and account holder name for quick payment verification before you send or collect money. Mobile to VPA resolves a mobile number to the UPI handle associated with it, along with the account holder name. For payouts this removes a step customers dislike. Rather than asking someone to find and type their UPI handle, you resolve it from the number you already have and ask them to confirm it. Use cases: - Resolving a UPI handle for payouts - Confirming the name behind a payment address - Simplifying payout setup in an app - Cross-checking a declared VPA against the customer's number Q: What if the number has several handles? A: Multiple UPI handles per number are common. Present them for the customer to choose rather than picking one. Q: Does it verify the account can receive money? A: It resolves the handle and holder name. VPA to Account Details maps it to the underlying bank account. Q: Is consent required? A: Yes. This links a phone number to financial payment details. ## PAN Aadhaar Link Lookup API URL: https://fastkyc.com/apis/pan-aadhaar-link-lookup/ Fetch a PAN's Aadhaar linkage status together with the masked Aadhaar number linked to it, confirming the PAN is operative for KYC and tax purposes. PAN Aadhaar Link Lookup returns the linkage status and, in addition, the masked Aadhaar number associated with the PAN. The masked number lets you confirm which Aadhaar is linked without ever handling the full value, so you can reconcile against a customer's declared Aadhaar while keeping your data footprint minimal. Use cases: - Confirming which Aadhaar is linked to a PAN - Reconciling a declared Aadhaar against tax records - Checking linkage without handling full Aadhaar numbers - Detecting mismatches between declared and linked identity Q: Why masked rather than full? A: The last four digits are enough to confirm which Aadhaar is linked, and avoiding the full number keeps you clear of unnecessary handling obligations. Q: What does a mismatch mean? A: The customer supplied a different Aadhaar from the one linked to their PAN. Worth investigating before proceeding. Q: When should I use the plain status endpoint? A: When you only need to know whether linkage exists, not which number is linked. ## PAN Advanced V2 API URL: https://fastkyc.com/apis/pan-advanced-v2/ Check a PAN and confirm its validity, holder details and Aadhaar linkage status in a single advanced verification call built for full KYC journeys. PAN Advanced V2 verifies a PAN and returns its validity, the holder's details and the current Aadhaar linkage status. It sits between a name-only lookup and the full comprehensive record: enough to make an onboarding decision, without pulling more data than the decision requires. That restraint matters when you are minimising what personal data you hold. Use cases: - Standard PAN verification during onboarding - Confirming holder details and linkage together - Balancing verification depth against data minimisation - Validating PANs collected in bulk Q: Which PAN endpoint should I use? A: PAN Lite for a name check, Advanced V2 for standard verification with linkage, Comprehensive when you need the full record. Q: Does it include linkage? A: Yes, Aadhaar linkage status comes back with the verification. Q: What does validity mean here? A: That the PAN exists in tax records and its current operational status, not merely that the format is correct. ## PAN Comprehensive API URL: https://fastkyc.com/apis/pan-comprehensive/ Retrieve extensive PAN card data for an individual, covering identity details, status and linked information in one call. PAN Comprehensive returns the full set of data available against an individual's PAN, going well beyond confirming the number is valid. PAN is the backbone identifier of Indian financial onboarding, and the comprehensive view is what most lenders and brokers standardise on. It supplies the identity details, current status and linked information needed to make a decision without chaining several calls together. Use cases: - Primary identity verification during financial onboarding - Confirming PAN validity and holder details before account opening - Enriching a customer record from a single identifier - Cross-checking declared identity against tax records Q: How does this differ from PAN Lite? A: PAN Lite returns just the registered name. Comprehensive returns the full data set, which is what most onboarding flows need. Q: Does it show Aadhaar linkage? A: Use PAN Comprehensive with Aadhaar Check for linkage validation, or Pan Aadhaar Link Status for that question alone. Q: What if the PAN is inoperative? A: Status is returned. An inoperative PAN, often from missing Aadhaar linkage, affects transactions and TDS and should block onboarding until resolved. ## PAN Lite API URL: https://fastkyc.com/apis/pan-to-name/ Get the registered name for a valid PAN in a lightweight check, built for name matching during onboarding and bulk PAN validation at scale. PAN Lite returns the name registered against a PAN and nothing more. The narrow scope is the point. Where you only need to confirm a PAN belongs to the person who gave it to you, pulling a full record collects personal data you have no use for and must then protect. Use cases: - Name matching during onboarding - Bulk validation of PAN data - Lightweight checks where full detail is unnecessary - Confirming a PAN matches the account holder Q: Why use this over the fuller endpoints? A: Data minimisation and cost. If the name answers your question, do not collect more. Q: How exact is the name match? A: It returns the registered name; comparing it is your decision. Allow for initials, expansions and spelling variants. Q: Does it confirm the PAN is operative? A: For status, use PAN Advanced V2 or Comprehensive. ## PAN to DIN API URL: https://fastkyc.com/apis/pan-to-din/ Find the Director Identification Numbers associated with a PAN, revealing an individual's company directorships for KYB and due diligence checks. PAN to DIN resolves a PAN to any Director Identification Numbers held by that individual. Directorships are exactly the sort of thing that goes undeclared. Discovering them from a PAN reveals corporate exposure a personal loan application would never mention, and is standard practice in serious due diligence. Use cases: - Discovering undeclared directorships during due diligence - Assessing corporate exposure for a personal borrower - Screening individuals in corporate onboarding - Mapping an individual's business interests Q: What is a DIN? A: The Director Identification Number, a unique identifier the Ministry of Corporate Affairs assigns to anyone appointed as a company director. Q: Why does it matter for lending? A: A director carries responsibilities and potential liabilities from the companies they are involved in, which affect their overall risk profile. Q: Can I search the other way? A: Yes. DIN to PAN resolves a DIN back to the PAN of the individual. ## Pan Aadhaar Link Status API URL: https://fastkyc.com/apis/pan-aadhaar-link-status/ Check whether a PAN is linked to an Aadhaar number and get the current linkage status directly, since an unlinked PAN becomes inoperative for tax. Pan Aadhaar Link Status answers one question: is this PAN linked to Aadhaar, and what is the current status. Linkage has become a gating condition across financial services. An unlinked PAN risks being made inoperative, so checking it before onboarding avoids acquiring a customer whose identifier fails weeks later. Use cases: - Checking linkage before account opening - Screening an existing base for unlinked PANs - Determining correct TDS treatment - Prompting customers to complete linkage Q: What happens if a PAN is not linked? A: It can be rendered inoperative, which disrupts financial transactions and attracts higher TDS rates. Q: Can I fix linkage through the API? A: No. Linkage is completed by the taxpayer with the tax department. This reports status only. Q: How does this differ from the lookup variant? A: Pan Aadhaar Link Lookup also returns the masked Aadhaar number alongside the status. ## Pan Aadhaar Link Verify API URL: https://fastkyc.com/apis/pan-aadhaar-link-verify/ Verify PAN-Aadhaar linkage against a specific Aadhaar number, confirming the PAN and Aadhaar pair a customer declared actually belong together. Pan Aadhaar Link Verify confirms whether a specific PAN and Aadhaar pair are actually linked, rather than reporting linkage in general. This is the check for a customer who has given you both numbers. It confirms not just that the PAN is linked to something, but that it is linked to the Aadhaar they claim, which is a meaningfully different assertion. Use cases: - Verifying a customer-declared PAN and Aadhaar pair - Detecting mismatched identity documents - Confirming linkage for a specific Aadhaar - Strengthening identity checks in high-risk onboarding Q: How does this differ from the status check? A: Status reports whether the PAN is linked at all. This verifies it is linked to the particular Aadhaar you supply. Q: What does a failed verification indicate? A: The documents belong to different linkage records. That may be an error, or it may signal one document does not belong to the customer. Q: Which is more rigorous? A: This one, because it tests the pair rather than the PAN in isolation. ## Pan Comprehensive with Aadhaar Check API URL: https://fastkyc.com/apis/pan-comprehensive-with-aadhaar-check/ Retrieve full PAN data and validate the linked Aadhaar number in a single call, covering identity and PAN-Aadhaar linkage together for complete KYC. Pan Comprehensive with Aadhaar Check returns everything the comprehensive PAN endpoint provides and additionally validates the associated Aadhaar number. Linkage is no longer optional. An unlinked PAN can become inoperative, with direct consequences for transactions and TDS, so checking both together avoids approving a customer whose primary identifier is about to stop working. Use cases: - Onboarding where PAN-Aadhaar linkage is mandatory - Confirming identity and linkage in one call - Screening for PANs at risk of becoming inoperative - Meeting compliance requirements on linkage Q: Why does linkage matter? A: An unlinked PAN can be rendered inoperative, which affects financial transactions and triggers higher TDS. It is a live operational risk, not paperwork. Q: What if they are not linked? A: The customer must complete linkage with the tax department. Most institutions hold onboarding until they do. Q: Can I check linkage on its own? A: Yes. Pan Aadhaar Link Status answers only that question, more cheaply. ## Pan Udyam Check API URL: https://fastkyc.com/apis/pan-udyam-check/ Check whether a PAN is registered under the Udyam MSME system, confirming small business status from a PAN alone for MSME lending and schemes. Pan Udyam Check reports whether a PAN carries an Udyam registration, the MSME registration system in India. It answers an eligibility question quickly. If the PAN is Udyam registered, priority sector lending products and government schemes may apply, and that changes what you can offer before any further diligence. Use cases: - Checking MSME eligibility from a PAN - Routing applications to priority sector products - Confirming a declared MSME status - Segmenting a business customer base Q: What does a positive result mean? A: The PAN holds an Udyam registration, so MSME-linked products and schemes may be available. Q: How do I get the full registration details? A: Use PAN to Udyam Details for the enterprise record, or MSME Verification with the Udyam number. Q: Is registration mandatory? A: No, it is voluntary. An unregistered business may still qualify as an MSME but cannot access registration-linked benefits. ## Passport Verification V2 API URL: https://fastkyc.com/apis/passport-verification-v2/ Validate Indian passport data using file number based verification against issuing authority records, for KYC, travel and employee onboarding. Passport Verification V2 validates passport details using the file number, checking them against issuing authority records. Passports are the strongest widely held identity document in India, combining photograph, address and nationality in one credential issued after in-person verification. Confirming one against source records is a high bar of assurance. Use cases: - High-assurance identity verification - Onboarding NRI and international customers - Verifying passports for travel and forex services - Confirming nationality alongside identity Q: What is the file number? A: The application reference issued during the passport process. It is used here as the verification key rather than the passport number itself. Q: Does it verify foreign passports? A: It verifies against Indian issuing authority records, so it covers Indian passports. Use OCR Passport to read foreign documents. Q: How do I read the passport first? A: OCR Passport extracts the printed and machine-readable fields, which you can then verify here. ## RC Advanced API URL: https://fastkyc.com/apis/rc-advanced/ Retrieve advanced vehicle registration data with owner, vehicle, insurance, permit and additional detail fields, for vehicle loans and insurance checks. RC Advanced returns the fullest vehicle record available: registration and owner details, vehicle particulars, insurance, permits and additional fields beyond the standard set. Use it where the decision is expensive. Vehicle finance and high-value insurance justify pulling everything, because a detail missed at underwriting is discovered later at cost. Use cases: - Vehicle finance underwriting - High-value motor insurance assessment - Comprehensive due diligence on a used vehicle - Fleet acquisition verification Q: What does advanced add? A: Additional vehicle detail fields beyond the standard registration, owner, insurance and permit set. Q: When is the extra detail worth it? A: Where the transaction value justifies it. For routine checks, RC V2 is sufficient and cheaper. Q: Does it include hypothecation? A: Financier details appear in the registration record where present, which tells you whether a loan is outstanding on the vehicle. ## RC V2 API URL: https://fastkyc.com/apis/rc-v2/ Verify a vehicle registration number and return registration, owner, vehicle, insurance and permit details, for vehicle loans, insurance and fleets. RC V2 verifies a registration number and returns the registration details, owner information, vehicle particulars, insurance and permit data. It covers what most vehicle verification flows actually need, without the extended fields of the advanced endpoint. For routine ownership and validity checks it is the sensible default. Use cases: - Standard vehicle verification during onboarding - Confirming ownership before a transaction - Checking registration validity and permits - Validating vehicle details in an insurance quote Q: How does this compare to RC Advanced? A: Advanced adds further vehicle details. V2 covers registration, owner, vehicle, insurance and permits, which suits most flows. Q: Is owner information included? A: Yes, which is the field that matters when confirming the seller actually owns the vehicle. Q: How current is the data? A: It reflects transport department records, which lag recent transfers by the time the RTO takes to process them. ## Reverse Geocode API URL: https://fastkyc.com/apis/reverse-geocode/ Convert geographic coordinates into a detailed physical address for location verification and address capture during field and digital onboarding. Reverse Geocode turns latitude and longitude into a structured physical address. In field operations this replaces typing entirely. An agent standing at a customer's premises captures the location, and the address derives from where they actually are rather than what someone dictated. Use cases: - Capturing addresses during field verification - Converting GPS coordinates to a structured address - Confirming an agent visited the stated location - Auto-filling address from a device's location Q: How accurate is the resulting address? A: It depends on coordinate precision and mapping data density. Urban areas resolve more precisely than rural ones. Q: Does it prove the customer lives there? A: It proves where the coordinates point. Linking that to residence requires your own verification process. Q: Can I go the other way? A: This endpoint converts coordinates to addresses. Forward geocoding is a separate capability. ## Risk Analyzer API URL: https://fastkyc.com/apis/risk-analyzer/ Detect identity mismatches across a customer's data points and get a fraud risk assessment for the application, before you approve or onboard. Risk Analyzer examines the identity data points collected on a customer, looks for inconsistencies between them, and returns a fraud risk assessment. Individual checks each pass or fail in isolation. Fraud usually shows itself in the relationships between them: a name that does not match the number, an address inconsistent with the documents, a date of birth that differs across records. Cross-referencing is what makes those patterns visible. Use cases: - Fraud screening during customer onboarding - Detecting synthetic identities assembled from mixed data - Prioritising which applications need manual review - Adding a consolidated risk score to a decision engine Q: What kinds of mismatch does it catch? A: Inconsistencies between names, addresses, dates of birth and identifiers across the data you have collected. Q: Should a high score decline automatically? A: Treat it as a routing signal into manual review rather than an automatic decline. Genuine customers do produce mismatches. Q: What data does it need? A: The more identity points you supply, the more relationships it can test. Sparse input yields a weaker assessment. ## TAN Validation API URL: https://fastkyc.com/apis/tan-validation/ Validate a Tax Deduction Account Number and retrieve the associated taxpayer details from tax records, for vendor, employer and deductor checks. TAN Validation checks a Tax Deduction and Collection Account Number and returns the taxpayer details registered against it. Every entity deducting tax at source must hold a valid TAN, and it appears on the TDS certificates they issue. Verifying it confirms the deductor is genuine and that the certificates they hand over actually mean something. Use cases: - Verifying a deductor before accepting TDS certificates - Confirming an employer's tax registration - Validating vendor TAN details - Reconciling TDS entries to the deducting entity Q: How does TAN differ from PAN? A: PAN identifies a taxpayer. TAN identifies an entity authorised to deduct or collect tax at source. They serve different purposes. Q: How does this differ from Tan Validation Basic? A: Both validate a TAN and return taxpayer details. Choose based on the response depth your workflow needs. Q: What does an invalid TAN mean? A: Any TDS certificate carrying it is unreliable, and the deduction may never have reached the tax department. ## TIN Verification API URL: https://fastkyc.com/apis/tin-verify/ Verify a Taxpayer Identification Number and retrieve dealer registration details, CST status and address information, for vendor and dealer checks. TIN Verification checks a Taxpayer Identification Number and returns the dealer's registration details, CST status, address and related registration information. TIN belongs to the pre-GST VAT regime, and it still appears in older records and legacy contracts. Being able to verify it matters when you are reconciling historical documentation rather than onboarding fresh. Use cases: - Verifying dealer registration in legacy records - Reconciling pre-GST documentation - Confirming historical registration details - Validating older vendor records during cleanup Q: Is TIN still used? A: It has been superseded by GST registration, but TINs persist in historical records and older agreements. Q: Should I collect TIN or GSTIN? A: GSTIN for anything current. TIN verification is for reconciling legacy data. Q: What is CST status? A: Central Sales Tax registration status, relevant to interstate sales under the pre-GST regime. ## Toll Check API URL: https://fastkyc.com/apis/toll-check/ Retrieve toll plaza tariff details, including vehicle-wise rates, validity dates and plaza information, for route costing in logistics and fleet apps. Toll Check returns the tariff structure for a toll plaza: rates by vehicle category, the dates those rates are valid, and the plaza's own details. Toll is a real cost line in road logistics and rates differ by vehicle class and plaza. Accurate tariffs make route costing and freight quoting precise rather than estimated. Use cases: - Calculating toll costs for route planning - Building accurate freight quotes - Verifying toll charges against expectation - Comparing route costs across alternatives Q: Do rates vary by vehicle? A: Yes. Tariffs are set by vehicle category, so the rate for a car differs substantially from a multi-axle truck. Q: How current are the rates? A: Validity dates come back with the tariff, so you can see which period a rate applies to. Q: Does it cover every plaza? A: Coverage follows published toll plaza data. Query the specific plaza you need. ## Udyam Verification Send OTP API URL: https://fastkyc.com/apis/send-udyam-otp/ Send an OTP to the mobile number registered for an Udyam registration, starting a consented MSME verification that returns full enterprise details. Udyam Verification Send OTP delivers a one-time password to the mobile number registered against an Udyam MSME registration, beginning the consented verification flow. The OTP establishes that the person authorising the lookup is connected to the registered enterprise, which matters when MSME status determines access to lending benefits. Use cases: - Starting consented MSME verification - Confirming authority to act for a registered enterprise - Capturing consent before retrieving Udyam details Q: Which number receives the OTP? A: The mobile number registered against the Udyam registration, which may differ from the contact you were given. Q: What if they no longer hold that number? A: They must update it with the Udyam portal. Fall back to MSME Verification for a non-OTP check. Q: What comes next? A: Validate Udyam OTP confirms the code and returns the full registration details. ## Validate Email OTP API URL: https://fastkyc.com/apis/validate-email-otp/ Validate an email one-time password and confirm the customer controls the address they supplied, completing email ownership verification. Validate Email OTP checks the code entered against the one sent and confirms whether email verification succeeded. A successful validation is the record that the address is genuinely reachable and controlled by the customer, which is what makes it usable for statements, notices and account recovery. Use cases: - Completing email verification at sign-up - Confirming a changed email address - Recording proof of address ownership for compliance Q: What if the code is wrong? A: Validation fails and the customer can retry until the code expires, after which you should send a new one. Q: How long should verification last? A: Treat it as valid until the address changes. Re-verify on any change. Q: Is email verification enough on its own? A: It confirms a communication channel, not identity. Pair it with document and mobile verification for KYC. ## Validate Udyam OTP API URL: https://fastkyc.com/apis/validate-udyam-otp/ Validate the Udyam OTP and retrieve complete MSME registration details for the verified enterprise, completing a consented Udyam verification. Validate Udyam OTP confirms the code and, on success, returns the complete Udyam registration details for the enterprise. Completing the consented flow gives you both the registration data and the record that it was authorised, which is the combination you want on file when MSME status drives a lending decision. Use cases: - Completing consented MSME verification - Retrieving full enterprise details after authorisation - Confirming classification for priority sector lending - Recording consent alongside registration data Q: What details are returned? A: The complete Udyam registration record, including enterprise details and micro, small or medium classification. Q: How does this differ from MSME Verification? A: That endpoint verifies a Udyam number directly. This completes a consented, OTP-authorised flow. Q: Why does classification matter? A: It determines eligibility for priority sector lending and government schemes. ## Vehicle RC API URL: https://fastkyc.com/apis/rc-text/ Get authoritative vehicle registration details including specifications, ownership, insurance and permit information, from a registration number alone. Vehicle RC returns the detailed registration record for a vehicle: specifications, ownership, insurance particulars and permit details as held by the transport department. This is the comprehensive vehicle lookup. For used-vehicle transactions and motor underwriting it supplies the whole picture in one call, rather than assembling it from the seller's paperwork and hoping it is complete. Use cases: - Due diligence before a used-vehicle purchase - Motor insurance underwriting - Verifying ownership before vehicle finance - Confirming permits for commercial vehicles Q: Which RC endpoint should I use? A: Vehicle RC for the detailed record, RC V2 for standard verification, RC Advanced for the fullest set including additional vehicle details. Q: Does it show insurance status? A: Insurance particulars are included where the transport database holds them, though currency varies. Q: Can I search without the registration number? A: Yes. Chassis To RC and Engine to RC Details resolve a vehicle from its physical identifiers. ## Voter Id Verification API URL: https://fastkyc.com/apis/voter-id-text/ Verify an Indian voter ID by EPIC number and access the essential details recorded on the card against electoral records, for KYC and address proof. Voter Id Verification checks an EPIC number against electoral records and returns the essential details held against it. Voter ID matters in reach. It is held by people who have neither a PAN nor a passport, particularly outside metros, so supporting it materially widens who you can onboard. Use cases: - Verifying identity for customers without PAN or passport - Using voter ID as address proof - Financial inclusion onboarding in rural areas - Cross-checking declared details against electoral records Q: What is an EPIC number? A: The Electors Photo Identity Card number printed on the voter ID, which uniquely identifies the entry in the electoral roll. Q: Is voter ID accepted as address proof? A: It is widely accepted, though whether it satisfies your requirements depends on your regulator and internal policy. Q: How do I extract details from the card image? A: Use OCR Voter Id first, then verify the extracted EPIC number here. --- # Merchant ## Merchant overview URL: https://fastkyc.com/apis/merchant/ Business verification APIs for merchant onboarding: GSTIN, MSME and Udyam, FSSAI, Import Export Code and company registry checks from official sources. ## Company Name to CIN API URL: https://fastkyc.com/apis/company-to-cin/ Find a company's Corporate Identity Number and registration status by searching its name in the MCA registry, without asking the business for its CIN. Company Name to CIN searches the Ministry of Corporate Affairs registry by company name and returns the matching CIN along with the company's current status. Customers rarely know their CIN, but they always know their company name. Starting from the name gets you to the identifier that unlocks every other registry lookup. Use cases: - Resolving a CIN when only the company name is known - Checking whether a claimed company exists on the registry - Starting corporate due diligence from a business name - Detecting similarly named entities before onboarding Q: What if several companies share a similar name? A: You may get multiple matches. Narrow them using status, state or incorporation date before proceeding. Q: Does it show whether the company is active? A: Yes, the registration status comes back with the result. Struck-off and dormant companies are visible. Q: What comes next? A: Pass the CIN to Get Company Details for directors, charges and compliance history. ## FSSAI Validation API URL: https://fastkyc.com/apis/fssai-validation/ Verify an FSSAI licence number and retrieve the food business's registration details, category and validity before onboarding restaurants or sellers. FSSAI Validation checks a Food Safety and Standards Authority of India licence number and returns the registered business details along with the licence category and validity. Any platform dealing with food businesses needs this. An expired or fabricated FSSAI licence is both a compliance exposure and a consumer safety issue, and both land on the platform. Use cases: - Onboarding restaurants and food sellers to a marketplace - Confirming licence validity before listing a food business - Periodic re-verification of licences across a merchant base - Checking licence category matches the activity claimed Q: What do the licence categories mean? A: FSSAI issues basic registration, state licences and central licences depending on turnover and scale. The category should match the size of the operation claimed. Q: How do I handle expiry? A: The response carries validity dates. Re-verify before expiry rather than after, since a lapsed licence means the business should not be trading. Q: Does it confirm the address? A: Registered premises details come back with the record and can be compared against what the merchant declared. ## GST Advanced API URL: https://fastkyc.com/apis/gst-verification-advanced/ Enhanced GSTIN verification with compliance and filing history, promoter details, turnover data and e-invoice applicability for deeper KYB checks. GST Advanced goes beyond confirming a registration exists. It returns the business details together with compliance history, promoter and director information, turnover bands and whether e-invoicing applies. Filing behaviour is the signal that matters most here. A business that files consistently looks very different from one with long gaps, and that difference is directly relevant to credit decisions and to your own input tax credit risk. Use cases: - Assessing a business borrower's compliance behaviour - Estimating turnover band for credit limits - Identifying promoters behind a merchant entity - Checking e-invoice applicability before transacting Q: What does filing history reveal? A: Consistency. Regular filings suggest an operating, organised business; extended gaps suggest distress or dormancy and warrant caution. Q: How precise is the turnover data? A: It is reported in bands rather than exact figures, which is enough for segmentation and credit limits. Q: Why does e-invoice applicability matter? A: Businesses above the threshold must issue e-invoices. If a supplier should be doing so and is not, their invoices may not support your input tax credit. ## GST Verification API URL: https://fastkyc.com/apis/gst-verification/ Verify a GST number and retrieve the registered business name, address, status and registration details from GST records. GST Verification checks a GSTIN against India's Goods and Services Tax records and returns the essential registration details: legal and trade name, registered address, taxpayer type and current status. This is the baseline check for onboarding any business customer. It confirms the entity exists, is registered, and matches the name it gave you, which is the minimum before extending credit or settling money. Use cases: - Verifying merchants during business onboarding - Confirming a supplier's GST registration before payment - Checking a business is active before extending credit - Validating GSTINs collected in bulk Q: What does the status field tell me? A: Whether the registration is active, cancelled or suspended. A cancelled GSTIN on an invoice is a serious problem for your input tax credit. Q: How is this different from GST Advanced? A: This returns core registration details. GST Advanced adds compliance history, promoter information, turnover and e-invoice details. Q: Can I check filing history? A: Use GST Advanced for filing and compliance data, or the GSTR return endpoints for specific periods. ## GST Verify API URL: https://fastkyc.com/apis/gst-verify/ Quickly verify a GST number and return the core business information, a lightweight validation built for high-volume merchant and vendor checks. GST Verify performs a straightforward GSTIN check and returns the business information registered against it. It suits high-volume validation where you need to confirm a number is real and belongs to the expected business, without the fuller compliance picture the advanced endpoint provides. Use cases: - Validating GSTINs at scale in a data cleaning run - Inline validation on a merchant sign-up form - Confirming a GSTIN before generating an invoice - Lightweight checks where compliance depth is not needed Q: Which GST endpoint should I use? A: GST Verify for lightweight checks, GST Verification for standard onboarding, GST Advanced when compliance and turnover matter. Q: Does it confirm the registration is active? A: Yes, current status is part of the core information returned. Q: Can I validate the format myself first? A: You can check the fifteen-character structure locally to catch typos, but only a lookup confirms the registration exists. ## GSTIN By Name API URL: https://fastkyc.com/apis/gst-by-name/ Find every GSTIN registered against a business name across Indian states, with the status of each registration, when a merchant can't share its GSTIN. GSTIN By Name searches GST registrations by business name and returns the GSTINs found, including registrations across multiple states. Businesses operating in more than one state hold a separate GSTIN per state. Seeing them together gives an accurate picture of the operation's real footprint, which a single number never shows. Use cases: - Finding a GSTIN when only the business name is known - Mapping a group's registrations across states - Checking whether a business is GST registered at all - Detecting similarly named entities before onboarding Q: Why does one business have several GSTINs? A: GST registration is state-wise, so a business operating in several states holds one GSTIN in each, all linked to the same PAN. Q: How exact must the name be? A: Matching tolerates variation, but the legal name often differs from the trade name customers use. Try both if the first search comes up short. Q: Can I search by PAN instead? A: Yes. GSTIN By Pan returns all GSTINs linked to a PAN, which is usually the more reliable route. ## GSTIN By Pan API URL: https://fastkyc.com/apis/gst-by-pan/ Retrieve every GSTIN linked to a PAN, with the state and current status of each registration, to see a business's full GST footprint in one call. GSTIN By Pan returns all GST registrations associated with a PAN, along with the state and status of each. Because every GSTIN embeds the PAN of the entity holding it, this is the most reliable way to enumerate a business's registrations. It is exact where a name search is approximate. Use cases: - Enumerating all GST registrations for a business entity - Verifying a declared GSTIN belongs to the expected PAN - Mapping multi-state operations during merchant onboarding - Detecting undisclosed registrations in due diligence Q: Why is PAN more reliable than name? A: The GSTIN contains the PAN, so the link is structural rather than a fuzzy text match. Q: What if a PAN has no GSTINs? A: The entity is not GST registered, which may be legitimate below the turnover threshold, or may contradict what they told you. Q: Does it show whether each registration is active? A: Yes. Status accompanies each GSTIN, so cancelled and suspended registrations are visible. ## Generate e-Way Bill API URL: https://fastkyc.com/apis/generate-eway-bill/ Generate a GST-compliant e-Way Bill from invoice and transport details, returning the bill number and validity so goods can move without delays. Generate e-Way Bill creates the electronic waybill required for moving goods above the prescribed value, using the invoice and transportation details you supply. Goods cannot legally move without a valid e-Way Bill, so generating it inside your own dispatch flow removes a manual portal step at exactly the moment a delay is most costly. Use cases: - Automating e-Way Bill generation at dispatch - Embedding compliance into a logistics workflow - Generating bills in bulk for scheduled shipments - Removing manual portal entry from warehouse operations Q: When is an e-Way Bill required? A: For movement of goods above the prescribed consignment value, with thresholds and exemptions that vary by state and goods type. Q: How long is it valid? A: Validity depends on the distance to be covered. The generated bill carries its own validity period. Q: What details do I need? A: Invoice details, the parties involved, goods information and transporter details, as prescribed by the GST rules. ## IEC Advanced API URL: https://fastkyc.com/apis/iec-advanced/ Retrieve exporter and firm details from an Import Export Code, confirming a business is authorised for foreign trade before you onboard or pay it. IEC Advanced returns the exporter and firm details registered against an Import Export Code, the identifier required for cross-border trade from India. Any business claiming to import or export must hold a valid IEC. Verifying it confirms both that the trade activity is authorised and that the entity behind it is the one you think you are dealing with. Use cases: - Onboarding importers and exporters - Verifying trade credentials before financing a shipment - Confirming firm details for cross-border payments - Screening counterparties in trade finance Q: What is an IEC? A: The Import Export Code, issued by the DGFT. It is mandatory for importing into or exporting from India, with limited exceptions. Q: How does this differ from IEC Basic? A: Advanced returns fuller exporter and firm details. Basic covers the code and stakeholder essentials. Q: Does it prove trading activity? A: No. It confirms authorisation to trade, not that any trade has occurred. ## IEC Basic API URL: https://fastkyc.com/apis/iec-basic/ Look up Import Export Code details with basic stakeholder information for a registered trading entity, a quick check for importers and exporters. IEC Basic returns the core details behind an Import Export Code together with basic information on the stakeholders associated with it. It is the lighter of the two IEC endpoints, suited to confirming a code is valid and identifying who stands behind it, without the fuller firm detail. Use cases: - Confirming an IEC is valid during onboarding - Identifying stakeholders behind a trading entity - Lightweight screening of trade counterparties - Validating IECs collected in bulk Q: When should I use IEC Advanced instead? A: When you need fuller exporter and firm details, typically for trade finance rather than basic onboarding. Q: Who are the stakeholders? A: The proprietors, partners or directors registered against the code, which is useful for cross-checking against other registries. Q: Do IECs expire? A: They require periodic updating with the DGFT. A code that has not been updated may be deactivated. ## MSME Verification API URL: https://fastkyc.com/apis/msme-verification/ Verify an MSME Udyam registration and retrieve official enterprise details, classification and registered address for MSME lending and onboarding. MSME Verification checks a Udyam registration number against the official registry and returns the enterprise details, its micro, small or medium classification, and the registered address. The classification is the operative field. It governs priority sector lending eligibility and access to government schemes, and it is exactly the thing a business has an incentive to overstate. Use cases: - Confirming MSME status for priority sector lending - Verifying enterprise classification before offering a scheme - Validating Udyam registrations during merchant onboarding - Periodic re-verification of MSME status across a portfolio Q: How is classification decided? A: By investment and turnover thresholds. A business can move between categories as it grows, so re-verify periodically. Q: What about older Udyog Aadhaar numbers? A: Udyam replaced Udyog Aadhaar. Use Udyog Aadhaar Verification for legacy UAM numbers. Q: Can I start from a PAN? A: Yes. PAN to Udyam Details resolves Udyam registration from a PAN. ## Mobile To Prefill API URL: https://fastkyc.com/apis/mobile-to-prefill/ Prefill a customer's KYC profile from a mobile number, returning name, contact details, addresses and demographic attributes. Mobile To Prefill assembles a customer profile from a mobile number: names on record, contact details, known addresses, identity attributes and demographic information. The effect on completion rates is substantial. A form that arrives mostly filled and asks only for confirmation converts far better than one presenting a dozen empty fields, particularly on a phone. Use cases: - Prefilling onboarding forms to reduce drop-off - Speeding up loan applications on mobile - Cross-checking declared details against records - Enriching a lead before deciding on diligence depth Q: What consent is required? A: Explicit, recorded consent. This returns substantial personal data, so be specific about the purpose and keep the record. Q: How complete is the returned profile? A: It varies by number. Treat every field as optional and design the form so the customer confirms or corrects what comes back. Q: How does it compare to Mobile 360? A: Prefill is oriented to filling a KYC form. Mobile 360 casts wider, including financial and business associations. ## Mobile to MSME API URL: https://fastkyc.com/apis/mobile-to-msme/ Find the MSME Udyam registration linked to a mobile number from official government and business registry sources, without asking for the Udyam number. Mobile to MSME resolves a mobile number to any Udyam registration associated with it, returning the MSME details on record. Small business owners seldom have their Udyam number to hand. Resolving it from the mobile number you already have removes a step that otherwise stalls the application entirely. Use cases: - Onboarding small businesses without asking for a Udyam number - Confirming MSME status for priority sector lending - Pre-filling business details in a loan application - Detecting undisclosed business registrations Q: Why does MSME status matter? A: It determines eligibility for priority sector lending and various government schemes, so it directly affects which products a business can be offered. Q: What if nothing is found? A: The business may not be registered under Udyam, or may have registered against a different number. Treat it as inconclusive. Q: How do I verify the registration itself? A: Pass the Udyam number to MSME Verification for the official enterprise record. ## PAN to Udyam Details API URL: https://fastkyc.com/apis/pan-to-udyam/ Fetch Udyam registration and enterprise details for a business using only its PAN, without needing the Udyam number, for MSME lending and onboarding. PAN to Udyam Details resolves a PAN to any Udyam registration held against it and returns the enterprise details. PAN is collected in essentially every business onboarding flow. Using it to discover MSME status means you learn whether priority sector products apply without adding a single field to the form. Use cases: - Discovering MSME status from a PAN already collected - Confirming priority sector eligibility during underwriting - Enriching a business profile without extra form fields - Cross-checking a declared Udyam number against PAN records Q: What if the PAN has no Udyam registration? A: The business is not registered under Udyam. That is common and legitimate, but it means MSME-linked benefits do not apply. Q: Can one PAN hold several registrations? A: Udyam is intended as one registration per enterprise. Multiple results are unusual and worth reviewing. Q: Does it confirm the classification? A: Yes, the enterprise details include the micro, small or medium category. ## Udyog Aadhaar Verification API URL: https://fastkyc.com/apis/udyog-aadhaar-verify/ Verify a legacy Udyog Aadhaar registration using its UAM number and retrieve the registered enterprise details, for older MSME registrations. Udyog Aadhaar Verification checks a Udyog Aadhaar Memorandum number and returns the enterprise details registered against it. Udyog Aadhaar was superseded by Udyam, but UAM numbers still circulate in older records and among businesses that have not migrated. Supporting both means legacy documentation does not block an application. Use cases: - Verifying MSME status from legacy documentation - Handling businesses that have not migrated to Udyam - Validating historical registration records - Reconciling older merchant files during data cleanup Q: Is Udyog Aadhaar still valid? A: It has been replaced by Udyam. Businesses were expected to migrate, so a UAM without a corresponding Udyam registration is worth querying. Q: What is a UAM number? A: The Udyog Aadhaar Memorandum number issued under the previous MSME registration system. Q: Should I ask for Udyam instead? A: Yes, where the business has one. Use MSME Verification for current Udyam registrations. --- # Mobile ## Mobile overview URL: https://fastkyc.com/apis/mobile/ Mobile number verification APIs: OTP generation and validation to prove ownership, plus Mobile 360 profiles that build a customer view from one number. ## MNV Generate OTP API URL: https://fastkyc.com/apis/mnv-generate-otp/ Send a verification OTP to an Indian mobile number and receive a reference ID for confirming the code and the subscriber details. MNV Generate OTP starts mobile number verification. It sends a one-time password to the number supplied and returns a reference ID that ties the eventual confirmation back to this attempt. The reference ID matters for correctness. It keeps concurrent verifications distinct, so a user with two attempts in flight cannot accidentally confirm the wrong one. Use cases: - Verifying a mobile number at sign-up - Confirming a number change on an existing account - Proving the customer controls the number before sending sensitive alerts Q: How long is the OTP valid? A: A few minutes. After that, generate a new one rather than asking the user to retry the old code. Q: Can I resend to the same number? A: Yes, and each request returns its own reference ID. Confirm against the reference from the most recent send. Q: Is there a way to verify without an OTP? A: Yes. MNV Without OTP returns subscriber and network details with no message sent, though it does not prove the person is holding the phone. ## MNV Submit OTP API URL: https://fastkyc.com/apis/mnv-submit-otp/ Confirm a mobile number by validating its OTP against the reference ID, returning verified subscriber and network details. MNV Submit OTP completes verification. Supply the reference ID from the generate step along with the code the user entered, and the API confirms the match and returns the subscriber and network details for the number. A successful response is strong evidence: the person completing your flow is physically holding the SIM. That is a materially higher bar than any check based on records alone. Use cases: - Completing sign-up verification for a new customer - Confirming possession of a SIM before a high-value action - Recording proof of number ownership for compliance Q: What if the code is wrong? A: Verification fails and the reference stays open for a retry until the OTP expires, at which point you should generate a new one. Q: What details come back on success? A: Subscriber and network information for the verified number, which you can reconcile against what the customer declared. Q: Does it detect a recently ported number? A: The network details reflect the current operator. For recycled-number risk, MNRL Check tells you whether a number has been revoked and reissued. ## Mobile 360 Profile API URL: https://fastkyc.com/apis/mobile-360/ Build a complete identity, financial and business profile from a single Indian mobile number, in one aggregated API call. Mobile 360 Profile collapses many separate lookups into one. From a mobile number it assembles what is known about the person across identity, financial and business sources: names and addresses on record, linked identifiers, and any business associations. For onboarding, this reverses the usual order. Instead of asking the customer for everything and verifying it afterwards, you resolve what you can from the number first and ask them to confirm, which is faster and exposes contradictions immediately. Use cases: - Pre-filling an onboarding form from a phone number alone - Enriching a lead before deciding how much diligence it warrants - Cross-checking a self-declared profile against independent records - Fraud screening where declared details conflict with what the number returns Q: What does it actually return? A: An aggregated view spanning identity attributes, financial links and business associations. Coverage varies by number, so treat every field as optional. Q: What are the consent obligations? A: They are significant. This aggregates personal data from several sources, so obtain explicit, recorded consent and be specific about the purpose. Q: Can I get the same data from individual APIs? A: Largely yes, through Mobile to Name, Mobile to PAN, Mobile to Address and similar. Mobile 360 trades granular control for a single call. --- # SMS ## SMS overview URL: https://fastkyc.com/apis/sms/ SMS compliance API to check mobile numbers against the Mobile Number Revocation List, so OTPs and alerts never reach disconnected or reassigned numbers. ## MNRL Check API URL: https://fastkyc.com/apis/mnrl-check/ Check whether an Indian mobile number appears on the Mobile Number Revocation List, flagging disconnected numbers before they are reassigned. MNRL Check tests a number against the Mobile Number Revocation List, the register of numbers disconnected by operators. Revoked numbers are eventually reissued to new subscribers. This is the check that prevents a quietly serious failure: continuing to send OTPs, statements or transaction alerts to a number that now belongs to a stranger. Screening your base against MNRL turns that from an incident into routine hygiene. Use cases: - Screening a customer base before an OTP or alert campaign - Preventing sensitive messages reaching a reassigned number - Cleaning stale contact data in a CRM - Reducing wasted spend on undeliverable messages Q: What does a hit mean? A: The number was disconnected and may already have been reissued. Stop sending to it and re-verify the customer through another channel. Q: How often should I run it? A: Periodically across the base, and before any campaign carrying personal or financial information. Q: Does it say who holds the number now? A: No. It reports revocation status only. Use mobile verification to establish who currently controls a number. --- # Utility ## Utility overview URL: https://fastkyc.com/apis/utility/ Utility verification APIs: vehicle RC by chassis or engine, e-challans, electricity bills, BIN lookups, geo-fencing and face liveness for fraud checks. ## BIN Lookup API URL: https://fastkyc.com/apis/bin-lookup/ Identify the issuing bank, card network, card type and country behind any payment card using its Bank Identification Number. BIN Lookup takes the leading digits of a payment card and returns what they encode: the issuing bank, the network, whether the card is debit, credit or prepaid, and the issuing country. Knowing the card type before authorisation lets you route payments intelligently, apply the right fee, and flag mismatches such as a foreign-issued card on a domestic-only journey. Use cases: - Routing payments by card type to reduce processing cost - Detecting foreign-issued cards during checkout - Displaying the correct card branding in a payment form - Flagging prepaid cards in higher-risk transactions Q: How many digits do I need? A: The first six to eight digits are enough. Never send the full card number to a lookup service. Q: Does it validate the card? A: No. It identifies the issuing range only. It says nothing about whether the card exists, is active or has funds. Q: Is this PCI relevant? A: A BIN alone is not cardholder data, but the surrounding flow usually is. Keep the lookup inside your existing PCI scope and controls. ## Chassis To RC API URL: https://fastkyc.com/apis/chassis-to-rc/ Find a vehicle's registration certificate details from its chassis number, when the registration number is unknown or disputed. Chassis To RC resolves a vehicle identification number to its registration record, returning the registration number and associated vehicle details. The chassis number is stamped into the vehicle itself and cannot be swapped like a number plate. That makes it the identifier to trust when you are verifying a physical vehicle rather than a document. Use cases: - Identifying a vehicle during a used-vehicle inspection - Verifying a vehicle where the plate is missing or suspect - Cross-checking chassis against the claimed registration - Investigating a vehicle in an insurance claim Q: Where is the chassis number found? A: Stamped on the vehicle body, and printed on the RC and insurance documents. Reading it from the vehicle is the point when you suspect the paperwork. Q: How does this differ from Chassis To RC Details? A: Both start from a chassis number. Chassis To RC Details returns a fuller vehicle record; use it when you need more than the registration mapping. Q: Can I search by engine number instead? A: Yes. Engine to RC Details resolves a vehicle from its engine number. ## Chassis To RC Details API URL: https://fastkyc.com/apis/chassis-to-rc-details/ Retrieve full registration and vehicle details from a chassis number, including owner, specifications and validity information. Chassis To RC Details returns the complete registration record behind a chassis number: registration and owner details, vehicle specifications and validity dates. Where the basic lookup answers which vehicle this is, this endpoint answers everything about it in one call, which suits inspection and claims workflows that need the full picture rather than an identifier. Use cases: - Full vehicle due diligence in a used-vehicle purchase - Verifying specifications and ownership during a claim - Confirming registration validity from the physical vehicle - Building a vehicle history file for finance Q: How is this different from Chassis To RC? A: It returns a fuller record. Use the simpler endpoint when you only need to map a chassis number to a registration number. Q: Does it show insurance status? A: The registration record includes insurance validity where the transport database holds it, though currency of that field varies. Q: What if the chassis number returns nothing? A: Check for transcription errors first, since these strings are long. A persistent nil result on a valid chassis is itself worth investigating. ## E-Challan Details API URL: https://fastkyc.com/apis/echallan-details/ Retrieve pending and disposed traffic challans for any Indian vehicle by registration number, for fleet checks, used-car deals and vehicle lending. E-Challan Details returns the traffic violations recorded against a vehicle registration number, covering both outstanding challans and those already settled. Outstanding challans are a liability that transfers with the vehicle, which makes this a standard check before a used-vehicle purchase. The violation history is also a useful behavioural signal for fleet operators and motor insurers. Use cases: - Checking outstanding fines before buying a used vehicle - Monitoring violations across a commercial fleet - Assessing driving behaviour for motor insurance - Confirming challans are cleared before ownership transfer Q: Does it cover the whole country? A: Coverage follows what states publish to the central challan system, and completeness varies between states. Q: Can I pay a challan through the API? A: No. It reports status only. Payment goes through the relevant transport department channel. Q: What is the difference between pending and disposed? A: Pending challans are unpaid and remain a liability on the vehicle. Disposed ones have been settled or closed. ## ESIC Details API URL: https://fastkyc.com/apis/esic-verification/ Verify an ESIC number and retrieve the registered employee's basic details from Employees' State Insurance records, for employment and payroll checks. ESIC Verification checks an Employees' State Insurance number and returns the basic details registered against it. ESIC covers employees below a wage threshold, so registration is itself a signal about employment and income band. It also serves as an additional employment proof for workers who may not appear in other records. Use cases: - Verifying employment for workers covered by ESIC - Confirming employee details during background checks - Supporting income assessment for lower-income segments - Cross-checking employment where provident fund records are absent Q: Who is covered by ESIC? A: Employees earning below the prescribed wage threshold at establishments within the scheme's scope. Higher earners generally appear in EPFO records instead. Q: How does this compare to EPFO checks? A: They cover different populations. ESIC skews to lower wage bands, EPFO more broadly, so which is useful depends on the applicant. Q: Does it return salary? A: It returns registered employee details. Coverage itself implies a wage band rather than giving an exact figure. ## Electricity Bill Lookup API URL: https://fastkyc.com/apis/electricity-bill-lookup/ Verify an electricity bill and customer ID across Indian distribution companies, confirming the connection and billing details. Electricity Bill Lookup validates a consumer identifier against the records of electricity distribution companies across India and returns the associated billing details. An electricity connection is a strong address signal because it is tied to a physical premises and maintained by an independent utility. That makes it a useful corroboration where a customer's declared address needs support. Use cases: - Corroborating a declared residential or business address - Verifying a utility bill submitted as address proof - Confirming a business operates from the premises it claims - Adding an independent signal to an address risk model Q: Which distribution companies are covered? A: Multiple discoms across India. Coverage depends on which utilities expose consumer records, so a nil result may reflect coverage rather than an invalid connection. Q: Does it prove the customer lives there? A: It confirms the connection and its billing details. Linking that to a specific person still depends on the name on the account matching your record. Q: Does it show payment history? A: It returns billing details as held by the discom. Depth varies between utilities. ## Engine to RC Details API URL: https://fastkyc.com/apis/engine-to-rc-details/ Look up a vehicle's registration certificate details using its engine number, for verification and inspection workflows. Engine to RC Details resolves an engine number to the vehicle's registration record and returns the associated details. Engine and chassis numbers are the two physical identifiers stamped on a vehicle. Being able to search on either matters in practice, because one is frequently obscured, corroded or simply hard to reach during an inspection. Use cases: - Identifying a vehicle when the chassis number is unreadable - Cross-verifying engine number against the registration record - Vehicle inspection in claims and used-vehicle sales - Detecting mismatches between engine and registered vehicle Q: When would I use engine rather than chassis? A: Usually when the chassis stamp is inaccessible or corroded. Where both are available, checking both is the stronger verification. Q: What does a mismatch indicate? A: An engine number that resolves to a different vehicle than the chassis suggests a replaced engine or, more seriously, a tampered identity. Investigate before proceeding. Q: Is the engine number on the RC? A: Yes, alongside the chassis number, which lets you compare the document against the physical vehicle. ## Face Liveness API URL: https://fastkyc.com/apis/face-liveness/ Detect whether a face is a real, live person rather than a photo, video or mask, blocking presentation attacks during onboarding. Face Liveness determines whether the face presented to the camera belongs to a real person who is physically present, or to a spoof: a printed photo, a screen replay or a mask. Without it, remote face verification is straightforward to defeat. Anyone holding a photograph of the customer could pass a face match, so liveness is what makes the comparison meaningful. Use cases: - Preventing photo and video replay attacks in remote onboarding - Securing video KYC journeys - Confirming a real person before a high-value transaction - Strengthening face match with anti-spoofing Q: Which attacks does it catch? A: The common presentation attacks: printed photographs, images and video replayed from a screen, and masks. Q: Does it identify the person? A: No. It answers whether a live person is present. Use Face Match to establish who they are. Q: Does it need special hardware? A: No. It works from an ordinary smartphone or webcam capture. ## Geo Fencing API URL: https://fastkyc.com/apis/geo-fencing/ Check whether an IP address falls inside a defined geographic boundary, adding location-based controls to your risk rules. The Geofencing API evaluates an IP address against geographic boundaries you define and reports whether it falls inside or outside them. Geographic controls are a blunt but effective risk tool. Blocking or flagging access from outside the regions you serve removes a large volume of automated abuse before it reaches your application logic. Use cases: - Restricting access to the regions a service operates in - Flagging logins from unexpected locations - Enforcing regulatory geographic restrictions - Adding a location signal to a fraud model Q: How accurate is IP-based location? A: Reliable at country level and reasonable at city level, but not precise. Treat it as a signal, not proof of where someone is. Q: Can it be evaded with a VPN? A: Yes, which is why it belongs alongside other signals. IP Quality Check helps by flagging addresses associated with VPNs and proxies. Q: How are boundaries defined? A: You specify the geographic areas relevant to your policy and evaluate addresses against them. ## Get FIR Details API URL: https://fastkyc.com/apis/get-fir-details/ Access First Information Report details linked to a vehicle registration or contact number for risk and claims screening. Get FIR Details retrieves First Information Report records associated with a vehicle or a contact number. For motor insurance and used-vehicle transactions this is a material check. An FIR against a vehicle can indicate theft or involvement in an incident, both of which change the picture considerably before you underwrite or purchase. Use cases: - Screening a vehicle for theft reports before purchase - Investigating a motor insurance claim - Checking a contact number against reported incidents - Adding a criminal-record signal to a risk assessment Q: How complete is the data? A: It reflects what police records expose, and coverage varies by state. Absence of an FIR is not proof that none exists. Q: What are the compliance obligations? A: These are sensitive records. Use them only for a legitimate, documented purpose with an appropriate legal basis, and restrict internal access. Q: Does an FIR mean guilt? A: No. An FIR records that a complaint was filed. Treat it as a flag for review, never as a finding. ## LEI Verification API URL: https://fastkyc.com/apis/lei-verification/ Verify a Legal Entity Identifier and retrieve the registered entity's details, required for large-value corporate transactions. LEI Verification validates a Legal Entity Identifier code and returns the registered details of the entity behind it. The Reserve Bank of India requires an LEI for large-value transactions by non-individual entities. Verifying it at onboarding avoids discovering a missing or lapsed identifier at the moment a payment needs to move. Use cases: - Verifying corporate counterparties before large-value transactions - Meeting RBI LEI requirements in payment flows - Confirming entity details in cross-border trade - Screening corporate clients during onboarding Q: Which entities need an LEI? A: Non-individual entities conducting large-value transactions, under thresholds set by the RBI. Requirements have widened over time, so check the current position. Q: Do LEIs expire? A: They require annual renewal. A lapsed LEI can block transactions, so status matters as much as existence. Q: Is an LEI the same as a CIN? A: No. A CIN is the Indian company registry identifier; an LEI is a global identifier used for financial transactions. ## Whatsapp Check API URL: https://fastkyc.com/apis/whatsapp-check/ Check whether an Indian mobile number is registered on WhatsApp and whether it is a personal or business account, before you message a customer. Whatsapp Check reports whether a mobile number has an active WhatsApp registration and distinguishes a personal account from a business one. If WhatsApp is a channel you use for onboarding or support, this tells you in advance whether a number can be reached that way, so you can route to SMS instead of discovering the failure after sending. Use cases: - Confirming reachability before starting a WhatsApp KYC journey - Routing communication between WhatsApp and SMS - Identifying business accounts among merchant contacts - Cleaning a contact list before a messaging campaign Q: Does it reveal anything personal? A: No. It reports registration status and account type only, not profile details or messages. Q: Why does the business distinction matter? A: Business accounts behave differently for messaging, and for merchant onboarding a business account is a mild positive signal about the contact. Q: Does registration prove the customer controls the number? A: No. Use mobile number verification with an OTP to establish control. --- # Vision ## Vision overview URL: https://fastkyc.com/apis/vision/ Document OCR and face APIs: extract data from Aadhaar, PAN, passports, cheques, invoices and bank statements, match selfies to IDs and mask Aadhaar. ## Aadhaar Masking API URL: https://fastkyc.com/apis/aadhaar-mask/ Mask the first eight digits of an Aadhaar number in a document image, returning a redacted copy that is compliant to store. Aadhaar Masking takes an image containing an Aadhaar number and returns the same image with the first eight digits obscured, leaving only the last four visible. UIDAI guidance and data protection practice both discourage storing full Aadhaar numbers without a specific lawful basis. Masking at the point of capture means your archive never holds the full number, which is a far stronger position than deleting it later. Use cases: - Redacting Aadhaar copies before storing them - Meeting UIDAI expectations on Aadhaar handling - Sharing identity documents with third parties safely - Retrofitting masking across an existing document archive Q: Which digits remain visible? A: The last four, which is the standard masked form and enough to reference the document without exposing the full number. Q: Can the masking be reversed? A: No. The returned image is redacted, not overlaid, so the original digits are not recoverable from it. Q: Should I mask before or after extraction? A: Extract first if you need the number for verification, then store only the masked copy. Never persist the unmasked image without a lawful basis. ## Bank Passbook OCR API URL: https://fastkyc.com/apis/bank-passbook-ocr/ Pull the account number, IFSC, branch and account holder name out of a bank passbook image as structured data, ready to verify without manual entry. Bank Passbook OCR extracts the key banking fields from a passbook's front page: account number, IFSC, bank and branch, and the account holder name. Many customers reach for a passbook rather than a cheque book, particularly with public sector banks and in rural onboarding. Supporting both means you are not turning people away over which document they happen to hold. Use cases: - Accepting a passbook as bank proof during onboarding - Serving customers who have no cheque book - Extracting account details for a penny-drop verification - Digitising passbook images collected in the field Q: Which page should be photographed? A: The front page carrying the account number, IFSC and holder name. Transaction pages are handled by Bank Statement OCR. Q: Does it read transaction entries? A: No. It targets the account identity fields. Use Bank Statement OCR for transaction-level data. Q: Does it verify the account? A: No. Follow with bank verification to confirm the account is live and correctly owned. ## Bank Statement OCR API URL: https://fastkyc.com/apis/bank-statement-ocr/ Convert a bank statement into structured data with transactions, balances and account details extracted across every page. Bank Statement OCR turns a statement document into structured data: account details, individual transactions with dates, descriptions and amounts, and running balances, aggregated across all pages. This is the raw material for income and affordability assessment. Every bank formats statements differently, and normalising them into one shape is what makes automated underwriting possible at all. Use cases: - Assessing income and affordability for a loan - Extracting salary credits to verify declared income - Building cash-flow views for small business lending - Replacing manual statement review in underwriting Q: Which formats does it handle? A: Statement layouts vary considerably by bank, and extraction covers the common ones. Digitally generated PDFs read more reliably than photographs of printed statements. Q: Does it analyse the transactions? A: It extracts them. Bank Statement Analyzer takes that further with financial insights and risk indicators. Q: Are password-protected statements supported? A: Remove protection before upload. Many banks issue statements locked with a PAN or date-of-birth derived password. ## Certificate Of Incorporation API URL: https://fastkyc.com/apis/coi-ocr/ Extract the company name, CIN, incorporation date and registered office from a Certificate of Incorporation image for faster business onboarding (KYB). Certificate Of Incorporation OCR reads a company's incorporation certificate and returns the registered company name, Corporate Identity Number, date of incorporation and registered office address. The CIN is the key that unlocks everything else about a company. Extracting it accurately from the certificate lets you move straight to registry lookups without asking the customer to find and retype a twenty-one-character identifier. Use cases: - Onboarding a company from its incorporation certificate - Extracting a CIN before querying MCA records - Confirming incorporation date and registered office - Digitising company documents in a corporate KYC file Q: What is a CIN? A: The Corporate Identity Number is the twenty-one-character identifier the Ministry of Corporate Affairs assigns to every registered company. It encodes listing status, industry, state and year of incorporation. Q: Does it verify the company is active? A: No. Use Get Company Details to pull current status, directors and compliance from MCA records. Q: Does it work for LLPs? A: LLPs are issued a similar certificate with an LLPIN rather than a CIN. Extraction of the printed fields works comparably. ## Cheque OCR API URL: https://fastkyc.com/apis/cheque-ocr/ Extract account number, IFSC, MICR code, bank name and account holder details from a cheque image for account verification. Cheque OCR reads a cheque leaf and returns the banking details printed on it: account number, IFSC, MICR code, bank and branch, and the account holder name. A cancelled cheque is still the standard proof of bank account in India. Reading it automatically removes the slowest, most error-prone step in collecting payout details, and the extracted fields feed straight into account verification. Use cases: - Collecting bank details from a cancelled cheque during onboarding - Extracting account and IFSC before a penny-drop check - Digitising cheque images in a mandate or loan file - Validating that a submitted cheque matches the declared account Q: Does it verify the account exists? A: No. Pass the extracted account number and IFSC to a bank verification endpoint to confirm the account and its holder. Q: Does the cheque need to be cancelled? A: Not for extraction. Whether you require a cancelled cheque is your own policy decision. Q: What is the MICR code for? A: It identifies the branch for cheque clearing. It is useful as a cross-check against the IFSC read from the same cheque. ## Face Match API URL: https://fastkyc.com/apis/face-match/ Compare two facial images and get a similarity score, confirming the person presenting a document is the person pictured on it. Face Match compares two facial images and returns a similarity score indicating how likely they are to be the same person. The usual pairing is a selfie against the photograph on an identity document. This closes the gap that document verification alone leaves open. Confirming a document is genuine proves nothing about who is holding it, and the face comparison is what ties the document to the person in front of you. Use cases: - Matching a selfie to an Aadhaar or PAN photograph - Confirming identity in remote onboarding - Detecting applications using someone else's documents - Re-verifying an existing customer before a sensitive action Q: What score should I accept? A: That is a policy decision balancing false accepts against friction. Higher thresholds are appropriate for higher-value actions; set it deliberately rather than taking a default. Q: Does it stop someone using a photo of a photo? A: Not by itself. Pair it with Face Liveness, which detects whether a real person is present. Q: How much do photo age and quality matter? A: Both matter. Document photographs are often years old and poorly printed, so expect lower scores against a current selfie and calibrate accordingly. ## GST OCR API URL: https://fastkyc.com/apis/gst-ocr/ Extract the GSTIN, legal and trade name, address and registration details from a GST registration certificate image, ready to verify without typing. GST OCR reads a GST registration certificate and returns the GSTIN, the legal and trade names, the principal place of business and the registration details printed on it. In merchant onboarding this is the fastest way to capture a GSTIN accurately. The fifteen-character identifier is easy to mistype, and reading it from the certificate feeds a clean value into GST verification. Use cases: - Onboarding merchants from their GST certificate - Extracting a GSTIN before running GST verification - Capturing the registered business address - Digitising GST certificates in a vendor file Q: Does it verify the GSTIN is active? A: No. Use GST Verification or GST Advanced to confirm the number and its current filing status. Q: Does it read the trade name as well as the legal name? A: Yes, where both are printed. They often differ, and knowing which is which matters when matching against other records. Q: What about the certificate annexures? A: Extraction targets the main certificate. Additional places of business listed in annexures may not be captured in full. ## Invoice OCR API URL: https://fastkyc.com/apis/invoice-ocr/ Extract vendor, buyer, tax and line-item details from invoice documents, aggregated across every page into structured data. Invoice OCR reads an invoice and returns the parties involved, financial totals, tax breakdowns and individual line items, combined across multi-page documents. Line-item extraction is what separates this from simple total capture. Having each row as data supports GST reconciliation, spend analysis and invoice-based lending, none of which work from a header figure alone. Use cases: - Automating accounts payable data entry - Reconciling invoices against GST returns - Assessing invoices submitted for invoice financing - Extracting line items for spend analysis Q: Does it handle multi-page invoices? A: Yes. Line items are aggregated across pages so a long invoice returns as one coherent record. Q: Does it extract GST details? A: Yes, including tax breakdowns and party GSTINs where printed. GST OCR is the better fit for GST certificates specifically. Q: What about handwritten invoices? A: Printed invoices read far more reliably. Handwritten documents will return partial results at best. ## KYC Document Classifier API URL: https://fastkyc.com/apis/kyc-doc-classifier/ Automatically identify whether an uploaded document is an Aadhaar, PAN, passport, voter ID or driving licence before extraction. KYC Document Classifier looks at an uploaded image and identifies which Indian identity document it is, before any field extraction happens. This removes a genuinely annoying step from upload flows. Rather than asking customers to pick the document type from a dropdown, which they get wrong often enough to matter, you accept the upload and route it to the right extractor yourself. Use cases: - Routing uploads to the correct OCR endpoint automatically - Removing document-type selection from the customer journey - Validating that the upload matches the document requested - Sorting a mixed archive of scanned identity documents Q: Which documents can it identify? A: Aadhaar, PAN, passport, voter ID and driving licence, the five that cover the overwhelming majority of Indian KYC. Q: What if someone uploads the wrong document? A: The classification tells you, so you can reject it with a clear message instead of failing later with a confusing extraction error. Q: Does it extract the fields too? A: No, it classifies. Super OCR combines classification and extraction in a single call. ## Mobile Invoice OCR API URL: https://fastkyc.com/apis/mobile-invoice-ocr/ Read invoice details, customer and retailer information, tax amounts and asset details from mobile device purchase invoices. Mobile Invoice OCR is tuned for device purchase invoices. It extracts the customer and retailer, tax amounts, and the asset details that matter for a handset: model, IMEI and serial numbers. Device financing depends on exactly those asset fields. Confirming the specific handset on the invoice is what ties a loan to a real, identifiable device rather than a generic purchase claim. Use cases: - Verifying purchase invoices for device financing - Capturing IMEI and model for warranty registration - Confirming retailer and price in a buy-now-pay-later flow - Detecting duplicate invoices submitted across applications Q: How is this different from Invoice OCR? A: It is specialised for device invoices and targets asset fields such as IMEI and model. Use general Invoice OCR for ordinary business invoices. Q: Does it extract the IMEI? A: Yes, where the invoice prints it. Many device invoices do, and it is the field that uniquely identifies the handset. Q: Does it confirm the invoice is genuine? A: No. It extracts what is printed. Cross-check the retailer and price against your own expectations to spot manipulation. ## OCR Aadhaar API URL: https://fastkyc.com/apis/aadhaar-ocr/ Extract the Aadhaar number, name, date of birth, gender and address from a photo of an Aadhaar card, ready for identity verification. OCR Aadhaar reads an uploaded Aadhaar image and returns its fields as structured data: Aadhaar number, name, date of birth, gender and full address. Typing those details by hand is where onboarding slows down and errors creep in, particularly with addresses. Reading them from the card and asking the customer to confirm is faster and produces cleaner data for the verification steps that follow. Use cases: - Auto-filling a KYC form from a photographed Aadhaar card - Capturing address data without manual typing - Feeding extracted details into Aadhaar validation - Digitising Aadhaar copies held in an existing document archive Q: Does this verify the Aadhaar is genuine? A: No. OCR reads what is printed on the card. Use Aadhaar Validation to check the number against records, and Aadhaar XML Verification for a cryptographically signed proof. Q: Should I store the Aadhaar number I extract? A: Only if you have a lawful basis. Where you do not, use Aadhaar Masking so only the last four digits remain. Q: What image quality is needed? A: A well-lit, in-focus photo where the whole card is visible. Glare across the number and heavy skew are the usual causes of a poor read. ## OCR DL API URL: https://fastkyc.com/apis/dl-ocr/ Extract licence number, holder name, date of birth, validity and vehicle classes from a driving licence image automatically. OCR DL reads a driving licence image and returns the essential fields: licence number, holder name, date of birth, issue and expiry dates and the vehicle classes covered. Driving licence layouts differ by state, which makes manual entry slow and inconsistent. Structured extraction gives you the same fields regardless of which state issued the licence. Use cases: - Onboarding drivers for fleet and delivery platforms - Using a licence as address and identity proof in KYC - Checking vehicle class entitlement before assigning work - Flagging expired licences during periodic re-verification Q: Does it verify the licence with the RTO? A: No. Use Driving License or DL Advanced to confirm the extracted number against transport department records. Q: Does it handle every state's format? A: It covers the common formats across states. Unusual or heavily worn cards may return partial fields. Q: Can it read both sides? A: Submit each side separately. The reverse typically carries endorsements and address details not printed on the front. ## OCR PAN API URL: https://fastkyc.com/apis/pan-ocr/ Read PAN number, name, father's name and date of birth from a PAN card image and return them as structured, verifiable data. OCR PAN extracts the printed fields from a PAN card photograph: the ten-character PAN, the holder's name, father's name and date of birth. PAN is the backbone identifier for financial onboarding in India, and it is exactly the field customers mistype. Reading it from the card removes that error class before the number goes on to be verified. Use cases: - Auto-filling PAN during account opening - Extracting PAN before running a verification call - Digitising PAN copies in a document backlog - Cutting rejections caused by mistyped PAN numbers Q: Does it confirm the PAN is valid? A: No. It reads the card. Follow it with PAN Comprehensive or PAN Advanced to confirm the number against the tax database. Q: Does it handle both old and new PAN card designs? A: Yes. Layouts have changed over the years and the extraction handles the common variants. Q: Can it tell a photocopy from an original? A: Not reliably. For document authenticity, combine it with the KYC Document Classifier and your own review policy. ## OCR Passport API URL: https://fastkyc.com/apis/passport-ocr/ Extract passport number, name, date of birth, nationality and expiry from a passport image, including the machine-readable zone. OCR Passport reads a passport data page and returns personal information, document metadata and address details in structured form. Passports follow an international standard, including the machine-readable zone at the foot of the page. That consistency makes extraction highly reliable and gives an internal cross-check between the printed fields and the encoded ones. Use cases: - Onboarding customers who use a passport as primary identity proof - Capturing traveller details for travel and forex services - Reading foreign passports during NRI onboarding - Screening for expired documents at point of capture Q: Does it read the machine-readable zone? A: Yes, and because the MRZ encodes several printed fields, it doubles as a consistency check on the extraction. Q: Does it work with non-Indian passports? A: The MRZ is an international standard, so extraction works broadly. Field coverage outside the MRZ varies by issuing country. Q: How do I verify the passport itself? A: Use Passport Verification to check the file number against issuing records. ## OCR RC API URL: https://fastkyc.com/apis/rc-ocr/ Extract the registration number, owner name, vehicle identifiers, fuel type and validity dates from a vehicle RC image, ready to verify without typing. OCR RC reads a vehicle registration certificate and returns the registration number, owner details, chassis and engine numbers, fuel type, vehicle class and validity dates. Chassis and engine numbers are long alphanumeric strings that people routinely mis-key. Extracting them from the certificate is both faster and considerably more accurate than manual entry. Use cases: - Onboarding vehicles for insurance or finance - Capturing vehicle details during a used-vehicle sale - Reading chassis and engine numbers without transcription errors - Digitising RC copies in a fleet document archive Q: Does it verify the vehicle with the transport department? A: No. Use Vehicle RC or RC Advanced to confirm the extracted registration number against official records. Q: Does it handle both card and paper RCs? A: Yes, though newer smart cards read more consistently than older laminated paper certificates. Q: Can I go from chassis number to RC? A: Yes. Chassis To RC resolves a chassis number to the registration details. ## OCR Voter Id API URL: https://fastkyc.com/apis/voter-id-ocr/ Read the EPIC number, name, relation name, date of birth, gender and address from a voter ID card image as structured data, without manual entry. OCR Voter Id extracts the printed fields from a voter ID card: the EPIC number, holder name, relation name, date of birth, gender and address. Voter ID is widely held and commonly used as address proof, especially outside metros where alternatives are scarcer. Reading it automatically avoids the transcription errors that come with regional-language printing. Use cases: - Using voter ID as address proof in KYC - Onboarding customers who hold no PAN or passport - Digitising voter ID copies from paper files - Extracting details before running voter ID verification Q: Does it confirm the voter ID is real? A: No. Use Voter Id Verification to check the extracted EPIC number against electoral records. Q: Does it handle regional scripts? A: Cards are often bilingual. Extraction targets the Latin-script fields, which are the ones you will match against other records. Q: Which fields are most reliable? A: EPIC number and name read most consistently. Addresses vary more, since layout and print quality differ considerably between states. ## Salary Slip OCR API URL: https://fastkyc.com/apis/salary-slip-ocr/ Extract salary components, employer details, banking information and employment data from payslip documents automatically. Salary Slip OCR reads a payslip and returns its structure as data: earnings and deduction components, net and gross pay, employer details, and the employment and banking information printed alongside. The component breakdown is what makes it useful for underwriting. Basic pay, allowances and deductions each behave differently in an affordability calculation, and a single net figure hides all of that. Use cases: - Verifying declared income for a salaried loan - Extracting salary components for affordability assessment - Confirming employer details from payroll documents - Automating income document review in underwriting Q: Does it verify the payslip is genuine? A: No. Payslips are among the easiest documents to fabricate, which is why it is worth corroborating with EPFO records or bank statement salary credits. Q: Does it handle every employer's format? A: Payslip layouts vary widely. Common formats extract well; unusual templates may return partial components. Q: What is the strongest cross-check? A: Match the net pay against salary credits in a bank statement, and the employer against Current Employment Details from EPFO. ## Super OCR API URL: https://fastkyc.com/apis/super-ocr/ Classify and extract any supported Indian KYC document in one call, covering Aadhaar, PAN, licence, passport, voter ID and utility bills. Super OCR combines document classification and field extraction. Submit an image and it identifies the document type and returns the appropriate structured fields for it, with no need to say in advance what you are sending. One endpoint replaces the branching logic you would otherwise write across half a dozen document-specific integrations, which is a significant simplification when your flow accepts several proof types. Use cases: - Accepting any identity proof through a single upload endpoint - Simplifying integration where several document types are permitted - Processing a mixed archive of scanned KYC documents - Building a flexible document upload step with no type selector Q: Which documents are covered? A: Aadhaar, PAN, driving licence, passport, voter ID and utility bills, plus other supported identity documents. Q: Should I use this or the individual OCR endpoints? A: Use Super OCR when the document type is unknown at upload. Use the specific endpoint when you already know what you are receiving and want its full field set. Q: Does it verify the documents? A: No. It classifies and extracts. Verification against source records is a separate step per document type. ## Udyam OCR API URL: https://fastkyc.com/apis/udyam-ocr/ Extract the Udyam registration number, enterprise name, classification and address from an MSME Udyam certificate image, ready to verify instantly. Udyam OCR reads an Udyam registration certificate and returns the registration number, enterprise name, its micro, small or medium classification, and the registered address. The classification carries real weight. It determines eligibility for priority sector lending and government schemes, so capturing it correctly at onboarding decides which products a business can even be offered. Use cases: - Onboarding MSMEs from their Udyam certificate - Confirming enterprise classification for priority sector lending - Extracting the Udyam number before verification - Digitising MSME registration documents Q: Does it verify the registration is current? A: No. Use MSME Verification to confirm the Udyam number against the official registry. Q: What does the classification mean? A: Micro, small and medium are defined by investment and turnover thresholds, and they govern eligibility for various lending and government schemes. Q: How does Udyam relate to Udyog Aadhaar? A: Udyam replaced the older Udyog Aadhaar system. Legacy UAM numbers are handled by Udyog Aadhaar Verification. --- # Industries ## Lending & NBFC URL: https://fastkyc.com/industries/lending/ Verification APIs for digital lending - identity, income, banking, employment and credit checks for loan origination and underwriting. Lending is the most verification-heavy journey in Indian financial services. Before disbursal you need to know the borrower is who they claim to be, that the bank account is theirs, that the income is real and that the credit history supports the amount. These APIs cover that sequence end to end - identity and address from PAN and Aadhaar, account ownership by penny drop, income from bank statements, salary slips and ITR filings, and repayment behaviour from CIBIL, CRIF and Experian. ## Banking URL: https://fastkyc.com/industries/banking/ Account opening and compliance APIs for banks - CKYC, Aadhaar and PAN verification, account validation and document OCR at branch and digital scale. Banks carry the strictest KYC obligations of any regulated entity, and the same checks must hold whether an account is opened at a branch counter or on a phone. These APIs cover the regulated set - CKYC search and download, PAN and Aadhaar verification, account and IFSC validation - alongside the OCR and face-match tooling that makes remote onboarding practical. ## Fintech & Payments URL: https://fastkyc.com/industries/fintech-payments/ Onboarding and payout APIs for fintechs - UPI and VPA validation, penny drop, PAN and Aadhaar checks, and BIN lookups for card programmes. Fintechs onboard at volume and pay out in real time, which makes every failed verification an operational cost rather than a compliance footnote. These APIs cover the payments-specific surface - VPA resolution, penny drop and penny-less account checks, BIN lookups - on top of the identity set every regulated product needs. ## Insurance URL: https://fastkyc.com/industries/insurance/ Verification APIs for insurers - proposer identity, vehicle records for motor cover, and document OCR for claims and policy issuance. Insurance verification splits in two: confirming the proposer at policy issuance, and confirming the asset and the paperwork at claim time. These APIs cover both - identity and address checks for the proposer, RC and chassis lookups for motor cover, and OCR for the documents that arrive with a claim. ## Gaming & Fantasy Sports URL: https://fastkyc.com/industries/gaming/ Age and identity verification APIs for real-money gaming - PAN and Aadhaar checks, liveness, geo-fencing and duplicate-account detection. Real-money gaming carries obligations most consumer apps do not: players must be of age, must be in a state where play is permitted, and must not be running duplicate accounts. These APIs cover that specific set - identity and age from PAN and Aadhaar, presence from geo-fencing and reverse geocoding, and genuineness from liveness and face match. ## Crypto & Web3 URL: https://fastkyc.com/industries/crypto/ KYC and AML APIs for virtual asset platforms - PAN and Aadhaar verification, liveness, sanctions and debarment screening, and bank account checks. Virtual asset service providers in India are reporting entities, which means full KYC and ongoing screening rather than light-touch signup. These APIs cover the required set - verified identity, a matched live face, a validated bank account for fiat rails, and screening against SEBI debarment and court records. ## Staffing & HR URL: https://fastkyc.com/industries/staffing-hr/ Background verification APIs for hiring - employment history, EPFO and UAN lookups, identity checks, and court record screening. Background verification is slow because it is manual: chasing former employers, collecting payslips, waiting on court searches. These APIs replace most of that with direct lookups - employment history and current employer from EPFO and UAN, identity from PAN and Aadhaar, and adverse records from court and FIR searches. ## Marketplaces & E-commerce URL: https://fastkyc.com/industries/marketplaces/ Seller onboarding APIs for marketplaces - GST and MSME verification, business registry checks, bank account validation and invoice OCR. A marketplace onboards businesses, not consumers, so the verification set shifts from personal identity to business existence and standing. These APIs cover that - GST and Udyam registration, company and DIN records, FSSAI and IEC licences where the category demands them, and the bank account that receives settlements. ## Telecom URL: https://fastkyc.com/industries/telecom/ Subscriber verification APIs for telecom - mobile number validation, MNRL checks, Aadhaar and PAN verification, and address confirmation. Telecom operators verify at the point of connection, and the number itself is both the product and the identifier. These APIs cover number integrity - MNV, MNRL revocation checks, WhatsApp presence - alongside the identity and address proof a new connection requires. ## Real Estate & Rentals URL: https://fastkyc.com/industries/real-estate/ Tenant and buyer verification APIs - identity and address checks, income assessment, court record screening and utility bill lookups. Letting a property or accepting a buyer is a credit decision with a physical asset attached, and the checks look much like lending's. These APIs cover tenant and buyer diligence - verified identity and address, income from bank statements and ITR, and adverse records from court and FIR searches. ## Healthcare URL: https://fastkyc.com/industries/healthcare/ Patient and provider verification APIs - identity confirmation, ESIC lookups, insurance document OCR and practitioner record checks. Healthcare verification runs on both sides of the counter: the patient claiming cover, and the provider or practitioner claiming to be registered. These APIs cover patient identity and ESIC entitlement, plus the OCR needed to process claim paperwork without manual entry. ## Logistics & Mobility URL: https://fastkyc.com/industries/logistics/ Fleet and driver verification APIs - driving licence checks, RC and chassis lookups, FASTag and challan history, and e-way bill generation. Logistics and mobility platforms verify two things constantly: the driver is licensed, and the vehicle is roadworthy and legally documented. These APIs cover driver licensing, vehicle registration from RC, chassis or engine number, toll and challan history, and the e-way bill and GST records that goods movement requires. --- # Blog ## Bank Statement Analyzer: How It Works, Key Insights and Business Use Cases URL: https://fastkyc.com/blog/bank-statement-analyzer/ Topic: Banking | Author: Vaitheeshwari J Explore how a bank statement analyzer extracts transactions, evaluates cash flow, identifies income patterns and supports financial assessment and risk analysis. A bank statement is more than a list of deposits and withdrawals. It is a detailed record of financial behaviour that reveals cash-flow patterns, balance trends and recurring obligations. For lenders, fintechs and financial service providers, turning this raw data into structured insights supports faster assessment and better operational decisions. A Bank Statement Analyzer (BSA) does exactly that: it converts bank-statement information into organised data and meaningful financial summaries. In India, Account Aggregators (AAs) can complement this process by enabling secure, consent-based access to eligible financial information from participating institutions. What Is a Bank Statement Analyzer? A Bank Statement Analyzer is a tool that extracts and analyses financial information from bank statements (PDFs, scanned images or structured data feeds). Instead of leaving the information in document form, it organises it into consistent fields and analytical summaries. Typical outputs include: Account holder and bank details Statement period and balances Total credits and debits Daily end-of-day balance trends Major transactions and categories Recurring credit and debit patterns Configurable financial indicators that may need further review The results support lending workflows, MSME assessments, reconciliation and internal reporting. A BSA provides analysis and flags; it does not independently verify every transaction or decide creditworthiness on its own. How Bank Statement Analysis Works The process generally follows these stages: Document or data input – The statement (or AA-sourced data) is submitted. Data extraction – Text is read directly or via OCR for scanned documents. Structuring – Account details and transactions are mapped into standard fields. Calculations – Metrics such as totals, averages and balance ranges are computed. Pattern analysis – Recurring items, categories and unusual movements are identified. Report generation – Structured output (often JSON) is returned for review or system integration. Multi-page handling, balance reconciliation and validation checks are essential to reduce missing or duplicated entries. What Information Can Be Extracted? Account information (when present in the source): name, bank, branch, account number, IFSC/MICR, account type and statement period. Transaction information: date, description, debit/credit amount, running balance, and payment mode (UPI, NEFT, IMPS, ATM, etc.) when identifiable. The structured output can be consumed by other applications without re-parsing the original document. Extracted fields should still be treated as derived data, not independently verified facts. Cash Flow and Balance Trends Useful metrics include: Total credits and total debits Opening and closing balances Average end-of-day balance Maximum and minimum end-of-day balances A high closing balance can be misleading if a large deposit arrived only at the end of the period. Daily end-of-day analysis shows how funds actually moved and how often the account was under pressure. The calculation method (especially treatment of missing days) should always be clearly defined. Transaction Patterns and Financial Indicators Categorisation groups transactions by type (UPI, NEFT/IMPS, ATM, salary-like credits, EMIs, rent, etc.). Recurring activity highlights repeated credits or debits that may represent salary, rent, subscriptions or supplier payments. Frequency and total amount are reported; the tool does not automatically confirm the true purpose of every entry. Major transactions surface the largest inflows and outflows for quick review. Risk indicators may flag unusual balance swings, large one-off movements, frequent withdrawals or patterns that differ from expected behaviour. These are signals for further investigation, not proof of fraud or poor credit quality. How Account Aggregators Use Bank Statement Analysis India’s Account Aggregator (AA) framework enables consent-based sharing of financial information between participating institutions. When combined with a Bank Statement Analyzer (BSA), it helps financial institutions obtain authorized financial data and convert it into meaningful financial insights. How AA and BSA Work Together Customer Consent: The customer provides consent to share financial information for a specified purpose. Data Sharing: The Account Aggregator facilitates the transfer of authorized data from the Financial Information Provider (FIP) to the Financial Information User (FIU). Data Processing: The receiving system prepares the retrieved information in a format supported by the Bank Statement Analyzer. Financial Analysis: The BSA analyzes transactions, credits, debits, cash flow, income patterns, recurring payments and balance trends. Generating Insights: The results help financial institutions assess account activity and support workflows such as customer onboarding and lending assessments. By combining AA-based data access with bank statement analysis, institutions can reduce manual statement collection and streamline financial assessment. Since AA data may arrive in a structured format rather than a PDF, the analyzer or an intermediate processing component must support that format. Customer consent, data validation and appropriate security safeguards remain essential throughout the process. Business Use Cases Lending and loan assessment – Cash-flow patterns, average balances and existing obligations help evaluate repayment capacity alongside bureau data. MSME / working-capital assessment – Seasonal revenue, irregular collections and operating expenses become visible, supporting cash-flow-based underwriting. Financial reconciliation – Structured transactions can be matched against internal records. Personal-finance applications – Categorisation and balance trends help users understand spending and savings. Internal reporting and dashboards – Consistent fields feed assessment tools and operational workflows. Q: Can a Bank Statement Analyzer identify salary credits? A: It can identify potential salary credits using transaction descriptions, recurring patterns and classification rules. The results may require verification if the transaction narration is unclear. Q: Is total credit the same as total income? A: No. Total credits include all recorded incoming transactions. Transfers, refunds, loan proceeds and other receipts may not represent income. Q: What information can a Bank Statement Analyzer provide? A: It provides account details, transaction history, credit and debit totals, cash flow, balance trends, income indicators, recurring transactions and other derived financial insights. Q: Can a Bank Statement Analyzer identify recurring payments? A: It can identify potential recurring credits and debits by examining repeated transaction patterns. The identified transactions should be checked before being treated as confirmed obligations. Q: Can bank statement analysis support loan assessment? A: Yes. It can provide supporting information about account activity, potential income, recurring commitments and balance trends. It should be used alongside other relevant checks and decision criteria. Q: Is a Bank Statement Analyzer the same as a credit bureau report? A: No. Bank statement analysis examines account activity and transaction patterns, while a credit bureau report provides credit-related information such as reported credit accounts and repayment history. They serve different purposes. Q: How can an Account Aggregator be used with a Bank Statement Analyzer? A: An AA can facilitate consent-based sharing of financial information through participating institutions. A compatible processing component can normalize the received data before it is analyzed. The required integration depends on the formats and capabilities supported by the application. Q: Does a Bank Statement Analyzer automatically approve or reject a loan? A: Not necessarily. Some implementations return a suggested score, rating or lending decision. Such outputs should be used according to documented rules and validated decision processes rather than treated as an unconditional final decision. Q: Can Account Aggregator data be used for automated financial analysis? A: Yes. When the receiving system supports the data format provided through the AA framework, the information can be processed by a Bank Statement Analyzer to generate structured financial insights and support financial assessment workflows. ## RC Verification: How to Check Vehicle Registration Details URL: https://fastkyc.com/blog/rc-verification/ Topic: Transportation | Author: Harsine K U Learn how RC verification works, what vehicle registration details it reveals, and how businesses use it for finance, insurance, used-car sales and fleet management. A Registration Certificate (RC) contains important information about a vehicle, including its specifications and registered-owner details. RC verification helps businesses validate a vehicle's registration information against available transport records, supporting vehicle loan processing, insurance, used-car transactions and fleet onboarding while reducing manual verification. 1. What Is RC Verification? RC verification is the process of checking a vehicle's registration details against an authorised data source to retrieve and validate the information associated with its registration number. It helps businesses compare available details, such as the registered owner's name, vehicle class, manufacturer, fuel type and registration dates, with information submitted by a customer or seller. 2. Why Is RC Verification Important for Businesses? RC verification helps businesses: Validate vehicle details: Compare submitted information with available registration records. Cross-check ownership: Identify discrepancies in registered-owner information. Check validity details: Review available registration and document validity dates. Support risk assessment: Use vehicle information in lending, insurance and transaction checks. Reduce manual effort: Retrieve structured vehicle details instead of repeatedly entering information from documents. 3. Key Use Cases of RC Verification Vehicle Finance and NBFCs Verify vehicle details and available financing information during loan applications and vehicle-backed financing. Motor Insurance Cross-check vehicle specifications and available insurance details during policy issuance, underwriting and claims assessment. Used-Car Transactions Compare registration, vehicle identification and registered-owner details with the seller's documents before purchase. Fleet and Logistics Operations Check vehicle registration, fitness and permit details when onboarding commercial vehicles and maintaining fleet records. Vehicle Rental and Mobility Platforms Verify vehicle particulars against submitted documents before adding vehicles to the platform. 4. What Information Does RC Verification Return? The information returned depends on the selected API, source record and applicable access restrictions. The following categories describe the details that may be available. Registration Details Vehicle registration number Registration date and validity Registration status and state Registering authority or RTO details Vehicle Specifications Manufacturer and model Vehicle class and category Fuel type, body type and colour Chassis number and engine number Manufacturing date, engine capacity and seating capacity Emission norms and weight details Owner Information Registered owner's name Owner number and ownership history, where available Insurance, Fitness and PUCC Details Insurance company name, policy number and validity Fitness certificate validity date PUCC number and validity date Permits and Transport Authorisations Permit type and number Permit validity dates Permit issuing authority and service type, where available National Permit and All India Tourist Permit (AITP) details, where available Financing Details Financing status Financier or finance company name Tax and Other Vehicle Information Tax payment mode and available tax validity details Blacklist status, where available Non-use status and related dates, where available No Objection Certificate (NOC) details, where available Purchase date and sale amount, where available Q: What details can be checked through RC verification? A: RC verification may provide registration details, vehicle specifications, registered-owner information, insurance particulars, fitness and PUCC validity, permit details and hypothecation information. Q: Can I verify vehicle details without a registration number? A: Yes. Vehicle details can be retrieved using an engine number or chassis number Q: Can RC verification reveal a vehicle's previous ownership? A: Yes. RC verification may provide available ownership history, including previous owner records. Q: Can RC verification check insurance and fitness validity? A: Yes. RC verification can return insurance details, fitness certificate validity and PUCC information, depending on data availability. Q: Can RC verification identify whether a vehicle is financed? A: Yes. RC verification can show whether a vehicle is financed and provide the financier's name, if available. Q: Are permit details available through RC verification? A: Yes. RC verification may provide National Permit, All India Tourist Permit (AITP) and other permit details, depending on availability. Q: Does RC verification support vehicle loan processing? A: Yes. Lenders can use RC verification to cross-check vehicle details and available financing information during loan processing. Q: Does RC verification support different types of vehicles? A: Yes. RC verification can support two-wheelers, cars and commercial vehicles Q: What can cause a vehicle to be blacklisted? A: A vehicle may be blacklisted due to unpaid challans or taxes, theft reports, court cases or forged documents. Q: Can RC verification help identify vehicle specification mismatches? A: Yes. Comparing RC details with the submitted vehicle documents can help identify discrepancies in specifications such as fuel type and engine capacity. ## UPI ID Verification: How Businesses Can Verify UPI Details URL: https://fastkyc.com/blog/upi-id-verification/ Topic: UPI | Author: Akshitha A V Learn how UPI ID verification works, where businesses use it, and how to check recipient details using a UPI ID or mobile number. Businesses that make payments through UPI need to ensure that the payment details they collect are associated with the intended recipient. Incorrect UPI IDs or mismatched recipient details can lead to payment delays, failed payouts, and additional reconciliation work. UPI ID verification helps businesses check available recipient information associated with a UPI ID. What Is UPI ID Verification? A UPI ID, also known as a Virtual Payment Address (VPA), is an address used to send and receive payments through the Unified Payments Interface (UPI). UPI ID verification involves checking a submitted UPI ID and retrieving available information associated with it, such as the account-holder name and bank account details. For example, an online marketplace collecting payment details from a new seller can check the seller's UPI ID and compare the returned information with the seller's submitted records before proceeding with payouts. This helps the business identify discrepancies that may need further review. Why Is UPI ID Verification Important for Businesses? Businesses collect payment details from customers, sellers, vendors, and other beneficiaries. Incorrect details can create additional work during onboarding, payment processing, and reconciliation. UPI ID verification can help businesses: Check recipient details: Retrieve available account-holder information associated with a UPI ID. Reduce manual data entry: Find an associated UPI ID using a mobile number where supported. Identify discrepancies: Compare returned information with submitted beneficiary records. Prepare payouts: Check recipient details before scheduled settlements. Improve payment workflows: Incorporate recipient checks into existing business processes. Verification is one part of a broader payment control process. A successful lookup does not guarantee that a future transaction will succeed or independently establish the recipient's complete identity. Where Is UPI ID Verification Used? Customer onboarding Merchant and seller onboarding Loan disbursement Gig worker and partner payouts Payouts and settlements Refund processing Beneficiary verification Vendor and supplier payments Marketplace payments Payment detail verification These are practical workflows where businesses need to check available UPI recipient details before proceeding with a payment. UPI ID verification can help businesses review associated account-holder information, identify discrepancies, and reduce manual checks during beneficiary setup and payout preparation. How to Verify a UPI ID with FastKYC FastKYC offers services to check available details associated with a UPI ID or find an associated UPI ID using a mobile number. Businesses can use these services to review beneficiary information during onboarding, payouts, and settlements. Option A: Using VPA to Account Details VPA to Account Details Choose this if: You already have the recipient's UPI ID. It checks: The available account-holder name and associated bank account details. You provide: The UPI ID. This option is useful for businesses that collect UPI IDs from sellers, vendors, customers, or other beneficiaries and need to review the associated details before making payments. Option B: Using Mobile to VPA Mobile to VPA Choose this if: You have the recipient's mobile number but not their UPI ID. It checks: Whether an associated UPI ID and account-holder name can be retrieved. You provide: The mobile number. This option is useful for businesses that need to find an associated UPI ID while setting up beneficiary details or preparing payout workflows. Both services help businesses review available recipient information before proceeding with payments. Results depend on the information available, and businesses should review discrepancies before approving a payout. Q: What is UPI ID verification? A: UPI ID verification checks a UPI payment address and retrieves available information associated with it, such as the account-holder name and bank details. Q: What is a VPA in UPI? A: VPA stands for Virtual Payment Address. It is another name for a UPI ID used to identify a recipient for UPI payments. Q: How can I verify a UPI ID online? A: You can use a supported verification service, such as FastKYC's VPA to Account Details, to retrieve available account-holder and bank information associated with a UPI ID. Q: Can I find a UPI ID using a mobile number? A: Yes. FastKYC's Mobile to VPA service can find an associated UPI ID and account-holder name where the lookup is supported and the information is available. Q: Why should businesses verify UPI IDs before payouts? A: Verification helps businesses review beneficiary details, identify discrepancies, and reduce errors during payout preparation. Q: Does successful UPI ID verification guarantee payment success? A: No. A successful lookup does not guarantee that a future transaction will succeed. Payment outcomes depend on other factors, including account status and payment-system availability. Q: Is UPI ID verification useful for vendor and supplier payments? A: Yes. Businesses can check available recipient details when registering vendors or updating supplier payment information, helping identify discrepancies before payments are processed. Q: When should I use FastKYC's VPA to Account Details service? A: Use this service when you already have a recipient's UPI ID and want to retrieve the available account-holder name and associated bank account details. Q: When should I use FastKYC's Mobile to VPA service? A: Use this service when you have a recipient's mobile number but not their UPI ID. It can help find an associated UPI ID and account-holder name where the information is available Q: Is a UPI ID the same as a UPI PIN? A: No. A UPI ID identifies a recipient for payments, while a UPI PIN is used to authorise transactions. ## Liveness Detection in KYC: How It Stops Deepfakes URL: https://fastkyc.com/blog/liveness-detection-kyc/ Topic: Liveness Detection | Author: Krithick T Learn what liveness detection is in digital KYC, how it prevents photo, video and deepfake spoofing What is Liveness Detection? Liveness detection is a technology that verifies whether a facial image or video comes from a live human being rather than a spoof (printed photo, screen replay, mask or deepfake). It answers a simple but important question: Is this a real person present right now? How Liveness Detection Works There are two main approaches: 1. Active Liveness The user is asked to perform specific actions such as blinking, turning their head, smiling or speaking a random phrase. The system checks whether the actions are performed correctly in real time. 2. Passive Liveness The system analyses a single image or short video without asking the user to do anything. It looks for natural signs of life such as skin texture, micro-movements, lighting consistency and depth. Most modern KYC solutions use a combination of both, along with AI models trained to detect deepfakes and injection attacks. Liveness Detection vs Face Match Face Match alone can be fooled by holding up a photo or using a deepfake. Liveness detection alone does not confirm the person matches the ID. Both are needed for strong biometric verification. Why Liveness Detection Matters Prevents photo and video spoofing Helps detect deepfakes and synthetic faces Required in RBI’s Video KYC (V-CIP) framework Strengthens remote onboarding security Reduces identity fraud in lending and account opening RBI’s KYC Master Directions require face liveness / spoof detection with a high degree of accuracy as part of V-CIP, along with face matching technology. Common Use Cases Digital customer onboarding Video KYC / V-CIP sessions Loan and credit card applications Account recovery and re-KYC High-risk or high-value verifications How Liveness Fits into a Full KYC Stack A strong digital onboarding flow usually combines: Document verification (OCR + authenticity) Face Match (selfie vs ID photo) Liveness Detection Other checks (PAN, Aadhaar, bank account, credit report, etc.) At FastKYC, Liveness Detection works together with Face Match and other identity APIs to create a more secure verification layer. Q: What is liveness detection in KYC? A: It is a check that confirms the person being verified is a real, live human present at the time of capture, not a photo, video or deepfake. Q: Is liveness detection mandatory under RBI guidelines? A: Yes. RBI’s KYC Master Directions require face liveness / spoof detection with a high degree of accuracy as part of Video-based Customer Identification Process (V-CIP). Q: What is the difference between active and passive liveness? A: Active liveness asks the user to perform actions (blink, turn head, etc.). Passive liveness analyses the image or video without requiring any action from the user. Q: Can liveness detection stop deepfakes? A: Modern systems are trained to detect many deepfake and injection attacks. However, no system is 100% perfect, which is why it is usually combined with Face Match and other risk signals. Q: Does the user need to perform specific gestures? A: Only in active liveness flows. Passive liveness does not require any special gestures. Q: How accurate is liveness detection? A: Accuracy depends on the technology and how well the model is updated against current attack methods. Regulated use cases expect high resistance to common spoofing techniques. Q: Can liveness detection work on low-end devices? A: Most modern solutions are designed to work on standard smartphones. Very old or low-quality cameras may reduce performance. Q: Is liveness detection the same as face recognition? A: No. Liveness checks whether the person is real and present. Face recognition or Face Match checks whether the person matches a specific identity. Q: How long does a liveness check take? A: Usually a few seconds. Passive checks can be almost instant; active checks take slightly longer because of the required actions. Q: Can liveness detection be automated through an API? A: Yes. Businesses can integrate a Liveness Detection API so the check runs automatically during onboarding or Video KYC flows. ## Driving Licence Verification: How to Validate DL Details Instantly for KYC & Business Use URL: https://fastkyc.com/blog/how-to-verify-driving-licence/ Topic: Driving Licence | Author: Vaitheeshwari J Verify Driving Licence details for KYC and business onboarding. Learn about DL status, validity, vehicle categories, RTO details, and more. A Driving Licence (DL) is one of India’s widely accepted photo identity and address proof documents. Issued by Regional Transport Offices (RTOs) under the Motor Vehicles Act, it contains important information about the licence holder, including name, date of birth, address, vehicle categories authorised, validity periods, and licence status. For businesses, simply accepting a scanned or uploaded copy is no longer enough. Manual checks can be slow, error-prone, and vulnerable to forged or expired documents. Driving Licence verification helps businesses validate a DL number against authorised transport records and retrieve structured information for use in onboarding, KYC, lending, logistics, and compliance workflows. What Is a Driving Licence Number? An Indian Driving Licence number generally follows a structured format that can include the state code, RTO code, year of issue, and a unique licence number. Examples include: GJ04 20120005008 MH1420210045896 MH0220250045678 The number uniquely identifies the licence record maintained by the relevant RTO or state transport department. Depending on the verification process, the DL number may be used along with additional information such as the date of birth to retrieve the licence details. What Is Driving Licence Verification? Driving Licence verification is the process of validating a DL number against authorised transport records and retrieving the associated licence and holder information in a structured format. Instead of relying only on a physical card, image, or self-declared information, a verification service can retrieve available licence details. This allows businesses to validate licence information and use the results directly in digital onboarding, KYC, compliance, and decision-making workflows. Why Businesses Need Driving Licence Verification Businesses may collect Driving Licences for identity verification, address verification, age verification, and professional eligibility, particularly for roles involving driving or transportation. Manual verification can result in: Accepting expired or invalid licences Processing forged or altered documents Manual data-entry errors Delays in high-volume onboarding Inconsistent verification processes Compliance and audit challenges Automated DL verification helps organisations: Validate licence details more efficiently Check licence status and validity Retrieve accurate holder and vehicle-category information Reduce fraud during customer or driver onboarding Speed up KYC and due-diligence processes Maintain a record of verification results for audit purposes Key Use Cases Lending & NBFCs Verify identity and address information during loan applications and customer onboarding. Logistics, Mobility & Ride-Hailing Confirm that drivers have valid licences and the required vehicle categories or transport authorisations. Insurance Use verified licence information during policy issuance, underwriting, and claims-related processes. Staffing & HR Verify driving credentials for employees and candidates whose roles require a valid Driving Licence. Banking & Fintech Use DL verification as part of customer onboarding and identity verification workflows. Marketplaces & E-commerce Verify delivery partners, sellers, or other users whose activities require driving credentials. Real Estate & Rentals Use DL information as part of tenant or customer identity verification. Digital KYC Use Driving Licence verification as one of the identity verification checks in a broader KYC workflow. What Information Does Driving Licence Verification Return? The exact response depends on the data source and the depth of verification. A comprehensive response may include the following categories. Core Licence Details Licence number and previous licence number, where available Licence status Issue date Issuing authority or RTO State and state code RTO name and code RTO office details, where available Non-transport validity period Transport validity period Endorsement details Application numbers, where available Personal & Biographical Details Full name First, middle, and last name Date of birth Gender Blood group Father's or dependent's name and relationship Citizenship information, where available Organ donor status, where available Aadhaar authentication status, where available Address Information Depending on the response, address details may include: Permanent address Present or temporary address Address lines District State Pincode Locality type, such as Urban or Rural Vehicle Categories (Classes of Vehicles or COVs) Vehicle categories indicate the types of vehicles the licence holder is authorised to drive. Depending on the response, these may include: COV abbreviation Full vehicle category description Category type, such as Non-Transport (NT) or Transport (TR) Issue date Endorsement date Category status Badge details, where applicable For example: LMV – Light Motor Vehicle MCWG – Motor Cycle With Gear TRANS – Transport Vehicle Additional & Historical Data More comprehensive responses may also contain: Transaction history Renewal details Additional endorsements NOC-related information PSV badge information Profile image, where available Signature, where available Photo or biometric capture dates Print and dispatch status Simpler Response Formats Some verification responses may provide a smaller set of fields, such as: Licence status Holder name Date of birth Non-transport validity Transport validity Vehicle categories Address Pincode Gender Blood group Dependent name RTO information The exact fields available depend on the underlying data source and verification response. How Driving Licence Verification Works via API A typical DL verification workflow works as follows: The application collects the customer's Driving Licence number. The application sends the DL number, and any required additional information, to the verification service. The verification service retrieves the available licence information from an authorised data source. A structured response is returned with the available verified details. The business uses the response for onboarding, decision-making, risk assessment, compliance, or audit purposes. This approach reduces dependency on manual document inspection and allows DL verification to become part of an automated KYC or business verification workflow. Q: Can I check if a Driving Licence is currently active? A: Yes. The response includes a clear licence status field (e.g., “Active”) along with the validity end dates for non-transport and transport categories. Q: What are vehicle categories or COVs? A: Classes of Vehicles (COVs) indicate the types of vehicles the licence holder is authorised to drive (e.g., LMV – Light Motor Vehicle, MCWG – Motor Cycle with Gear, TRANS – Transport Vehicle). Each category has its own issue date and status. Q: Is there a difference between non-transport and transport validity? A: Yes. Non-transport validity covers private vehicle use. Transport validity (and related badges) is required for commercial / passenger / goods transport operations. Both periods are usually returned separately. Q: Can expired or suspended licences be detected? A: Yes. The status field and validity end dates allow systems to identify licences that are no longer valid or have restrictions. Q: How accurate is the data returned by DL verification? A: The data is sourced from official transport authority records. Accuracy depends on the completeness and currency of those records, the verification itself confirms what is present in the official system at the time of the query. Q: Can DL verification be used for driver onboarding in logistics or ride-hailing? A: Yes. It is particularly valuable for confirming that a driver holds a valid licence with the required vehicle categories and transport endorsements. Q: How does DL verification fit into a complete KYC stack? A: It is commonly used alongside PAN, Aadhaar, face match, bank account, and address verification to create a multi-layered identity and eligibility check. Q: What details are required to verify a Driving Licence? A: The DL number is the primary detail required for verification. Depending on the verification method, additional information such as the date of birth may also be required to retrieve or validate the licence details. Q: Can Driving Licence verification identify the vehicle types a driver can operate? A: Yes. Where COV information is available, the verification response can show the vehicle categories associated with the licence, along with relevant category status and validity information. Q: Can DL verification be used for periodic driver re-verification? A: Yes. Businesses can use DL verification periodically to check licence status, validity, and authorised vehicle categories. This is particularly useful for logistics, mobility, and fleet-management businesses. ## Bank Account Verification: What It Is, How It Works and Why Businesses Need It URL: https://fastkyc.com/blog/bank-account-verification/ Topic: Banking | Author: Harsine K U Learn how bank account verification works, including Penny Drop, Pennyless, IFSC checks, and API-based verification for businesses. Bank account verification helps businesses validate bank account details before payouts, disbursements, refunds, and other financial transactions. Learn how Penny Drop, Pennyless, and Hybrid verification work, what IFSC actually verifies, and how businesses can automate bank account verification through an API. What Is Bank Account Verification?  Bank account verification is the process of validating a bank account using details such as the account number and IFSC code. The Indian Financial System Code(IFSC) is an 11-character alphanumeric code that identifies a bank branch participating in the NEFT system. It is used to route transactions to the appropriate bank and branch. However, a valid IFSC does not verify a specific bank account. It only identifies the bank and branch associated with that IFSC. The account number must be validated separately through an appropriate bank account verification method. Why Do Businesses Need Bank Account Verification?  Businesses often collect bank details before they need to transfer money. An incorrect account number or other banking detail can result in failed transactions, delays, and additional manual work. Bank account verification can help businesses validate beneficiary details before using them for: Customer payouts Merchant settlements Loan disbursements Insurance settlements Refunds Vendor payments Customer onboarding For example, a marketplace can verify a seller's bank account during onboarding instead of discovering an incorrect account only when the first settlement is attempted. The verification step therefore becomes part of the process of preparing an account for a financial transaction. What Details Are Required for Verification?  The most common inputs are: Bank Account Number  The account number identifies the specific bank account that needs to be verified. IFSC Code  The IFSC identifies the relevant bank branch. RBI describes IFSC as the code used by the NEFT system to identify and route transactions to participating bank branches. The two details serve different purposes: the IFSC identifies the bank branch, while the account number identifies the account to be checked. A valid IFSC therefore does not mean that the account number is valid or that the account belongs to that branch. What is Penny Drop Verification  Penny Drop is a transaction-based method of bank account verification. A small amount, commonly ₹1, is deposited into the provided bank account. The transaction response can return the account holder's name and other available information, allowing the business to use the result as part of its account validation process. FastKYC's Penny Drop API describes the method as depositing one rupee and reading the account holder name returned by the bank. Penny Drop can be useful when a business wants to establish that the provided account can accept the transaction and retrieve the account-holder information returned by the banking network. What is Pennyless Verification  Pennyless verification validates eligible bank account details without transferring money to the account. Instead of making a small deposit, the verification service queries available banking network data using the account details. FastKYC's Pennyless API describes this as validating the account number and IFSC and returning the registered account-holder name and branch details without transferring money. This can be particularly useful for: High-volume onboarding Beneficiary verification Payout workflows Account validation where a transaction is not desirable What is Reverse Penny Drop Verification  Reverse Penny Drop is a transaction-based bank account verification method that uses a transaction initiated from the customer's bank account as part of the verification process. Unlike a conventional Penny Drop, where money is deposited into the beneficiary's account, the transaction originates from the account being verified. The transaction details can then be used to validate the bank account and retrieve supported account information. The exact transaction flow, verification process, and information returned may vary depending on the service provider. What is Hybrid Bank Account Verification  Hybrid Bank Verification combines more than one verification method within a single workflow. Hybrid Bank Verification attempts a Pennyless check first and can fall back to Penny Drop when the account cannot be confirmed through the initial lookup. This approach can reduce the need for businesses to build separate verification logic for different methods while providing an alternative when the first verification route cannot confirm an account. Bank Account Verification vs IFSC Verification  IFSC verification checks the bank and branch linked to an IFSC code. It helps businesses confirm the branch details associated with the provided IFSC. Bank account verification checks the specific bank account using the account number and IFSC. It helps businesses validate the account before using it for payments, payouts, or other financial transactions. Where Is Bank Account Verification Used?  Customer onboarding KYC workflows Merchant and seller onboarding Loan disbursement Payouts and settlements Insurance claims Refunds Beneficiary verification Vendor payments These are practical workflows where businesses need to validate bank details before using an account for a financial transaction. Bank Account Verification Through an API  For businesses that verify accounts at scale, integrating verification directly into the application is more practical than handling each account manually. A Bank Account Verification API allows an application to submit the account details and receive the verification result programmatically. The result can then be used within the existing workflow instead of requiring a separate manual bank check. FastKYC provides Penny Drop, Pennyless, and Hybrid Bank Verification APIs, along with a separate IFSC Search API. Q: What is bank account verification? A: Bank account verification is the process of validating a specific bank account using details such as the account number and IFSC through an appropriate verification method. Q: Does IFSC verify a bank account? A: No. IFSC identifies the bank branch; it does not verify the existence or ownership of a specific bank account. Account verification requires the account number to be checked through an appropriate verification method. Q: What details are required for bank account verification? A: The commonly required details are the bank account number and IFSC code. Additional inputs may depend on the verification method and provider. Q: What is Penny Drop verification? A: Penny Drop is a transaction-based bank account verification method where a small amount, commonly ₹1, is deposited into the provided account. The transaction response can provide the account-holder name and other available information. Q: What is Pennyless bank verification? A: Pennyless verification validates eligible bank account details without transferring money. It uses available banking network data to validate and returns supported account-holder and bank details. Q: What is the difference between Penny Drop and Pennyless verification? A: Penny Drop uses a small monetary transaction as part of the verification process, while Pennyless verification validates the account without transferring money. Q: What is Reverse Penny Drop verification? A: Reverse Penny Drop is a transaction-based bank account verification method where the transaction is initiated from the customer's bank account rather than money being deposited into the account. The exact implementation can vary by provider. Q: Can a bank account be verified without sending money? A: Yes. Pennyless verification is designed to validate eligible bank accounts without transferring money to the account. Q: Does bank account verification prevent fraud? A: Bank account verification should not be treated as a complete fraud-prevention solution. It is a validation step that can help businesses identify incorrect or mismatched banking information before proceeding with a financial workflow. Q: Can bank account verification be automated? A: Yes. Businesses can integrate a Bank Account Verification API into their applications and use the verification result directly within onboarding, KYC, payout, lending, or settlement workflows. ## Voter ID Verification: How to Verify EPIC Details URL: https://fastkyc.com/blog/voter-id-verification/ Topic: Voter ID | Author: Akshitha A V Learn how Voter ID verification works, how EPIC numbers connect to electoral records, and how businesses can automate verification using an API. Voter ID verification helps validate information associated with a Voter ID or EPIC number through an applicable verification service. A Voter ID is commonly used as an identity document, but the card itself is only one part of the picture. An elector's registration information is maintained in the Electoral Roll, and the EPIC number is associated with the corresponding voter record. For individuals, understanding this relationship makes it easier to understand what Voter ID verification actually checks. For businesses, it can provide an additional identity verification step for onboarding, KYC, HR, lending, insurance, and other workflows. What is a Voter ID? A Voter ID is an identity card issued to an enrolled elector in India. It is officially known as the Electors Photo Identity Card (EPIC). The card contains an EPIC number that is associated with the elector's voter record. A Voter ID can exist as a physical card as well as a digital e-EPIC. However, the Voter ID card and the Electoral Roll are not the same thing. The card is the identity document, while the Electoral Roll is the official record of registered electors. What is an Electoral Roll? The Electoral Roll, commonly referred to as the voter list, is the official record of registered electors. It contains the information used to maintain electoral registration for a particular area. This distinction is important because having a Voter ID card does not, by itself, determine whether a person can vote. The Election Commission of India states that a person's name must appear in the Electoral Roll to vote. So, in simple terms: Voter ID = identity card Electoral Roll = official voter record The two are different, but they are closely connected. How are Voter ID and Electoral Roll connected? The EPIC number is the key identifier associated with the Voter ID and the corresponding voter record. When an elector is registered, their information is maintained in the Electoral Roll and an EPIC is issued to them. The EPIC number can then be used to identify the relevant voter record. Think of it as: Voter ID → EPIC number → Electoral Roll record There is no need to think of this as manually linking a physical card to a database. The important point is that the EPIC number identifies the corresponding voter record. This is also why the EPIC number is important for Voter ID verification. What is an EPIC number? EPIC stands for Electors Photo Identity Card. The EPIC number is the identifying number associated with a Voter ID. It is used to identify an elector's record in voter-related services. For verification purposes, the EPIC number is particularly useful because it gives the verification process a specific identifier to check. Instead of relying only on the information printed on a card, a verification service can use the EPIC number as an identifier to validate the available voter information. What is Voter ID verification? Voter ID verification is the process of validating information associated with a Voter ID or EPIC number through a verification service. The basic process is: EPIC number / Voter ID details → Verification service → Verification result Depending on the verification service and the available data, the result can provide information associated with the Voter ID or EPIC number. This is different from simply looking at a Voter ID card and checking whether the printed information appears correct. The key part of verification is validating the submitted information using the data available to the verification service. Why does Voter ID verification matter for businesses? Businesses often need to verify identity information before providing a service, approving an application, or completing onboarding. Traditional verification may involve manually inspecting documents, entering details, and checking information separately. An automated Voter ID verification process can reduce this manual work. Common use cases include: Banking and lending: Identity checks during customer onboarding Insurance: Customer verification Staffing and HR: Candidate and employee verification Real estate and rentals: Tenant or customer onboarding Healthcare: Identity verification during registration Digital onboarding: Additional identity checks within an application The value is not simply in checking whether someone has a Voter ID. It is in being able to validate the information associated with that identity document as part of a digital verification workflow. What information can Voter ID verification provide? The exact response depends on the verification service and the information available to it. Depending on the verification service and the available data, the response may include information associated with the Voter ID or EPIC number, such as: EPIC number Name Date of birth or age Gender Address Other available voter details For businesses, this structured information can then be used within an existing onboarding or verification workflow. Voter ID verification through an API For businesses processing verification as part of a digital workflow, an API can make the process easier to integrate. Instead of handling each verification manually, an application can send the required information to a verification API and receive a structured response. With FastKYC, businesses can integrate Voter ID verification into their existing KYC, onboarding, HR, lending, insurance, or identity verification workflows. The goal is simple: instead of building the verification process from scratch, businesses can connect the verification check directly to the application where the user is being onboarded. Q: What is an EPIC number? A: EPIC stands for Electors Photo Identity Card. The EPIC number is the identifying number associated with a Voter ID. Q: What is Voter ID verification? A: Voter ID verification is the process of checking information associated with a Voter ID or EPIC number against the relevant electoral record. Q: Is Voter ID the same as an Electoral Roll? A: No. A Voter ID is an identity card issued to an elector, while the Electoral Roll is the official record of registered electors. Q: Does having a Voter ID mean a person can vote? A: Not necessarily. The person's name must appear in the Electoral Roll to vote. Q: What information can be checked using a Voter ID? A: Depending on the verification service, information such as the EPIC number, name, date of birth or age, gender, address, and other available electoral details may be returned. Q: Can businesses automate Voter ID verification? A: Yes. Businesses can integrate a Voter ID verification API into their applications and use it as part of their digital onboarding or KYC workflows. Q: Why do businesses need Voter ID verification? A: Voter ID verification can help businesses reduce manual verification work and incorporate an additional identity check into digital onboarding, customer verification, employee verification, and other workflows ## What is Face Match in Digital KYC? A Complete Guide URL: https://fastkyc.com/blog/face-match/ Topic: Face Match | Author: Krithick T Face Match in KYC explained: learn how selfie-to-ID comparison works, why it matters for lenders, and how it strengthens digital verification. What is Face Match? Face Match (also called face verification or 1:1 face comparison) is a technology that compares two facial images and returns a similarity score. In KYC, the two images are usually: A reference photo extracted from an identity document A live selfie captured during the onboarding process If the similarity score crosses a set threshold, the system treats it as a match. How Face Match Works The process typically follows these steps: The user uploads or captures an identity document. The system extracts the face photo from the document (often using OCR). The user takes a live selfie (sometimes with liveness checks). The Face Match engine converts both faces into numerical templates. It calculates a similarity score between the two templates. The score is compared against a threshold to decide match or no-match. Modern systems are designed to handle variations in lighting, angle, age, and image quality while keeping false match rates very low. Why Face Match Matters for Lenders and Fintechs Reduces identity fraud during onboarding Helps meet RBI expectations for remote verification Strengthens Video KYC (V-CIP) flows Improves trust in self-served digital journeys Works well with Aadhaar, PAN, Passport and other OVDs RBI’s KYC Master Directions require face matching technology with a high degree of accuracy in Video-based Customer Identification Process (V-CIP), along with liveness/spoof detection. Common Use Cases Customer onboarding for loans, credit cards and bank accounts Video KYC / V-CIP sessions Re-KYC and account recovery Employee verification High-risk or high-value account opening How Face Match Fits into a Full KYC Stack A robust digital onboarding flow usually combines: Document verification (OCR + authenticity checks) Face Match (selfie vs ID photo) Liveness detection Other checks (PAN, Aadhaar, bank account, credit report, etc.) At FastKYC, Face Match can be used together with Aadhaar verification, PAN checks, liveness detection and other APIs for a complete identity verification layer. Q: What is Face Match in KYC? A: Face Match is a biometric check that compares a live selfie with the photograph on a government ID to confirm they belong to the same person. Q: How accurate is Face Match technology? A: Modern Face Match systems used in regulated KYC achieve very low false match rates (often below 0.01–0.05% in controlled conditions) while keeping false rejection rates manageable for real-world use. Q: Is Face Match mandatory under RBI guidelines? A: RBI’s KYC Master Directions require face matching technology with a high degree of accuracy as part of V-CIP (Video KYC). It is a key component of compliant remote onboarding. Q: What is the difference between Face Match and Face Recognition? A: Face Match is a 1:1 comparison (selfie vs one ID photo). Face Recognition is usually a 1:N search against a database of many faces. Q: Does Face Match work with poor quality photos? A: Performance depends on image quality. Systems are trained to handle moderate variations in lighting, angle and resolution, but very blurry or low-resolution images can lower the similarity score. Q: Can Face Match detect deepfakes? A: Face Match itself compares facial features. Deepfake protection mainly comes from strong liveness detection (active or passive) that runs alongside Face Match. Q: What documents can be used for Face Match? A: Commonly used documents include Aadhaar, PAN card, Passport, Driving Licence and Voter ID — any official photo ID from which a clear face can be extracted. Q: How long does a Face Match check take? A: Most API-based Face Match solutions return results in under a second, making them suitable for real-time onboarding flows. Q: Do users need to perform specific gestures for Face Match? A: Not for the Face Match comparison itself. Gestures (blink, head turn, etc.) are typically part of the separate liveness check. Q: Can Face Match be automated through an API? A: Yes. Businesses can integrate a Face Match API to automatically compare the selfie and ID photo during onboarding, lending or account opening journeys. ## UAN Employment History Verification: Confirm Work Records Instantly URL: https://fastkyc.com/blog/how-to-verify-employment-history/ Topic: UAN | Author: Vaitheeshwari J UAN employment history verification helps businesses check EPFO records, validate joining and exit dates, and streamline background checks. A UAN is more than a PF number. It holds a person’s formal employment history across jobs where PF contributions were filed. Here’s how businesses can use it to verify work records quickly and accurately. Every formal employee in India who contributes to the Employees’ Provident Fund gets a Universal Account Number (UAN) from the Employees’ Provident Fund Organisation (EPFO). This number links every Member ID created by different employers into one record. When you verify employment history with a UAN, you get a government-sourced timeline of establishments, joining and exit dates, and related details — not just what appears on a resume. What is a UAN? UAN stands for Universal Account Number. It is a permanent 12-digit number issued by EPFO that acts as an umbrella for all PF Member IDs allotted to an individual across different jobs. It never changes, even when the person switches employers. Each new employer creates a fresh Member ID and links it to the same UAN. The UAN is the key to the EPFO Unified Member Portal, passbook, claims, transfers, and service history. Because employers file Electronic Challan cum Returns (ECR) against the UAN, the records reflect actual PF contributions and are therefore a strong, independent source of employment evidence. How to find your UAN? Most formal employees already have a UAN, even if they have never used it. You can find it in four ways: UAN card or EPF passbook - Your employer often shares the UAN when you join. Salary slip - Many employers print the UAN on the monthly payslip. EPFO portal - Go to the EPFO Unified Member Portal and use the “Know your UAN” option. Enter your registered mobile number and verify with an OTP. Employer HR or payroll team - They can retrieve the UAN from their EPF records. Once you have the UAN, you can access the service history and employment timeline described above. Why employment history verification matters for businesses Common use cases include: Background verification and pre-employment checks Detecting résumé fraud or inflated tenures Spotting overlapping employment (potential moonlighting) when contribution periods overlap Lending and credit underwriting (confirming stable employment and income source) Staffing, HR, and payroll onboarding Compliance and risk checks in regulated industries Reducing manual HR reference calls that take days or weeks Traditional verification often relies on calling previous employers, waiting for certificates, or trusting self-declared details. UAN verification pulls data rooted in official PF contribution filings, making it faster and more consistent at scale. What information does employment history verification provide? When you verify a UAN, you typically receive structured details such as: Employee name (as registered with EPFO) Guardian / father’s or mother’s name Member ID for each employment stint Establishment (employer) name Date of joining Date of exit This gives you a clear, sequential view of formal employment periods linked to the UAN. How Businesses Use Employment History Data After Verification ? Once you receive the employment history, the real value comes from how you use it: Resume matching — Cross-check claimed job titles, company names, and tenure against the official EPFO records. Gap analysis — Identify unexplained gaps between exit and joining dates. Overlap detection — Flag cases where contribution periods from two different employers overlap (possible dual employment). Risk scoring — Feed tenure stability and number of job changes into lending or hiring risk models. Audit trail — Store the verified response as part of the candidate’s or applicant’s compliance record. This turns a simple verification into an actionable decision layer for HR, lending, and compliance teams. Verifying Employment History Online and via API Through the official EPFO portal (for individuals) Go to the EPFO Unified Member Portal. Log in with the UAN and password (OTP authentication on the registered mobile number is required). Navigate to the Service History section. Review the list of establishments, Member IDs, dates of joining and exit, and related EPF/EPS records. Members can also download the service history for their own reference. This is useful for personal checks or when a candidate voluntarily shares the details, but it is not practical for high-volume business workflows. Through an API For businesses that need to verify large volumes of candidates or applicants, an API is far more practical. You send the UAN (with appropriate consent) in the request and receive the structured employment history in the response — ready for automated onboarding, background verification, lending, or HR systems. With FastKYC, businesses can integrate UAN-based employment history verification through an API, making it easy to add this check to KYC, onboarding, or verification flows. Limitations to keep in mind Only formal employment covered under EPF appears. Freelance, self-employment, or informal work is not visible. Older or unlinked Member IDs (especially pre-UAN legacy accounts) may sometimes be missing until the member or previous employer corrects the records. Date of exit may show a placeholder if the employer has not yet marked the exit. International experience falls outside EPFO scope. Q: Can overlapping employment periods be detected? A: Yes. When contribution or employment periods from two different establishments overlap on the same UAN, it can indicate concurrent formal employment. Q: Is UAN verification available only for current employment? A: No. The response typically returns the full available employment history linked to the UAN, including past and current establishments. Q: What is the difference between UAN and Member ID? A: UAN is the permanent 12-digit number that stays with the employee for life. A Member ID is created by each employer and is linked under that UAN. Q: Can this replace traditional background verification completely? A: It is a strong, fast, government-sourced layer that catches many discrepancies instantly. For highly sensitive roles, organisations often use it alongside traditional HR outreach or additional document checks. Q: How accurate is the data? A: The records are based on employer PF filings (ECR) with EPFO. Accuracy depends on the completeness of those filings and any subsequent corrections by the member or employer. Q: Can I verify employment history without the UAN? A: Yes. If you have the candidate’s mobile number, FastKYC’s Mobile-to-UAN API can first retrieve the linked UAN. You can then use that UAN to run the employment-history verification and obtain the full structured work record. ## DigiLocker Document Verification: How It Works for Businesses URL: https://fastkyc.com/blog/digilocker-document-verification/ Topic: DigiLocker | Author: Harsine K U DigiLocker helps businesses access eligible digital documents and data with user consent, reducing document collection and speeding up onboarding. What is DigiLocker? DigiLocker is a secure digital platform that allows users to access and share documents issued by participating organizations. Users can access eligible identity, driving, educational, employment, and other government-issued records, depending on the issuer and available services. For businesses, DigiLocker provides a way to retrieve eligible documents and associated information directly through an authorized digital flow, instead of relying entirely on customer-uploaded copies. What Makes Document Verification Difficult for Businesses? When businesses rely on uploaded documents, verification can involve several additional steps: OCR and data extraction to capture document information Quality checks for unclear or incomplete documents Tampering checks for potentially altered documents Data matching against information provided by the customer Manual review when automated verification is inconclusive These steps can increase processing time and manual effort, especially when businesses handle large volumes of customers. How Does DigiLocker Simplify Document Verification? DigiLocker provides an alternative for eligible records by allowing businesses to retrieve information through a user-authorized digital flow. Businesses can request the required information through DigiLocker. The customer authenticates, reviews the request, and authorizes access. The information can then be retrieved digitally and used within the business's KYC, onboarding, or verification process. Depending on the integration, it can be received as a digital document or structured JSON data. This can help businesses: Save onboarding time by reducing document-collection steps Reduce manual effort involved in processing uploaded documents Simplify the customer experience with a smoother digital journey Use retrieved information directly in existing workflows Consent and Transparency The DigiLocker flow is built around user consent. Before access is granted, users can review the request and decide whether to authorize document sharing. The request shows why the information is needed and who is requesting it, so users can understand the request before they choose to share. How Does DigiLocker Document Verification Work? 1. Initiate the request: The business starts a DigiLocker document request through an integrated API. 2. Redirect the user: The user is redirected to the DigiLocker authorization journey. 3. Authenticate: The user logs in and completes the required authentication, including OTP verification where applicable. 4. Select and authorize: The user reviews the request, selects the required document, and authorizes access. 5. Retrieve the document: Once authorized, the eligible document and associated information can be retrieved through the API and used in the verification workflow. What Can Be Retrieved Through DigiLocker? The availability depends on the issuer, document type, user's account, and applicable integration. Common examples include: Identity: PAN and Aadhaar-related information Driving & vehicle: Driving Licence and Registration Certificate Education: Marksheets and certificates Employment: UAN and other eligible records Government records: Other documents issued by participating departments Where Can DigiLocker Be Used? DigiLocker can support KYC, customer onboarding, lending, banking, insurance, education, and employment workflows. It is useful wherever businesses need to retrieve and verify eligible digital documents or information. Integrating DigiLocker Into Your Application With FastKYC, businesses can integrate DigiLocker through an API, making it easy to add document retrieval to their KYC and onboarding processes. This provides a smoother customer experience, faster onboarding, and seamless access to retrieved information. Q: Is a DigiLocker account a prerequisite for document verification? A: No. An existing DigiLocker account is not required to start the verification process. The user can complete registration and authentication during the flow. Q: Does every organization need to onboard separately with DigiLocker? A: No. Businesses can integrate with DigiLocker through an authorized integration provider and add the document retrieval flow to their applications without building the complete DigiLocker flow themselves Q: Can multiple DigiLocker accounts use the same mobile number? A: Yes. Up to five Aadhaar-verified DigiLocker accounts can be linked to the same mobile number, with each account associated with a different Aadhaar number. Q: How does the user authorize document access? A: The user logs in to DigiLocker, completes authentication, reviews the request, selects the required document, and authorizes access. Q: Can businesses choose which documents to request through DigiLocker? A: Yes. Businesses can customize the documents requested based on their specific use case from the available documents. Q: Can users cancel or deny a DigiLocker request? A: Yes. Users can choose not to authorize the request. The business will not receive the requested document if access is not authorized. Q: Is a DigiLocker document the same as a scanned copy? A: No. A DigiLocker document is a digitally issued document from the respective issuer and may contain a digital signature for verification. This is different from a scanned copy, which is simply a digital image or copy of a physical document. ## Udyam Verification Online: How to Verify MSME Registration URL: https://fastkyc.com/blog/msme-verification/ Topic: MSME | Author: Krithick T Need to confirm if a business is a registered MSME? Here’s how Udyam verification works, what details you get, and how to check it online or through an API. What is a Udyam Registration Number? The Udyam Registration Number follows a fixed format, for example: UDYAM-MH-18-1234567 “UDYAM” is fixed Next two characters = State code Followed by district and unique serial number It is free, paperless, based on self-declaration, and valid for the lifetime of the enterprise (no renewal needed). What information does Udyam verification provide? When you verify a Udyam number, you typically get: Name of the enterprise Type of organisation (Proprietorship, Partnership, etc.) Enterprise classification (Micro / Small / Medium) Major activity (Manufacturing or Services) NIC codes (nature of business) Date of Udyam registration Official address Registration status This makes it useful for vendor onboarding, MSME lending, government scheme eligibility and fraud checks. Why Udyam verification matters for businesses Common use cases include: MSME loan underwriting Vendor and supplier onboarding Checking eligibility for government schemes and tenders Confirming the size classification of a business Reducing the risk of dealing with fake or inactive registrations How to verify Udyam registration online 1. Through the official Udyam portal Go to the official website: udyamregistration.gov.in Click on Print / Verify Select Verify Udyam Registration Number Enter the 19-character Udyam Registration Number Complete the captcha and submit You will see the enterprise details if the number is valid. You can also recover a forgotten URN using the Aadhaar or mobile number linked to the registration on the same portal. 2. Through an API For businesses that need to verify large volumes of MSME registrations, an API is far more practical. You send the Udyam Registration Number in the request and receive the verified enterprise details in the response - useful for automated onboarding, lending workflows and vendor checks. If you are looking for an API-based solution, FastKYC offers Udyam verification through its API, which can be easily integrated into your existing systems. Q: Is Udyam registration mandatory? A: It is not mandatory for every business to operate. However, it is required if you want to avail government benefits, priority sector lending, subsidies, or participate in certain tenders meant for MSMEs. Q: Can one business have multiple Udyam numbers? A: No. Each enterprise is allowed only one Udyam Registration Number. Multiple units of the same business are usually added under a single registration. Q: What is the difference between Udyam and the old Udyog Aadhaar? A: Udyam replaced the earlier Udyog Aadhaar system in 2020. Old UAM numbers are no longer valid for new benefits or schemes. Q: How long is the Udyam certificate valid? A: It remains valid for the lifetime of the enterprise. No renewal is required. Q: Can Udyam verification be automated? A: Yes. APIs allow real-time verification so the check can run automatically inside onboarding or lending workflows. Q: How can I find my Udyam Registration Number if I have forgotten it? A: You can recover it on the official Udyam portal using the Aadhaar number or mobile number linked to the registration. Go to Print/Verify → Forgot Udyam/UAM Number and follow the OTP process. Q: What is the current classification criteria for Micro, Small and Medium enterprises? A: As of 2026: Micro: Investment up to ₹1 crore and turnover up to ₹5 crore Small: Investment up to ₹10 crore and turnover up to ₹50 crore Medium: Investment up to ₹50 crore and turnover up to ₹250 crore Q: Does Udyam registration require any documents? A: No. Udyam registration is completely paperless and based on self-declaration. Only Aadhaar is required to start the process. PAN and GST details are fetched automatically where available. Q: Can I verify someone else’s Udyam registration? A: Yes. Anyone can verify a Udyam Registration Number on the official portal using the “Verify Udyam Registration Number” option. No login is needed for basic verification. Q: Is the Udyam certificate the same as an MSME certificate? A: Yes. The Udyam Registration Certificate is the official MSME certificate issued by the Ministry of MSME. It has replaced the older MSME/Udyog Aadhaar certificates. ## PAN–Aadhaar Linking: A complete guide to link and verify the status URL: https://fastkyc.com/blog/how-to-link-and-verify-pan-aadhaar-status/ Topic: PAN Aadhaar Linking | Author: Subramaniyaswamy Chellakumaran Link PAN with Aadhaar and check the status in 2026. Covers the ₹1,000 fee, step-by-step linking, who is exempt, and API verification for businesses. An unlinked PAN turns inoperative and quietly breaks tax filing, refunds, and banking. This guide shows how to link PAN with Aadhaar in 2026, pay the ₹1,000 fee, check your status online, and verify a specific PAN–Aadhaar pair through the FastKYC API. What is PAN–Aadhaar linking? PAN–Aadhaar linking connects your Permanent Account Number (PAN) with your 12-digit Aadhaar number in the income tax records. Section 262(6) of the Income Tax Act, 2025 (formerly Section 139AA of the 1961 Act) makes this mandatory for most PAN holders. When the two are linked, your PAN stays active, or "operative." Why link PAN with Aadhaar? The law requires it. Section 262(6) of the Income Tax Act, 2025 (formerly Section 139AA of the 1961 Act) makes it mandatory for most PAN holders. An unlinked PAN stops working. It becomes "inoperative" and blocks tax and financial tasks. New PAN applications need it. For new applicants, the system links Aadhaar and PAN at the time of application. Who is exempt? Four groups do not need to link, under a 2017 CBDT notification: Residents of Assam, Jammu & Kashmir, and Meghalaya. Non-residents under the Income-tax Act. Persons aged 80 years or above. Foreign nationals. If you are in one of these groups, you can stop here. You do not need to link or pay. Is there still a deadline in 2026? No free window is open in 2026. Here is the timeline: 30 June 2023 — Free linking deadline closed. 31 May 2024 — Extended deadline, with the ₹1,000 fee. 31 December 2025 — Special window closed, for PANs obtained via an Aadhaar enrolment ID. 1 January 2026 — PANs from that special group became inoperative if not linked. If you have not linked yet, you can still do it. You must pay a ₹1,000 fee — a fee for delayed linking, not a criminal penalty. What happens if your PAN becomes inoperative? An unlinked PAN becomes inoperative under Rule 162 of the Income-tax Rules, 2026. When this happens: You cannot file income tax returns. Refunds are held back, with no interest. Tax is deducted at the higher rates under Section 397(2). High-value transactions, mutual fund purchases, and some banking services can be blocked. The PAN stays inoperative until you link it and it becomes active again. How to link inoperative PAN with Aadhaar Step 1 : Pay the ₹1,000 fee. Open the income tax e-filing portal. Go to e-Pay Tax. Enter your PAN and mobile number. Verify with the OTP. Pay ₹1,000. Step 2 : Submit the link request. Return to the portal. Use the Link Aadhaar quick link. You do not need to log in. Enter your PAN, Aadhaar number, and name exactly as on your Aadhaar. Click Validate. Enter the OTP sent to your Aadhaar-registered mobile number. Submit the form. Your request goes to UIDAI for validation. Reactivation takes from a few working days to about a month. If linking fails: A name, spelling, or date-of-birth mismatch between PAN and Aadhaar is the common cause. Correct it, then retry. How to check the link status online You can check the status two ways. Option A : On the income tax portal Open the income tax e-filing portal. Click Link Aadhaar Status (on the dashboard, or under My Profile). Enter your PAN and Aadhaar number. Click View Status. Official help page: https://www.incometax.gov.in/iec/foportal/help/how-to-link-aadhaar Option B : Using the FastKYC API or platform FastKYC offers both a platform and APIs to check the status and verify the linking. A business can use the console directly, or integrate the APIs into an existing application for verification during customer onboarding flows. PAN Aadhaar Link Status Choose this if: you hold only the PAN. It checks: whether any Aadhaar is linked to that PAN (not which one). You send: the PAN. PAN Aadhaar Link Verify Choose this if: you hold a customer's name, PAN, and Aadhaar. It checks: whether that specific PAN and Aadhaar are linked. You send: name as per PAN, PAN, Aadhaar number, consent. What do the statuses mean? Linked / Already Linked — PAN and Aadhaar are connected. No action needed. Not Linked — The two are not connected. Follow the steps in How to link inoperative PAN with Aadhaar. Pending with UIDAI — Your request is under validation. Check again after a few working days. Q: Can I still link PAN with Aadhaar for free in 2026? A: No. The free window closed on 30 June 2023. Any pending linking now needs the ₹1,000 fee. Q: Do I need to log in to link or check status? A: No. The Link Aadhaar and Link Aadhaar Status quick links on the income tax portal home page work without login. Q: How long does linking take? A: Your request goes to UIDAI for validation. Reactivation takes from a few working days to about a month. Q: My linking request failed. Why? A: Usually a mismatch in name, spelling, initials, or name order between PAN and Aadhaar. Correct it, then retry. Q: Do new PAN applicants need to link separately? A: No. For new applicants, the system links Aadhaar and PAN at the time of application. Q: Can I get a tax refund with an inoperative PAN? A: No. Refunds are held while the PAN is inoperative, and no interest is paid on the held amount. Q: Which API should a business use for onboarding? A: Link Verify. In onboarding you hold the customer's name, PAN, and Aadhaar and need to confirm they match. Link Status cannot do this, because it does not check a specific Aadhaar. Q: When is Link Status API the better choice? A: When you hold only the PAN and need one fact: is it operative. It is lighter — no Aadhaar number and no consent required. Q: Do I need customer consent when using these APIs? A: Yes Q: Does a "linked" result prove the PAN belongs to this customer? A: No. It confirms the PAN and Aadhaar are linked to each other. It does not prove the person presenting them owns them. Keep your other identity checks. ## Credit Report Verification for Lenders: CIBIL, Experian, CRIF & Equifax Explained URL: https://fastkyc.com/blog/credit-report-for-lenders/ Topic: Credit Report | Author: Krithick T A guide to credit report verification in India using CIBIL, Experian, CRIF High Mark and Equifax — what their reports show, and how to check them by API. A credit report is a summary of a person’s borrowing and repayment history, maintained by one of the four RBI-licensed credit bureaus in India: TransUnion CIBIL, Experian, CRIF High Mark and Equifax. Most lenders review at least one of these before approving a loan, credit card or any other credit product. What’s inside a credit report? A typical credit report includes: A three-digit credit score (most bureaus use a 300–900 range) List of active and closed loans and credit cards Current outstanding amounts Payment history, including late payments or defaults Recent credit enquiries Overall utilisation and risk indicators The same person can have slightly different scores across CIBIL, Experian, CRIF and Equifax. Each bureau uses its own scoring model and receives data from lenders at different times, so small variations are normal. Why lenders pull credit reports Decide whether to approve a personal, business or MSME loan Assess risk before increasing existing credit limits Identify early warning signs in the portfolio Spot applicants who already have multiple overdue accounts Meet regulatory expectations around responsible lending In short, a credit report helps avoid lending to people who are already over-leveraged or have a history of delayed repayments. How credit checks fit into the wider verification process In most lending flows, the credit report is not the first step. Teams usually start with basic identity verification - PAN verification is the most common starting point. If the applicant is a business or MSME, many lenders also check GST registration details. You can read our full guide on GST verification. Once identity and business status are confirmed, the credit report becomes the next logical layer. It shows not just who the person is and whether their business is registered, but how they have actually handled credit over time. How lenders get credit reports 1. Through the official bureau websites Individuals can request one free credit report per year from each bureau. Visit the official sites, enter basic details (usually PAN, name, date of birth and mobile number), complete OTP verification, and download the report. TransUnion CIBIL Experian India CRIF High Mark Equifax India This works for personal use, but is not practical when checking large volumes of applications. 2. Through an API Most lenders and fintechs use APIs. You send the required details (typically PAN + name + date of birth + mobile) and receive the score and report in the response. At FastKYC we support reports from: CIBIL Experian (including the newer V2 version) CRIF Equifax You can pull a single bureau or multiple ones. Many lenders start with CIBIL and add Experian or CRIF for a second opinion, especially for thin-file or new-to-credit applicants. Q: Why do scores differ across bureaus? A: Each bureau uses its own scoring model and may receive data from lenders at different times. A difference of 20–50 points is common and does not necessarily mean one report is wrong. Q: Do I need all four reports for every application? A: Not always. Many lenders begin with CIBIL. Adding a second bureau (Experian or CRIF) often gives a fuller picture, particularly when the first report has limited history or the applicant is new to credit. Q: What details are required to pull a report? A: Usually PAN, full name, date of birth and mobile number. Some flows may also require user consent or an OTP for authentication. Q: Can credit report checks be automated? A: Yes. APIs allow the check to run in real time during the application flow, so there is no need to download reports manually for each applicant. Q: How often is credit data updated? A: Lenders report data regularly (often every 15–30 days). An API pull reflects the latest information available at the bureau at that moment. ## GST Verification Online: How to Verify a GST Number URL: https://fastkyc.com/blog/how-to-verify-gst-online/ Topic: GST & Tax | Author: Harsine K U Verify a GSTIN online to confirm a business is registered and compliant: what the 15 characters mean, how to check it on the portal, and how to automate it. GST verification helps you verify a GSTIN and access the available registration details of the associated taxpayer. It provides businesses with a reliable way to confirm GST and registration information before entering into a business relationship. What is GSTIN? GSTIN is a 15-character, PAN-based unique identification number assigned to entities registered under GST in India. It serves as a unique identifier for registered taxpayers and is commonly included on business documents such as tax invoices and bills of supply. Understanding the GSTIN structure A GSTIN follows a specific format, such as 29ABCDE1234F1Z5: First 2 characters: State or Union Territory code Characters 3-12: PAN of the taxpayer 13th character: Entity or registration number 14th character: Default character, generally Z 15th character: Checksum character Understanding the GSTIN structure can help identify an incorrectly formatted GST number. Why is GST verification important? GST verification helps businesses validate the GST details provided by customers, vendors, suppliers, and other businesses. Common use cases include: Vendor and supplier verification Customer onboarding Invoice verification B2B verification Fraud and risk checks What information can GST verification provide? GST verification can provide key details about a registered taxpayer, including: Legal name Trade name GST registration status Registration date Business address Nature of business Taxpayer type HSN/SAC information How to verify GST online You can verify a GST number online through the official GST portal or automate the process using a GST verification API. 1. Verify a GST number through the official GST portal For an single GST check: Go to the official GST portal (https://www.gst.gov.in/) and open Search Taxpayer. Select Search by GSTIN/UIN. Enter the 15-digit GSTIN. Enter the displayed captcha. Click Search to view the available GST registration details. This method is suitable for manually checking individual GST numbers. 2. Verify a GST number using an API Businesses can automate GST verification using the GST Verification API: Integrate the verification API with your application. Send the GSTIN in the API request. Receive the available GST registration details in the API response. This is useful for customer onboarding, vendor verification, KYC, and automated business verification. Q: How can I get a company's GST number? A: A company's GSTIN is public business information. It can be found on its GST registration certificate, tax invoice, or bill of supply, and is required to be displayed at its primary place of business. Q: Can one business have multiple GST numbers? A: Yes. Normally a business has one GSTIN per state or Union Territory for a single PAN. However, a business may have multiple GST registrations in the same state for separate business verticals or other eligible reasons under GST rules. Q: What information does a GSTIN contain? A: A GSTIN contains information about the taxpayer, including the state or Union Territory, PAN, and entity registration details. The PAN portion can also indicate the category of the taxpayer based on its fourth character. Q: What details can I get from GST verification? A: GST verification can provide details such as the legal name, trade name, registration status, registration date, business address, nature of business, taxpayer type, and HSN/SAC information. Q: How can I check if a GST number is active? A: You can search the GSTIN on the official GST portal to check the available registration status and taxpayer details. Q: Can I find a GST number using a PAN? A: Yes. You can search for GST registration details using a PAN through the GST portal. This can help identify GST registrations associated with that PAN. Q: Can GST verification be automated? A: Yes. Businesses can use a GST verification API to automate GSTIN verification and retrieve available GST registration details within their applications. ## Identity Verification Using PAN URL: https://fastkyc.com/blog/identity-verification-using-pan/ Topic: PAN | Author: Vaitheeshwari J Discover how PAN-based identity verification helps businesses validate PAN details and support KYC, KYB, digital onboarding, and compliance. Collecting a PAN number during onboarding is easy. Ensuring it actually belongs to the applicant and is currently active is where most digital workflows break down. PAN verification bridges this gap by validating customer-provided numbers against authoritative database records in real time. For fintechs, banks, and enterprises, this single step prevents identity fraud, eliminates manual KYC bottlenecks, and keeps compliance tight. What Is PAN? PAN stands for Permanent Account Number. It is a unique identifier issued by the Income Tax Department and is widely used for taxation, financial transactions, KYC, and identity verification in India. A PAN is a 10-character alphanumeric identifier with a defined structure: AAAAA9999A First three characters: Alphabetic series from AAA to ZZZ. Fourth character: Identifies the category of the PAN holder, such as Individual (P), Company (C), HUF (H), Firm/LLP (F), Trust (T), or Government (G). Fifth character: Represents the first letter of the individual's surname or the entity name, as applicable. Sixth to ninth characters: Sequential numbers from 0001 to 9999. Tenth character: Alphabetic check character. PAN Verification: A Key Step in Customer Validation PAN verification helps businesses validate customer-provided PAN details before proceeding with KYC, onboarding, or other verification processes.This is useful for: Validating PAN details during customer onboarding Identifying incorrect or mismatched information Supporting KYC and compliance processes Reducing manual verification efforts Maintaining more reliable customer records For businesses handling digital onboarding, lending, financial services, or compliance workflows, PAN verification provides an additional layer of confidence before proceeding with a transaction or application. What Information Can PAN Verification Provide? The information available through PAN verification can vary depending on the verification method and the type of check being performed. Depending on the service, PAN verification may help businesses validate or retrieve information such as: PAN validity and status Registered name associated with the PAN PAN holder or entity type Date of birth or incorporation details, where supported Aadhaar linkage status, where supported Udyam registration details for eligible businesses Associated director information for business-related verification Operational Challenges PAN Verification Eliminates Businesses often rely on customer-provided PAN details during onboarding and verification. Without an automated verification process, incorrect information and manual checks can slow down these workflows. Invalid or incorrect PAN: Identifies PAN numbers that are invalid or incorrectly entered. Fuzzy Name Matching: Identifies name discrepancies caused by initials, middle names, or spelling variations between customer inputs and official records. Duplicate or unreliable records: Helps businesses validate PAN information before creating or updating customer records. Manual verification effort: Reduces repetitive manual checks and makes verification easier to handle at scale. Business verification: PAN can support business-related checks involving Udyam registration and associated director information, where applicable. By validating PAN information early in the process, businesses can identify discrepancies before they affect subsequent KYC, financial, or compliance processes. How to Verify PAN Online? PAN can be verified online either through the Income Tax Department's PAN verification service or through an API for automated business workflows. 1. Verify PAN Online Through the Income Tax Portal Individuals can verify their PAN online using the Income Tax Department's PAN verification service. To verify your PAN: Enter your PAN, Full Name, Date of Birth, and Mobile Number, then click Continue. Enter the OTP received on your mobile number and click Validate. The portal will process the details and display the PAN verification result. This option is useful when you need to verify a PAN manually through the Income Tax Department's online portal. 2. Verify PAN Using an API Businesses that need to verify PAN details as part of digital onboarding, KYC, KYB, or other verification workflows can automate the process using a PAN Verification API. A typical API-based verification flow involves: Integrate the PAN verification API with your application. Send the PAN details in the API request. Receive the available PAN details in the API response. Use the verification result as part of your onboarding or KYC workflow. API-based verification can help businesses reduce manual verification efforts and incorporate PAN validation directly into their existing workflows. Q: Why should I verify my PAN? A: PAN verification helps you confirm that the details associated with your PAN are accurate and up to date. It can help you to check whether your name, date of birth, and other PAN details match the information available in the PAN database.And Confirm whether your PAN is active and valid. Q: What is KYB-based PAN verification? A: PAN verification can be part of a KYB process by helping validate business-related information and its associated individuals. PAN can be used to retrieve director-related details, verify connections with Udyam registration, and perform additional checks on associated entities. Q: Can PAN validation be performed through DigiLocker? A: Yes, PAN validation can be performed through DigiLocker with the customer's consent. During the verification process, the customer must provide consent to access their DigiLocker information, and the PAN must be available in their DigiLocker account. Q: Is PAN verification also check Aadhaar linkage? A: PAN verification can support checking the PAN-Aadhaar linkage status. If Aadhaar linkage status is the specific requirement, you can also refer to PAN-Aadhaar Link Status feature. Q: How is PAN verification used during digital onboarding? A: During digital onboarding, the customer provides their PAN details, which are then verified against available records. The verification can confirm the PAN's validity and validate associated details before the customer proceeds with KYC or other onboarding processes.