Bank Account Verification API
Confirm a bank account is valid via penny drop and optionally match the account-holder name.
What it verifies
Confirms that a bank account exists and can receive a payment, using a penny-drop check. Optionally compares a name you send with the name held at the bank. Leading zeros on the account number are kept exactly as sent.
Who uses it
- Lenders and NBFCs verifying disbursement accounts
- Payroll and payout platforms validating beneficiary accounts
- Marketplaces confirming seller settlement accounts
Request and response
https://verification.techinnoverz.com/api/v1/banking-finance/bank-accountVerify a bank account by IFSC and account number, and optionally match a name. This call is billed when it returns a successful result.
Request body
accountNumberstringrequiredBank account number, 6 to 18 digits. Keep any leading zeros exactly as on the passbook.
ifscstringrequired11-character IFSC of the account.
namestringoptionalOptional. Account-holder name to compare with the name at the bank. Letters, digits, spaces and & . , ' ( ) / - only, 2 to 100 characters. When you send it, the response includes nameMatch and nameMatchScore.
consentstringrequiredMust be "Y". Records that the end customer consented to this check; logged against the transaction.
referenceIdstringoptionalYour own id, echoed back in the response for reconciliation.
Example requests
curl -X POST "https://verification.techinnoverz.com/api/v1/banking-finance/bank-account" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"accountNumber": "36666661234",
"ifsc": "SBIN0003375",
"name": "Asha Sample",
"consent": "Y",
"referenceId": "app_20915"
}'const res = await fetch("https://verification.techinnoverz.com/api/v1/banking-finance/bank-account", {
method: "POST",
headers: {
"x-api-key": "YOUR_API_KEY",
"Content-Type": "application/json",
},
body: JSON.stringify({
"accountNumber": "36666661234",
"ifsc": "SBIN0003375",
"name": "Asha Sample",
"consent": "Y",
"referenceId": "app_20915"
}),
});
const result = await res.json();import requests
res = requests.post(
"https://verification.techinnoverz.com/api/v1/banking-finance/bank-account",
headers={"x-api-key": "YOUR_API_KEY"},
json={
"accountNumber": "36666661234",
"ifsc": "SBIN0003375",
"name": "Asha Sample",
"consent": "Y",
"referenceId": "app_20915",
},
timeout=15,
)
result = res.json()200 response — status "found"
{
"status": "found",
"data": {
"accountNumber": "36666661234",
"ifsc": "SBIN0003375",
"nameAtBank": "Asha Sample",
"nameMatch": true,
"nameMatchScore": 90,
"rrn": "414515746177",
"paymentMode": "STANDARD",
"transactionId": "ca3059a5f8374ce5bc77c91ceb626489",
"bank": {
"bankName": "STATE BANK OF INDIA",
"bankBranch": "CHURCH ROAD",
"bankAddress": "ST PAUL'S COLLEGE, CHURCH ROAD, MUMBAI, MAHARASHTRA"
}
},
"source": "provider",
"dataAsOf": "2026-11-03T09:30:00.000Z",
"referenceId": "app_20915",
"billing": {
"charged": true,
"walletBalance": "12450.00"
},
"txnId": "txn_8c31ba90",
"livemode": true
}Fields returned in data
accountNumberstringoptionalThe account number that was verified.
ifscstringoptionalThe IFSC that was verified.
nameAtBankstringoptionalAccount-holder name as returned by the bank. null when not held.
nameMatchbooleanoptionalWhether the name you sent meets the bank's matching threshold (70). null when you sent no name.
nameMatchScoreintegeroptionalHow closely the name you sent matches, from 0 to 100. null when you sent no name.
rrnstringoptionalBank retrieval reference number for the penny drop. null when not held.
paymentModestringoptionalVerification mode returned by the source. Currently STANDARD.
transactionIdstringoptionalProvider transaction id for this check.
bankobjectoptionalIFSC directory details when enabled on the Digitap account: bankName, bankBranch, bankAddress. null when not held.
Error codes
Errors return a non-200 HTTP status and the same envelope, so your retry logic and your reconciliation agree.
400 INVALID_INPUTA field is missing or malformed. The details list each problem. Not charged.
401 INVALID_KEYThe key is missing, revoked, or not a key we issued.
402 WALLET_EMPTYYour available balance is below the price of this call. Top up and retry. Not charged.
403 PRODUCTION_NOT_ENABLEDA live key was used before live access was enabled for your account. Use a test key, or ask us to enable live access.
403 TEST_NOT_ENABLEDA test key was used before test (UAT) access was enabled for your account. Ask us to enable it.
403 API_NOT_ENABLEDThis check is switched off for your account, or is not available for live use yet.
403 IP_NOT_ALLOWEDThe key is restricted to certain IP addresses and this call came from another.
403 ACCOUNT_SUSPENDEDThe account is suspended. Contact support.
404 NO_DATAA valid request, but no record was found. Not charged.
404 ROUTE_NOT_FOUNDThere is no endpoint at that path.
405 METHOD_NOT_ALLOWEDUse the method shown in the Allow header.
409 IDEMPOTENCY_IN_PROGRESSA call with the same Idempotency-Key is still being processed. Retry after the delay in Retry-After.
413 PAYLOAD_TOO_LARGEThe request body is too large. Not charged.
415 UNSUPPORTED_MEDIA_TYPESend the request with Content-Type: application/json.
422 IDEMPOTENCY_KEY_REUSEDThis Idempotency-Key was already used with a different request body. Use a new key for a new request.
429 RATE_LIMITEDToo many requests or too many at once. Wait for the Retry-After delay.
500 INTERNAL_ERRORSomething went wrong on our side. Not charged. Quote the txnId if you contact support.
502 SOURCE_ERRORThe data source returned an error. Not charged.
503 SOURCE_DOWNThe data source is unavailable right now. Not charged. Retry after the delay in Retry-After.
504 SOURCE_TIMEOUTThe data source did not answer in time. Not charged.
{
"status": "error",
"error": {
"code": "NO_DATA",
"message": "No record found for the given input. Not charged."
},
"billing": {
"charged": false
},
"txnId": "txn_8c31ba91",
"livemode": true
}Billing
You are charged only on successful hits. Failed, no-data and error calls are free.
Every response carries billing.charged and your remaining billing.walletBalance. Per-hit pricing is set on your rate card; book a demo to get yours.
All API documentation · OpenAPI specification · Docs as plain text
