Skip to content

Bank Account Verification APIs

Popular

Send a nominal credit to a bank account and read back the beneficiary name the account holder's bank returns. That tells you a payout account is live before you use it.

Overview

Penny drop verification confirms a bank account by sending a nominal credit to it over standard interbank payment rails. The account holder's bank replies with the beneficiary name recorded against the account. That evidence comes from the bank, not from the form a customer filled in. Businesses that disburse loans, settle claims, pay sellers or onboard vendors run the check before any real value moves. It confirms that the account details are correct and that the account can receive money. A mistyped digit caught here costs a form field, while the same digit caught at payout costs a reversal and a customer who was promised money. With an API, the check runs inside the onboarding or payout workflow you already have. You compare the returned name against the name you hold, using your own match and review rules.

Coverage
Indian bank accounts reachable over standard interbank payment rails. Scope depends on the selected service contract.
Input
Bank account number and IFSC code
Output
Beneficiary name returned by the account holder's bank, with account and transfer status. Available fields vary by data source and account record.
Typical users
Lenders, insurers, payment service providers, marketplaces, fleet operators, and gig platforms
Coverage note
A nominal credit goes into the account. The account holder may see a small credit in their statement.

The overview and the sections after the reference are the FinSour API catalog’s own record for this service, rendered unaltered.

Endpoint URL and method

POSThttps://gateway.staging.finsour.io/v1/banking/bank-account-penny-drop

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Authentication

Scheme API key travels in the X-Api-Key header

Send your API key in this header on every call, from your own server: a key sent from a browser is refused. A key starting fs_test_ calls the sandbox and one starting fs_live_ calls production, at the same address. Create keys in the FinSour console.

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Request parameters

Content type application/json

Headers

NameTypeRequiredDescriptionConstraints
Idempotency-KeystringRequiredA key you generate for each attempt. Sending the same key again returns the first answer instead of running the check twice; the same key with a different body is refused.8 to 255 characters. Matches ^[A-Za-z0-9._:-]+$

Body

NameTypeRequiredDescriptionConstraints
inputobjectRequiredThe details to check.—
input.accountNumberstringRequired—Matches ^[0-9]{9,18}$
input.ifscstringRequired—Matches ^[A-Z]{4}0[A-Z0-9]{6}$. Exactly 11 characters
optionsobjectOptionalSettings for this call.—
options.referencestringOptionalYour own reference for this call. It comes back unchanged as meta.reference.1 to 128 characters
options.consentobjectOptionalThe person's consent to this check.—
options.consent.obtainedbooleanRequiredSend true once the person has agreed to the check.Always true
options.consent.atstring (date-time)RequiredWhen the person gave consent.—
options.consent.purposestringRequiredWhat the check is for, for example kyc.1 to 64 characters

Request samples

cURL

curl -X POST https://gateway.staging.finsour.io/v1/banking/bank-account-penny-drop \
  -H "X-Api-Key: $FINSOUR_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
  "input": {
    "accountNumber": "<accountNumber>",
    "ifsc": "<ifsc>"
  }
}'

Node.js

const response = await fetch("https://gateway.staging.finsour.io/v1/banking/bank-account-penny-drop", {
  method: "POST",
  headers: {
    "X-Api-Key": process.env.FINSOUR_API_KEY,
    "Idempotency-Key": crypto.randomUUID(),
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "input": {
      "accountNumber": "<accountNumber>",
      "ifsc": "<ifsc>"
    }
  }),
});

console.log(response.status, await response.json());

Python

import os
import uuid

import requests

response = requests.post(
    "https://gateway.staging.finsour.io/v1/banking/bank-account-penny-drop",
    headers={
        "X-Api-Key": os.environ["FINSOUR_API_KEY"],
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "input": {
            "accountNumber": "<accountNumber>",
            "ifsc": "<ifsc>",
        },
    },
    timeout=30,
)

print(response.status_code, response.json())

