Penny Less Bank Account Verification API
New
Check bank account details and get the name held against the account without moving money. Nothing shows up in a customer's statement and nothing needs reversing.
Overview
Penny less verification checks bank account details without transferring a verification amount. The request looks the account up against available information and returns the name recorded against it. There is no token credit and no wait for the receiving bank to answer. Nothing needs explaining or reconciling, because nothing moves. There is no small credit in a customer's statement, no float to fund and no reversal to chase. That makes the check a practical fit for high-volume onboarding and for re-checking accounts you have already verified once. The trade-off is worth stating plainly. Because no money is placed, the answer describes the account as available information records it, without showing that a credit will land today. Many teams run a penny less check first and keep a penny drop check for exceptions and high-value transfers.
- Category
- Banking Services
- Coverage
- Indian bank accounts held in available information. Reach and fields depend on the selected service contract.
- Input
- Bank account number and IFSC code
- Output
- Name held against the account and a validation status. The fields available vary with the data source and the account record.
- Typical users
- Payment service providers, lenders, insurers, marketplaces, staffing and gig platforms
- Coverage note
- No money is transferred. The result reflects available information, not a settled credit into the account.
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
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
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
Headers
| Name | Type | Required | Description | Constraints |
|---|---|---|---|---|
Idempotency-Key | string | Required | A 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
| Name | Type | Required | Description | Constraints |
|---|---|---|---|---|
input | object | Required | The details to check. | — |
input. | string | Required | — | Matches ^[0-9]{9,18}$ |
input. | string | Required | — | Matches ^[A-Z]{4}0[A-Z0-9]{6}$. Exactly 11 characters |
input. | string | Optional | OPTIONAL (Release 1.1): a name to compare with the name at the bank; the answer's nameMatchScore is the comparison. | Matches ^(?=.*[A-Za-z])[A-Za-z .'-]+$. 1 to 120 characters |
options | object | Optional | Settings for this call. | — |
options. | string | Optional | Your own reference for this call. It comes back unchanged as meta.reference. | 1 to 128 characters |
options. | object | Optional | The person's consent to this check. | — |
options. | boolean | Required | Send true once the person has agreed to the check. | Always true |
options. | string (date-time) | Required | When the person gave consent. | — |
options. | string | Required | What 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 \
-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", {
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",
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
| Name | Type | Present | Description | Constraints |
|---|---|---|---|---|
data | object | Always | The result of the check. | — |
data. | boolean | Always | — | — |
data. | string | Always | The account number sent, as its display form — never the full number. | Matches ^X{5,14}[0-9]{4}$ |
data. | string | Always | — | Matches ^[A-Z]{4}0[A-Z0-9]{6}$. Exactly 11 characters |
data. | string or null | Always | The account holder's name as the bank holds it. | — |
data. | string or any or null | Always | — | — |
data. | string or any or null | Always | What the bank said about the check (Release 1.1): it answered in full, or it confirmed the account without a name. | — |
data. | number or null | Always | How closely nameToMatch matches the name at the bank, 0 to 100, to two decimals; null when no name was sent. | Minimum 0. Maximum 100 |
data. | boolean or null | Always | Whether the check credited the account (false for this API's penny-less check, as the source states it). | — |
data. | object or any or null | Always | The branch the IFSC names and the payment rails it accepts (Release 1.1). | — |
data. | object | Always | — | — |
data. | string | Always | When 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
| Code | Status | Meaning | Retrying |
|---|---|---|---|
API_VERSION_UNSUPPORTED | 400 | That API version is no longer supported. | Do not retry automatically |
IDEMPOTENCY_KEY_INVALID | 400 | That Idempotency-Key does not meet the required format. | Do not retry automatically |
IDEMPOTENCY_KEY_REQUIRED | 400 | An Idempotency-Key header is required for this request. | Do not retry automatically |
REQUEST_MALFORMED | 400 | The request could not be parsed. | Do not retry automatically |
AUTH_KEY_EXPIRED | 401 | The API key is not valid. | Do not retry automatically |
AUTH_KEY_INVALID | 401 | The API key is not valid. | Do not retry automatically |
AUTH_KEY_MISSING | 401 | No API key was presented. | Do not retry automatically |
AUTH_KEY_REVOKED | 401 | The API key is not valid. | Do not retry automatically |
INSUFFICIENT_BALANCE | 402 | The available balance is not enough for this request. | Do not retry automatically |
AUTH_IP_NOT_ALLOWED | 403 | This API key may not be used from this address. | Do not retry automatically |
ENTITLEMENT_MISSING | 403 | This organization is not entitled to that product in this environment. | Do not retry automatically |
ORGANIZATION_SUSPENDED | 403 | This organization is not active. | Do not retry automatically |
PRODUCT_NOT_AVAILABLE | 403 | That product is not available. | Do not retry automatically |
PRODUCT_RETIRED | 403 | That product has been withdrawn. | Do not retry automatically |
SCOPE_INSUFFICIENT | 403 | This API key does not carry the scope this product requires. | Do not retry automatically |
PRODUCT_NOT_FOUND | 404 | No such product. | Do not retry automatically |
IDEMPOTENCY_KEY_REUSED | 409 | That idempotency key was already used for a different request. | Do not retry automatically |
PRICE_UNAVAILABLE | 409 | No active price covers this product right now. | Safe to retry |
REQUEST_IN_PROGRESS | 409 | An earlier attempt with this key is still running. | Safe to retry |
SETTLEMENT_PENDING | 409 | This request is awaiting reconciliation by an operator. | Do not retry automatically |
API_VERSION_SUNSET | 410 | That API version passed its announced sunset date. | Do not retry automatically |
REQUEST_TOO_LARGE | 413 | The request body is too large. | Do not retry automatically |
UNSUPPORTED_MEDIA_TYPE | 415 | That content type is not accepted on this route. | Do not retry automatically |
SANDBOX_FIXTURE_MISSING | 422 | No sandbox fixture exists for this input. Use a different test value. | Do not retry automatically |
UPSTREAM_REJECTED | 422 | The upstream source rejected the input. | Do not retry automatically |
VALIDATION_FAILED | 422 | The request payload is invalid. | Do not retry automatically |
CONCURRENCY_LIMIT | 429 | Too many simultaneous requests. | Safe to retry |
QUOTA_EXCEEDED | 429 | The allowance for this window is spent. | Do not retry automatically |
RATE_LIMITED | 429 | Too many requests. | Safe to retry |
INTERNAL_ERROR | 500 | An unexpected error occurred. | Safe to retry |
OUTCOME_UNCERTAIN | 502 | The outcome of this request is not yet known. Retry with the same Idempotency-Key. | Do not retry automatically |
UPSTREAM_UNAVAILABLE | 502 | The upstream source is unavailable. Retry shortly. | Safe to retry |
MAINTENANCE_MODE | 503 | The service is in a maintenance window. | Safe to retry |
NO_PROVIDER_AVAILABLE | 503 | No provider can serve this product right now. | Safe to retry |
SERVICE_OVERLOADED | 503 | The service is shedding load. Retry shortly. | Safe to retry |
UPSTREAM_TIMEOUT | 504 | The 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
| Scope | Limit | Window | At the limit |
|---|---|---|---|
| Your API key, within your organisation's limit | The figure in X-RateLimit-Limit | Per minute | 429 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
- Fintech and PSPs: validate merchant settlement accounts at sign-up
- Lending and NBFCs: check borrower account details early in an application
- Marketplaces: re-check stored seller payout accounts in bulk
- Staffing and gig platforms: validate worker accounts at onboarding volumes
- Insurance: confirm payee account details while a claim is assessed
- Logistics and fleet: verify transporter accounts without an unexplained credit
What this service does
No verification amount leaves your account
The check runs without a transfer. There is no token credit to fund, no unexplained entry in the customer's statement, and no reversal or reconciliation to handle afterward.
Suits bulk cleanups and re-checks
Because nothing settles, you can validate the same account as often as your risk policy requires. That suits vendor-list cleanups, payout-file screening and periodic re-checks of stored accounts.
A name you can match against your file
The response can carry the name held against the account. You can match it to the name you already hold using your own scoring and review thresholds. The fields available depend on the data source and the account record.
What a penny less check cannot show
Without a settled credit, the result describes the account as available information records it. It does not show that a payout will land. Teams that need that stronger evidence keep a penny drop check for exceptions and high-value transfers.
How a check runs
Capture the details for a stated purpose
Take the account number and IFSC code for a stated purpose, and get the consent your own regulatory and privacy obligations require before running the check.
Send the account number and IFSC
Your onboarding form, vendor master or payout console sends the account details through the API, with no verification amount involved.
Read the name and validation status
The response can carry the name held against the account and a validation status, subject to what the underlying data source holds for that record.
Match the name against your record
Score the returned name against your existing record and apply your review thresholds, allowing for initials, expanded names and transliteration differences.
Send exceptions to a stronger check
Route mismatches, unresolved accounts, and first or high-value payouts to a stronger check or a manual review, following the rule your risk team has written down.
Questions
- What is penny less verification?
- A bank account check that transfers no verification amount. The request looks the account up against available information, and can return the name held against it along with a validation status, without any money moving.
- When should I choose penny less instead of penny drop?
- When the cost of a wrong account is a corrected form field rather than a failed payout. Typical cases are validating details early in an application, cleaning or re-checking a vendor or seller list in bulk, and screening a payout file. It also suits any journey where an unexplained credit in the customer's account would cause confusion or support queries.
- What is the trade-off of a penny less check?
- A penny drop result shows that a credit actually reached the account. A penny less result describes the account as available information records it, which is a weaker claim. An account can be recorded correctly and still be dormant, frozen or closed, and reach may also be narrower, particularly across smaller cooperative and regional banks.
- Can I run penny less and penny drop together?
- Yes, and many teams do. A common pattern is to run the penny less check routinely, for storage and low-value payouts. Teams then require a penny drop check before a first disbursal or a high-value transfer, and after a customer changes their settlement account.
- What does a penny less response contain?
- Depending on the available information, the response may include the name held against the account and a validation status. Which fields you get depends on the underlying data source, on the account record, and on the selected service contract.
- Do I need consent when no money moves?
- Yes. An account number, an IFSC code and the name held against them are personal financial data whether or not a credit accompanies the check. Collect them for a stated purpose, get the consent your obligations require, and use the result only for that purpose.
Catalog entry last updated .