In brief: a bank account verification API confirms an account exists and returns the account holder’s name, so you can check it belongs to your customer before money moves.
On this page
What is a Bank Account Verification API?
A Bank Account Verification API confirms that a bank account number and IFSC combination corresponds to a real, active account, and returns the name registered against it.
Two methods
Penny drop verification transfers a nominal amount — often one rupee — into the account and reads back the beneficiary name returned by the banking system. It is definitive, because a successful credit proves the account can receive money, but it costs a transaction and takes a few seconds.
Penny-less verification queries account validity without moving money, typically through banking network APIs. It is faster and cheaper, and coverage varies by bank. Many businesses use penny-less as the default and fall back to penny drop where coverage is incomplete or the payout value justifies certainty. Both are available through the Veriqos Technologies bank account verification API.
Why the name match matters more than the account check
Confirming an account exists is rarely the point. The valuable output is the registered holder’s name, which lets a business check that the account belongs to the person or entity it believes it is paying. Mismatches here are a common fraud signal — and equally a common source of false rejections, because bank records hold names in inconsistent formats.
Where it is used
Before any payout: lending disbursals, insurance claim settlements, gig worker and driver payments, refunds, vendor payments and marketplace seller settlements. Also in onboarding, as one of several independent checks establishing that a customer is real.
A note on sequencing
Account verification is often run late in an onboarding flow, immediately before disbursal. Running it earlier, in parallel with identity checks rather than after them, is one of the simpler ways to reduce total onboarding time.
Related terms: Penny Drop Verification · Penny-less Verification · IFSC Code · Name Match
Designing around a bank account verification API
The technical call is the easy part; the decisions around it matter more. Decide when in your flow to ask for bank details, usually only once you actually need to pay or collect money. Validate the IFSC and account number format as the customer types, so the bank account verification API is only called on plausible inputs. Decide how name matches will be scored and what each band means: proceed, review or ask the customer for an account in their own name.
Choosing between methods
A bank account verification API usually offers penny drop, which sends a token credit, and penny-less, which confirms the account without moving money. Penny-less is faster and cheaper at scale; penny drop proves the account can receive a credit right now. Many teams use penny-less by default with penny drop as a fallback.
When to re-check
Re-run the bank account verification API whenever a customer changes their account, and consider a fresh check before unusually large payments. An account verified months ago may since have been closed or changed. Payment-system rules are published by the Reserve Bank of India.
