Bank Account & UPI ID Verification API

Bank account verification confirms that an account number and IFSC actually exist and returns the registered account holder's name, so you can check it matches the person you are about to pay. It is done through a verification API rather than by eye: the service queries the banking network and responds in seconds with whether the account is valid and whose name is on it. Businesses use it before making payouts, onboarding vendors or issuing refunds, because a wrong account number sends real money to a stranger.

Use a bank account verification API from a regulated payment provider. You send the account number and IFSC, and the service returns whether the account is valid along with the registered name, usually within a few seconds. Two methods exist: penny drop, where a token amount of ₹1 is credited to confirm the account is live and reachable, and pennyless verification, which checks against the banking network without moving money and is faster and cheaper at volume.

Penny drop verification credits a token amount — typically ₹1 — to the account being checked, and reads back the account holder's name from the transaction response. Because money actually moves, it proves the account is live and can receive credit, not merely that the number is well-formed. It is the more conclusive of the two methods, and correspondingly slower and costlier than a pennyless lookup, so businesses often use pennyless first and penny drop only where the payout is large.

Penny drop moves a small real amount into the account and confirms it is live and receivable, which is conclusive but slower and costs more per check. Pennyless verification queries the banking network for validity and the registered name without transferring anything, returning a result faster and cheaper. For high-volume onboarding, pennyless is the sensible default; for a large one-off payout, the extra certainty of a penny drop is usually worth its cost.

A UPI ID verification API checks whether a VPA — the name@bank handle — is valid and active, and returns the registered name behind it. You send the UPI ID and receive back validity and the account holder's name in a couple of seconds. It is the standard check before sending a UPI payout, and it also catches the common case where a customer supplies a UPI ID that was deactivated after they changed banks.

Because a wrong account number sends real money to a real stranger, and recovering it depends entirely on their goodwill. Verification catches typos, stale details and outright fraud before the transfer, not after. It also prevents the quieter cost: failed payouts that bounce back days later, by which time a vendor is unpaid, a refund is unresolved, and someone has spent an afternoon on it.

Name matching compares the account holder's registered name against the name you hold, and returns a similarity result rather than a simple yes or no — because banks store names inconsistently. Initials, an expanded middle name, a married surname or a trading name instead of a legal entity name all produce a genuine mismatch on a perfectly valid account. Good practice is to treat a near match as needing human review rather than auto-rejecting it.

Yes. Verification suites from Indian payment providers typically cover bank account, UPI ID, PAN and GSTIN checks through the same account and the same credentials. Businesses onboarding vendors or merchants usually need several of these together — a PAN check to confirm identity, a GSTIN check for tax compliance, and a bank check before the first payout.

Verification is charged per successful check, and rates depend on the method and your volume — pennyless lookups cost less than penny drops because no money moves. Providers publish rate cards and negotiate at volume, so confirm current pricing on the provider's own page. Weighed against a single misdirected payout, or the staff time spent unwinding a failed one, the per-check cost is rarely the deciding factor.

Yes, when done through a regulated payment provider for a legitimate business purpose such as onboarding, payouts or refunds. What matters is the basis on which you hold the data: verify accounts your customers or vendors have given you for a stated purpose, tell them what you are checking, and do not retain returned names beyond what that purpose needs. Verifying accounts you have no relationship with is not a legitimate use.

A pennyless verification typically returns in a couple of seconds, which is fast enough to run inside a signup form without the user noticing. A penny drop takes longer because a real transfer has to be initiated and acknowledged. For onboarding flows, run the check while the user is still on the page — verifying afterwards means chasing people who have already left.

Yes, and it is the best moment to do it. Verifying at signup means a wrong account number is corrected by the person who typed it, while they are still on the page and still care. Verifying later means finding the error when a payout fails, contacting a customer who has moved on, and doing the whole thing again — which is why so many refund and payout problems trace back to a check that was skipped at onboarding.