What is Penny Drop Bank Account Verification?
How the penny-drop method confirms an account number, IFSC and the real account-holder name before you send money — and how to call it from an API.
If you send payouts, refunds, salaries or loan disbursals, the single most expensive mistake is money landing in the wrong account. Penny-drop verification exists to stop exactly that: before you transfer the real amount, you confirm the account is valid and read back the name actually registered on it.
How does penny drop work?
A penny-drop verification makes a tiny real-time credit attempt to the target account (historically a single paisa, hence the name). The bank's response reveals whether the account number and IFSC are valid and returns the registered account-holder name — all without the account holder doing anything.
- You send an account number and IFSC (optionally a name to match).
- The API attempts a real-time credit and reads the bank's response.
- You get back the registered account-holder name and a validity status.
- You compare that name to the one you expect before paying out.
Penny drop vs. penny-less verification
Penny-less (or "pennyless") verification confirms account validity and holder name without moving any money, using a bank network lookup instead of a credit attempt. Penny-drop uses an actual micro-credit. Both return the holder name; penny-less is often faster and avoids a real transaction, while penny-drop is the traditional, widely-supported method. BILAPI offers both.
Calling the penny-drop API
POST https://api.bilapi.com/v1/bank-verification-penny-drop
X-Bilapi-Api-Key: <your_api_key>
Content-Type: application/json
{
"account_number": "1234567890",
"ifsc": "HDFC0001234",
"name": "Rahul Sharma"
}{
"status_code": 200,
"success": true,
"data": {
"account_holder_name": "RAHUL SHARMA",
"name_match": true,
"account_status": "VALID"
}
}When should you use it?
- Before the first payout to any new beneficiary (vendors, sellers, employees).
- During customer onboarding when you collect bank details for refunds or disbursals.
- Before loan disbursal, to confirm funds reach the borrower's own account.
- For claim settlements and marketplace seller payouts.
Best practices
- Always compare the returned name to your expected name before paying.
- Verify once at onboarding and store the result, rather than on every payout.
- Treat a name mismatch as a hold-and-review signal, not an outright block.