Generated from the fields above. Replace each value in angle brackets with your own; the key is read from FINSOUR_API_KEY.

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Response schema

Status 200 · content type application/json

NameTypePresentDescriptionConstraints
dataobjectAlwaysThe result of the check.—
data.foundbooleanAlways——
data.maskedAccountNumberstringAlwaysThe account number sent, as its display form — never the full number.Matches ^X{5,14}[0-9]{4}$
data.ifscstringAlways—Matches ^[A-Z]{4}0[A-Z0-9]{6}$. Exactly 11 characters
data.nameAtBankstring or nullAlwaysThe account holder's name as the bank holds it.—
data.statusstring or any or nullAlways——
data.bankResponsestring or any or nullAlwaysWhat the bank said about the check (Release 1.1): it answered in full, or it confirmed the account without a name.—
data.bankReferencestring or nullAlwaysThe bank's reference for the ₹1 credit, as given — what the account holder's statement shows (Release 1.1).—
data.sourceobjectAlways——
data.source.fetchedAtstringAlwaysWhen the answer was fetched: RFC 3339 UTC with a Z, never an epoch or an IST offset.Matches ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d{1,9})?Z$

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Error codes

CodeStatusMeaningRetrying
API_VERSION_UNSUPPORTED400That API version is no longer supported.Do not retry automatically
IDEMPOTENCY_KEY_INVALID400That Idempotency-Key does not meet the required format.Do not retry automatically
IDEMPOTENCY_KEY_REQUIRED400An Idempotency-Key header is required for this request.Do not retry automatically
REQUEST_MALFORMED400The request could not be parsed.Do not retry automatically
AUTH_KEY_EXPIRED401The API key is not valid.Do not retry automatically
AUTH_KEY_INVALID401The API key is not valid.Do not retry automatically
AUTH_KEY_MISSING401No API key was presented.Do not retry automatically
AUTH_KEY_REVOKED401The API key is not valid.Do not retry automatically
INSUFFICIENT_BALANCE402The available balance is not enough for this request.Do not retry automatically
AUTH_IP_NOT_ALLOWED403This API key may not be used from this address.Do not retry automatically
ENTITLEMENT_MISSING403This organization is not entitled to that product in this environment.Do not retry automatically
ORGANIZATION_SUSPENDED403This organization is not active.Do not retry automatically
PRODUCT_NOT_AVAILABLE403That product is not available.Do not retry automatically
PRODUCT_RETIRED403That product has been withdrawn.Do not retry automatically
SCOPE_INSUFFICIENT403This API key does not carry the scope this product requires.Do not retry automatically
PRODUCT_NOT_FOUND404No such product.Do not retry automatically
IDEMPOTENCY_KEY_REUSED409That idempotency key was already used for a different request.Do not retry automatically
PRICE_UNAVAILABLE409No active price covers this product right now.Safe to retry
REQUEST_IN_PROGRESS409An earlier attempt with this key is still running.Safe to retry
SETTLEMENT_PENDING409This request is awaiting reconciliation by an operator.Do not retry automatically
API_VERSION_SUNSET410That API version passed its announced sunset date.Do not retry automatically
REQUEST_TOO_LARGE413The request body is too large.Do not retry automatically
UNSUPPORTED_MEDIA_TYPE415That content type is not accepted on this route.Do not retry automatically
SANDBOX_FIXTURE_MISSING422No sandbox fixture exists for this input. Use a different test value.Do not retry automatically
UPSTREAM_REJECTED422The upstream source rejected the input.Do not retry automatically
VALIDATION_FAILED422The request payload is invalid.Do not retry automatically
CONCURRENCY_LIMIT429Too many simultaneous requests.Safe to retry
QUOTA_EXCEEDED429The allowance for this window is spent.Do not retry automatically
RATE_LIMITED429Too many requests.Safe to retry
INTERNAL_ERROR500An unexpected error occurred.Safe to retry
OUTCOME_UNCERTAIN502The outcome of this request is not yet known. Retry with the same Idempotency-Key.Do not retry automatically
UPSTREAM_UNAVAILABLE502The upstream source is unavailable. Retry shortly.Safe to retry
MAINTENANCE_MODE503The service is in a maintenance window.Safe to retry
NO_PROVIDER_AVAILABLE503No provider can serve this product right now.Safe to retry
SERVICE_OVERLOADED503The service is shedding load. Retry shortly.Safe to retry
UPSTREAM_TIMEOUT504The upstream source did not respond in time.Safe to retry

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Rate limits

