---
title: "Bank Account Verification (Pennyless) API Reference"
description: "Confirm an account number + IFSC and fetch the registered beneficiary name without transferring any money."
canonical: "https://eps.eko.in/docs/bank-account-verification-pennyless"
---


> **Canonical URL:** https://eps.eko.in/docs/bank-account-verification-pennyless
> This is a machine-readable Markdown version of the page for AI agents and LLMs. The primary (HTML) version lives at the canonical URL above.

# Bank Account Verification (Pennyless) API Reference

`POST https://staging.eko.in/ekoapi/v3/tools/kyc/bank-acc-verify-pennyless`

Confirm an account number + IFSC and fetch the registered beneficiary name without transferring any money.

Validates a bank account and returns the beneficiary name registered with the bank, without performing a ₹1 penny-drop transfer. Because no money moves, there is no stray credit to reverse if the account details turn out to be wrong. Use the penny-drop API instead when you need proof that a real credit reached the account (a UTR).

> View product & pricing details: [Bank Account Verification](https://eps.eko.in/products/bank-verification-api.md)

## Body parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| initiator_id | string | yes | Registered mobile number of the API user (see Platform Credentials). e.g. 9962981729 |
| client_ref_id | string | no | Unique reference ID per API call, generated by your system (max 20 characters). e.g. 2026010100123456789 |
| account | string | yes | Complete bank account number to be verified. e.g. 38759149196 |
| ifsc | string | yes | IFSC code of the bank account to be verified (11-character alphanumeric). e.g. SBIN0007515 |

## Headers

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| developer_key | string | yes | Static API key issued to your account after KYC. |
| secret-key | string | yes | Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))). |
| secret-key-timestamp | string | yes | Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time. |
| content-type | string | yes | application/json e.g. application/json |

## Response

⭐ marks fields highlighted as verifiable.

| Field | Type | Description |
| --- | --- | --- |
| status | number | Primary success indicator (0 = success). |
| message | string | Human-readable response / error message. |
| response_status_id | number | Granular status id; see the shared error-codes table. |
| response_type_id | number | A unique id for every possible response shape (success or error) — useful for client logic branching and analytics. |
| data | object | API-specific response payload. |
| data.verified_beneficiary_name ⭐ | string | Account holder name as registered with the bank. Use for name matching against the details you hold. |
| data.status ⭐ | string | Verification outcome for the account, e.g. success. |
| data.bank_account_no | string | Bank account number echoed back from the request. |
| data.bank_ifsc | string | IFSC code echoed back from the request. |
| data.message | string | Human-readable outcome of the verification. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "client_ref_id": "2026010100123456789",
  "account": "38759149196",
  "ifsc": "SBIN0007515"
}
```

## Example response

```json
{
  "response_status_id": 0,
  "data": {
    "bank_ifsc": "SBIN0007515",
    "bank_account_no": "38759149196",
    "verified_beneficiary_name": "Master YASHWANT  BASNETT",
    "message": "Bank account verification successful",
    "status": "success"
  },
  "response_type_id": 0,
  "status": 0
}
```