API Marketplace

Solutions

Resources

Our Company

Book a Demo

← Back to Glossary

Penny Drop Verification (India)

Overview

Penny drop verification confirms Indian bank account ownership by sending a nominal credit (often ₹1) and reading back the beneficiary name from the receiving bank. The name is then matched (exact/normalized/fuzzy) to the customer’s declared name, establishing ownership and account activity without full statement access.

It’s widely used by fintechs, brokers, lenders, and payroll/remittance platforms as a quick, low-cost verification during onboarding or payouts. Compared to microdeposits, penny drop leverages local rails (IMPS/NEFT/UPI) for faster resolution; compared to IAV APIs, it requires fewer permissions but provides less data. Institutions log UTRs and responses for audit trails and re-run checks upon changes to bank details.

Stay ahead of risk with Signzy

Explore tools that help you onboard, monitor, and verify with confidence

Bank Account Verification

Instantly verify bank account details to confirm account ownership and validity for secure financial transactions.

One Touch KYC

Launch global KYC flows with built-in document OCR, liveness checks, deepfake detection, and AML, all through a single, customizable dashboard.

Database Verification

Instantly verify user information by connecting to trusted databases across jurisdictions for accurate, compliant, and faster onboarding.

Related Terms

Instant Account Verification (IAV)

Bank Account Verification

Beneficiary Name Matching

FAQ

How does it work end-to-end?

Push ₹1 → receive bank returns beneficiary name → system compares against customer name with normalization rules → decision + audit log.

How accurate is name matching?

High with good normalization (case, initials, order). Handle joint accounts, maiden names, and transliteration edge cases.

When should I prefer penny drop vs IAV?

Use penny drop for light-touch ownership checks; IAV for richer data/affordability analytics.

Any compliance considerations?

Store consent, mask sensitive data, log UTRs, and define retry/exception flows for failures.