ScopeLimitWindowAt the limit
Your API key, within your organisation's limitThe figure in X-RateLimit-LimitPer minute429 RATE_LIMITED, with Retry-After in seconds. Every answer past authentication carries X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset.

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Use cases

  • Lending and NBFCs: confirm a borrower's payout account before disbursal
  • Insurance: verify the payee account before a claim settlement or refund
  • Fintech and PSPs: verify a merchant's settlement account at onboarding
  • Marketplaces: check seller payout accounts, and re-check when they change
  • Logistics and fleet: verify transporter accounts onboarded in the field
  • Staffing and gig platforms: validate worker accounts before payout runs

What this service does

  • The name comes from the bank

    The beneficiary name comes back from the bank that holds the account. You can compare it against the name you already hold. Which fields come back varies with the data source and the account record.

  • Proof the account can take a credit

    A nominal amount actually settles. A successful check indicates the account is live and reachable. A cancelled cheque or a statement page cannot show that.

  • Checks inside your onboarding screen

    Connect the check to an onboarding screen, payout console, vendor master or internal dashboard. Your workflow then validates account details before it saves the record.

  • A path for closed, dormant and frozen accounts

    Accounts can be closed, dormant or frozen, and a returned name can be close without matching. Structured status information lets you route each case to auto-approval, manual review, or a request for corrected details.

How a check runs

  1. Ask for the account number and IFSC

    Capture the account number and IFSC code from the customer or vendor. Tell them a nominal credit is part of verifying the account, and get the consent your own obligations require.

  2. Send the details to the API

    Your application sends the captured account details through the API as part of onboarding, vendor creation or payout setup.

  3. The credit lands and the bank replies

    A token amount is credited to the account over standard interbank payment rails, and the account holder's bank responds with the name recorded against it.

  4. Score the returned name

    Match the returned beneficiary name against the name you already hold, using your own scoring and review thresholds, allowing for initials, expanded names and transliteration differences.

  5. Save the result, then pay or pause

    Keep the returned name, the match result and the timestamp against the account record. Then release the payout, queue a review, or ask for corrected details.

Questions

What is penny drop verification?
A check that confirms a bank account by sending a nominal credit to it and reading back the beneficiary name the receiving bank holds against that account. Because a small amount actually settles, the result can also indicate whether the account is live and able to receive money.
How is penny drop different from collecting a cancelled cheque?
A cancelled cheque or a bank statement shows what the customer submitted. A penny drop response comes from the bank that holds the account. It reflects the account's current state.
Will the customer see the penny drop credit in their statement?
The account holder may see a small credit, since a nominal amount is actually transferred. Most teams say on screen that a token credit is part of the verification, which avoids support queries about an unexplained entry.
What if the returned name does not match my records?
Partial matches are normal. Initials, expanded middle names, honorifics and different transliterations of the same name all produce differences. Teams generally compare the two names with a match score, then decide in advance which scores auto-approve, which go to a human reviewer, and which are rejected.
What does a penny drop response contain?
Depending on the available information, the response may include the beneficiary name held by the account holder's bank, along with status information about the account and the transfer. The exact fields vary with the underlying data source and the account record, and depend on the selected service contract.
Do I need consent to run a penny drop check?
Yes. Account details and the name attached to them are personal financial data. Collect them for a stated purpose, tell the person what the verification is for, and get the consent your regulatory and privacy obligations require before submitting a request.

Catalog entry last updated .