Bank Account
Verification API

Building it? Read the developer integration guide for bank account verification APIs.

A complete guide to the bank account verification API

A bank account verification API confirms that a bank account exists and tells you whose name it is in, before you send money to it or take money from it. It is one of the most widely used checks in Indian fintech, because almost every payout, refund, loan disbursal or salary payment depends on getting the account right. This guide explains how a bank account verification API works, the two main methods it uses, and how to design a flow around the result.

Why bank account checks matter

A payment to the wrong account is hard to reverse. It can come from a simple typo in an account number, a customer entering someone else's account, or a deliberate attempt to redirect funds. A bank account verification API catches these before the money moves, which is far cheaper than recovering a failed or misdirected payment afterwards.

The inputs: account number and IFSC

Every check starts with two values: the account number and the IFSC. The IFSC is an 11-character code: the first four letters identify the bank, the fifth character is zero, and the last six identify the branch. Validate the IFSC format in your form as the customer types, and consider an IFSC lookup so customers can pick their branch instead of typing the code. Clean inputs mean fewer failed calls to the bank account verification API.

Method one: penny drop

A penny drop check sends a very small credit, typically one rupee, to the account and reads the beneficiary name that comes back with the transfer. Because a real transfer happens, it confirms that the account can receive money today. The trade-offs are cost and a small credit showing up in the customer's account, which some customers notice and ask about.

Method two: penny-less

A penny-less check confirms the account and returns the account holder's name without moving any money. It is faster and cheaper to run at scale and leaves nothing in the customer's account. Coverage depends on what each bank makes available, so many teams use penny-less as the default and fall back to penny drop for accounts it cannot cover. A good bank account verification API lets you choose the method per check.

The name match is the real check

Confirming that an account exists is only half the job. The important question is whether it belongs to your customer. That is answered by comparing the name returned by the bank account verification API with the customer's verified name, for example the name on their PAN. Banks record names in many formats, so an exact text comparison fails far too often. Use a name-match score instead:

• Normalise both names by removing titles, punctuation and extra spaces.
• Allow for initials, reordered names and common spelling variants.
• Set bands: approve automatically on a strong match, send partial matches to review, stop on a clear mismatch.

Where the bank account verification API is used

• Lending: confirming the disbursal account belongs to the borrower before releasing funds.
• Payroll and gig platforms: checking salary or payout accounts before the first payment.
• Marketplaces: verifying seller settlement accounts.
• Insurance: confirming the account for claim payouts and refunds.
• Investments and broking: confirming the account linked to a customer's investments.

Designing the flow

Ask for bank details only when you need them, not at the very start of sign-up. Validate formats in the form, call the bank account verification API on submission, and show the customer a clear message if the account cannot be verified, asking them to re-check the details. If the name does not match, explain that the account must be in their own name rather than showing a generic error. Most failures are fixable by the customer in seconds if the message tells them what to fix.

Re-checking accounts over time

Accounts are closed and changed. For one-off payments, a check at the time of payment is enough. For ongoing relationships, such as monthly payouts or repayments, re-run the bank account verification API when a customer changes their account, and consider a fresh check before unusually large payments.

Fraud patterns to watch

Watch for the same bank account being added by several unrelated customers, accounts whose names have nothing in common with the customer, and frequent changes to payout accounts shortly before large payments. A bank account verification API gives you the data to spot these patterns; the rules that act on them are part of your own risk policy.

Record keeping

Store the account number in masked form, the IFSC, the name returned, the match result, the method used and the time of each check. That record lets you explain every payout decision and investigate any dispute quickly. Banking rules and payment-system guidance are published by the Reserve Bank of India.

Choosing a bank account verification API

When comparing options, look at which methods are supported, how name matching is handled, how failures are reported, how quickly results come back at your volumes, and how easy it is to fall back from one method to another. Run a pilot on real traffic before committing, because the mix of banks your customers use decides how any bank account verification API performs for you.

Related bank account checks

The bank account verification API is one of three ways to confirm an account on Veriqos. If you want the bank's own confirmation through a small credit, use the Penny Drop Verification API. If you want to confirm the account without moving any money, use the Penny-less Bank Account Verification API. To check that the account belongs to the same person as a PAN, add the PAN Account Linkage API.