---
title: "Bank Account Verification API Reference"
description: "Verify a bank account by transferring ₹1 (penny drop) and retrieve the account holder name, account status, and branch details in real time."
canonical: "https://eps.eko.in/docs/bank-account-verification"
---


> **Canonical URL:** https://eps.eko.in/docs/bank-account-verification
> 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 API Reference

`POST https://staging.eko.in/ekoapi/v3/tools/kyc/bank-account/sync`

Verify a bank account by transferring ₹1 (penny drop) and retrieve the account holder name, account status, and branch details in real time.

**Behaviour**

- **Moves money**: Moves real money and cannot be undone. After a timeout, confirm the outcome before ever re-sending.
- **[₹3.00 + GST / verification](https://eps.eko.in/pricing?apis=bank-pennydrop#calculator)**: Charged per successful call; failed calls are free.

Performs a live penny-drop transaction of ₹1 to the specified bank account and returns the account holder name as registered with the bank, account status, bank/branch details, and the Eko transaction id (tid). Use this before payouts to prevent failures and fraud. The ₹1 is credited to the beneficiary — no refund occurs. Supports all IMPS-enabled banks in India.

> 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 (10–20 characters; 10 recommended). The SDKs generate one for every non-GET call when you don't. e.g. 2026010100123456789 |
| bank_account | string | yes | Complete bank account number to be verified. Send as a string to preserve leading zeros. e.g. 026291800001191 |
| ifsc | string | yes | IFSC code of the bank account to be verified (11-character alphanumeric). e.g. YESB0000262 |

## 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 | UI display hint only (-1/0 success, 1 failure, 2 initiated, 3 refund initiated, 4 refunded). Never branch on it — use `status` (and `tx_status` for financial APIs), or `response_type_id` where documented. |
| 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.name_at_bank ⭐ | string | Account holder name as registered with the bank. Use for name matching against provided details. |
| data.account_status ⭐ | string | Verification outcome for the account (e.g. VALID). |
| data.account_status_code ⭐ | string | Machine-readable account status code (e.g. ACCOUNT_IS_VALID). |
| data.bank_name ⭐ | string | Name of the bank associated with the account. |
| data.branch | string | Branch name associated with the IFSC code. |
| data.city | string | City where the bank branch is located. |
| data.micr | number | MICR (ECS identification) code of the branch. |
| data.reference_id | number | Unique reference id created for this verification. |
| data.tid | number | Eko transaction id for this verification. Persist it for reconciliation. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "client_ref_id": "2026010100123456789",
  "bank_account": "026291800001191",
  "ifsc": "YESB0000262"
}
```

## Example response

```json
{
  "response_status_id": 0,
  "data": {
    "reference_id": 5205950,
    "city": "MUMBAI",
    "bank_name": "YES BANK",
    "micr": 400065001,
    "account_status_code": "ACCOUNT_IS_VALID",
    "account_status": "VALID",
    "name_at_bank": "JOHN DOE",
    "branch": "SANTACRUZ, MUMBAI",
    "tid": 2887347145
  },
  "response_type_id": 0,
  "status": 0
}
```

## Error scenarios

| Status | response_type_id | Scenario |
| --- | --- | --- |
| 200 | — | Invalid IFSC code — malformed or non-existent IFSC provided |
| 200 | — | Invalid or non-existent bank account number — penny drop failed |
| 200 | — | Bank not supported — not live on IMPS (e.g. Deutsche Bank, Fincare SFB) |