Bank Verification Penny Drop
Confirm a bank account is valid and fetch the real account-holder name before you send money.
What is the Bank Verification Penny Drop?
The BILAPI Bank Account Verification API uses a real-time penny-drop to confirm that an account number and IFSC are valid and to return the actual name registered on the account — so you never send a payout, refund or salary to the wrong account.
It is essential for payroll and vendor-payout platforms, lenders disbursing loans, insurers paying claims and marketplaces settling to sellers. Verifying the account holder name up front eliminates failed transfers and reduces fraud and reconciliation overhead.
Pass an account number and IFSC and receive a verified holder name and status as JSON. Billed only on a successful verification.
What the Bank Verification Penny Drop returns
Every successful call returns a clean, predictable JSON envelope. The data object includes the fields below (exact fields vary by record availability).
| Field | Description |
|---|---|
account_number | The bank account number that was verified. |
ifsc | The IFSC used for the verification. |
account_holder_name | The name registered on the bank account (as returned by the bank). |
name_match | Match flag/score when you pass an expected name to compare. |
account_status | Whether the account is valid and able to receive credit. |
bank_name | Name of the bank/branch resolved from the IFSC. |
Sample request & response
Call the endpoint with your API key in the X-Bilapi-Api-Key header. The same request shape works in the free sandbox and in production.
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,
"message": "Account verified",
"data": {
"account_number": "1234567890",
"ifsc": "HDFC0001234",
"account_holder_name": "RAHUL SHARMA",
"name_match": true,
"account_status": "VALID"
}
}Key features
Real-time results
Sub-300ms median response so bank account checks never slow your onboarding funnel.
Predictable JSON
The same clean response envelope as every BILAPI endpoint — parse once, reuse everywhere.
Only pay for hits
Invalid inputs and failed lookups are never charged to your wallet.
Secure by design
TLS 1.3 in transit, PII tokenisation at rest and a full audit log on every request.
One key, every API
Sandbox to production on a single key — no per-vendor contracts or integrations.
Built to scale
99.9% uptime target with bulk and webhook-friendly workflows for high volume.
Where it's used
Customer onboarding
Auto-fill and validate identity during signup to cut drop-off and manual review.
Lending & underwriting
Add a verified data point to credit decisions and reduce first-party fraud.
Fraud & risk
Flag mismatches and synthetic identities before they enter your system.
Compliance & audit
Keep a tamper-evident trail of every verification for KYC/AML reviews.
How it works
Create a free account
Sign up on the BILAPI console and get a live API key instantly.
Send a request
POST the required bank account fields to the endpoint with your API key in the header.
Get structured JSON
Receive a clean, predictable JSON response in milliseconds.
Plug into your flow
Drop the result straight into onboarding, underwriting or risk decisioning.
Frequently asked questions
How does penny-drop bank verification work?
The API makes a real-time credit attempt to the account and reads back the registered account-holder name, confirming the account number and IFSC are valid before you make an actual payout.
Does it return the account holder name?
Yes — it returns the name registered on the account, and an optional match flag when you pass the name you expect.
Why verify accounts before payouts?
It prevents money going to wrong or closed accounts, cuts failed transfers and reconciliation work, and reduces payout fraud for payroll, lending, claims and marketplace settlements.
What inputs are required?
The account number and the IFSC. Optionally a name to match against the registered holder name.
Do I pay for an invalid account?
You are billed per successful verification from your wallet; failed lookups are not charged.
Related Bank Verification APIs
Start verifying with BILAPI
One key, a free sandbox and a predictable JSON envelope across every endpoint.