Before a lender disburses a loan<\/a>, they need to confirm that the bank account provided belongs to the borrower. Providing a bank account number and IFSC code is trivially easy \u2014 providing the correct name and legitimate ownership is the actual verification challenge<\/a>. Penny drop verification solves this through a live, micro-transaction-based bank account validation that confirms account existence, account holder name, and account ownership simultaneously. Penny drop verification involves sending a minimal-denomination transfer (typically \u20b91) to the bank account to be verified, via IMPS or NEFT, and using the transaction response data to confirm: the account is active and capable of receiving funds; the account holder name returned by the receiving bank matches the borrower’s KYC name; and the account belongs to the individual (not a third party or fictitious account). The ‘penny’ is not about the amount \u2014 it is about using the IMPS\/NEFT beneficiary validation The lender sends a small credit (\u20b91) to the borrower’s declared account. The IMPS transaction response from the receiving bank includes the account holder name as registered. This name is compared against the borrower’s KYC-verified name. A match confirms ownership; a mismatch flags the account as potentially fraudulent<\/a> or third-party.<\/p>\n\n\n\n Instead of the lender sending money, the borrower initiates a small UPI-based payment <\/a>to a designated collection account. The UPI transaction returns the payer VPA (Virtual Payment Address) details and linked bank account information. This method confirms the borrower actively controls the UPI ID and linked account<\/a>, providing an additional layer of verification that the borrower has access to the declared account.<\/p>\n\n\n\n Bank account fraud<\/a> is more common than generally acknowledged in digital lending. Borrowers submit third-party bank accounts \u2014 often accounts of family members, associates, or fraudulently opened accounts<\/a> \u2014 to route loan disbursements and complicate recovery. Penny drop verification, combined with KYC name matching, identifies mismatches before disbursement.<\/p>\n\n\n\n Additionally, for NACH (National Automated Clearing House) mandate-based EMI collection<\/a>, confirming the account is active and the correct holder before creating the mandate prevents NACH return failures \u2014 which carry processing costs and operational complexity. Penny drop verification integrates at the disbursement stage of the loan processing workflow. The API accepts: account number, IFSC code, and the KYC-verified account holder name. It initiates the micro-transaction, waits for the response (typically under 30 seconds for IMPS), extracts the returned account holder name, performs fuzzy name matching against the KYC name, and returns a verification status with match confidence score. NPCI governs<\/a> the IMPS and NEFT infrastructure used for penny drop verification. While penny drop is widely used, NPCI guidelines require that transactions represent genuine payment intent– micro- transactions purely for verification purposes exist in a compliance gray area<\/a>. Many lenders include penny drop as part of the onboarding process where a credit of \u20b91 is genuinely part of the account setup. API providers handling penny drop must confirm their NPCI compliance posture.
<\/p>\n\n\n\nWhat Is Penny Drop Verification?<\/h2>\n\n\n\n
response to extract the account holder name returned by the receiving bank, which cannot be manipulated by the borrower.<\/a>
<\/p>\n\n\n\nStandard Penny Drop vs Reverse Penny Drop<\/h2>\n\n\n\n
Standard Penny Drop<\/h3>\n\n\n\n
Reverse Penny Drop<\/h3>\n\n\n\n
Why Lenders Use Penny Drop Verification<\/h2>\n\n\n\n
<\/p>\n\n\n\nIntegration Architecture<\/h2>\n\n\n\n
<\/p>\n\n\n\nNPCI Rules and Compliance Context<\/h2>\n\n\n\n
<\/p>\n\n\n\nWhere BeFiSc Fits<\/h2>\n\n\n\n